GuardDuty off in Regions you do not use
LOWWhat's the problem
Attackers often launch resources in Regions nobody watches. Grouped into one LOW finding because no workload runs there today (AWS recommends GuardDuty in every Region)
How 6WAF detects it
- Deterministic checks through AWS API calls (IAM, S3, EC2/VPC, CloudTrail, KMS) — 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: Threat detection (GuardDuty, Regions outside the scan)
Scan this check (and the other 91) automatically in ~10 minutes
Start free