Skip to content
Merged
Show file tree
Hide file tree
Changes from 2 commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Original file line number Diff line number Diff line change
Expand Up @@ -3,18 +3,29 @@ pcx_content_type: concept
title: Clientless Web Isolation
sidebar:
order: 5

---

import { GlossaryTooltip, Render } from "~/components"
import { GlossaryTooltip, Render } from "~/components";

Clientless Web Isolation allows users to securely browse high risk or sensitive websites in a remote browser without having to install the Cloudflare WARP client on their device.

## Set up Clientless Web Isolation

<Render file="clientless-browser-isolation" />

3. To configure permissions, select **Manage**. You can add authentication methods and [rules](/cloudflare-one/policies/access/) to control who can access the remote browser.
3. To configure permissions, in **Setting** > **Browser Isolation**> select **Manage** next to Permissions. You can add authentication methods and [rules](/cloudflare-one/policies/access/) to control who can access the remote browser.

4. Under **Policies** > Access Policies > select **Create new policy**.

5. Name your policy and define who will have access to your isolated application. Refer to the [Access policy documentation](/cloudflare-one/policies/access/#actions) to construct your policy.

6. Select **Save**.

7. Under **Policies** > Access Policies > select **Select existing policies** and select the policy or policies you created in the previous step > select **Confirm**.

8. At the bottom of the page, select **Save**.

Your application will now be served in an isolated browser for users matching your policies.

## Filter DNS queries

Expand Down Expand Up @@ -121,33 +132,33 @@ If you want to isolate a website without Cloudflare WARP installed, you will nee
```html
<!DOCTYPE html>
<html>
<head>
<title>Redirecting website to a remote browser</title>
<script>
window.location.href =
"https://<your-team-name>.cloudflareaccess.com/browser/<URL>}";
</script>
<noscript>
<meta
http-equiv="refresh"
content="0; url=https://<your-team-name>.cloudflareaccess.com/browser/<URL>"
/>
</noscript>
</head>
<body>
<p>
This website is being redirected to a remote browser. Select
<a href="https://<your-team-name>.cloudflareaccess.com/browser/<URL>"
>here</a
>
if you are not automatically redirected.
</p>
</body>
<head>
<title>Redirecting website to a remote browser</title>
<script>
window.location.href =
"https://<your-team-name>.cloudflareaccess.com/browser/<URL>}";
</script>
<noscript>
<meta
http-equiv="refresh"
content="0; url=https://<your-team-name>.cloudflareaccess.com/browser/<URL>"
/>
</noscript>
</head>
<body>
<p>
This website is being redirected to a remote browser. Select
<a href="https://<your-team-name>.cloudflareaccess.com/browser/<URL>"
>here</a
>
if you are not automatically redirected.
</p>
</body>
</html>
```

## Troubleshooting

Review troubleshooting guidance related to Clientless Web Isolation.

- [Clientless Web Isolation is loading a blank screen on a Windows device](/cloudflare-one/faq/troubleshooting/#clientless-web-isolation-is-loading-with-a-blank-screen-on-a-windows-device)
- [Clientless Web Isolation is loading a blank screen on a Windows device](/cloudflare-one/faq/troubleshooting/#clientless-web-isolation-is-loading-with-a-blank-screen-on-a-windows-device)
Original file line number Diff line number Diff line change
Expand Up @@ -6,7 +6,7 @@ sidebar:
label: Get started
---

Browser Isolation is enabled through Secure Web Gateway HTTP policies. By default, no traffic is isolated until you have added an Isolate policy to your HTTP policies.
Browser Isolation is enabled through [Secure Web Gateway HTTP policies](/cloudflare-one/policies/gateway/http-policies/). By default, no traffic is isolated until you have added an Isolate policy to your HTTP policies.

## 1. Connect devices to Cloudflare

Expand Down