Critical Protect Regional

MSK clusters should have public access disabled

FSBP

Description

This control checks whether public access is disabled for an Amazon MSK cluster. The control fails if public access is enabled for the MSK cluster. By default, clients can access an Amazon MSK cluster only if they are in the same Virtual Private Cloud (VPC) as the cluster. All communication between Kafka clients and an MSK cluster is private by default, and streaming data does not traverse the internet. However, if an MSK cluster is configured to allow public access, anyone on the internet can establish a connection to Apache Kafka brokers running within the cluster. This can lead to serious security issues such as unauthorized access, data breaches, or exploitation of vulnerabilities. Restricting access to a cluster by requiring authentication and authorization measures helps protect sensitive information and maintain the integrity of resources.


Remediation

To remediate MSK clusters with public access enabled, you need to disable public access and ensure the cluster is only accessible within the VPC.

Steps

  1. Navigate to the Amazon MSK console
  2. Select the MSK cluster with public access enabled
  3. Click on 'Edit' or 'Modify' cluster
  4. Go to 'Network' settings
  5. Disable 'Public access' option
  6. Ensure the cluster is in a private subnet
  7. Configure VPC security groups properly
  8. Review the network configuration
  9. Apply the changes to the cluster
  10. Verify public access is disabled

Compliance

FSBP