Round 1 of updating ui copy

Oxyjun · Oxyjun · commit d0562904fa86 · 2025-10-27T16:23:31.000Z
diff --git a/src/content/docs/cloudflare-one/integrations/service-providers/custom.mdx b/src/content/docs/cloudflare-one/integrations/service-providers/custom.mdx
@@ -5,12 +5,12 @@ sidebar:
   label: Custom integration
   order: 1
 
-description: Configure custom device posture checks in Cloudflare Zero Trust using a service-to-service integration.
+description: Configure custom device posture checks in Cloudflare One using a service-to-service integration.
 ---
 
 import { Render } from "~/components";
 
-Cloudflare Zero Trust allows you to enforce custom device posture checks on your applications. This involves configuring a WARP service-to-service integration that periodically calls the external API of your choice, whether it is a third-party endpoint provider or a home built solution. When called, the API will receive device identifying information from Cloudflare and be expected to return a value between `0` to `100`. You can then set up a device posture check that determines if the returned value counts as a pass or fail; for example, you could allow access to a user only if their device has a posture value greater than `60`.
+Cloudflare One allows you to enforce custom device posture checks on your applications. This involves configuring a WARP service-to-service integration that periodically calls the external API of your choice, whether it is a third-party endpoint provider or a home built solution. When called, the API will receive device identifying information from Cloudflare and be expected to return a value between `0` to `100`. You can then set up a device posture check that determines if the returned value counts as a pass or fail; for example, you could allow access to a user only if their device has a posture value greater than `60`.
 
 ```mermaid
 sequenceDiagram
@@ -124,7 +124,7 @@ To create a custom service-to-service integration:
 
 5. In **Access client ID** and **Access client secret**, enter the Access service token used to authenticate to your external API.
 6. In **Rest API URL**, enter the external API endpoint that Cloudflare will query for posture information (for example, `https://api.example.com`). For more information, refer to [External API requirements](#external-api-requirements).
