GuardDuty on but a protection plan is off for resources you have
HIGHWhat's the problem
Checks 6 plans: S3 Protection, EKS Audit Log, EKS Runtime Monitoring (automated agent), Malware Protection for EC2, RDS Protection, Lambda Protection. A plan is reported only when the Region has that kind of resource (S3 buckets, EKS clusters, EC2, Aurora/RDS PostgreSQL/MySQL/MariaDB, Lambda)
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: AWS Security Hub GuardDuty.5–GuardDuty.10
Scan this check (and the other 129) automatically in ~10 minutes
Start free