Ensure GuardDuty high severity findings are addressed within SLA
High and critical severity findings should be investigated within defined SLAs.
Security Impact
Delayed response to high severity findings increases risk of successful attacks.
How to Remediate
Define SLAs for finding severity levels. Track mean time to acknowledge and resolve.
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, NIST 800-53 compliance
- Drift Detection
Get alerted if this configuration drifts back to an insecure state after remediation
Check Details
- Check ID
- aws-guardduty-14
- Service
- Amazon GuardDuty
- Category
- Incident Response
- Severity
- HIGH
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