In an effort to reshape modern web security against increasingly sophisticated, AI-driven threats, Cloudflare has announced a major expansion of its web application firewall (WAF). The security platform is introducing two powerful new capabilities: full transaction detections and response rules. This dual approach allows the firewall to evaluate incoming HTTP requests alongside the corresponding server responses, answering not only whether a request looks malicious, but also determining what actually happened when the backend application processed it.
These protections arrive at a critical time in the cybersecurity landscape. Modern frontier artificial intelligence models are rapidly uncovering deeply buried vulnerabilities in widely used software components, providing defenders with much-needed clarity on what needs patching while simultaneously opening new, automated pathways for attackers. Incidents like the recent php2shell vulnerability underscore the high stakes involved, demonstrating how a single flaw in a common software component can instantly place applications across the global Internet at risk. Today’s AI-powered scanning agents are remarkably persistent, capable of adapting payloads based on real-time feedback and seamlessly chaining vulnerabilities, credentials, and permissions together. Because an application’s response can immediately reveal whether an exploitation attempt was successful, it often hands attackers the exact information they need to dig deeper into a compromised system.
Traditionally, web application firewalls have relied heavily on inspecting incoming requests to stop recognizable attack patterns before they ever reach an application backend. While this request-level inspection remains a foundational pillar of web security, it is no longer enough on its own. Some threats only become entirely clear when an incoming request is evaluated in direct context with what the origin server returns. A suspicious input followed by a response that accidentally exposes sensitive corporate information tells a completely different security story than the exact same input followed by an immediate server rejection or an error code.
By bridging this gap, the newly introduced capabilities enable customers to leverage Cloudflare-managed protections or construct custom security policies that seamlessly combine both request and response properties. This enhancement significantly extends the platform’s always-on application security framework, with all detection results directly accessible within Security Analytics to streamline forensic investigations. Notably, Cloudflare’s initial managed protections utilizing this fresh architectural approach are specifically engineered to address the recently disclosed php2shell vulnerability. In a notable win for web administrators, the company is making these advanced capabilities generally available across all customer tiers, including free plans.
Request Inspection Is Not Enough
Cloudflare’s WAF has long protected websites and application programming interfaces through a combination of managed rules, custom rules, and rate-limiting features. Managed rules provide robust baseline protections against well-known attack methodologies and specific software vulnerabilities, while custom rules empower security teams to craft bespoke policies using parameters such as client IP addresses, specific URL paths, HTTP headers, and request bodies. Historically, these controls have operated exclusively at the request level to halt exploits or unwanted traffic before reaching the origin.
For many standard threat scenarios, acting at the request boundary remains the most effective course of action. However, treating every single suspicious request as a confirmed exploit presents security engineers with a difficult operational dilemma. Broad request signatures can successfully catch a higher volume of potential attacks, but they frequently trigger false positives by incorrectly flagging legitimate traffic, which can inadvertently break normal application functionality. Conversely, deploying only conservative rules that minimize false positives reduces that operational risk, but it inevitably leaves more room for ambiguous or sophisticated traffic to slip through to the server.
The response phase provides the missing evidentiary link. By correlating the server response directly with the HTTP request that produced it, Cloudflare’s WAF can now ensure that security detections account for the ultimate outcome of the entire transaction.
As an illustrative example, consider a web application that permits users to download files. An attacker might manipulate the file parameter in an attempt to request a private configuration file residing far outside the permitted directory structure. Request inspection mechanisms can easily recognize this classic path traversal attempt and block it upfront. However, a request alone cannot establish whether the target application would actually expose the file. The backend might reject the request outright, ignore the traversal string, or return a standard application error. If the request does manage to reach the origin and successfully retrieve data, the resulting server response provides definitive, undeniable evidence of exposure.
Full transaction detection provides the missing piece of the puzzle by correlating the attempted file access with response content characteristics typically found in private configuration files. Because configuration-like text can sometimes appear legitimately in public documentation or example downloads, combining it with a traversal attempt delivers a much stronger, more accurate indicator of sensitive data exposure than either signal evaluated in isolation. A response rule can then intercept this server output, replacing the origin response with a standard WAF block page and an HTTP 403 status code before it ever reaches the requester, effectively neutralizing the exploit by keeping sensitive information out of the attacker’s hands.
Detection and Mitigation Are Separate by Design
Full transaction detection naturally extends the always-on detection framework that Cloudflare introduced earlier this year. Under this architecture, detections analyze live traffic and attach rich metadata to both the request and response objects, leaving downstream rules to decide how to handle those results.
Separating these two distinct functions provides customers with unprecedented visibility before they even design a mitigation policy. Security teams can thoroughly inspect detections within their own live traffic, understand precisely which endpoints and signatures are involved, and choose a response strategy tailored to their specific application architecture. Similar to the methodology used for request-based attack signature detection, the outcomes of these detections are stored in dedicated fields that can be referenced in response custom rules or leveraged by managed detections to block malicious traffic automatically.
The platform now incorporates specific new fields to mirror existing request detection capabilities. These include fields dedicated to tracking confidence values associated with matching signatures, categories tied to matching signatures, and signature reference IDs. The initial rollout of full transaction detections focuses heavily on exploit confirmation for high-profile vulnerabilities, correlating suspicious inputs directly with response signals that indicate an active exploit may have succeeded.

