ToolScore
API Security 4 min read

WAF Fine-Print Traps

8 verified fine-print traps the number that matters here

By Stan K.

CAPTCHA attempts at $4 per 10,000. A Challenge price that never renders on the static pricing page. Oversized inspection billed on the whole request, not the overage. Eight verified fine-print traps in WAF pricing — plus one webhook observation marked as analysis.

WAF pricing pages quote one number and invoice another — not dishonestly, but through fine print that only executes after deployment. Here are eight traps we verified against official pricing and docs pages (checked 2026-11-13), plus one field observation we explicitly mark as analysis. The bills these traps move are worked out in API Security: What 50 Million Requests Actually Cost.

The meter traps — AWS bills actions, not traffic

  1. CAPTCHA attempts are the most expensive requests you will ever serve. AWS WAF CAPTCHA bills $0.40 per 1,000 attempts — $4.00 per 10,000, computed on the official pricing page itself (Case G). Articles still quoting “$0.40 per 10K” are 10× understated. One attempt prices like 667 plain requests at the $0.60/1M meter; a site-wide challenge converts your bill into a function of attacker enthusiasm.
  2. The Challenge price is served dynamically. AWS WAF’s Challenge action is billed “per million responses served” — that basis is confirmed. The exact per-million figure never renders in the static pricing page (it arrives from the pricing API), so any specific number circulating in articles is uncheckable until you open the live calculator. Re-verify before modeling.
  3. Oversized inspection bills the whole request, not the overage. $0.20/1M for each 500 WCUs beyond the default 1,500 — but the official example (Case I) runs the arithmetic on the entire request: at 2,000 WCU, every request bills at $0.80/1M, not base-plus-delta. At 100M requests that is +$20/month per extra 500 WCU. Body inspection stacks the same way: $0.30/1M per additional 16KB.
  4. Shield Advanced’s $3,000 has dependents. A 1-year commitment per payer account, a paid Business or Enterprise Support plan (a hard requirement, priced separately), data-transfer-out fees (CloudFront/Global Accelerator $0.025/GB for the first 100TB, tiering to $0.01), and an included WAF allowance (50B requests/month) that only holds at up to 1,500 WCUs. Above that, WCU charges bill fully — the official Example 9 prices 60B requests at 2,000 WCU at $12,000/month in WCU charges alone.

The plan-limit traps — Cloudflare hides limits in features

  1. Free cannot say “60 per minute”. One rate-limiting rule, IP-only counting, a 10-second counting period: “60 req/min” is not expressible on Free. 1-minute windows start at Pro, 10-minute at Business; counting characteristics beyond IP (headers, cookies, JWT claims) are Business+. Related corpse: the legacy per-10K-requests rate-limiting product is retired — the docs say “no longer available”, all rules upgraded. Articles still billing it describe a product that no longer exists.
  2. Regex starts at Business. Free gets 5 custom rules, Pro gets 20 — both literal expressions only. Regex support begins at Business ($200/mo billed annually, 100 rules). Teams discover this the day they try to write ^/api/v[0-9]+/ and the editor rejects it: the same rule costs $0 on a Business plan and is impossible on Pro.

The procurement and false-positive traps

  1. Fastly’s request volumes are unpublished. The pricing page shows three tiers (Security Core / Core Plus / Total), rule counts (5 / 25 / 100) and workspaces — every price cell says “Contact sales”, and Bot Management exists only in Total. The request-pool figures circulating in articles (2.5B/1.5B) appear nowhere on fastly.com. Imperva and Akamai are the same religion minus the tiers: not one dollar figure on the official page (Akamai even returned 403 to our probes). Everything a rep quotes is negotiable — and unverifiable.
  2. Managed rules break webhooks (analysis). Stripe and GitHub webhook senders are not browsers, and rulesets that score requests by browser-shaped signals flag them. The documented dials exist — the OWASP Core’s paranoia level (higher paranoia, more false positives) and Cloudflare’s Browser Integrity Check docs, which themselves advise disabling it selectively. The webhook breakage itself is field analysis, not a documented failure — but the safe pattern is cheap: route webhooks around managed rules entirely.
The pattern behind all eight

Flat-plan vendors hide limits in features (windows, regex, rule counts). Meter vendors hide costs in actions — the request is cheap until you challenge it, CAPTCHA it, or grow rules past 1,500 WCU. Quote-only vendors hide the price itself. Re-price every option at your own request volume before comparing — the worked example at 50M requests/month lives in API Security: What 50 Million Requests Actually Cost, full tables in the API Security hub.

Numbers change — the math doesn't
Token prices and plan limits shift monthly; the structural arguments in this guide age slowly. For current per-tool numbers see the live rankings.