HIGH

Ensure Redshift cluster security groups restrict access to known IPs

Security groups should implement least privilege by allowing access only from known IP addresses or security groups, not 0.0.0.0/0.

Security Impact

Overly permissive security groups allow unauthorized network access to the cluster from any location.

How to Remediate

Review and restrict security group ingress rules to specific IP ranges or security groups that require Redshift access.

Affected Resources

AWS::EC2::SecurityGroup

Compliance Frameworks

SOC 2NIST 800-53Least Privilege

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 SOC 2, NIST 800-53, Least Privilege compliance

  • Drift Detection

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

Check Details

Check ID
aws-redshift-13
Service
Amazon Redshift
Category
Network Security
Severity
HIGH

Automate This Check

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

Start Free Trial