Cloudflare plans to systematically expand this coverage over time to support additional use cases, including the active detection of data exposure and exfiltration signals. This expansion holds significant value for the wider Internet ecosystem, enabling defenses to reliably distinguish harmless probing from actual evidence of impact, while ensuring that even organizations without dedicated security teams tuning individual WAF rules benefit from robust protection.
Create Rules on the Response
Detecting evidence of exploitation is most valuable when security systems can act upon it in real time. Response custom rules transform full transaction detections into inline protection mechanisms by blocking matching origin responses before they reach the requester, though they cannot inherently undo actions that have already been executed at the origin.
Security teams can now combine request attributes, response properties, and detection results to exercise granular control over which responses should be blocked. When a blocking rule matches, Cloudflare substitutes the origin’s response with a standard WAF block page or a customized response. These response phase controls are conveniently located within the Cloudflare dashboard, encompassing both managed protections and custom rules.
Both managed and custom response rules are available across all account tiers, including Free plans. Over time, the platform will follow its established approach for request detections, where managed detections on free plans focus primarily on high-profile vulnerabilities, while paying customers gain access to a much broader and richer catalog of specialized detections.
Managed Detections
All customers immediately receive the protection of full transaction detections through the Cloudflare Managed Response Firewall Default ruleset, which is engineered for straightforward, one-click deployment and simplified administration. When a signature matches, the managed detection automatically blocks the response and returns a standard WAF block page.
Administrators can easily edit the scope of this managed ruleset to run detections selectively across portions of their applications, such as excluding specific paths or restricting the checks to sensitive directories. Paying customers can further leverage detection fields in custom response rules to build highly tailored security policies.
Custom Rules
Custom response rules are engineered to grant customers absolute control over underlying rule logic. A practical application of this capability involves preventing an administrative interface from being exposed to the public internet when an authentication gateway fails to mark a request as internal. By combining path criteria, header evaluations, response status codes, and content types, administrators can ensure that blocking actions trigger only when an unauthenticated request targets an administrative path and the origin actually succeeds in returning a valid HTML page. This precise targeting ensures that ordinary authentication failures, routine redirects, and non-administration traffic proceed normally without disruption.
All customers can configure up to three custom response rules supporting both log and block actions. The fields and functions available for response custom rules directly mirror the capabilities already provided in request custom rules, though creating rules directly targeting the response body is not yet supported. Paying customers also gain access to signature-based response fields, which can be combined with hostnames, URL paths, source IP addresses, and request headers to enforce path-specific protections.
Investigating Matching Requests
When a managed or custom response rule successfully logs or blocks an transaction, the complete event is immediately logged within Security Events. This ensures that security responders can trace any detection back to the full context of the incoming request alongside the specific rule that initiated the action.
Currently, request-only rules and full-transaction rules appear together within the same centralized analytics interface. Events generated by response rules are categorized under the Managed Rules or Custom Rules services, allowing administrators to filter events belonging to specific rule IDs easily. Full transaction detection is generally available today for all zones proxying traffic through Cloudflare, with users encouraged to review their security rules and dashboard analytics to verify their active protection posture.