High-severity GuardDuty findings not sent to anyone
MEDIUMWhat's the problem
GuardDuty is on, but no EventBridge rule sends High or Critical findings to email, Slack or ticketing. A compromised instance or leaked key is only noticed when someone opens the GuardDuty console
How 6WAF detects it
- Deterministic checks through AWS API calls (IAM, S3, EC2/VPC, CloudTrail, KMS, Secrets Manager, ACM, detection services) — no LLM is used for detection; severity is the value the scanner assigns, shown above.
- Scanning uses an IAM Role you deploy yourself via CloudFormation; 6WAF stores no credentials and you revoke access any time by deleting the stack.
- Automated scoring covers only part of the scope of standards such as ISO 27001 — this is a technical assessment, not a certification.
Pillar: Security — Fast Scan
Group: Detection services (GuardDuty, Security Hub, Config, Inspector, Access Analyzer, Cost Anomaly Detection, Regions outside the scan)
Reference standard: 6WAF classification (no Security Hub control)
Scan this check (and the other 132) automatically in ~10 minutes
Start free