Ensure backup plans have sufficient retention periods
Backup retention should align with regulatory requirements and business needs. Consider long-term retention for compliance and audit purposes.
Security Impact
Insufficient retention prevents recovery from incidents discovered after backups are deleted.
How to Remediate
Configure retention periods in backup plans based on compliance requirements (e.g., 7 years for some regulations). Use lifecycle policies for cost optimization.
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 AWS Backup 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, SEC 17a-4, FINRA compliance
- Drift Detection
Get alerted if this configuration drifts back to an insecure state after remediation
Check Details
- Check ID
- aws-backup-4
- Service
- AWS Backup
- 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 AWS Backup Checks
View all checksEnsure AWS Backup has backup plans configured for critical resources
Ensure backup vaults have encryption enabled
Ensure backup vaults have access policies configured
Ensure backup plans include cross-region copy for disaster recovery
Ensure backup plans have appropriate backup frequency