GuardDuty not enabled (or suspended) in a scanned Region
HIGHWhat's the problem
Without GuardDuty, leaked credentials, crypto-mining instances and calls from known malicious IPs in that Region go undetected
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)
Reference standard: AWS Security Hub GuardDuty.1
Scan this check (and the other 91) automatically in ~10 minutes
Start free