turbot/steampipe-mod-aws-compliance

Control: 3 MSK Connect connectors should be encrypted in transit

Description

This control checks whether an Amazon MSK Connect connector is encrypted in transit. This control fails if the connector isn't encrypted in transit.

Data in transit refers to data that moves from one location to another, such as between nodes in your cluster or between your cluster and your application. Data may move across the internet or within a private network. Encrypting data in transit reduces the risk that an unauthorized user can eavesdrop on network traffic.

Remediation

You can enable encryption in transit when you create an MSK Connect connector. You can't change encryption settings after creating a connector. For more information, see Create a connector in the Amazon Managed Streaming for Apache Kafka Developer Guide.

Usage

Run the control in your terminal:

powerpipe control run aws_compliance.control.foundational_security_msk_3

Snapshot and share results via Turbot Pipes:

powerpipe login
powerpipe control run aws_compliance.control.foundational_security_msk_3 --share

SQL

This control uses a named query:

select
arn as resource,
case
when kafka_cluster_encryption_in_transit ->> 'EncryptionType' = 'TLS' then 'ok'
else 'alarm'
end as status,
case
when kafka_cluster_encryption_in_transit ->> 'EncryptionType' = 'TLS' then title || ' encryption in transit enabled.'
else title || ' encryption in transit enabled with plaintext.'
end as reason
, region, account_id
from
aws_mskconnect_connector;

Tags