Cribl Stream lets you use the Transport Layer Security (TLS) to secure communications in the following contexts.

Leader-Worker Node Communications ​

You can secure communication between the Leader Node, Outpost Nodes, and Worker Nodes with either one-directional, standard TLS or mutual TLS (mTLS). With standard TLS, you create a certificate on the Leader (and on Outpost Nodes) that the Worker Nodes must trust to confirm a secure connection.

Standard TLS is enabled by default on the Leader Node in Cribl.Cloud, but needs to be enabled and configured manually in on-prem deployments.

See Secure Leader-Node Communication with TLS for more information about standard TLS, and Secure Leader-Node Communication with mTLS for guidelines about mTLS (on-prem only).

Source/Destination Communications ​

You can secure communication between Worker Nodes and supported integrations via TLS or mTLS to authenticate data senders and receivers, protect data in transit, and prevent unauthorized access.

Create or import a certificate to a Worker Group and enable TLS to ensure only TLS traffic is accepted by a Cribl Source or sent by a Cribl Destination.

See Secure Sources and Destinations with TLS and mTLS for more information.

Leader API and UI Access ​

You can also secure the Leader by enabling TLS for the UI and API inbound communications.

See Configure TLS for API and UI Access for more information.