Cloudflare Docs
Learning Paths
Cloudflare Docs
Secure your Internet traffic and SaaS apps (Learning Path)
Edit this page
Give us feedback
Set theme to dark (⇧+D)
  1. Learning Paths
  2. Secure your Internet traffic and SaaS apps
  3. Build HTTP security policies
  4. Configure Browser Isolation

Configure Browser Isolation

  4 min read

Cloudflare Browser Isolation seamlessly executes active webpage content in a secure isolated browser to protect users from zero-day attacks, malware, and phishing.

Browser Isolation provides unique and transparent protection for your users using methods that surpass the capabilities of a traditional secure web gateway. This section focuses primarily on Browser Isolation for external services, assuming that most traffic from a device or a network is being forwarded to Cloudflare. For other applications of Browser Isolation, refer to the Zero Trust Web Access (ZTWA) learning path.

As a note, Cloudflare’s Browser Isolation technology was built to be used for 100% of your user’s daily browsing. These recommendations do not suggest that you should limit or be cautious with your use of Browser Isolation, but instead help identify practical outcomes that balance technology with actualized security benefits.

​​ Get the most out of Browser Isolation

If your organization is interested in implementing Browser Isolation, there are a few methods that Cloudflare recommends exploring.

​​ Block copy, paste, and upload/download for shadow IT

As you have begun deploying Cloudflare Zero Trust, you may have started to visualize user traffic patterns using Shadow IT Discovery. This feature gives you visibility into detected SaaS applications that your users use. Administrators can categorize applications and services on the basis of proper organizational use. If you do not use Shadow IT Discovery and instead maintain a similar list manually or with other tools, you can port that data into a Zero Trust list, update it via the API, and achieve the same outcomes.

You can control potential risk and shape user behavior without applying heavy-handed block policies by applying policies to isolate user traffic to applications that match your defined categories. You can then set additional parameters in the policy, such as the ability to restrict copy/paste and upload/download. Users can still access information in the tools – if not use the tools to a lesser extent – while you minimize the risk of data loss.

  1. In Zero Trust, go to Gateway > Firewall Policies.

  2. In the HTTP tab, select Add a policy.

  3. Name the policy.

  4. In Traffic, add the following expression:

    SelectorOperatorValueAction
    Hostin listShadow ITIsolate

  5. In Configure policy settings, turn on the following options:

    • Disable copy / paste
    • Disable file downloads
    • Disable file uploads

  6. Select Create policy.

curl --request POST \
    --url https://api.cloudflare.com/client/v4/accounts/{account_id}/gateway/rules \
    --header 'Content-Type: application/json' \
    --header 'X-Auth-Email: <EMAIL>' \
    --header 'X-Auth-Key: <API_KEY>' \
    --data '{
    "action": "isolate",
    "description": "Block copy, paste, and upload/download for shadow IT",
    "enabled": true,
    "filters": [
      "http"
    ],
    "name": "Block shadow IT interaction",
    "precedence": 0,
    "traffic": "http.request.host in <SHADOW_IT_LIST_UUID>",
    "rule_settings": {
      "block_page_enabled": false,
      "block_reason": "",
      "override_ips": null,
      "override_host": "",
      "l4override": null,
      "biso_admin_controls": {
        "dp": false,
        "dcp": true,
        "dd": true,
        "du": true,
        "dk": false,
        "dcr": false
      },
    }'

​​ Isolate all “gray-listed” traffic

A common method for using Browser Isolation to protect against unknown or zero-day threats can dramatically enhance your security posture: Separate all HTTP traffic into known acceptable, known malicious, and unknown buckets. Once your sort your traffic, isolate everything in the unknown bucket.

You can accomplish this by creating the following policies:

  • Explicit allow policies for all of your known applications and trusted websites using either Cloudflare application definitions or a list
  • Explicit block policies for all security risks, known malicious traffic, and against-acceptable-use intentional denies
  • A policy to isolate all other traffic in this middle

In this context, if some traffic is unknown to your organization, Cloudflare will isolate it by default. Cloudflare will also prevent any malicious code from being executed client side, with additional controls available.

  • Allow known applications and websites:

    SelectorOperatorValueAction
    Domainin listKnown DomainsAllow

  • Block security risks:

    SelectorOperatorValueAction
    Security RisksinAll Security RisksBlock

  • Isolate all other traffic:

    SelectorOperatorValueAction
    Hostmatches regex.*Isolate
Allow known applications and websites
curl --request POST \
    --url https://api.cloudflare.com/client/v4/accounts/{account_id}/gateway/rules \
    --header 'Content-Type: application/json' \
    --header 'X-Auth-Email: <EMAIL>' \
    --header 'X-Auth-Key: <API_KEY>' \
    --data '{
    "action": "isolate",
    "description": "Allow known applications and websites",
    "enabled": true,
    "filters": [
      "http"
    ],
    "name": "Allow known apps and sites",
    "precedence": 0,
    "traffic": "http.request.domains in <TRUSTED_DOMAINS_LIST_UUID>",
    "rule_settings": {
      "block_page_enabled": false,
      "block_reason": "",
      "override_ips": null,
      "override_host": "",
      "l4override": null
    }'

Block security risks
curl --request POST \
    --url https://api.cloudflare.com/client/v4/accounts/{account_id}/gateway/rules \
    --header 'Content-Type: application/json' \
    --header 'X-Auth-Email: <EMAIL>' \
    --header 'X-Auth-Key: <API_KEY>' \
    --data '{
    "action": "isolate",
    "description": "Block all security risks",
    "enabled": true,
    "filters": [
      "http"
    ],
    "name": "Block security risks",
    "precedence": 0,
    "traffic": "http.request.uri.security_category in {68 178 80 83 176 175 117 131 134 151 153}",
    "rule_settings": {
      "block_page_enabled": false,
      "block_reason": "",
      "override_ips": null,
      "override_host": "",
      "l4override": null
    }'

Isolate all other traffic
curl --request POST \
    --url https://api.cloudflare.com/client/v4/accounts/{account_id}/gateway/rules \
    --header 'Content-Type: application/json' \
    --header 'X-Auth-Email: <EMAIL>' \
    --header 'X-Auth-Key: <API_KEY>' \
    --data '{
    "action": "isolate",
    "description": "Isolate all other traffic",
    "enabled": true,
    "filters": [
      "http"
    ],
    "name": "Isolate traffic",
    "precedence": 0,
    "traffic": "http.request.host matches \".*\"",
    "rule_settings": {
      "block_page_enabled": false,
      "block_reason": "",
      "override_ips": null,
      "override_host": "",
      "l4override": null
    }'

Many vendors that may exist within your security framework support URL manipulation. You can use URL manipulation as an on-ramp for Browser Isolation to add additional security controls.

For example, vendors like Zscaler and Proofpoint allow you to prepend links to URLs in a static or dynamic format. You can prepend the clientless isolation link generated for your Cloudflare account to derive additional security benefits for potentially risky clicks. This means that if you have traffic not sent through Cloudflare today (such as through another proxy), you can potentially prepend specific filtered requests with a link to automatically send the traffic to a Cloudflare isolated browser session without an endpoint agent installed.




Previous Next