Ensure Redshift cluster manual snapshots are not publicly accessible
Manual snapshots should never be publicly accessible as they contain full cluster data and can be restored by anyone with access.
Security Impact
Public snapshots allow anyone to restore full cluster data, leading to complete data breach and regulatory violations.
How to Remediate
Review all manual snapshots and ensure none are marked as public. Use private snapshots and cross-account sharing when needed.
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 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-14
- Service
- Amazon Redshift
- Category
- Data Protection
- Severity
- CRITICAL
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 are not publicly accessible
Ensure 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