Review managed WAF protection
500,000 HTTP requests in 7 days; no effective managed-WAF deployment at zone or applicable account scope.
Recommended next step
Review the appropriate managed ruleset, validate application compatibility, and stage deployment with monitoring.
Evidence, assumptions & measurement
Impact
Potentially improve request inspection coverage. No monetary savings are asserted.
Effort & risk
Configuration review and staged rollout. Rules can block legitimate application traffic; review matches before enforcement.
Measure the outcome
Rescan after deployment and review false positives and application error rates.
Assumptions
- Deployment absence does not prove an attack occurred.
- Paid entitlement and commercial value require separate confirmation.
Evidence
- Zone inventory
Fictional active zone: assets.example.com.
- Customer confirmation
Fictional customer marked this scope production and non-test.
- Zone managed-WAF entrypoint
Fixture confirms readable zone scope with no effective deployment.
- Applicable account managed-WAF entrypoint
Fixture confirms readable account scope with no applicable deployment.
- HTTP analytics
500,000 eyeball requests; 12 GB response bytes; seven complete UTC days; unsampled fixture.
Rule CF-001 · Version 2026-09-19.2 · All sources are sample fixtures.