HIGH

Ensure Redshift clusters have encryption in transit enabled

SSL/TLS encryption for client connections protects data in transit from interception and man-in-the-middle attacks.

Security Impact

Unencrypted connections allow network sniffing and data interception, exposing sensitive query data and credentials.

How to Remediate

Modify the cluster parameter group to require SSL connections. Set require_ssl parameter to true and configure client applications to use SSL.

Affected Resources

AWS::Redshift::ClusterParameterGroup

Compliance Frameworks

PCI-DSSHIPAASOC 2NIST 800-53

How TigerGate Helps

TigerGate continuously monitors your AWS environment to detect and alert on this misconfiguration. Here's what our platform does for this specific check:

  • Continuous Scanning

    Automatically scans all Amazon Redshift resources across your AWS accounts every hour

  • Instant Alerts

    Get notified via Slack, email, or webhooks when this misconfiguration is detected

  • One-Click Remediation

    Fix this issue directly from the TigerGate dashboard with our guided remediation

  • Compliance Evidence

    Automatically collect audit evidence for PCI-DSS, HIPAA, SOC 2 compliance

  • Drift Detection

    Get alerted if this configuration drifts back to an insecure state after remediation

Check Details

Check ID
aws-redshift-3
Service
Amazon Redshift
Category
Encryption
Severity
HIGH

Automate This Check

TigerGate automatically scans your AWS environment for this and 575+ other security checks.

Start Free Trial

Related Amazon Redshift Checks

View all checks
aws-redshift-1critical

Ensure Redshift clusters are not publicly accessible

aws-redshift-2high

Ensure Redshift clusters have encryption at rest enabled

aws-redshift-4high

Ensure Redshift clusters have audit logging enabled

aws-redshift-5medium

Ensure Redshift clusters have automated snapshots configured

aws-redshift-6high

Ensure Redshift cluster snapshots are encrypted