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/remote-browser-isolation/setup/non-identity.mdx
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -19,6 +19,6 @@ If you want to apply Isolate policies based on user identity, you will need to e
19
19
- Configure your browser to forward traffic to a Gateway proxy endpoint with [PAC files](/cloudflare-one/team-and-resources/devices/agentless/pac-files/).
20
20
- Connect your enterprise site router to Gateway with the [anycast GRE or IPsec tunnel on-ramp to Magic WAN](/magic-wan/zero-trust/cloudflare-gateway/).
21
21
3. Enable non-identity browser isolation:
22
-
1. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Browser isolation** > *Browser isolation settings**.
23
-
2. Turn on **Non-identity on-ramp support**.
22
+
1. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Browser isolation** > **Browser isolation settings**.
23
+
2. Turn on **Allow isolated HTTP traffic when user identity is unknown**.
24
24
4. Build a non-identity [HTTP policy](/cloudflare-one/remote-browser-isolation/isolation-policies/) to isolate websites in a remote browser.
Copy file name to clipboardExpand all lines: src/content/docs/cloudflare-one/traffic-policies/http-policies/file-sandboxing.mdx
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -49,8 +49,8 @@ flowchart TD
49
49
50
50
To begin quarantining downloaded files, turn on file sandboxing:
51
51
52
-
1. In [Zero Trust](https://one.dash.cloudflare.com), go to **Settings** > **Network**.
53
-
2.In **Firewall**, turn on **File sandboxing**.
52
+
1. In [Zero Trust](https://one.dash.cloudflare.com), go to **Traffic policies** > **Traffic settings**.
53
+
2.Turn on **File sandboxing**.
54
54
3. (Optional) To block requests containing [non-scannable files](#non-scannable-files), select **Block requests for files that cannot be scanned**.
55
55
56
56
You can now create [Quarantine HTTP policies](/cloudflare-one/traffic-policies/http-policies/#quarantine) to determine what files to scan in the sandbox.
Copy file name to clipboardExpand all lines: src/content/glossary/cloudflare-one.yaml
+12-12Lines changed: 12 additions & 12 deletions
Original file line number
Diff line number
Diff line change
@@ -3,11 +3,11 @@ productName: Cloudflare One
3
3
entries:
4
4
- term: App Launcher
5
5
general_definition: |-
6
-
the App Launcher portal provides end users with a single dashboard to open applications secured by Cloudflare Zero Trust.
6
+
the App Launcher portal provides end users with a single dashboard to open applications secured by Cloudflare One.
7
7
8
8
- term: application
9
9
general_definition: |-
10
-
the resource protected by Cloudflare Zero Trust, which can be a subdomain, a path, or a SaaS application.
10
+
the resource protected by Cloudflare One, which can be a subdomain, a path, or a SaaS application.
11
11
12
12
- term: application token
13
13
general_definition: |-
@@ -19,7 +19,7 @@ entries:
19
19
20
20
- term: CGNAT IP
21
21
general_definition: |-
22
-
a unique, virtual IP address assigned to each WARP device from the `100.96.0.0/12` range. You can view the CGNAT IP for a device in **My Team** > **Devices** > **Virtual IPv4/IPv6**.
22
+
a unique, virtual IP address assigned to each WARP device from the `100.96.0.0/12` range. You can view the CGNAT IP for a device in **Team & Resources** > **Devices** > **Virtual IPv4/IPv6**.
23
23
24
24
- term: cloudflared
25
25
general_definition: |-
@@ -47,7 +47,7 @@ entries:
47
47
48
48
- term: Cloudflare DEX
49
49
general_definition: |-
50
-
Cloudflare Digital Experience Monitoring (DEX) provides visibility into device, network, and application performance across your Zero Trust organization.
50
+
Cloudflare Digital Experience Monitoring (DEX) provides visibility into device, network, and application performance across your Cloudflare One organization.
51
51
52
52
- term: Cloudflare Gateway
53
53
general_definition: |-
@@ -91,7 +91,7 @@ entries:
91
91
92
92
- term: DoH subdomain
93
93
general_definition: |-
94
-
a unique DoH subdomain for each DNS location in Cloudflare Zero Trust used in WARP client settings.
94
+
a unique DoH subdomain for each DNS location in Cloudflare One used in WARP client settings.
95
95
96
96
- term: DNS location
97
97
general_definition: |-
@@ -101,7 +101,7 @@ entries:
101
101
102
102
- term: fleet
103
103
general_definition: |-
104
-
a fleet is a collection of user devices. All devices in a fleet have WARP installed and are connected to a [Cloudflare Zero Trust organization](/cloudflare-one/setup/#create-a-zero-trust-organization).
104
+
a fleet is a collection of user devices. All devices in a fleet have WARP installed and are connected to a [Cloudflare One organization](/cloudflare-one/setup/#create-a-cloudflare-one-organization).
105
105
106
106
- term: identity provider
107
107
general_definition: |-
@@ -133,7 +133,7 @@ entries:
133
133
134
134
- term: MCP server portal
135
135
general_definition: |-
136
-
a web application in Cloudflare Zero Trust that serves as a gateway to multiple MCP servers.
136
+
a web application in Cloudflare One that serves as a gateway to multiple MCP servers.
137
137
138
138
- term: MCP server tool
139
139
general_definition: |-
@@ -169,7 +169,7 @@ entries:
169
169
170
170
- term: remotely-managed tunnel
171
171
general_definition: |-
172
-
a Cloudflare Tunnel that was created in Zero Trust under **Networks** > **Tunnels**. Tunnel configuration is stored in Cloudflare, which allows you to manage the tunnel from the dashboard or using the API.
172
+
a Cloudflare Tunnel whose configuration is stored on Cloudflare rather than on your local machine. You can manage the tunnel in the dashboard under **Networks** > **Connectors** or by using the API.
173
173
174
174
- term: RDP
175
175
general_definition: |-
@@ -241,11 +241,11 @@ entries:
241
241
242
242
- term: team domain
243
243
general_definition: |-
244
-
a unique subdomain assigned to your Cloudflare account (for example, `<your-team-name>.cloudflareaccess.com`), where users will find the apps you have secured behind Cloudflare Zero Trust.
244
+
a unique subdomain assigned to your Cloudflare account (for example, `<your-team-name>.cloudflareaccess.com`), where users will find the apps you have secured behind Cloudflare One.
245
245
246
246
- term: team name
247
247
general_definition: |-
248
-
the customizable portion of your team domain (`<your-team-name>.cloudflareaccess.com`). You can view your team name in Zero Trust under **Settings** > **Custom Pages**.
248
+
the customizable portion of your team domain (`<your-team-name>.cloudflareaccess.com`). You can view your team name in Cloudflare One under **Settings**.
249
249
250
250
- term: Terraform
251
251
general_definition: |-
@@ -259,11 +259,11 @@ entries:
259
259
260
260
- term: User risk score
261
261
general_definition: |-
262
-
Cloudflare Zero Trust user risk score ranks the likelihood of a user to introduce risk to your organization's systems and data based on the detection of security risk behaviors. Risk scores add user and entity behavior analytics (UEBA) to the Zero Trust platform.
262
+
User risk score ranks the likelihood of a user to introduce risk to your organization's systems and data based on the detection of security risk behaviors. Risk scores add user and entity behavior analytics (UEBA) to the Cloudflare One platform.
263
263
264
264
- term: User risk score level
265
265
general_definition: |-
266
-
Cloudflare Zero Trust assigns a risk score of Low, Medium or High based on detections of users' activities, posture, and settings. A user's risk score is equal to the highest-level risk behavior they trigger.
266
+
Cloudflare One assigns a risk score of Low, Medium or High based on detections of users' activities, posture, and settings. A user's risk score is equal to the highest-level risk behavior they trigger.
0 commit comments