Cloudflare has added full transaction detection to its web application firewall, letting it judge each HTTP request together with the response the origin sends back. The company is also adding response rules that can block an origin’s response before it reaches the requester, according to Cloudflare’s announcement of the feature.
Cloudflare said both capabilities are generally available to all customers, including Free plans. Its first managed protections using full transaction detection address the recently disclosed php2shell vulnerability.
Why Full Transaction Detection Matters
Cloudflare WAF already protects sites with managed rules, custom rules and rate limiting that act on incoming requests. The company said treating every suspicious request as a confirmed exploit creates a hard choice.

Broad request signatures can catch more attacks but can also match legitimate traffic and break applications. Narrower rules reduce that risk but let more ambiguous traffic reach the server.
Cloudflare said the response supplies the missing evidence. A suspicious input followed by a response exposing sensitive information tells a different story from the same input followed by a rejection or an error.
The company linked the change to AI. It said the latest frontier models are uncovering vulnerabilities deep in widely used software, and AI agents scanning for flaws can adapt payloads using feedback.
How Response Rules Work
Response custom rules block a matching origin response before it reaches the requester. Cloudflare noted that they cannot undo actions already performed at the origin. When a blocking rule matches, Cloudflare replaces the response with a WAF block page or a custom response.
All customers can create up to three custom response rules with Log and Block actions, combining request and response fields. Rules on the response body are not yet available.
Cloudflare gave one example rule. It blocks only when an unauthenticated request targets an admin path and the origin actually returns a successful HTML administration page.
Managed Detections For Every Plan
All customers get full transaction detection through the Cloudflare Managed Response Firewall Default ruleset, designed for one-click deployment. When a signature matches, it blocks the response and returns a standard WAF block page.
The ruleset runs on every request by default. To reduce false positives, customers can limit it to part of an application, such as a specific path. Paying customers can use detection fields in custom rules for more tailored policies.
Cloudflare said free plans will get managed detections focused on high-profile vulnerabilities, while paying customers get a richer catalog. It plans to add detection of data exposure and exfiltration signals over time.
Where To Find It
Response phase controls sit at the bottom of the Security Rules page in the Cloudflare dashboard. Logged or blocked transactions appear in Security Events, where responders can trace a detection back to the full request and the rule that acted.
Cloudflare said it is still rolling out the response fields to all accounts, and customers without access yet can contact their account team.
Related coverage: Cloudflare’s new range-request caching, a Cloudflare Containers security fix and AI tools that help WordPress find flaws.









