TL;DR: Managed rulesets on Enable the Cloudflare managed rulesets appropriate for your stack. # Workflow: WAF hardening ## 1. They cover the OWASP-style basics; your custom rules cover your app's specifics.

## Fix
1. Managed rulesets on Enable the Cloudflare managed rulesets appropriate for your stack.
   Expected: this specific failure stops.
2. Skip rules for known-good traffic first Before adding blocks, add Skip rules for health checks, monitoring probes, partner webhooks, and office IPs.
   Expected: this specific failure stops.
3. Remember terminating actions stop evaluation: the first Block wins. ## 4.
   Expected: this specific failure stops.
4. Rate limiting in Log mode Add rate limits for auth endpoints and expensive APIs.
   Expected: this specific failure stops.
5. Deploy in Log, use the request-rate analysis to pick thresholds, count failures (401s) rather than raw hits for login endpoints, then switch to block or challenge. ## 5.
   Expected: the request routes instead of erroring.
6. Weekly review in the first month: every false positive gets a narrower expression or a skip; every missed attack gets a new rule. ## Checklist - Skips first, then specific blocks, then broad challenges. - Log before enforce, for both custom rules and rate limits. - Never disable the whole WAF to fix one rule.
   Expected: this specific failure stops.

## Details
# Workflow: WAF hardening ## 1. Skips must evaluate before the blocks they exempt: order them first. ## 3. Name them by intent. Tune from the events log The Security events log shows every action and which rule fired.

## When to use
You hit exactly this: Workflow: hardening a zone with the WAF in Workflow.

## When not to use
A different error, or the same symptom in a different tool. This page only covers the failure above.

## Compatibility
Workflow.

## Edge cases
- They cover the OWASP-style basics; your custom rules cover your app's specifics.
- Know the execution order: custom rules, managed rules, Bot Fight Mode are separate phases. ## 2.
- Custom rules for your attack surface Write narrow rules for your stack's known-bad patterns (admin paths, legacy endpoints, probe signatures).