API Gateway stage not associated with a WAF Web ACL
- Severity
- Medium
- Service
- API Gateway
- Check ID
- WAF_NOT_ON_APIGW
What this check finds
This API Gateway REST API stage has no AWS WAF Web ACL attached. Without WAF, the API lacks protection against common web exploits and bot traffic.
Passing looks like: API Gateway associated with a WAF Web ACL.
How to fix it
Associate a WAF Web ACL with the API Gateway stage.
AWS CLI
aws wafv2 associate-web-acl --web-acl-arn WEB_ACL_ARN --resource-arn API_STAGE_ARN --scope REGIONAL
Names in capitals are placeholders for your own resource. Review a command before you run it.
AWS console
WAF → Web ACLs → select ACL → Associated AWS resources → Add.
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 |
|---|---|
| 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
More API Gateway checks
- HighAPI Gateway execute-api endpoint not disabled — CloudFront WAF bypassable
- HighAPI Gateway REST API method has no authorization
- HighHTTP API (v2) has no JWT authorizer configured
- HighPrivate API has no resource policy restricting access
- MediumAPI Gateway custom domain TLS minimum version below 1.2
- MediumAPI Gateway REST API has no request validators configured
- LowAPI Gateway stage does not have access logging enabled
- LowAPI Gateway stage has no method-level throttling configured