
Cloudflare for Teams, launched in January 2020, was built around Cloudflare Access and Cloudflare Gateway. Gateway's first iteration arrived in March 2020 as a secure DNS filtering service: it blocked queries to destinations tied to malware, phishing, or ransomware, and an organization could enforce that protection across an office by changing its router settings in about five minutes.
That model assumed users sat behind known network boundaries. Once staff dispersed to home offices that have since become permanent, security stopped being a single office-level configuration and became a problem of managing users and devices across hundreds or thousands of locations. The threat picture shifted as well, with phishing and malware activity rising; identifying those attacks requires inspecting more than the DNS query.
Cloudflare Gateway now addresses both gaps in two ways. It integrates with the Cloudflare WARP desktop client, which is built on WireGuard, a modern VPN protocol described as more efficient and flexible than legacy alternatives. And Gateway becomes a Secure Web Gateway, performing L7 filtering to catch threats that DNS alone cannot see. Both capabilities draw on Cloudflare's experience running WARP for millions of users; like the DNS filtering and the 1.1.1.1 resolver, they run on that same infrastructure.
Why DNS filtering alone falls short
VPNs present distributed organizations with two problems Gateway was created to solve: they grant internal access on an all-or-nothing basis, which Cloudflare Access and its Zero Trust approach address for internal and, now, SaaS applications; and they are slow and expensive, yet backhauling traffic to a centralized security boundary has been the standard way to enforce content and security policy for roaming users.
DNS filtering itself carried three limitations for customers:
- The source IP of every location sending queries had to be registered so Gateway could identify that organization's traffic for policy enforcement—tedious, and close to intractable for organizations with hundreds of locations.
- Policies were coarse, enforced all-or-nothing per domain. An organization could not, for example, permit a cloud storage provider while blocking downloads of harmful files from known-malicious URLs.
- Organizations registering IP addresses often rely on Network Address Translation to share public IPs among many users, which removes per-user visibility from DNS activity logs. Admins can see a malicious domain was blocked but need additional forensic tools to find a potentially compromised device.
Pairing the Cloudflare for Teams client with a cloud L7 firewall moves Gateway past secure DNS filtering, letting customers retire another hardware appliance from their centralized security boundary and enforce enterprise-level security at the Cloudflare edge.
Layer 7 policy enforcement
DNS filtering secures entire systems and networks because every application uses DNS for Internet communication, but application-specific protection delivers granular enforcement and visibility into whether traffic is malicious. The new L7 firewall applies security and content policies to HTTP traffic, giving administrators finer controls inside HTTP sessions as well as insight into enforcement, and giving organizations more say over where their data resides: rules can allow or block a request by file type, by upload versus download, or by whether the destination is an approved cloud storage provider.
Users reach Cloudflare through the Cloudflare for Teams client, which connects to the nearest Cloudflare data center over the same WARP application millions of users already rely on—evidence of scale testing—with WireGuard optimizing performance to the edge. Traffic is filtered without backhauling to a centralized boundary, so all outbound Internet traffic is subject to policy, protecting users as they browse and preventing corporate data loss.
Gateway now filters HTTP traffic on a range of criteria:
Criteria | Example |
|---|---|
URL, path, and/or query string | https://www.myurl.com/path?query |
HTTP method | GET, POST, etc. |
HTTP response code | 500 |
File type and file name | myfilename.zip |
MIME type | application/zip |
URL security or content category | Malware, phishing, adult themes |
These L7 rules complement DNS filtering policies. Some examples:

To guard against data loss, an admin can permit downloads from popular cloud storage providers while blocking uploads of selected file types from corporate devices.

Another might block compressed file downloads to stop malicious files smuggled in through zip archives.

URL filtering also lets admins act on the classification of full URLs rather than whole domains. Because malware payloads are frequently delivered via cloud storage, DNS filtering forced a choice between allowing or denying an entire storage domain; URL-level rules target the exact URLs hosting payloads while keeping the provider's useful parts available.

All of it depends on the Cloudflare for Teams client, so distributed workforces with roaming clients get the same protection through the nearest Cloudflare data center.

What comes after HTTP
Non-HTTP traffic will follow later this year, when Gateway gains a cloud L4 firewall supporting IP, port, and protocol filtering. Administrators will then apply rules to all Internet-bound traffic—allowing outbound SSH, for example, or deciding whether HTTP traffic on a non-standard port goes to the L7 firewall for inspection.
At launch, policies filter DNS and HTTP traffic across all users in an organization, a solid security baseline. Because exceptions are part of reality, Cloudflare is working on rules based on user and group identity by integrating Cloudflare Access with a customer's existing identity provider, adding user context to rules. For instance: deny social media to everyone but allow John Doe in marketing to reach those sites for his role; or allow Jane Doe to connect only to specific SaaS applications through Gateway, or only from a certain device posture.
Identity-based enforcement and logging visibility matter precisely because users are no longer tied to fixed, known workplaces, and the Cloudflare for Teams client delivers that protection wherever they are.
The Secure Web Gateway foundation laid by the Teams client and L7 firewall points toward integrations including antivirus scanning, CASB, and remote browser isolation, all performed at the Cloudflare edge.
Availability
The new capabilities are available today. The L7 firewall is offered in Gateway standalone, Teams Standard, and Teams Enterprise plans; setup starts by signing up for a Gateway account and following the onboarding directions.



