# Ensure Kafka Cluster Encryption in Transit Is Enabled

- Source: https://support.icompaas.com/support/solutions/articles/62000233561-ensure-kafka-cluster-encryption-in-transit-is-enabled
- Section: [Solutions](https://support.icompaas.com/support/solutions) › [AWS Checks New Version](https://support.icompaas.com/support/solutions/62000112673) › [AWS New Checks](https://support.icompaas.com/support/solutions/folders/62000169206)
- Last updated: 2026-05-29
- Publisher: iCompaas, Inc. (https://www.icompaas.com)

**Profile Applicability**

-   **Level 2**

#### **Description**

Encryption in transit ensures that all communication between Kafka clients, brokers, and ZooKeeper nodes is protected from interception and unauthorized access. Enabling encryption in transit helps safeguard sensitive data and meets compliance with security and privacy requirements.

#### **Rationale**

-   Enhanced Security: Prevents interception and unauthorized access to data transmitted between Kafka components.
    
-   Compliance: Meets regulatory requirements for ensuring secure data communication.
    
-   Risk Mitigation: Reduces the risk of man-in-the-middle attacks and data breaches.
    

#### **Impact**

**Pros:**

-   Secures communication between Kafka clients, brokers, and ZooKeeper.
    
-   Mitigates risks of data breaches and unauthorized access.
    
-   Aligns with security standards and compliance policies.
    

**Cons:**

-   May introduce slight latency due to encryption processing.
    
-   Requires proper configuration of TLS certificates.
    

#### **Default Value**

By default, Amazon MSK clusters support encryption in transit, but explicit configuration is required to enforce secure connections.

#### **Pre-Requisite**

IAM Permissions:

-   kafka:DescribeCluster
    
-   kafka:UpdateClusterConfiguration
    
-   AWS CLI installed and configured.
    

  

#### **Remediation**

#### **Test Plan:** 

**Using AWS Console:**

1.  Sign in to the AWS Management Console.
    
2.  Navigate to the MSK Dashboard.
    
3.  Select Clusters from the left-hand menu.
    
4.  Check the Encryption Settings for each cluster and verify that TLS encryption in transit is enabled.
    

**Using AWS CLI:**

1.  Verify Encryption in Transit Settings:  
    
    aws kafka describe-cluster --cluster-arn <cluster-arn> --query "ClusterInfo.EncryptionInfo.EncryptionInTransit"
    
2.  Ensure that ClientBroker is set to TLS or TLS\_PLAINTEXT (TLS-enabled) and InCluster is set to true.
    

#### **Implementation Steps:**

 **Using AWS Console:**

1.  Sign in to the AWS Management Console.
    
2.  Navigate to the MSK Dashboard.  
    ![](https://support.icompaas.com/assets/kb/25c29c5cf9892683.png)
    
3.  Select the Kafka cluster to update.  
    ![](https://support.icompaas.com/assets/kb/73f8a58d608b6903.png)
    
4.  Edit the cluster configuration to enable encryption in transit using TLS.
    
5.  Save the changes.
    

**Using AWS CLI:**

1.  Enable Encryption in Transit:  
    
    aws kafka update-cluster-configuration --cluster-arn <cluster-arn> --configuration-info file://config.json
    
2.  Verify the Changes:  
    
    aws kafka describe-cluster --cluster-arn <cluster-arn> --query "ClusterInfo.EncryptionInfo.EncryptionInTransit"
    

#### **Backout Plan**

#### **Using AWS Console:**

1.  #### If enabling encryption causes issues with cluster performance or connectivity, navigate to Amazon MSK in the AWS Management Console.  
    ![](https://support.icompaas.com/assets/kb/e85cfffba1bdd1ff.png)
    
2.  #### Select the Kafka cluster and disable encryption in transit by editing the cluster settings and setting TLS encryption to off.  
    ![](https://support.icompaas.com/assets/kb/baf38ec138c0fb48.png)
    
3.  #### Save the changes and verify that the cluster is no longer using encryption.
    

#### **Using AWS CLI:**

1.  #### To disable encryption in transit, run the following command:  
    
    aws kafka update-cluster-configuration --cluster-arn <CLUSTER\_ARN> --encryption-in-transit '{"enabled":false}' --region <REGION>
    
2.  #### Verify that the encryption has been disabled by describing the cluster:  
    
    aws kafka describe-cluster --cluster-arn <CLUSTER\_ARN> --region <REGION>
    

#### **References**

-   [Amazon MSK Encryption in Transit Documentation](https://docs.aws.amazon.com/msk/latest/developerguide/msk-encryption.html)
    
-   [AWS Security Best Practices for MSK](https://docs.aws.amazon.com/msk/latest/developerguide/security.html)
    
-   [Configuring MSK TLS Encryption](https://docs.aws.amazon.com/msk/latest/developerguide/msk-encryption-in-transit.html)

## Related compliance guidance

- [SOC 2 compliance: a practical implementation guide for cloud-native SaaS teams](https://support.icompaas.com/compliance/soc-2-trust-services-criteria): Configuration checks like this one are the technical half of a SOC 2 / ISO 27001 programme — the guide shows where they fit, what else an auditor expects, and how to evidence them.
- [ISO/IEC 27001:2022 compliance: a practical implementation guide](https://support.icompaas.com/compliance/iso-27001-2022): ISO 27001 Annex A.8 (technological controls) is where cloud hardening evidence lands; the guide shows how to run the ISMS around it.
