Ensure RDS backup retention is at least 7 days
RDS backup retention period should be at least 7 days to allow recovery from recent incidents.
Security Impact
Short retention periods may not provide sufficient recovery window for security incidents discovered after the fact.
How to Remediate
Modify RDS instance backup retention period to at least 7 days. Consider longer retention for compliance.
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 Relational Database Service (RDS) 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, PCI-DSS, HIPAA compliance
- Drift Detection
Get alerted if this configuration drifts back to an insecure state after remediation
Check Details
- Check ID
- aws-rds-5
- Service
- Relational Database Service (RDS)
- Category
- Data Protection
- Severity
- MEDIUM
Automate This Check
TigerGate automatically scans your AWS environment for this and 575+ other security checks.
Start Free TrialRelated Relational Database Service (RDS) Checks
View all checksEnsure RDS instances are not publicly accessible
Ensure RDS instances have encryption at rest enabled
Ensure RDS instances use KMS customer managed keys
Ensure RDS instances have automated backups enabled
Ensure RDS instances have Multi-AZ enabled