Ensure Redshift clusters are not publicly accessible
Redshift clusters should not be accessible from the internet. Public accessibility increases the attack surface and risk of unauthorized access to sensitive data warehouse data.
Security Impact
Publicly accessible Redshift clusters are vulnerable to brute-force attacks, SQL injection, and unauthorized data exfiltration.
How to Remediate
Modify the cluster to set PubliclyAccessible to false. Ensure the cluster is in a private subnet and access is through VPN, Direct Connect, or bastion hosts.
Affected Resources
Compliance Frameworks
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 CIS AWS v1.5.0, PCI-DSS, HIPAA compliance
- Drift Detection
Get alerted if this configuration drifts back to an insecure state after remediation
Check Details
- Check ID
- aws-redshift-1
- Service
- Amazon Redshift
- Category
- Network Security
- Severity
- CRITICAL
- CIS Benchmark
- 5.1
Automate This Check
TigerGate automatically scans your AWS environment for this and 575+ other security checks.
Start Free TrialRelated Amazon Redshift Checks
View all checksEnsure Redshift clusters have encryption at rest enabled
Ensure Redshift clusters have encryption in transit enabled
Ensure Redshift clusters have audit logging enabled
Ensure Redshift clusters have automated snapshots configured
Ensure Redshift cluster snapshots are encrypted