Ensure GuardDuty findings are exported
GuardDuty findings should be exported to S3 and EventBridge for retention and response.
Security Impact
Findings only retained for 90 days in GuardDuty. Long-term retention requires export.
How to Remediate
Configure findings export to S3 for long-term retention. Use EventBridge for real-time processing.
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 GuardDuty 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-guardduty-7
- Service
- Amazon GuardDuty
- Category
- Logging
- Severity
- MEDIUM
Automate This Check
TigerGate automatically scans your AWS environment for this and 575+ other security checks.
Start Free TrialRelated Amazon GuardDuty Checks
View all checksEnsure GuardDuty is enabled in all regions
Ensure GuardDuty has S3 Protection enabled
Ensure GuardDuty has EKS Protection enabled
Ensure GuardDuty has Malware Protection enabled
Ensure GuardDuty has RDS Protection enabled