You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: src/content/docs/cloudflare-one/policies/browser-isolation/setup/clientless-browser-isolation.mdx
+37-26Lines changed: 37 additions & 26 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -3,18 +3,29 @@ pcx_content_type: concept
3
3
title: Clientless Web Isolation
4
4
sidebar:
5
5
order: 5
6
-
7
6
---
8
7
9
-
import { GlossaryTooltip, Render } from "~/components"
8
+
import { GlossaryTooltip, Render } from "~/components";
10
9
11
10
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.
12
11
13
12
## Set up Clientless Web Isolation
14
13
15
14
<Render file="clientless-browser-isolation" />
16
15
17
-
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.
16
+
3. To configure permissions, in **Settings** > **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.
17
+
18
+
4. Under **Policies** > Access Policies > select **Create new policy**.
19
+
20
+
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.
21
+
22
+
6. Select **Save**.
23
+
24
+
7. Under **Policies** > Access Policies > select **Select existing policies** and select the policy or policies you created in the previous step > select **Confirm**.
25
+
26
+
8. At the bottom of the page, select **Save**.
27
+
28
+
Your application will now be served in an isolated browser for users matching your policies.
18
29
19
30
## Filter DNS queries
20
31
@@ -121,33 +132,33 @@ If you want to isolate a website without Cloudflare WARP installed, you will nee
121
132
```html
122
133
<!DOCTYPE html>
123
134
<html>
124
-
<head>
125
-
<title>Redirecting website to a remote browser</title>
Review troubleshooting guidance related to Clientless Web Isolation.
152
163
153
-
- [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)
164
+
- [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)
Copy file name to clipboardExpand all lines: src/content/docs/cloudflare-one/policies/browser-isolation/setup/index.mdx
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,7 +6,7 @@ sidebar:
6
6
label: Get started
7
7
---
8
8
9
-
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.
9
+
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.
0 commit comments