Ensure Security Hub data is retained for compliance requirements
Security Hub findings should be exported to S3 or SIEM for long-term retention beyond the 90-day Security Hub retention limit.
Security Impact
Findings older than 90 days are deleted by Security Hub, preventing historical analysis and compliance audit evidence.
How to Remediate
Configure automatic export of findings to S3 via EventBridge and Kinesis Firehose. Retain for required compliance period (e.g., 7 years).
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 Security Hub 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-securityhub-15
- Service
- AWS Security Hub
- Category
- Compliance
- Severity
- MEDIUM
Automate This Check
TigerGate automatically scans your AWS environment for this and 575+ other security checks.
Start Free TrialRelated AWS Security Hub Checks
View all checksEnsure AWS Security Hub is enabled in all regions
Ensure Security Hub has CIS AWS Foundations Benchmark enabled
Ensure Security Hub has AWS Foundational Security Best Practices enabled
Ensure Security Hub has PCI-DSS standard enabled if applicable
Ensure Security Hub findings are integrated with incident response workflow