// AI Platform Drift

Cloudflare adds response custom rules to WAF

Cloudflare developer changelog · published 2026-11-14 18:05 UTC
WORTH KNOWING VERIFY_ONLY APISECURITY
WHAT CHANGEDCloudflare added response custom rules to the WAF, available in the http_response_firewall_custom phase. Every plan includes three response custom rules per zone, supporting block, log, and execute actions. At most one execute rule is allowed within the three-rule allowance. Rules can combine request and response fields in expressions.
WHY IT MATTERSYou can now block responses before they reach visitors based on response characteristics combined with request context. This enables blocking error responses from specific endpoints or preventing sensitive data leakage based on response content, without requiring changes to origin servers.
WHAT TO DOReview your application's error handling and data exposure patterns. Identify endpoints where response-based blocking would prevent information disclosure or improve security posture, then configure response custom rules in the Cloudflare dashboard.
Model-reported confidence 85% (not measured accuracy) Primary source ↗ written by anthropic/claude-sonnet-4.5
Show the reasoning — raw diff, triage verdict, confidence
RAW DIFF
+## WAF - Response custom rules
+https://developers.cloudflare.com/changelog/post/2026-10-21-response-custom-rules/
+Wed, 21 Oct 2026 00:00:00 GMT
+
+The response firewall can block responses before they reach visitors. Cloudflare turns on default protections for everyone, on every plan.
+Every plan includes three response custom rules per zone. These rules run in the http_response_firewall_custom phase.
+Rules support the block, log, and execute actions. You can include at most one execute rule within the three-rule allowance.
+Response custom rules can combine request fields with response fields. For requests to /api/ paths, this expression matches responses with status code 500:
+starts_with(http.request.uri.path, "/api/") and http.response.code eq 500
+For background, refer to the full transaction detection announcement ↗︎.
+For supported actions, fields, and limits, refer to Response firewall.
HOW IT WAS JUDGED
Triage signals below are model-reported assertions, preserved verbatim; they are not independent arithmetic verification.
triage verdictMATERIAL at 0.92, needed 0.5
triage reasoningNew WAF feature with quotas, actions, and execution constraints affects API surface and rate-limit planning.
signalsnew feature announcement · new capability: response firewall custom rules · quota introduced: three response custom rules per zone · new execution phase: http_response_firewall_custom · new supported actions: block, log, execute · constraint: at most one execute rule per three-rule allowance · new capability: combining request and response fields in expressions · availability: all plans included
suppression—
triage modelanthropic/claude-haiku-4.5 ($0.00000)
writer modelanthropic/claude-sonnet-4.5 ($0.00000)