-7. In **Polling frequency**, choose how often Cloudflare Zero Trust should query the external API for information.
+7. In **Polling frequency**, choose how often Cloudflare One should query the external API for information.
 8. Select **Test and save**. The test checks if Cloudflare can authenticate to the API URL using the provided Access credentials.
 
 Next, [configure a device posture check](#4-configure-the-posture-check) to determine if a given posture score constitutes a pass or fail.
diff --git a/src/content/docs/cloudflare-one/integrations/service-providers/kolide.mdx b/src/content/docs/cloudflare-one/integrations/service-providers/kolide.mdx
@@ -44,7 +44,7 @@ import { Render } from "~/components";
 />
 
 5. Enter the **Client secret** you noted down above.
-6. Choose a **Polling frequency** for how often Cloudflare Zero Trust should query Kolide for information.
+6. Choose a **Polling frequency** for how often Cloudflare One should query Kolide for information.
 7. Select **Test and save**.
 
 ### 3. Configure the posture check
diff --git a/src/content/docs/cloudflare-one/integrations/service-providers/microsoft.mdx b/src/content/docs/cloudflare-one/integrations/service-providers/microsoft.mdx
@@ -60,7 +60,7 @@ To retrieve those values:
 />
 
 5. Enter the **Client ID**, **Client secret** and **Customer ID** as you noted down above.
-6. Select a **Polling frequency** for how often Cloudflare Zero Trust should query Microsoft Graph API for information.
+6. Select a **Polling frequency** for how often Cloudflare One should query Microsoft Graph API for information.
 7. Select **Test and save**.
 
 ## 3. Configure the posture check
diff --git a/src/content/docs/cloudflare-one/integrations/service-providers/sentinelone.mdx b/src/content/docs/cloudflare-one/integrations/service-providers/sentinelone.mdx
@@ -54,7 +54,7 @@ To retrieve those values:
 <Render file="posture/add-service-provider" params={{ provider: "SentinelOne" }} product="cloudflare-one"/>
 5. In **Client Secret**, enter your **API Token**.
 6. In **Rest API URL**, enter `https://<S1-DOMAIN>.sentinelone.net`.
-7. Choose a **Polling frequency** for how often Cloudflare Zero Trust should query SentinelOne for information.
+7. Choose a **Polling frequency** for how often Cloudflare One should query SentinelOne for information.
 8. Select **Test and save**.
 
 ### 3. Configure the posture check
diff --git a/src/content/docs/cloudflare-one/integrations/service-providers/taniums2s.mdx b/src/content/docs/cloudflare-one/integrations/service-providers/taniums2s.mdx
@@ -62,7 +62,7 @@ To retrieve the API URL, determine your Tanium Gateway root endpoint:
 />
 
 5. Enter the **Client Secret** and **REST API URL** you noted down above.
-6. Choose a **Polling frequency** for how often Cloudflare Zero Trust should query Tanium for information.
+6. Choose a **Polling frequency** for how often Cloudflare One should query Tanium for information.
 7. Select **Test and save**.
 
 ### 3. Configure the posture check
diff --git a/src/content/docs/cloudflare-one/integrations/service-providers/uptycs.mdx b/src/content/docs/cloudflare-one/integrations/service-providers/uptycs.mdx
@@ -48,7 +48,7 @@ To obtain these values:
 />
 
 5. Enter the **Client ID**, **Client secret** and **Customer ID** as you noted down above.
-6. Select a **Polling frequency** for how often Cloudflare Zero Trust should query Uptycs for information.
+6. Select a **Polling frequency** for how often Cloudflare One should query Uptycs for information.
 7. Select **Test and save**.
 
 ## 3. Configure the posture check
diff --git a/src/content/docs/cloudflare-one/integrations/service-providers/workspace-one.mdx b/src/content/docs/cloudflare-one/integrations/service-providers/workspace-one.mdx
@@ -57,7 +57,7 @@ To retrieve those values:
 />
 
 5. Enter the **Client ID** and **Client secret** you noted down above.
-6. Select a **Polling frequency** for how often Cloudflare Zero Trust should query Workspace ONE for information.
+6. Select a **Polling frequency** for how often Cloudflare One should query Workspace ONE for information.
 7. Enter the **Region-specific token URL** and **REST API URL** you noted down above.
 8. Select **Test and save**.
 
diff --git a/src/content/docs/cloudflare-one/reusable-components/posture-checks/access-integrations/mutual-tls-authentication.mdx b/src/content/docs/cloudflare-one/reusable-components/posture-checks/access-integrations/mutual-tls-authentication.mdx
@@ -45,7 +45,7 @@ The mTLS certificate is used only to verify the client certificate. It does not
 
 6. Save the policy.
 
-7. Go to **Access** > **Policies**.
+7. Go to **Access controls** > **Policies**.
 
 8. [Create an Access policy](/cloudflare-one/access-controls/policies/policy-management/#create-a-policy) using one of the following [selectors](/cloudflare-one/access-controls/policies/#selectors):
    - **Valid Certificate**: Any client certificate that can authenticate with the Root CA will be allowed to proceed.
@@ -63,7 +63,7 @@ The mTLS certificate is used only to verify the client certificate. It does not
 
    </Example>
 
-10. Save the policy, then go to **Access** > **Applications**.
+10. Save the policy, then go to **Access controls** > **Applications**.
 
 11. Select the application you would like to enforce mTLS on and select **Configure**. The application must be included in the **Associated hostnames** list from Step 5.
 
diff --git a/src/content/docs/cloudflare-one/reusable-components/posture-checks/access-integrations/tanium.mdx b/src/content/docs/cloudflare-one/reusable-components/posture-checks/access-integrations/tanium.mdx
@@ -44,9 +44,9 @@ The integration does not currently support Safari.
 
 1. Configure your Tanium deployment using the [step-by-step documentation](https://docs.tanium.com/endpoint_identity/endpoint_identity/userguide.html) provided. You will need the public key to integrate your Tanium deployment with Cloudflare Access.
 
-2. In [Zero Trust](https://one.dash.cloudflare.com), go to **Settings** > **WARP Client**.
+2. In [Cloudflare One](https://one.dash.cloudflare.com), go to **Reusable components** > **Posture checks**.
 
-3. Scroll down to **WARP client checks** and select **Add new**.
+3. Go to **WARP client checks** and select **Add a check**.
 
 4. Select **Tanium** from the list of providers.
 
diff --git a/src/content/docs/cloudflare-one/reusable-components/posture-checks/index.mdx b/src/content/docs/cloudflare-one/reusable-components/posture-checks/index.mdx
@@ -21,7 +21,7 @@ Setup instructions and requirements vary depending on the device posture attribu
 
 Before integrating a device posture check in a Gateway or Access policy, verify that the Pass/Fail results match your expectations. To view the latest test results for a specific device:
 
-1. In [Zero Trust](https://one.dash.cloudflare.com/), go to **My Team** > **Devices**.
+1. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Team & Resources** > **Devices**.
 2. Select the device.
 3. Select **View details**.
 4. Select the **Posture checks** tab.
diff --git a/src/content/docs/cloudflare-one/reusable-components/posture-checks/warp-client-checks/application-check.mdx b/src/content/docs/cloudflare-one/reusable-components/posture-checks/warp-client-checks/application-check.mdx
@@ -22,9 +22,9 @@ The Application Check device posture attribute checks that a specific applicatio
 
 ## Configure an application check
 
-1. In [Zero Trust](https://one.dash.cloudflare.com), go to **Settings** > **WARP Client**.
+1. In [Cloudflare One](https://one.dash.cloudflare.com), go to **Reusable components** > **Posture checks**.
 
-2. Scroll down to **WARP client checks** and select **Add new**.
+2. Go to **WARP client checks** and select **Add a check**.
 
 3. Select **Application Check**.
 
@@ -43,7 +43,7 @@ The Application Check device posture attribute checks that a specific applicatio
 
 7. Select **Save**.
 
-Next, go to **Logs** > **Posture** and verify that the application check is returning the expected results.
+Next, go to **Insights** > **Logs** > **Posture logs** and verify that the application check is returning the expected results.
 
 ## Determine the signing thumbprint
 
diff --git a/src/content/docs/cloudflare-one/reusable-components/posture-checks/warp-client-checks/carbon-black.mdx b/src/content/docs/cloudflare-one/reusable-components/posture-checks/warp-client-checks/carbon-black.mdx
@@ -7,7 +7,7 @@ sidebar:
 
 import { Render } from "~/components";
 
-Cloudflare Zero Trust can check if [Carbon Black](https://www.carbonblack.com/) is running on a device to determine if a request should be allowed to reach a protected resource.
+Cloudflare One can check if [Carbon Black](https://www.carbonblack.com/) is running on a device to determine if a request should be allowed to reach a protected resource.
 
 ## Prerequisites
 
@@ -23,9 +23,9 @@ Cloudflare Zero Trust can check if [Carbon Black](https://www.carbonblack.com/)
 
 ## Configure the Carbon Black check
 
-1. In [Zero Trust](https://one.dash.cloudflare.com), go to **Settings** > **WARP Client**.
+1. In [Cloudflare One](https://one.dash.cloudflare.com), go to **Reusable components** > **Posture checks**.
 
-2. Scroll down to **WARP client checks** and select **Add new**.
+2. Go to **WARP client checks** and select **Add a check**.
 
 3. Select **Carbon Black**.
 
@@ -36,4 +36,4 @@ Cloudflare Zero Trust can check if [Carbon Black](https://www.carbonblack.com/)
    4. **Signing certificate thumbprint (recommended)**: Enter the thumbprint of the publishing certificate used to sign the binary. This proves the binary came from Carbon Black and is the recommended way to validate the process.
    5. **SHA-256 (optional)**: Enter a SHA-256 value. This is used to validate the SHA256 signature of the binary and ensures the integrity of the binary file on the device. Note: do not fill out this field unless you strictly control updates to Carbon Black, as this will change between versions.
 
-Next, go to **Logs** > **Posture** and verify that the Carbon Black check is returning the expected results.
+Next, go to **Insights** > **Logs** > **Posture logs** and verify that the Carbon Black check is returning the expected results.
diff --git a/src/content/docs/cloudflare-one/reusable-components/posture-checks/warp-client-checks/client-certificate.mdx b/src/content/docs/cloudflare-one/reusable-components/posture-checks/warp-client-checks/client-certificate.mdx
@@ -33,7 +33,7 @@ The Client Certificate device posture attribute checks if the device has a valid
 
   :::note[Upload the signing certificate that issued the client certificate]
 
-  When uploading a certificate to use in posture checks, Cloudflare does not differentiate between root and intermediate certificates. You must upload the actual signing certificate – the one that directly signed the client certificate.
+  When uploading a certificate to use in posture checks, Cloudflare does not differentiate between root and intermediate certificates. You must upload the actual signing certificate - the one that directly signed the client certificate.
 
   If you upload a different certificate, even if it exists higher up in the trust chain (for example, the root that issued the signing certificate), the posture check will fail.
 
@@ -58,9 +58,9 @@ To generate a sample root CA for testing, refer to [Generate mTLS certificates](
    	}}
    />
 
-2. In [Zero Trust](https://one.dash.cloudflare.com), go to **Settings** > **WARP Client**.
+2. In [Cloudflare One](https://one.dash.cloudflare.com), go to **Reusable components** > **Posture checks**.
 
-3. Scroll down to **WARP client checks** and select **Add new**.
+3. Go to **WARP client checks** and select **Add a check**.
 
 4. Select **Client certificate**.
 
@@ -93,7 +93,7 @@ To generate a sample root CA for testing, refer to [Generate mTLS certificates](
 
 6. Select **Save**.
 
-Next, go to **Logs** > **Posture** and verify that the client certificate check is returning the expected results.
+Next, go to **Insights** > **Logs** > **Posture logs** and verify that the client certificate check is returning the expected results.
 
 ## Troubleshooting
 
diff --git a/src/content/docs/cloudflare-one/reusable-components/posture-checks/warp-client-checks/corp-device.mdx b/src/content/docs/cloudflare-one/reusable-components/posture-checks/warp-client-checks/corp-device.mdx
@@ -7,7 +7,7 @@ sidebar:
 
 import { Render } from "~/components";
 
-Cloudflare Zero Trust allows you to build Zero Trust rules based on device serial numbers. You can create these rules so that access to applications is granted only to users connecting from company devices.
+Cloudflare One allows you to build Zero Trust rules based on device serial numbers. You can create these rules so that access to applications is granted only to users connecting from company devices.
 
 ## Prerequisites
 
@@ -24,7 +24,7 @@ Cloudflare Zero Trust allows you to build Zero Trust rules based on device seria
 
 To create rules based on device serial numbers, you first need to create a [Gateway List](/cloudflare-one/reusable-components/lists/) of numbers.
 
-1. In [Zero Trust](https://one.dash.cloudflare.com), go to **My Team** > **Lists**.
+1. In [Cloudflare One](https://one.dash.cloudflare.com), go to **Reusable components** > **Lists**.
 
 2. Select **Create manual list** or **Upload CSV**. For larger teams, we recommend uploading a CSV or using Cloudflare's [API endpoint](/api/resources/zero_trust/subresources/gateway/subresources/lists/methods/list/).
 
diff --git a/src/content/docs/cloudflare-one/reusable-components/posture-checks/warp-client-checks/device-uuid.mdx b/src/content/docs/cloudflare-one/reusable-components/posture-checks/warp-client-checks/device-uuid.mdx
@@ -7,7 +7,7 @@ sidebar:
 
 import { Render } from "~/components";
 
-Cloudflare Zero Trust allows you to build Zero Trust rules based on device UUIDs supplied in an MDM file. You can create these rules so that access to applications is granted only to users connecting from company devices.
+Cloudflare One allows you to build Zero Trust rules based on device UUIDs supplied in an MDM file. You can create these rules so that access to applications is granted only to users connecting from company devices.
 
 ## Prerequisites
 
@@ -32,7 +32,7 @@ You will need to use a [managed deployment tool](/cloudflare-one/team-and-resour
 
 To create rules based on device UUIDs, you first need to create a [Gateway List](/cloudflare-one/reusable-components/lists/) of UUIDs.
 
-1. In [Zero Trust](https://one.dash.cloudflare.com), go to **My Team** > **Lists**.
+1. In [Cloudflare One](https://one.dash.cloudflare.com), go to **Reusable components** > **Lists**.
 
 2. Select **Create manual list** or **Upload CSV**. For larger teams, we recommend uploading a CSV or using Cloudflare's [API endpoint](/api/resources/zero_trust/subresources/gateway/subresources/lists/methods/list/).
 
@@ -51,9 +51,9 @@ Hyphens are automatically stripped from UUIDs. For example, the posture check wi
 
 ## 3. Enable the posture check
 
-1. In [Zero Trust](https://one.dash.cloudflare.com), go to **Settings** > **WARP Client**.
+1. In [Cloudflare One](https://one.dash.cloudflare.com), go to **Reusable components** > **Posture checks**.
 
-2. Scroll down to **WARP client checks** and select **Add new**.
+2. Go to **WARP client checks** and select **Add a check**.
 
 3. Select **Unique Client ID**.
 
diff --git a/src/content/docs/cloudflare-one/reusable-components/posture-checks/warp-client-checks/disk-encryption.mdx b/src/content/docs/cloudflare-one/reusable-components/posture-checks/warp-client-checks/disk-encryption.mdx
@@ -25,15 +25,15 @@ The Disk Encryption device posture attribute ensures that disks are encrypted on
 
 ## Enable the disk encryption check
 
-1. In [Zero Trust](https://one.dash.cloudflare.com), go to **Settings** > **WARP Client**.
-2. Scroll down to **WARP client checks** and select **Add new**.
+1. In [Cloudflare One](https://one.dash.cloudflare.com), go to **Reusable components** > **Posture checks**.
+2. Go to **WARP client checks** and select **Add a check**.
 3. Select **Disk Encryption**.
 4. Enter a descriptive name for the check.
 5. Select your operating system.
 6. Either enable disk encryption for all volumes, or input the specific volume(s) you want to check for encryption (for example, `C`).
 7. Select **Save**.
 
-Next, go to **Logs** > **Posture** and verify that the disk encryption check is returning the expected results.
+Next, go to **Insights** > **Logs** > **Posture logs** and verify that the disk encryption check is returning the expected results.
 
 ## Validate disk encryption status
 
diff --git a/src/content/docs/cloudflare-one/reusable-components/posture-checks/warp-client-checks/domain-joined.mdx b/src/content/docs/cloudflare-one/reusable-components/posture-checks/warp-client-checks/domain-joined.mdx
@@ -25,8 +25,8 @@ The Domain Joined device posture attribute ensures that a user is a member of a
 
 ## Enable the Domain Joined check
 
-1. In [Zero Trust](https://one.dash.cloudflare.com), go to **Settings** > **WARP Client**.
-2. Scroll down to **WARP client checks** and select **Add new**.
+1. In [Cloudflare One](https://one.dash.cloudflare.com), go to **Reusable components** > **Posture checks**.
+2. Go to **WARP client checks** and select **Add a check**.
 3. Select **Domain Joined**.
 4. Enter a descriptive name for the check.
 5. Select your operating system.
@@ -36,7 +36,7 @@ The Domain Joined device posture attribute ensures that a user is a member of a
    :::
 7. Select **Save**.
 
-Next, go to **Logs** > **Posture** and verify that the Domain Joined check is returning the expected results.
+Next, go to **Insights** > **Logs** > **Posture logs** and verify that the Domain Joined check is returning the expected results.
 
 ## Validate the domain value
 
diff --git a/src/content/docs/cloudflare-one/reusable-components/posture-checks/warp-client-checks/file-check.mdx b/src/content/docs/cloudflare-one/reusable-components/posture-checks/warp-client-checks/file-check.mdx
@@ -22,9 +22,9 @@ The File Check device posture attribute checks for the presence of a file on a d
 
 ## Configure a file check
 
-1. In [Zero Trust](https://one.dash.cloudflare.com), go to **Settings** > **WARP Client**.
+1. In [Cloudflare One](https://one.dash.cloudflare.com), go to **Reusable components** > **Posture checks**.
 
-2. Scroll down to **WARP client checks** and select **Add new**.
+2. Go to **WARP client checks** and select **Add a check**.
 
 3. Select **File Check**.
 
@@ -37,4 +37,4 @@ The File Check device posture attribute checks for the presence of a file on a d
 
 5. Select **Save**.
 
-Next, go to **Logs** > **Posture** and verify that the file check is returning the expected results.
+Next, go to **Insights** > **Logs** > **Posture logs** and verify that the file check is returning the expected results.
diff --git a/src/content/docs/cloudflare-one/reusable-components/posture-checks/warp-client-checks/firewall.mdx b/src/content/docs/cloudflare-one/reusable-components/posture-checks/warp-client-checks/firewall.mdx
@@ -25,15 +25,15 @@ The Firewall device posture attribute ensures that a firewall is running on a de
 
 ## Enable the firewall check
 
-1. In [Zero Trust](https://one.dash.cloudflare.com), go to **Settings** > **WARP Client**.
-2. Scroll down to **WARP client checks** and select **Add new**.
+1. In [Cloudflare One](https://one.dash.cloudflare.com), go to **Reusable components** > **Posture checks**.
+2. Go to **WARP client checks** and select **Add a check**.
 3. Select **Firewall**.
 4. Enter a descriptive name for the check.
 5. Select your operating system.
 6. Turn on **Enable firewall check**.
 7. Select **Save**.
 
-Next, go to **Logs** > **Posture** and verify that the firewall check is returning the expected results.
+Next, go to **Insights** > **Logs** > **Posture logs** and verify that the firewall check is returning the expected results.
 
 ## How WARP checks the firewall status
 
diff --git a/src/content/docs/cloudflare-one/reusable-components/posture-checks/warp-client-checks/os-version.mdx b/src/content/docs/cloudflare-one/reusable-components/posture-checks/warp-client-checks/os-version.mdx
@@ -22,8 +22,8 @@ The OS Version device posture attribute checks whether the version of a device's
 
 ## Enable the OS version check
 
-1.  In [Zero Trust](https://one.dash.cloudflare.com), go to **Settings** > **WARP Client**.
-2.  Scroll down to **WARP client checks** and select **Add new**.
+1.  In [Cloudflare One](https://one.dash.cloudflare.com), go to **Reusable components** > **Posture checks**.
+2.  Go to **WARP client checks** and select **Add a check**.
 3.  Select **OS version**.
 4.  Configure the **Operating system**, **Operator**, and **Version** fields to specify the [OS version](#determine-the-os-version) you want devices to match.
 
@@ -51,7 +51,7 @@ The OS Version device posture attribute checks whether the version of a device's
 
 6.  Select **Save**.
 
-Next, go to **Logs** > **Posture** and verify that the OS version check is returning the expected results.
+Next, go to **Insights** > **Logs** > **Posture logs** and verify that the OS version check is returning the expected results.
 
 ## Determine the OS version
 
diff --git a/src/content/docs/cloudflare-one/reusable-components/posture-checks/warp-client-checks/require-gateway.mdx b/src/content/docs/cloudflare-one/reusable-components/posture-checks/warp-client-checks/require-gateway.mdx
diff --git a/src/content/docs/cloudflare-one/reusable-components/posture-checks/warp-client-checks/require-warp.mdx b/src/content/docs/cloudflare-one/reusable-components/posture-checks/warp-client-checks/require-warp.mdx
diff --git a/src/content/docs/cloudflare-one/reusable-components/posture-checks/warp-client-checks/sentinel-one.mdx b/src/content/docs/cloudflare-one/reusable-components/posture-checks/warp-client-checks/sentinel-one.mdx
