Skip to content

Commit c43132b

Browse files
authored
[CF1] IA revamp: update branding (#26200)
* revert cloudflare one organization * ZT--> CF1
1 parent 7ab1c2a commit c43132b

File tree

10 files changed

+29
-30
lines changed

10 files changed

+29
-30
lines changed

src/content/docs/cloudflare-one/index.mdx

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -1,13 +1,13 @@
11
---
2-
title: Cloudflare Zero Trust
2+
title: Cloudflare One
33

44
pcx_content_type: overview
55
sidebar:
66
order: 1
77
head:
88
- tag: title
99
content: Overview
10-
description: Learn how to secure self-hosted and SaaS applications with Cloudflare Zero Trust. Configure a unified dashboard for seamless access and security.
10+
description: Learn how to secure self-hosted and SaaS applications with Cloudflare One. Configure a unified dashboard for seamless access and security.
1111
---
1212

1313
import {
@@ -25,13 +25,13 @@ import {
2525

2626
<Description>
2727

28-
Secure your organization with Cloudflare Zero Trust — a cloud security model that replaces legacy perimeters with Cloudflares global network.
28+
Secure your organization with Cloudflare One — a cloud security platform that replaces legacy perimeters with Cloudflare's global network.
2929

3030
</Description>
3131

3232
<Plan type="all" />
3333

34-
Cloudflare Zero Trust is part of Cloudflare One, our name for the Secure Access Service Edge (SASE) platform that protects enterprise applications, users, devices, and networks.
34+
Cloudflare One is a Secure Access Service Edge (SASE) platform that combines Zero Trust security and enterprise networking services.
3535

3636
By progressively adopting Cloudflare One, organizations can move away from a patchwork of hardware appliances and point solutions, and instead consolidate security and networking through a unified control plane that includes products like [Cloudflare Access](/cloudflare-one/access-controls/policies/), [Secure Web Gateway (SWG)](/cloudflare-one/traffic-policies/), [Cloudflare Tunnel](/cloudflare-one/networks/connectors/cloudflare-tunnel/), [Data Loss Prevention (DLP)](/cloudflare-one/data-loss-prevention/), [Remote Browser Isolation (RBI)](/cloudflare-one/remote-browser-isolation/), [Cloud Access Security Broker (CASB)](/cloudflare-one/integrations/cloud-and-saas/), and [Email security](/cloudflare-one/email-security/).
3737

@@ -47,7 +47,7 @@ Refer to our [SASE reference architecture](/reference-architecture/architectures
4747
Get started
4848
</LinkButton>
4949
<LinkButton variant="secondary" href="https://one.dash.cloudflare.com/">
50-
Zero Trust dashboard
50+
Cloudflare One dashboard
5151
</LinkButton>
5252
<LinkButton variant="primary" href="/cloudflare-one/implementation-guides/">
5353
Implementation guides
@@ -63,7 +63,7 @@ Authenticate users accessing your applications, seamlessly onboard third-party u
6363

6464
<RelatedProduct header="Cloudflare Tunnel" href="/cloudflare-one/networks/connectors/cloudflare-tunnel/" product="zero-trust-networks">
6565

66-
Securely connect your resources to Cloudflare without exposing a public IP by using Cloudflare Tunnel, which establishes outbound-only connections from your infrastructure to Cloudflares global network via the lightweight `cloudflared` daemon.
66+
Securely connect your resources to Cloudflare without exposing a public IP by using Cloudflare Tunnel, which establishes outbound-only connections from your infrastructure to Cloudflare's global network via the lightweight `cloudflared` daemon.
6767

6868
</RelatedProduct>
6969

src/content/docs/cloudflare-one/insights/analytics-overview.mdx

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -11,7 +11,7 @@ To view the Analytics overview, log into [Cloudflare One](https://one.dash.cloud
1111

1212
The Analytics overview includes reports and insights across the following products and categories:
1313

14-
- [Global status](#global-status) of your Cloudflare One organization
14+
- [Global status](#global-status) of your Zero Trust Organization
1515
- [Access](#access)
1616
- Gateway
1717
- [HTTP traffic](#proxy-traffic)
@@ -30,7 +30,7 @@ In **Global status**, you can view a report on your organization's Cloudflare On
3030
- SaaS integrations
3131
- DLP profiles
3232

33-
You can also view a report on your [seat usage](/cloudflare-one/team-and-resources/users/seat-management/) across your Cloudflare One organization that contains the following metrics:
33+
You can also view a report on your [seat usage](/cloudflare-one/team-and-resources/users/seat-management/) across your Zero Trust Organization that contains the following metrics:
3434

3535
- Total seats
3636
- Used seats

src/content/docs/cloudflare-one/integrations/identity-providers/adfs.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -190,7 +190,7 @@ To enable Cloudflare One to accept the claims and assertions sent from AD FS, fo
190190

191191
This is the default location. You can find your federation service identifier in AD FS.
192192

193-
6. In the **IdP Entity ID or Issuer URL** field, enter your Cloudflare One team domain and include this callback at the end of the path: `/cdn-cgi/access/callback`. For example:
193+
6. In the **IdP Entity ID or Issuer URL** field, enter your Cloudflare Zero Trust team domain and include this callback at the end of the path: `/cdn-cgi/access/callback`. For example:
194194

195195
```txt
196196
https://<your-team-name>.cloudflareaccess.com/cdn-cgi/access/callback

src/content/docs/cloudflare-one/integrations/identity-providers/okta.mdx

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -12,7 +12,7 @@ Additionally, you can configure Okta to use risk information from Cloudflare One
1212

1313
## Prerequisites
1414

15-
- A [Cloudflare One organization](/cloudflare-one/setup/) with any subscription tier (including Free)
15+
- A [Zero Trust Organization](/cloudflare-one/setup/) with any subscription tier (including Free)
1616
- A [Cloudflare One administrator role](/cloudflare-one/roles-permissions/) with `Access Edit` permissions
1717

1818
## Supported features
@@ -30,7 +30,7 @@ To set up the Okta integration using the Okta Integration Network (OIN) App Cata
3030
4. Search for `Cloudflare` and select the **Cloudflare One** app.
3131
5. Select **Add integration**.
3232
6. In **Application label**, enter a name for the application (for example, `Cloudflare Access`).
33-
7. In **Team domain**, enter your Cloudflare One team domain:
33+
7. In **Team domain**, enter your Cloudflare Zero Trust team domain:
3434

3535
```txt
3636
<your-team-name>.cloudflareaccess.com

src/content/docs/cloudflare-one/setup.mdx

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ sidebar:
77

88
import { Render } from "~/components";
99

10-
This guide covers the recommended steps to start securing your users and devices with Cloudflare One.
10+
This guide covers the recommended steps to start securing your users and devices with Cloudflare Zero Trust.
1111

1212
:::note
1313

@@ -18,26 +18,26 @@ To get started with a specific use case, refer to our [implementation guides](/c
1818

1919
Sign up for a [Cloudflare account](https://dash.cloudflare.com/sign-up).
2020

21-
## Create a Cloudflare One organization
21+
## Create a Zero Trust Organization
2222

2323
<Render file="choose-team-name" product="cloudflare-one" />
2424

25-
Welcome to Cloudflare One! You can now explore a list of one-click actions we have designed to help you kickstart your Cloudflare One experience.
25+
Welcome to Cloudflare Zero Trust! You can now explore a list of one-click actions we have designed to help you kickstart your experience.
2626

2727
## Install the WARP client on your devices
2828

2929
If you want to enable security features such as Browser Isolation, HTTP filtering, AV scanning, and device posture, or connect networks to Cloudflare, here are the next steps you need to take:
3030

31-
1. **Set up a login method.** Configure [One-time PIN](/cloudflare-one/integrations/identity-providers/one-time-pin/) or connect a [third-party identity provider](/cloudflare-one/integrations/identity-providers/) in Cloudflare One. This is the login method your users will utilize when authenticating to add a new device to your Cloudflare One setup.
31+
1. **Set up a login method.** Configure [One-time PIN](/cloudflare-one/integrations/identity-providers/one-time-pin/) or connect a [third-party identity provider](/cloudflare-one/integrations/identity-providers/) in Cloudflare Zero Trust. This is the login method your users will utilize when authenticating to add a new device to your Cloudflare Zero Trust setup.
3232

33-
2. **Next, define [device enrollment permissions](/cloudflare-one/team-and-resources/devices/warp/deployment/device-enrollment/)**. Create device enrollment rules to define which users in your organization should be able to connect devices to your organization's Cloudflare One setup. As you create your rule, you will be asked to select which login method you would like users to authenticate with.
33+
2. **Next, define [device enrollment permissions](/cloudflare-one/team-and-resources/devices/warp/deployment/device-enrollment/)**. Create device enrollment rules to define which users in your organization should be able to connect devices to your organization's Cloudflare Zero Trust setup. As you create your rule, you will be asked to select which login method you would like users to authenticate with.
3434

3535
3. **Install the [Cloudflare root certificate](/cloudflare-one/team-and-resources/devices/user-side-certificates/) on your devices.** Advanced security features including HTTP traffic inspection require users to install and trust the Cloudflare root certificate on their machine or device. If you are installing certificates manually on all your devices, these steps will need to be performed on each new device that is to be subject to HTTP filtering.
3636

3737
4. **[Download](/cloudflare-one/team-and-resources/devices/warp/download-warp/) and deploy the WARP client to your devices**. Choose one of the [different ways](/cloudflare-one/team-and-resources/devices/warp/deployment/) to deploy the WARP client, depending on what works best for your organization.
3838

39-
5. **Log in to your organization's Cloudflare One instance from your devices**. On your device, go to the Settings section in the WARP client and insert your organization's team name.
39+
5. **Log in to your organization's Cloudflare Zero Trust instance from your devices**. On your device, go to the Settings section in the WARP client and insert your organization's team name.
4040

41-
Your devices are now connected to Cloudflare One through the WARP client. You can go to **Team & Resources** > **Devices** to find a list of your enrolled devices, when they were last seen, and the WARP client version they are running.
41+
Your devices are now connected to Cloudflare Zero Trust through the WARP client. You can go to **Team & Resources** > **Devices** to find a list of your enrolled devices, when they were last seen, and the WARP client version they are running.
4242

4343
Next, [enforce security policies](/cloudflare-one/traffic-policies/) on your traffic and access requests.

src/content/docs/cloudflare-one/team-and-resources/devices/warp/deployment/mdm-deployment/protocol-handler.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -50,7 +50,7 @@ You can configure your browser to automatically launch the Cloudflare WARP appli
5050

5151
### Chromium-based browsers
5252

53-
Chromium-based browsers such as Google Chrome and Microsoft Edge have a policy setting called [AutoLaunchProtocolsFromOrigins](https://learn.microsoft.com/en-us/DeployEdge/microsoft-edge-policies#autolaunchprotocolsfromorigins). This setting takes in two parameters: a protocol for the browser to launch and the origins that are allowed to launch it. For the browser to launch WARP, you need to set the protocol to `com.cloudflare.warp` and the origin to your <GlossaryTooltip term="team domain">Zero Trust team domain</GlossaryTooltip> (`https://<your-team-name>.cloudflareaccess.com`).
53+
Chromium-based browsers such as Google Chrome and Microsoft Edge have a policy setting called [AutoLaunchProtocolsFromOrigins](https://learn.microsoft.com/en-us/DeployEdge/microsoft-edge-policies#autolaunchprotocolsfromorigins). This setting takes in two parameters: a protocol for the browser to launch and the origins that are allowed to launch it. For the browser to launch WARP, you need to set the protocol to `com.cloudflare.warp` and the origin to your <GlossaryTooltip term="team domain">Cloudflare Zero Trust team domain</GlossaryTooltip> (`https://<your-team-name>.cloudflareaccess.com`).
5454

5555
<Tabs>
5656
<TabItem label="Windows">

src/content/docs/cloudflare-one/team-and-resources/users/seat-management.mdx

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -29,7 +29,7 @@ To check the number of seats consumed by active users in your organization, log
2929

3030
When you revoke a user, this action will terminate active sessions, but will not remove the user's consumption of an active seat.
3131

32-
To revoke a user from your Cloudflare One organization:
32+
To revoke a user from your Zero Trust Organization:
3333

3434
1. In [Cloudflare One](https://one.dash.cloudflare.com), go to **Team & Resources** > **Users**.
3535
2. Select the checkbox next to a user with an **Active** status in the **Seat usage** column.
@@ -40,9 +40,9 @@ Revoked users can still log in if your policies allow them.
4040

4141
### Remove a user
4242

43-
Removing a user from your Cloudflare One organization will free up the seat the user consumed. The user will still appear in your list of users.
43+
Removing a user from your Zero Trust Organization will free up the seat the user consumed. The user will still appear in your list of users.
4444

45-
To remove a user from your Cloudflare One organization:
45+
To remove a user from your Zero Trust Organization:
4646

4747
1. In [Cloudflare One](https://one.dash.cloudflare.com), go to **Team & Resources** > **Users**.
4848
2. Select the checkbox next to a user with an **Active** status in the **Seat usage** column.
@@ -54,7 +54,7 @@ The user will now show as **Inactive** and will no longer occupy a seat. If a us
5454
To automate the removal of users who have not logged in or triggered a device enrollment in a specific amount of time, turn on [seat expiration](#enable-seat-expiration).
5555

5656
:::note[User record persistence]
57-
You cannot delete or archive a user record. You can [remove a user](#remove-a-user) from a seat, but their user record will remain in your Cloudflare One organization. Inactive users do not count towards billing.
57+
You cannot delete or archive a user record. You can [remove a user](#remove-a-user) from a seat, but their user record will remain in your Zero Trust Organization. Inactive users do not count towards billing.
5858
:::
5959

6060
### Enable seat expiration

src/content/glossary/cloudflare-one.yaml

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -47,7 +47,7 @@ entries:
4747
4848
- term: Cloudflare DEX
4949
general_definition: |-
50-
Cloudflare Digital Experience Monitoring (DEX) provides visibility into device, network, and application performance across your Cloudflare One organization.
50+
Cloudflare Digital Experience Monitoring (DEX) provides visibility into device, network, and application performance across your Zero Trust Organization.
5151
5252
- term: Cloudflare Gateway
5353
general_definition: |-
@@ -101,7 +101,7 @@ entries:
101101

102102
- term: fleet
103103
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 One organization](/cloudflare-one/setup/#create-a-cloudflare-one-organization).
104+
a fleet is a collection of user devices. All devices in a fleet have WARP installed and are connected to a [Zero Trust Organization](/cloudflare-one/setup/#create-a-zero-trust-organization).
105105
106106
- term: identity provider
107107
general_definition: |-

src/content/partials/cloudflare-one/choose-team-name.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
import { GlossaryTooltip, DashButton } from "~/components";
22

3-
1. In the [Cloudflare dashboard](https://dash.cloudflare.com/), select **Cloudflare One**.
3+
1. In the [Cloudflare dashboard](https://dash.cloudflare.com/), select **Zero Trust**.
44

55
<DashButton url="https://one.dash.cloudflare.com" />
66

Lines changed: 3 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,14 +1,13 @@
1-
name: Cloudflare Zero Trust
1+
name: Cloudflare One
22

33
product:
4-
title: Cloudflare Zero Trust
4+
title: Cloudflare One
55
url: /cloudflare-one/
66
group: Cloudflare One
77
wrap: true
88
preview_tryout: true
99

1010
meta:
11-
title: Cloudflare Zero Trust docs
11+
title: Cloudflare One docs
1212
description: Replace legacy security perimeters with Cloudflare's network to protect your organization
1313
author: "@cloudflare"
14-

0 commit comments

Comments
 (0)