From consumer WARP to enterprise client

Cloudflare has taken Cloudflare WARP for desktop out of beta and into general availability, and is extending the same client application to security teams through Cloudflare for Teams. The WARP app can now connect corporate desktops to Cloudflare Gateway, bringing advanced web filtering to the connection. Filtering rides on the same performance and security properties of the underlying WARP technology.

Teams organizations get a way to protect users wherever they are without backhauling traffic to a centralized security boundary. The WARP client sends remote users' traffic through a nearby Cloudflare data center, and Gateway administrators apply policies to the outbound Internet traffic proxied by that client — guarding against Internet threats and against corporate data leaving the organization.

BoringTun, 1.1.1.1 and the privacy model

WARP runs on Cloudflare's own WireGuard implementation, BoringTun, which encrypts all device traffic and sends it directly to Cloudflare's edge so nobody in between can snoop. Content from sites already on Cloudflare is sent straight down to the device. The WARP+ tier applies Argo Smart Routing to pick the shortest path across Cloudflare's global data center network.

1.1.1.1, the fastest public DNS resolver per dnsperf.com, sits underneath WARP: because nearly everything online begins with a DNS request, the resolver speeds up much of what users do. DNS lookups themselves were historically unencrypted, leaving them visible to parties such as an ISP; using DNS-over-HTTPS or DNS-over-TLS to 1.1.1.1 puts those requests on a secure channel. Cloudflare states it will never snoop on or sell personal data, and earlier this year published the results of a third-party privacy examination of the 1.1.1.1 public resolver.

For Gateway customers, Cloudflare says it will not sell personal data to third parties or use it to retarget users with advertisements. Administrators can audit organizational traffic, set data retention rules and define where users may go.

Replacing the VPN model

Traditional VPNs gate corporate access and enforce filtering rules, but they scale poorly: organizations must manage and grow on-premises VPN servers as traffic rises, servers are overwhelmed at peak times, clients are bulky and rarely built for performance, and a single intrusion exposes everything.

Cloudflare for Teams launched in January 2020 as a replacement. Cloudflare Access is a Zero Trust solution that connects internal and SaaS applications to Cloudflare's edge with rules enforcing safe access, so users can work from anywhere. Cloudflare Gateway's first features covered DNS-based protection with a policy engine built for enterprises.

WARP clients, already used by millions on mobile, enable new use cases for security teams:

  • Encrypted user traffic — traffic is encrypted with WARP and sent privately to the nearest endpoint regardless of location; a traditional VPN on top of Access for encryption is no longer necessary.
  • WARP+ for Teams — Teams customers deploying the Teams client applications automatically receive the premium WARP+ speed benefits.
  • Policy for remote workers — Gateway previously required tracking users' IP addresses and building per-location policies; with the client installed, policies apply anywhere.
  • L7 firewall and user-based policies — the Gateway SWG and Secure DNS announcement lets organizations enforce device authentication to their Teams account, build user-specific policies and force all traffic through the firewall.
  • Device and user auditing — administrators can audit specific user and device traffic; combined with logpush, this supports detailed tracing during a breach or audit.

Deployment paths

Setup starts at the sign-up page; existing accounts go straight to the Cloudflare for Teams dashboard onboarding flow. After configuring the team, administrators set up a Gateway policy and choose one of three installation methods.

Self install

Small organizations without an IT department can have users download the client and enter the required settings themselves — the fastest route.

Introducing WARP for Desktop and Cloudflare for Teams Embedded Image - KT8xXs

Scripted install

The desktop installers can be scripted for quick deployment. On Windows, this takes a single command line:

Cloudflare_WARP_Release-x64.msi /quiet ORGANIZATION="<insert your org>" SERVICE_MODE="warp" ENABLE="true" GATEWAY_UNIQUE_ID="<insert your gateway DoH domain>" SUPPORT_URL=”<mailto or http of your support person>"

Managed devices

Organizations with MDM tools such as Intune or JAMF can deploy WARP to their whole fleet in one operation and preconfigure it like any other device setting; end users then just log in with the team's identity provider by clicking the Cloudflare WARP client.

Introducing WARP for Desktop and Cloudflare for Teams Embedded Image - uo3RGj

Full installation options, required fields and step-by-step instructions for all platforms are in the WARP Client documentation.

What's next

  • Partner integrations with CrowdStrike and VMware Carbon Black (Tanium is available today) will support Cloudflare Access policies that check device health before granting application access.
  • Split Tunnel support will let organizations exclude chosen applications, sites or IP addresses — games, streaming services or anything else — from the WARP connection.

Desktop downloads are available at https://one.one.one.one.