Ensure Redshift clusters have automated snapshots configured
Automated snapshots provide point-in-time recovery capability for data protection and disaster recovery. Snapshots should be retained for appropriate periods.
Security Impact
Without automated snapshots, data loss from corruption, accidental deletion, or ransomware cannot be recovered.
How to Remediate
Enable automated snapshots with retention period of at least 7 days. Consider longer retention for production clusters based on RPO requirements.
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 SOC 2, Business Continuity, NIST 800-53 compliance
- Drift Detection
Get alerted if this configuration drifts back to an insecure state after remediation
Check Details
- Check ID
- aws-redshift-5
- Service
- Amazon Redshift
- Category
- Backup and Recovery
- Severity
- MEDIUM
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 cluster snapshots are encrypted