diff --git a/src/content/docs/cloudflare-one/connections/connect-devices/warp/configure-warp/warp-modes/index.mdx b/src/content/docs/cloudflare-one/connections/connect-devices/warp/configure-warp/warp-modes/index.mdx index 5cc5f3d503acba4..0154482d0864044 100644 --- a/src/content/docs/cloudflare-one/connections/connect-devices/warp/configure-warp/warp-modes/index.mdx +++ b/src/content/docs/cloudflare-one/connections/connect-devices/warp/configure-warp/warp-modes/index.mdx @@ -11,25 +11,25 @@ You can deploy the WARP client in different modes to control the types of traffi This mode is best suited for organizations that want to use advanced firewall/proxy functionalities and enforce device posture rules. -| DNS filtering | HTTP filtering | Features enabled | -| ------------- | -------------- | ------------------------------------------------------------------------------------------------------------------------------------- | -| Yes | Yes | DNS policies, HTTP policies, Browser Isolation, identity-based policies, device posture checks, AV scanning, and Data Loss Prevention | +| DNS filtering | Network filtering | HTTP filtering | Features enabled | +| ------------- | ----------------- | -------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------- | +| Yes | Yes | Yes | DNS policies, network policies, HTTP policies, Browser Isolation, identity-based policies, device posture checks, AV scanning, and Data Loss Prevention | ## Gateway with DoH This mode is best suited for organizations that only want to apply DNS filtering to outbound traffic from their company devices. Network and HTTP traffic is handled by the default mechanisms on your devices. -| DNS filtering | HTTP filtering | Features enabled | -| ------------- | -------------- | ---------------- | -| Yes | No | DNS policies | +| DNS filtering | Network filtering | HTTP filtering | Features enabled | +| ------------- | ----------------- | -------------- | ---------------- | +| Yes | No | No | DNS policies | ## Secure Web Gateway without DNS filtering This mode is best suited for organizations that want to proxy network and HTTP traffic but keep their existing DNS filtering software. DNS traffic is handled by the default mechanism on your device. -| DNS filtering | HTTP filtering | Features enabled | -| ------------- | -------------- | ----------------------------------------------------------------------------------------------------------------------- | -| No | Yes | HTTP policies, Browser Isolation, identity-based policies, device posture checks, AV scanning, and Data Loss Prevention | +| DNS filtering | Network filtering | HTTP filtering | Features enabled | +| ------------- | ----------------- | -------------- | ----------------------------------------------------------------------------------------------------------------------------------------- | +| No | Yes | Yes | Network policies, HTTP policies, Browser Isolation, identity-based policies, device posture checks, AV scanning, and Data Loss Prevention | :::note @@ -42,9 +42,9 @@ This mode is best suited for organizations that want to proxy network and HTTP t Proxy mode is best suited for organizations that want to filter traffic directed to specific applications. -| DNS filtering | HTTP filtering | Features enabled | -| ------------- | -------------- | ----------------------------------------------------------------------------------------------------------------------------------------- | -| No | Yes | HTTP policies, Browser Isolation, identity-based policies, AV scanning, and Data Loss Prevention for traffic sent through localhost proxy | +| DNS filtering | Network filtering | HTTP filtering | Features enabled | +| ------------- | ----------------- | -------------- | ----------------------------------------------------------------------------------------------------------------------------------------- | +| No | No | Yes | HTTP policies, Browser Isolation, identity-based policies, AV scanning, and Data Loss Prevention for traffic sent through localhost proxy | :::note @@ -58,6 +58,6 @@ Proxy mode is best suited for organizations that want to filter traffic directed This mode is best suited for organizations that only want to enforce [WARP client device posture checks](/cloudflare-one/identity/devices/warp-client-checks/) for zones in your account. DNS, Network and HTTP traffic is handled by the default mechanisms on your devices. To setup Device Information Only mode, refer to the [dedicated page](/cloudflare-one/connections/connect-devices/warp/configure-warp/warp-modes/device-information-only/). -| DNS filtering | HTTP filtering | Features enabled | -| ------------- | -------------- | --------------------------------------------------------------------------- | -| No | No | Device posture rules in [Access policies](/cloudflare-one/policies/access/) | +| DNS filtering | Network filtering | HTTP filtering | Features enabled | +| ------------- | ----------------- | -------------- | --------------------------------------------------------------------------- | +| No | No | No | Device posture rules in [Access policies](/cloudflare-one/policies/access/) |