Data at riskConnections to Redshift cluster not encrypted in transit
Platform(s)
Compliance Frameworks
- AWS Foundational Security Best Practices Controls ,
- Brazilian General Data Protection (LGPD) ,
- CCM-CSA ,
- CCPA ,
- cis_8 ,
- coppa ,
- CPRA ,
- Data Security Posture Management (DSPM) Best Practices ,
- GDPR ,
- hdh ,
- HITRUST ,
- ISO 27701 ,
- iso_27001_2022 ,
- iso_27002_2022 ,
- Mitre ATT&CK ,
- mpa ,
- New Zealand Information Security Manual ,
- NIST 800-171 ,
- NIST 800-53 ,
- PDPA ,
- pipeda
Description
An Amazon Redshift cluster consists of nodes. Each cluster has a leader node and one or more compute nodes. The leader node receives queries from client applications, parses the queries, and develops query execution plans. The leader node coordinates the parallel execution of these plans with the compute nodes and aggregates the intermediate results from these nodes. It then finally returns the results back to the client applications. It was detected that the Redshift cluster {AwsRedshiftCluster} connections are not encrypted in transit. Transport Layer Security (TLS) can be used to help prevent potential attackers from using man-in-the-middle (MiTM) or similar attacks to eavesdrop on or manipulate network traffic. It is recommended to allow only encrypted connections over TLS.
Personalized Demo
See Orca Security in Action
Gain visibility, achieve compliance, and prioritize risks with the Orca Cloud Security Platform.