Check ID:
Provider: AWS
Service:
Severity: HIGH
Categories:
Resource type:
kafka_connector_in_transit_encryption_enabledProvider: AWS
Service:
kafkaSeverity: HIGH
Categories:
encryptionResource type:
OtherWhat this check verifies
MSK Connect connectors are evaluated for in-transit encryption usingTLS on client connections to Kafka brokers and connected systems.
Risk
Without TLS, data streams can be intercepted or modified in transit. Attackers on the path can perform man-in-the-middle, replay, or message tampering, exposing records and secrets. This degrades confidentiality and integrity and can enable unauthorized access to downstream systems.Recommendation
Require TLS for all connector communications and disallow plaintext. Prefer private connectivity, validate certificates, and use modern cipher suites. Pair with mutual authentication and least privilege roles for defense-in-depth. Regularly review connector configs to avoid non-TLS endpoints.Remediation
- Terraform
- Native IaC
- Dashboard steps
References
- https://docs.aws.amazon.com/msk/latest/developerguide/msk-connect.html
- https://docs.aws.amazon.com/msk/latest/developerguide/mkc-create-connector-intro.html
Where this check fires
This check runs on every scheduled scan against your AWS account. Findings appear at Cloud Security → Findings filterable byCheck ID = kafka_connector_in_transit_encryption_enabled. To re-evaluate after a fix, hit Run now on the account’s schedule under Cloud Security → Schedules — the next scan re-checks this control and marks the finding fixed or keeps it persistent.
← Back to AWS checks