WAF Web ACL has no AWS managed rule groups enabled
- Severity
- High
- Service
- AWS WAF
- Check ID
- WAF_NO_MANAGED_RULES
What this check finds
This Web ACL contains no AWS managed rule groups. Managed rules provide protection against common threats (OWASP Top 10, known bad IPs, bot signatures) with no custom rule authoring.
Passing looks like: WAF has AWS managed rule groups enabled.
How to fix it
Add at least the AWSManagedRulesCommonRuleSet to the Web ACL.
AWS console
WAF → Web ACLs → Rules → Add managed rule groups.
Compliance controls it is evidence for
A failing result counts against these controls in KloudLytics; a passing one is evidence towards them. How compliance mapping works
| Framework | Controls |
|---|---|
| PCI-DSS v4.0.1 |
|
| NIST SP 800-53 Rev5 (Moderate) |
|
| NIST Cybersecurity Framework 2.0 |
|
| ISO/IEC 27001:2022 Annex A |
|
Checked on every scan
KloudLytics runs this check each time it scans a connected AWS account, through a read-only role, and lists every affected resource with its region. On Pro and Business a fix is written for the specific resource rather than the general case above. The exact access it needs