# Ensure Mutual TLS Authentication Is Enabled for Kafka Clusters

- Source: https://support.icompaas.com/support/solutions/articles/62000233562-ensure-mutual-tls-authentication-is-enabled-for-kafka-clusters
- 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** 

Mutual TLS (mTLS) authentication ensures that both the client and the server authenticate each other during communication. This provides an additional layer of security for Kafka clusters by ensuring that only trusted clients can connect to the cluster. Enabling mTLS is a critical step in securing sensitive data and preventing unauthorized access.

#### **Rationale**

-   Enhanced Security: Ensures that only trusted clients can connect to Kafka clusters.
    
-   Compliance: Meets regulatory requirements for secure communication and data protection.
    
-   Risk Mitigation: Reduces the risk of unauthorized access and man-in-the-middle attacks.
    

#### Impact

Pros:

-   Provides strong authentication for both clients and servers.
    
-   Enhances data security by encrypting communication.
    
-   Aligns with compliance and security standards.
    

**Cons:**

-   Requires additional configuration and management of certificates.
    
-   May introduce slight latency due to encryption overhead.
    

#### **Default Value**

By default, Kafka clusters do not enforce mTLS authentication. This must be explicitly configured.

#### **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 Security Settings for each cluster and verify if mTLS authentication is enabled.
    

**Using AWS CLI:**

1.  Verify mTLS Authentication Settings:  
    
    aws kafka describe-cluster --cluster-arn <cluster-arn> --query "ClusterInfo.ClientAuthentication.Tls"
    
2.  Ensure that the Tls field is set to Enabled.
    

**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/85c3786f2fe2cf41.png)
    
3.  Select the cluster to update.  
    ![](https://support.icompaas.com/assets/kb/160e1af86134ffbe.png)
    
4.  Edit the cluster configuration to enable mTLS authentication using AWS Certificate Manager (ACM).   
      
    ![](https://support.icompaas.com/assets/kb/94d80254f828b976.png)  
    
5.  Save the changes.
    

**Using AWS CLI:**

1.  Enable mTLS Authentication:  
    
    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.ClientAuthentication.Tls"
    

#### **Backout Plan**

**Using AWS Console:**

1.  If enabling Mutual TLS Authentication causes issues with client connections, sign in to the AWS Management Console.
    
2.  Navigate to Amazon MSK, select the Kafka cluster, and go to Edit.  
      
    ![](https://support.icompaas.com/assets/kb/f9a06eaf1453d0fb.png) ![](https://support.icompaas.com/assets/kb/d9490ae0ae598889.png)
    
3.  Disable Mutual TLS Authentication and switch to standard TLS encryption (i.e., without client authentication).
    
4.  Save the changes and verify that clients are able to reconnect.
    

**Using AWS CLI:**

1.  To disable Mutual TLS Authentication, run the following command:  
    
    aws kafka update-cluster-configuration --cluster-arn <CLUSTER\_ARN> --encryption-in-transit '{"enabled": true, "clientBroker": "TLS"}' --region <REGION>
    
2.  Verify that Mutual TLS Authentication is no longer enabled:  
    
    aws kafka describe-cluster --cluster-arn <CLUSTER\_ARN> --region <REGION>
    

#### **References**

-   [Enable Mutual TLS Authentication for Kafka Clients](https://www.trendmicro.com/cloudoneconformity/knowledge-base/aws/MSK/enable-mutual-tls-authentication-for-kafka-clients.html)
    
-   [Configure mTLS Authentication and RBAC for Kafka Brokers](https://docs.confluent.io/platform/current/kafka/configure-mds/mutual-tls-auth-rbac.html)
    
-   [Use TLS Authentication in Confluent Platform](https://docs.confluent.io/platform/current/security/authentication/mutual-tls/overview.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.
