Ensure WAF has rate limiting rules
WAF should have rate-based rules to protect against DDoS and brute force attacks.
Security Impact
Without rate limiting, applications are vulnerable to DDoS and credential stuffing.
How to Remediate
Create rate-based rules with appropriate thresholds (e.g., 2000 requests per 5 minutes per IP).
Affected Resources
Compliance Frameworks
How TigerGate Helps
TigerGate continuously monitors your AWS environment to detect and alert on this misconfiguration. Here's what our platform does for this specific check:
- Continuous Scanning
Automatically scans all AWS WAF resources across your AWS accounts every hour
- Instant Alerts
Get notified via Slack, email, or webhooks when this misconfiguration is detected
- One-Click Remediation
Fix this issue directly from the TigerGate dashboard with our guided remediation
- Compliance Evidence
Automatically collect audit evidence for SOC 2, PCI-DSS, NIST 800-53 compliance
- Drift Detection
Get alerted if this configuration drifts back to an insecure state after remediation
Check Details
- Check ID
- aws-waf-5
- Service
- AWS WAF
- Category
- Rate Limiting
- Severity
- MEDIUM
Automate This Check
TigerGate automatically scans your AWS environment for this and 575+ other security checks.
Start Free Trial