From 904e00280cd324ea4cd1cd759e37ee6e13c857cc Mon Sep 17 00:00:00 2001 From: Nikita Cano Date: Wed, 24 Jun 2026 13:13:16 +0100 Subject: [PATCH] fix: migrate one.dash.cloudflare.com links to dash.cloudflare.com MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The Zero Trust dashboard is now embedded within the Core Cloudflare dashboard at dash.cloudflare.com/:account/one/. Update all 231 instances of one.dash.cloudflare.com across 136 files: - Bare links: [Cloudflare One](https://one.dash.cloudflare.com/) → [Cloudflare dashboard](https://dash.cloudflare.com/) - HTML links: Cloudflare One → Cloudflare dashboard - Deeplinks: one.dash.cloudflare.com/?to=/:account/ → dash.cloudflare.com/?to=/:account/one/ Intentionally left unchanged: - global-policies.mdx: one.dash.cloudflare.com appears as a literal DNS hostname in policy tables, not as a clickable link. - core.json: dash-routes registry entry. All deeplink paths validated against ztx-frontend route definitions. --- src/components/DashButton.astro | 12 ++-- .../access/2025-11-14-SSH-CA-enhancements.mdx | 2 +- ...6-01-08-Access-audit-log-for-DoH-users.mdx | 2 +- ...-05-01-browser-isolation-overview-page.mdx | 6 +- ...5-04-30-zero-trust-dashboard-dark-mode.mdx | 4 +- .../2025-07-09-onboarding-resources.mdx | 2 +- .../2025-08-27-shadow-it-analytics.mdx | 2 +- .../2025-12-17-shadow-it-domain-analytics.mdx | 2 +- .../cloudflare-one/access-analytics-v2.mdx | 6 +- .../cf1-data-security-analytics-v1.mdx | 6 +- .../dashboards-access-report.mdx | 2 +- .../cloudflare-one/gateway-analytics-v2.mdx | 2 +- .../cloudflare-one/new-applications-71825.mdx | 6 +- .../2025-09-23-invalid-submissions.mdx | 2 +- ...-gateway-authorization-proxy-open-beta.mdx | 7 ++- .../2026-02-20-tunnel-core-dashboard.mdx | 2 +- ...plica-overview-and-multi-log-streaming.mdx | 2 +- .../billing/understand/preview-services.mdx | 2 +- .../how-to/add-policies.mdx | 12 +++- .../docs/cloudflare-one/api-terraform.mdx | 7 ++- .../manage-findings.mdx | 57 +++++++++++++++---- .../troubleshoot-casb.mdx | 7 ++- .../email-security/directories/index.mdx | 14 +++-- .../directories/manage-es-directories.mdx | 7 ++- .../manage-integrated-directories/index.mdx | 13 +++-- .../manage-groups-directory.mdx | 7 ++- .../manage-users-directory.mdx | 7 ++- .../cloudflare-one/email-security/index.mdx | 7 ++- .../investigation/search-email.mdx | 52 +++++++++++++---- .../monitoring/download-report.mdx | 17 +++++- .../email-security/monitoring/index.mdx | 8 +-- .../email-security/phishguard.mdx | 8 ++- .../email-security/retro-scan.mdx | 18 +++--- .../email-security/settings/auto-moves.mdx | 2 +- .../additional-detections.mdx | 2 +- .../detection-settings/allow-policies.mdx | 2 +- .../detection-settings/blocked-senders.mdx | 2 +- .../configure-link-actions.mdx | 2 +- .../configure-text-add-ons.mdx | 2 +- .../impersonation-registry.mdx | 2 +- .../detection-settings/trusted-domains.mdx | 9 ++- .../settings/phish-submissions/index.mdx | 2 +- .../phish-submissions/phishnet-365.mdx | 2 +- .../submission-addresses.mdx | 2 +- .../email-security/setup/manage-domains.mdx | 8 +-- .../post-delivery-deployment/api/m365-api.mdx | 22 +++++-- .../gmail-bcc-setup/add-bcc-rules.mdx | 9 ++- .../gmail-bcc-setup/connect-domains.mdx | 7 ++- .../gmail-bcc-setup/enable-auto-moves.mdx | 7 ++- .../enable-gmail-integration.mdx | 11 ++-- .../journaling-setup/m365-journaling.mdx | 9 ++- .../journaling-setup/manual-add.mdx | 4 +- .../mx-inline-deployment-setup.mdx | 9 ++- .../partner-domain-tls.mdx | 7 ++- .../email-security/submissions/index.mdx | 9 ++- .../submissions/invalid-submissions.mdx | 4 +- .../submissions/team-submissions.mdx | 2 +- .../submissions/user-submissions.mdx | 2 +- .../insights/analytics-overview.mdx | 6 +- .../insights/dex/ip-visibility.mdx | 12 +++- .../insights/dex/monitoring.mdx | 12 +++- .../cloudflare-one/insights/dex/rules.mdx | 22 +++++-- .../insights/dex/tests/traceroute.mdx | 7 ++- .../insights/dex/tests/view-results.mdx | 12 +++- .../gateway-logs/manage-pii.mdx | 7 ++- .../insights/logs/dashboard-logs/index.mdx | 2 +- .../logs/dashboard-logs/posture-logs.mdx | 2 +- .../logs/dashboard-logs/ssh-command-logs.mdx | 9 ++- .../insights/logs/logpush/index.mdx | 7 ++- .../diagnostics/buckets.mdx | 10 +++- .../diagnostics/packet-captures.mdx | 5 +- .../integrations/cloud-and-saas/aws-s3.mdx | 7 ++- .../cloud-and-saas/findings/index.mdx | 57 +++++++++++++++---- .../cloud-and-saas/gcp-cloud-storage.mdx | 12 +++- .../cloud-and-saas/troubleshooting/casb.mdx | 7 ++- .../troubleshoot-compute-accounts.mdx | 12 +++- .../troubleshoot-integrations.mdx | 12 +++- .../integrations/cloud-and-saas/webhooks.mdx | 17 +++++- .../dns/dns-over-tls.mdx | 7 ++- .../dns/locations/dns-resolver-ips.mdx | 7 ++- .../proxy-endpoints/index.mdx | 31 ++++++++-- .../setup/clientless-browser-isolation.mdx | 7 ++- .../remote-browser-isolation/setup/index.mdx | 7 ++- .../setup/non-identity.mdx | 7 ++- .../custom-pages/gateway-block-page.mdx | 12 +++- .../docs/cloudflare-one/setup/index.mdx | 2 +- .../setup/replace-vpn/device-to-network.mdx | 6 +- .../secure-private-apps/clientless-ssh.mdx | 4 +- .../secure-private-apps/in-browser-rdp.mdx | 4 +- .../secure-private-apps/private-web-app.mdx | 4 +- .../tutorials/entra-id-risky-users.mdx | 6 +- .../integrate-microsoft-mcas-teams.mdx | 7 ++- .../tutorials/m365-dedicated-egress-ips.mdx | 6 +- .../docs/cloudflare-one/tutorials/r2-logs.mdx | 5 +- .../docs/dns/internal-dns/get-started.mdx | 5 +- .../migrate-to-email-security.mdx | 2 +- .../terraform/publish-apps-with-terraform.mdx | 2 +- .../active-directory-sync.mdx | 4 +- .../create-allow-policies.mdx | 2 +- .../impersonation-registry.mdx | 2 +- .../set-additional-detections.mdx | 2 +- .../configure-auto-moves.mdx | 2 +- .../get-started/setup-google-workspace.mdx | 2 +- .../get-started/setup-ms-graph-api.mdx | 2 +- .../monitor-your-inbox/index.mdx | 2 +- .../architectures/sase.mdx | 2 +- .../docs/security-center/indicator-feeds.mdx | 7 ++- .../casb/aws-compute-account.mdx | 7 ++- .../casb/manage-integrations.mdx | 17 +++++- .../clientless-browser-isolation.mdx | 7 ++- .../dex/http-test-create-steps.mdx | 7 ++- .../cloudflare-one/dex/pcaps-download.mdx | 7 ++- .../partials/cloudflare-one/dex/pcaps-run.mdx | 7 ++- .../dex/pcaps-view-warp-diag.mdx | 7 ++- .../email-security/domain-information.mdx | 2 +- .../post-verification-setup.mdx | 7 ++- .../analytics/site-analytics.mdx | 2 +- .../analytics/traceroutes.mdx | 2 +- .../cloudflare-wan/third-party/ubiquiti.mdx | 8 +-- .../mconn/configure-connectors.mdx | 6 +- .../maintenance/deactivate-connector.mdx | 2 +- .../mconn/maintenance/edit-basic-info.mdx | 2 +- .../maintenance/edit-network-settings.mdx | 2 +- .../mconn/maintenance/edit-sites.mdx | 2 +- .../maintenance/edit-traffic-steering.mdx | 2 +- .../mconn/maintenance/heartbeat.mdx | 2 +- .../register-hardware-appliance.mdx | 2 +- .../mconn/maintenance/remove-connectors.mdx | 4 +- .../breakout-prioritized.mdx | 6 +- .../mconn/network-options/dhcp/dhcp-relay.mdx | 2 +- .../network-options/dhcp/dhcp-server.mdx | 2 +- .../network-options/network-segmentation.mdx | 6 +- .../routing/configure-routes.mdx | 8 +-- .../routing/configure-tunnels.mdx | 2 +- .../networking-services/sites/sites.mdx | 4 +- .../check-tunnel-healthchecks-dash.mdx | 4 +- .../update-tunnel-health-checks-frequency.mdx | 2 +- 137 files changed, 708 insertions(+), 276 deletions(-) diff --git a/src/components/DashButton.astro b/src/components/DashButton.astro index 11aa0472286..cc93a83b739 100644 --- a/src/components/DashButton.astro +++ b/src/components/DashButton.astro @@ -40,11 +40,15 @@ if (!route) { */ const name = buttonName ?? route.name; -const baseUrl = zeroTrust - ? "https://one.dash.cloudflare.com" - : "https://dash.cloudflare.com"; +const baseUrl = "https://dash.cloudflare.com"; -let { href } = new URL(route.deeplink, baseUrl); +// Zero Trust routes use internal paths (e.g. /?to=/:account/email-security/...) +// that need the /one/ prefix when accessed via the Core dashboard. +const deeplink = zeroTrust + ? route.deeplink.replace("/?to=/:account/", "/?to=/:account/one/") + : route.deeplink; + +let { href } = new URL(deeplink, baseUrl); --- **Service credentials** page. +Previously, users had to generate this certificate by using the [Cloudflare API](https://developers.cloudflare.com/api/) directly. With this update, you can now create and manage this certificate in the [Cloudflare dashboard](https://dash.cloudflare.com/?to=/:account/one/access-controls/settings) from the **Access controls** > **Service credentials** page. ![Navigate to Access controls and then Service credentials to see where you can generate an SSH CA](~/assets/images/changelog/access/SSH-CA-generation.png) diff --git a/src/content/changelog/access/2026-01-08-Access-audit-log-for-DoH-users.mdx b/src/content/changelog/access/2026-01-08-Access-audit-log-for-DoH-users.mdx index 0cf547400cd..e2c9ca71470 100644 --- a/src/content/changelog/access/2026-01-08-Access-audit-log-for-DoH-users.mdx +++ b/src/content/changelog/access/2026-01-08-Access-audit-log-for-DoH-users.mdx @@ -8,4 +8,4 @@ products: Cloudflare [admin activity logs](/cloudflare-one/insights/logs/) now capture each time a [DNS over HTTP (DoH) user](/cloudflare-one/networks/resolvers-and-proxies/dns/dns-over-https/) is created. -These logs can be viewed from the [Cloudflare One dashboard](https://one.dash.cloudflare.com/), pulled via the [Cloudflare API](/api/), and exported through [Logpush](/cloudflare-one/insights/logs/logpush/). +These logs can be viewed from the [Cloudflare dashboard](https://dash.cloudflare.com/), pulled via the [Cloudflare API](/api/), and exported through [Logpush](/cloudflare-one/insights/logs/logpush/). diff --git a/src/content/changelog/browser-isolation/2025-05-01-browser-isolation-overview-page.mdx b/src/content/changelog/browser-isolation/2025-05-01-browser-isolation-overview-page.mdx index a8d29952014..db4f185cf95 100644 --- a/src/content/changelog/browser-isolation/2025-05-01-browser-isolation-overview-page.mdx +++ b/src/content/changelog/browser-isolation/2025-05-01-browser-isolation-overview-page.mdx @@ -4,6 +4,8 @@ description: A new home page experience for deploying and managing browser isola date: 2025-05-01 --- +import { DashButton } from "~/components"; + A new **Browser Isolation Overview** page is now available in the Cloudflare Zero Trust dashboard. This centralized view simplifies the management of [Remote Browser Isolation (RBI)](/cloudflare-one/remote-browser-isolation/) deployments, providing: - **Streamlined Onboarding:** Easily set up and manage isolation policies from one location. @@ -15,4 +17,6 @@ This update consolidates previously disparate settings, accelerating deployment, ![Browser Isolation Overview](~/assets/images/changelog/browser-isolation/browser-isolation-overview.png) -To access the new overview, log in to your Cloudflare [Zero Trust dashboard](https://one.dash.cloudflare.com/) and find Browser Isolation in the side navigation bar. +To access the new overview, log in to your [Cloudflare dashboard](https://dash.cloudflare.com/) and go to **Zero Trust** > **Browser Isolation**. + + diff --git a/src/content/changelog/cloudflare-one/2025-04-30-zero-trust-dashboard-dark-mode.mdx b/src/content/changelog/cloudflare-one/2025-04-30-zero-trust-dashboard-dark-mode.mdx index 33c6c6c4965..62dc0349d81 100644 --- a/src/content/changelog/cloudflare-one/2025-04-30-zero-trust-dashboard-dark-mode.mdx +++ b/src/content/changelog/cloudflare-one/2025-04-30-zero-trust-dashboard-dark-mode.mdx @@ -6,7 +6,7 @@ date: 2025-04-30 import { Tabs, TabItem } from "~/components"; -The [Cloudflare Zero Trust dashboard](https://one.dash.cloudflare.com/) now supports Cloudflare's native dark mode for all accounts and plan types. +The [Cloudflare dashboard](https://dash.cloudflare.com/) now supports Cloudflare's native dark mode for all accounts and plan types. Zero Trust Dashboard will automatically accept your user-level preferences for system settings, so if your Dashboard appearance is set to 'system' or 'dark', the Zero Trust dashboard will enter dark mode whenever the rest of your Cloudflare account does. @@ -16,7 +16,7 @@ Zero Trust Dashboard will automatically accept your user-level preferences for s To update your view preference in the Zero Trust dashboard: -1. Log into the [Zero Trust dashboard](https://one.dash.cloudflare.com/). +1. Log into the [Cloudflare dashboard](https://dash.cloudflare.com/). 2. Select your user icon. 3. Select **Dark Mode**. diff --git a/src/content/changelog/cloudflare-one/2025-07-09-onboarding-resources.mdx b/src/content/changelog/cloudflare-one/2025-07-09-onboarding-resources.mdx index a6914ae86e8..44621f2bc25 100644 --- a/src/content/changelog/cloudflare-one/2025-07-09-onboarding-resources.mdx +++ b/src/content/changelog/cloudflare-one/2025-07-09-onboarding-resources.mdx @@ -21,4 +21,4 @@ There are eight brand new onboarding guides in total: Each flow walks the user through the steps to configure the essential elements, and provides a “more details” panel with additional contextual information about what the user will accomplish at the end, along with why the steps they take are important. -Try them out now in the [Zero Trust dashboard](https://one.dash.cloudflare.com/?to=/:account/home)! +Try them out now in the [Zero Trust dashboard](https://dash.cloudflare.com/?to=/:account/one/home)! diff --git a/src/content/changelog/cloudflare-one/2025-08-27-shadow-it-analytics.mdx b/src/content/changelog/cloudflare-one/2025-08-27-shadow-it-analytics.mdx index e9dd30bde3f..88a7d923a9c 100644 --- a/src/content/changelog/cloudflare-one/2025-08-27-shadow-it-analytics.mdx +++ b/src/content/changelog/cloudflare-one/2025-08-27-shadow-it-analytics.mdx @@ -14,4 +14,4 @@ You can review these metrics against application type, such as Artificial Intell These application statuses can also be used in Gateway HTTP policies, so you can block, isolate, limit uploads and downloads, and more based on the application status. -Both the analytics and policies are accessible in the Cloudflare [Zero Trust dashboard](https://one.dash.cloudflare.com/), empowering organizations with better visibility and control. +Both the analytics and policies are accessible in the [Cloudflare dashboard](https://dash.cloudflare.com/), empowering organizations with better visibility and control. diff --git a/src/content/changelog/cloudflare-one/2025-12-17-shadow-it-domain-analytics.mdx b/src/content/changelog/cloudflare-one/2025-12-17-shadow-it-domain-analytics.mdx index de5d350a10f..3b2f38f648c 100644 --- a/src/content/changelog/cloudflare-one/2025-12-17-shadow-it-domain-analytics.mdx +++ b/src/content/changelog/cloudflare-one/2025-12-17-shadow-it-domain-analytics.mdx @@ -14,4 +14,4 @@ With this update, you can review data transfer metrics at the domain level, rath These metrics can be filtered by all available filters on the dashboard, including user, application, or content category. -Both the analytics and policies are accessible in the Cloudflare [Zero Trust dashboard](https://one.dash.cloudflare.com/), empowering organizations with better visibility and control. +Both the analytics and policies are accessible in the [Cloudflare dashboard](https://dash.cloudflare.com/), empowering organizations with better visibility and control. diff --git a/src/content/changelog/cloudflare-one/access-analytics-v2.mdx b/src/content/changelog/cloudflare-one/access-analytics-v2.mdx index 636d58bb197..b6a79088cc1 100644 --- a/src/content/changelog/cloudflare-one/access-analytics-v2.mdx +++ b/src/content/changelog/cloudflare-one/access-analytics-v2.mdx @@ -6,6 +6,8 @@ products: - access --- +import { DashButton } from "~/components"; + A new Access Analytics dashboard is now available to all Cloudflare One customers. Customers can apply and combine multiple filters to dive into specific slices of their Access metrics. These filters include: - Logins granted and denied @@ -19,4 +21,6 @@ A new Access Analytics dashboard is now available to all Cloudflare One customer ![Access Analytics](~/assets/images/changelog/cloudflare-one/accessanalytics.png) -To access the new overview, log in to your Cloudflare [Zero Trust dashboard](https://one.dash.cloudflare.com/) and find Analytics in the side navigation bar. +To access the new overview, log in to your [Cloudflare dashboard](https://dash.cloudflare.com/) and go to **Zero Trust** > **Insights** > **Analytics**. + + diff --git a/src/content/changelog/cloudflare-one/cf1-data-security-analytics-v1.mdx b/src/content/changelog/cloudflare-one/cf1-data-security-analytics-v1.mdx index 456b47c7909..9994867f3ad 100644 --- a/src/content/changelog/cloudflare-one/cf1-data-security-analytics-v1.mdx +++ b/src/content/changelog/cloudflare-one/cf1-data-security-analytics-v1.mdx @@ -7,6 +7,8 @@ products: - casb --- +import { DashButton } from "~/components"; + Zero Trust now includes **Data security analytics**, providing you with unprecedented visibility into your organization sensitive data. The new dashboard includes: @@ -23,4 +25,6 @@ The new dashboard includes: ![Data Security Analytics](~/assets/images/changelog/cloudflare-one/cf1-data-security-analytics-v1.png) -To access the new dashboard, log in to [Cloudflare One](https://one.dash.cloudflare.com/) and go to **Insights** on the sidebar. +To access the new dashboard, log in to [Cloudflare dashboard](https://dash.cloudflare.com/) and go to **Zero Trust** > **Insights** on the sidebar. + + diff --git a/src/content/changelog/cloudflare-one/dashboards-access-report.mdx b/src/content/changelog/cloudflare-one/dashboards-access-report.mdx index bedfae29995..c23abe0fb0d 100644 --- a/src/content/changelog/cloudflare-one/dashboards-access-report.mdx +++ b/src/content/changelog/cloudflare-one/dashboards-access-report.mdx @@ -14,4 +14,4 @@ Additionally, a new exportable access report is available, allowing customers to ![Cloudflare One Analytics Dashboards](~/assets/images/changelog/cloudflare-one/access-report.png) -Both features are accessible in the Cloudflare [Zero Trust dashboard](https://one.dash.cloudflare.com/), empowering organizations with better visibility and control. +Both features are accessible in the [Cloudflare dashboard](https://dash.cloudflare.com/), empowering organizations with better visibility and control. diff --git a/src/content/changelog/cloudflare-one/gateway-analytics-v2.mdx b/src/content/changelog/cloudflare-one/gateway-analytics-v2.mdx index 5f1981bccc2..85bb28053ce 100644 --- a/src/content/changelog/cloudflare-one/gateway-analytics-v2.mdx +++ b/src/content/changelog/cloudflare-one/gateway-analytics-v2.mdx @@ -17,4 +17,4 @@ You can now visualize and explore: ![Gateway Analytics](~/assets/images/changelog/cloudflare-one/gateway-analytics.png) -To access the new overview, log in to your Cloudflare [Zero Trust dashboard](https://one.dash.cloudflare.com/) and go to Analytics in the side navigation bar. +To access the new overview, log in to your [Cloudflare dashboard](https://dash.cloudflare.com/) and go to Analytics in the side navigation bar. diff --git a/src/content/changelog/cloudflare-one/new-applications-71825.mdx b/src/content/changelog/cloudflare-one/new-applications-71825.mdx index 3732caa8114..330f4662cda 100644 --- a/src/content/changelog/cloudflare-one/new-applications-71825.mdx +++ b/src/content/changelog/cloudflare-one/new-applications-71825.mdx @@ -5,10 +5,14 @@ date: 2025-05-18 product: Gateway --- +import { DashButton } from "~/components"; + 42 new applications have been added for Zero Trust support within the Application Library and Gateway policy enforcement, giving you the ability to investigate or apply inline policies to these applications. 33 of the 42 applications are Artificial Intelligence applications. The others are Human Resources (2 applications), Development (2 applications), Productivity (2 applications), Sales & Marketing, Public Cloud, and Security. -To view all available applications, log in to your Cloudflare [Zero Trust dashboard](https://one.dash.cloudflare.com/), navigate to the **App Library** under **My Team**. +To view all available applications, log in to your [Cloudflare dashboard](https://dash.cloudflare.com/) and go to **Zero Trust** > **Team resources** > **App Library**. + + For more information on creating Gateway policies, see our [Gateway policy documentation](/cloudflare-one/traffic-policies/). diff --git a/src/content/changelog/email-security-cf1/2025-09-23-invalid-submissions.mdx b/src/content/changelog/email-security-cf1/2025-09-23-invalid-submissions.mdx index ecd78ebb27e..3b3484647dd 100644 --- a/src/content/changelog/email-security-cf1/2025-09-23-invalid-submissions.mdx +++ b/src/content/changelog/email-security-cf1/2025-09-23-invalid-submissions.mdx @@ -8,7 +8,7 @@ Email security relies on your submissions to continuously improve our detection To ensure all customer feedback is actionable, we have launched two new features to manage invalid submissions sent to our team and user [submission aliases](/cloudflare-one/email-security/settings/phish-submissions/submission-addresses/): -- **Email Notifications:** We now automatically notify users by email when they provide an invalid submission, educating them on the correct format. To disable notifications, go to **[Settings](https://one.dash.cloudflare.com/?to=/:account/email-security/settings)** > **Invalid submission emails** and turn the feature off. +- **Email Notifications:** We now automatically notify users by email when they provide an invalid submission, educating them on the correct format. To disable notifications, go to **[Settings](https://dash.cloudflare.com/?to=/:account/one/email-security/settings)** > **Invalid submission emails** and turn the feature off. ![EmailSec-Invalid-Submissions-Toggle](~/assets/images/changelog/email-security/EmailSec-Invalid-Submissions-Toggle.png) diff --git a/src/content/changelog/gateway/2026-03-04-gateway-authorization-proxy-open-beta.mdx b/src/content/changelog/gateway/2026-03-04-gateway-authorization-proxy-open-beta.mdx index 514e857b47b..3f2a6511baf 100644 --- a/src/content/changelog/gateway/2026-03-04-gateway-authorization-proxy-open-beta.mdx +++ b/src/content/changelog/gateway/2026-03-04-gateway-authorization-proxy-open-beta.mdx @@ -6,6 +6,8 @@ products: date: 2026-03-04 --- +import { DashButton } from "~/components"; + The [Gateway Authorization Proxy](/cloudflare-one/networks/resolvers-and-proxies/proxy-endpoints/#authorization-endpoint) and [PAC file hosting](/cloudflare-one/networks/resolvers-and-proxies/proxy-endpoints/#create-a-hosted-pac-file) are now in open beta for all plan types. Previously, [proxy endpoints](/cloudflare-one/networks/resolvers-and-proxies/proxy-endpoints/#source-ip-endpoint) relied on static source IP addresses to authorize traffic, providing no user-level identity in logs or policies. The new authorization proxy replaces IP-based authorization with [Cloudflare Access](/cloudflare-one/access-controls/policies/) authentication, verifying who a user is before applying Gateway filtering without installing the WARP client. @@ -21,7 +23,10 @@ This is ideal for environments where you cannot deploy a device client, such as ### Get started -1. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Networks** > **Resolvers & Proxies** > **Proxy endpoints**. +1. In [Cloudflare dashboard](https://dash.cloudflare.com/), go to **Zero Trust** > **Networks** > **Resolvers & Proxies** > **Proxy endpoints**. + + + 2. [Create an authorization proxy endpoint](/cloudflare-one/networks/resolvers-and-proxies/proxy-endpoints/#authorization-endpoint) and configure Access policies. 3. [Create a hosted PAC file](/cloudflare-one/networks/resolvers-and-proxies/proxy-endpoints/#create-a-hosted-pac-file) or write your own. 4. [Configure browsers](/cloudflare-one/networks/resolvers-and-proxies/proxy-endpoints/#3b-configure-browser-to-use-pac-file) to use the PAC file URL. diff --git a/src/content/changelog/tunnel/2026-02-20-tunnel-core-dashboard.mdx b/src/content/changelog/tunnel/2026-02-20-tunnel-core-dashboard.mdx index 03aae7f4939..a2d1f87188f 100644 --- a/src/content/changelog/tunnel/2026-02-20-tunnel-core-dashboard.mdx +++ b/src/content/changelog/tunnel/2026-02-20-tunnel-core-dashboard.mdx @@ -27,7 +27,7 @@ This new experience provides everything you need to manage Tunnels for [public a - Securing origin servers and [public applications](/cloudflare-one/networks/connectors/cloudflare-tunnel/routing-to-tunnel/) with CDN, WAF, Load Balancing, and DDoS protection - Connecting [Workers to private services](/workers-vpc/) via Workers VPC -**Cloudflare One Dashboard**: Navigate to [Zero Trust > Networks > Connectors](https://one.dash.cloudflare.com/?to=/:account/networks/connectors) to manage Tunnels for: +**Cloudflare One Dashboard**: Navigate to [Zero Trust > Networks > Connectors](https://dash.cloudflare.com/?to=/:account/one/networks/connectors) to manage Tunnels for: - Securing your public applications with [Zero Trust access policies](/cloudflare-one/access-controls/applications/http-apps/self-hosted-public-app/) - Connecting users to [private applications](/cloudflare-one/access-controls/applications/non-http/self-hosted-private-app/) diff --git a/src/content/changelog/tunnel/2026-03-20-tunnel-replica-overview-and-multi-log-streaming.mdx b/src/content/changelog/tunnel/2026-03-20-tunnel-replica-overview-and-multi-log-streaming.mdx index 2849122ee7c..ae84ca29515 100644 --- a/src/content/changelog/tunnel/2026-03-20-tunnel-replica-overview-and-multi-log-streaming.mdx +++ b/src/content/changelog/tunnel/2026-03-20-tunnel-replica-overview-and-multi-log-streaming.mdx @@ -14,6 +14,6 @@ In the Cloudflare One dashboard, the overview page for a specific Cloudflare Tun Previously, you could only stream logs from one replica at a time. With this update: - **Replicas on the tunnel overview** — All active replicas for the selected tunnel now appear on that tunnel's overview page under **Connectors**. Select any replica to stream its logs. -- **Multi-connector log streaming** — Stream logs from multiple replicas simultaneously, making it easier to correlate events across your infrastructure during debugging or incident response. To try it out, log in to [Cloudflare One](https://one.dash.cloudflare.com/) and go to **Networks** > **Connectors** > **Cloudflare Tunnels**. Select **View logs** next to the tunnel you want to monitor. +- **Multi-connector log streaming** — Stream logs from multiple replicas simultaneously, making it easier to correlate events across your infrastructure during debugging or incident response. To try it out, log in to [Cloudflare dashboard](https://dash.cloudflare.com/) and go to **Networks** > **Connectors** > **Cloudflare Tunnels**. Select **View logs** next to the tunnel you want to monitor. For more information, refer to [Tunnel log streams](/cloudflare-one/networks/connectors/cloudflare-tunnel/monitor-tunnels/logs/) and [Deploy replicas](/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/tunnel-availability/deploy-replicas/). diff --git a/src/content/docs/billing/understand/preview-services.mdx b/src/content/docs/billing/understand/preview-services.mdx index b6d0b5e4aa7..6de6beb9179 100644 --- a/src/content/docs/billing/understand/preview-services.mdx +++ b/src/content/docs/billing/understand/preview-services.mdx @@ -32,7 +32,7 @@ To turn on a preview service, use the **Dashboard link** in the following table. | Waiting Room | [Waiting Room dashboard](https://dash.cloudflare.com/?to=/:account/:zone/traffic/waiting-rooms) | [Waiting Room docs](/waiting-room/) | [Waiting Room community](https://community.cloudflare.com/) | | Web3 | [Web3 dashboard](https://dash.cloudflare.com/?to=/:account/:zone/web3) | [Web3 docs](/web3/) | [Web3 discord](https://discord.cloudflare.com) | | Workers | [Workers dashboard](https://dash.cloudflare.com/?to=/:account/workers) | [Workers docs](/workers/) | [Workers discord](https://discord.com/invite/cloudflaredev) | -| Zero Trust | [Zero Trust dashboard](https://one.dash.cloudflare.com/) | [Zero Trust docs](/cloudflare-one/) | [Zero Trust community](https://community.cloudflare.com/c/security/access/51) | +| Zero Trust | [Cloudflare dashboard](https://dash.cloudflare.com/) | [Zero Trust docs](/cloudflare-one/) | [Zero Trust community](https://community.cloudflare.com/c/security/access/51) | ## Recommendations diff --git a/src/content/docs/cloudflare-network-firewall/how-to/add-policies.mdx b/src/content/docs/cloudflare-network-firewall/how-to/add-policies.mdx index be51334acf7..ae22431adc7 100644 --- a/src/content/docs/cloudflare-network-firewall/how-to/add-policies.mdx +++ b/src/content/docs/cloudflare-network-firewall/how-to/add-policies.mdx @@ -10,11 +10,16 @@ sidebar: order: 5 --- +import { DashButton } from "~/components"; + By default, you can create a maximum of 200 policies. We recommend you create lists of IP addresses to reference within policies to streamline policy management. ## Add a policy -1. In the [Cloudflare One](https://one.dash.cloudflare.com) dashboard, go to **Firewall policies** > **Custom policies**. +1. In the [Cloudflare dashboard](https://dash.cloudflare.com/), go to **Zero Trust** > **Firewall policies** > **Custom policies**. + + + 2. Select **Add a policy**. 3. Fill out the information for your new policy. All existing policies apply to IPv4. You can use a managed [IP list](https://www.cloudflare.com/en-gb/ips/) when populating the **Value**. 4. When you are done, select **Add new policy**. @@ -29,7 +34,10 @@ To disable an existing policy, from the **Custom policies** tab, set the **Enabl ## Update a policy -1. In the [Cloudflare One](https://one.dash.cloudflare.com) dashboard, go to **Firewall policies** > **Custom policies**. +1. In the [Cloudflare dashboard](https://dash.cloudflare.com/), go to **Zero Trust** > **Firewall policies** > **Custom policies**. + + + 2. Locate the policy you want to edit and select the three dots > **Edit**. 3. Update the policy with your changes and select **Save**. diff --git a/src/content/docs/cloudflare-one/api-terraform.mdx b/src/content/docs/cloudflare-one/api-terraform.mdx index 941275a8ff6..807c71497e2 100644 --- a/src/content/docs/cloudflare-one/api-terraform.mdx +++ b/src/content/docs/cloudflare-one/api-terraform.mdx @@ -11,6 +11,8 @@ tags: - REST API --- +import { DashButton } from "~/components"; + You can manage your Cloudflare Zero Trust configuration using the API or Terraform. For more information, refer to the following links: - [API reference](/api/) @@ -25,7 +27,10 @@ Super Administrators can lock all settings as read-only in the Cloudflare One da To enable read-only mode: -1. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Settings** > **Admin controls**. +1. In [Cloudflare dashboard](https://dash.cloudflare.com/), go to **Zero Trust** > **Settings** > **Admin controls**. + + + 2. Enable **Set dashboard to read-only**. All users, regardless of [user permissions](/cloudflare-one/roles-permissions/), will be prevented from making configuration changes through the UI. diff --git a/src/content/docs/cloudflare-one/cloud-and-saas-findings/manage-findings.mdx b/src/content/docs/cloudflare-one/cloud-and-saas-findings/manage-findings.mdx index badb208bcb3..c7e4f53a27f 100644 --- a/src/content/docs/cloudflare-one/cloud-and-saas-findings/manage-findings.mdx +++ b/src/content/docs/cloudflare-one/cloud-and-saas-findings/manage-findings.mdx @@ -13,7 +13,7 @@ tags: - Compliance --- -import { TabItem, Tabs, Details } from "~/components"; +import { DashButton, TabItem, Tabs, Details } from "~/components"; Findings are security issues detected within SaaS and cloud applications that involve users, data at rest (files stored in your apps), and other configuration settings. With Cloudflare CASB, you can review a comprehensive list of findings in Cloudflare One and take action on the issues found. @@ -28,7 +28,10 @@ Posture findings include misconfigurations, unauthorized user activity, and othe To view details about the posture findings that CASB found: -1. In [Cloudflare One](https://one.dash.cloudflare.com), go to **Cloud & SaaS findings** > **Posture Findings**. +1. In [Cloudflare dashboard](https://dash.cloudflare.com/), go to **Zero Trust** > **Cloud & SaaS findings** > **Posture Findings**. + + + 2. Choose **SaaS** or **Cloud**. 3. To view details about a finding, select the finding's name @@ -51,7 +54,10 @@ Cloudflare CASB labels each finding with one of the following severity levels: You can change the severity level for a finding at any time in case the default assignment does not suit your environment: -1. In [Cloudflare One](https://one.dash.cloudflare.com), go to **Cloud & SaaS findings** > **Posture Findings**. +1. In [Cloudflare dashboard](https://dash.cloudflare.com/), go to **Zero Trust** > **Cloud & SaaS findings** > **Posture Findings**. + + + 2. Locate the finding you want to modify and select **Manage**. 3. In the severity level drop-down menu, choose your desired setting (_Critical_, _High_, _Medium_, or _Low_). @@ -63,7 +69,10 @@ Content findings include instances of potential data exposure as identified by [ To view details about the content findings that CASB found: -1. In [Cloudflare One](https://one.dash.cloudflare.com), go to **Cloud & SaaS findings** > **Content Findings**. +1. In [Cloudflare dashboard](https://dash.cloudflare.com/), go to **Zero Trust** > **Cloud & SaaS findings** > **Content Findings**. + + + 2. Choose **SaaS** or **Cloud**. 3. To view details about a finding, select the finding's name. @@ -77,7 +86,10 @@ File findings for some integrations (such as [Microsoft 365](/cloudflare-one/int -1. In [Cloudflare One](https://one.dash.cloudflare.com), go to **Cloud & SaaS findings** > **Posture Findings**. +1. In [Cloudflare dashboard](https://dash.cloudflare.com/), go to **Zero Trust** > **Cloud & SaaS findings** > **Posture Findings**. + + + 2. Choose **SaaS** or **Cloud**. 3. Locate the individual finding, then select **Manage**. 4. In **Active Instances**, select the file name. @@ -87,7 +99,10 @@ File findings for some integrations (such as [Microsoft 365](/cloudflare-one/int -1. In [Cloudflare One](https://one.dash.cloudflare.com), go to **Cloud & SaaS findings** > **Content Findings**. +1. In [Cloudflare dashboard](https://dash.cloudflare.com/), go to **Zero Trust** > **Cloud & SaaS findings** > **Content Findings**. + + + 2. Choose **SaaS** or **Cloud**. 3. Select the file name of the detected asset. 4. In **Sharing details**, select the linked file instance. @@ -103,7 +118,10 @@ After reviewing your findings, you may decide that certain posture findings are ### Ignore a finding -1. In [Cloudflare One](https://one.dash.cloudflare.com), go to **Cloud & SaaS findings** > **Posture Findings**. +1. In [Cloudflare dashboard](https://dash.cloudflare.com/), go to **Zero Trust** > **Cloud & SaaS findings** > **Posture Findings**. + + + 2. Locate the active finding you want to hide. 3. In the three-dot menu, select **Move to ignore**. @@ -111,7 +129,10 @@ The finding's status will change from **Active** to **Ignored**. CASB will conti ### Hide an instance of a finding -1. In [Cloudflare One](https://one.dash.cloudflare.com), go to **Cloud & SaaS findings** > **Posture Findings**. +1. In [Cloudflare dashboard](https://dash.cloudflare.com/), go to **Zero Trust** > **Cloud & SaaS findings** > **Posture Findings**. + + + 2. Choose the active finding you want to hide, then select **Manage**. 3. In **Active**, find the instance you want to hide. 4. In the three-dot menu, select **Move to hidden**. @@ -124,7 +145,10 @@ After you configure one or more [CASB webhooks](/cloudflare-one/integrations/clo CASB webhooks currently support posture finding instances only. -1. In [Cloudflare One](https://one.dash.cloudflare.com), go to **Cloud & SaaS findings** > **Posture Findings**. +1. In [Cloudflare dashboard](https://dash.cloudflare.com/), go to **Zero Trust** > **Cloud & SaaS findings** > **Posture Findings**. + + + 2. Choose **SaaS** or **Cloud**. 3. Choose the finding you want to review, then select **Manage**. 4. In **Active Instances**, select an instance. @@ -144,7 +168,10 @@ In addition to detecting and surfacing misconfigurations or issues with SaaS and Before you can remediate findings, [add a new integration](/cloudflare-one/integrations/cloud-and-saas/) and choose _Read-Write mode_ during setup. Alternatively, you can update an existing integration: -1. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Cloud & SaaS findings** > **Integrations**. +1. In [Cloudflare dashboard](https://dash.cloudflare.com/), go to **Zero Trust** > **Cloud & SaaS findings** > **Integrations**. + + + 2. Choose your integration, then select **Configure**. 3. In **Integration permissions**, choose _Read-Write mode_. 4. Select **Update integration**. CASB will redirect you to your Microsoft 365 configuration. @@ -156,7 +183,10 @@ CASB can now remediate supported findings directly. To remediate a supported finding: -1. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Cloud & SaaS findings** > **Posture Findings**. +1. In [Cloudflare dashboard](https://dash.cloudflare.com/), go to **Zero Trust** > **Cloud & SaaS findings** > **Posture Findings**. + + + 2. Choose a supported finding type, then select **Manage**. 3. In **Active Instances**, select an instance. 4. In **Remediation details**, choose a remediation action to take. @@ -201,7 +231,10 @@ Ensure that you have [enabled HTTP filtering](/cloudflare-one/traffic-policies/g To create a Gateway policy directly from a CASB finding: -1. In [Cloudflare One](https://one.dash.cloudflare.com), go to **Cloud & SaaS findings** > **Posture Findings** or **Cloud & SaaS findings** > **Content Findings**. +1. In [Cloudflare dashboard](https://dash.cloudflare.com/), go to **Zero Trust** > **Cloud & SaaS findings** > **Posture Findings** or **Cloud & SaaS findings** > **Content Findings**. + + + 2. Choose **SaaS** or **Cloud**. 3. Choose the finding you want to modify, then select **Manage**. 4. Find the instance you want to block and select its three-dot menu. diff --git a/src/content/docs/cloudflare-one/cloud-and-saas-findings/troubleshoot-casb.mdx b/src/content/docs/cloudflare-one/cloud-and-saas-findings/troubleshoot-casb.mdx index d77ec045a80..af417ad118a 100644 --- a/src/content/docs/cloudflare-one/cloud-and-saas-findings/troubleshoot-casb.mdx +++ b/src/content/docs/cloudflare-one/cloud-and-saas-findings/troubleshoot-casb.mdx @@ -10,6 +10,8 @@ tags: - Debugging --- +import { DashButton } from "~/components"; + Use this guide to troubleshoot common issues with Cloud Access Security Broker (CASB). This guide covers troubleshooting steps for CASB integrations and webhooks. For integration-specific issues, refer to the integration's documentation. @@ -48,7 +50,10 @@ CASB integrations do not provide real-time updates. Scans are performed periodic To trigger a new scan: -1. In [Cloudflare One](https://one.dash.cloudflare.com), go to **Cloud & SaaS findings** > **Integrations**. +1. In [Cloudflare dashboard](https://dash.cloudflare.com/), go to **Zero Trust** > **Cloud & SaaS findings** > **Integrations**. + + + 2. Find your integration and select **Configure**. 3. Turn off **Scan for findings**. 4. After a few minutes, turn on **Scan for findings** again. diff --git a/src/content/docs/cloudflare-one/email-security/directories/index.mdx b/src/content/docs/cloudflare-one/email-security/directories/index.mdx index ff393a60390..bf15b517b12 100644 --- a/src/content/docs/cloudflare-one/email-security/directories/index.mdx +++ b/src/content/docs/cloudflare-one/email-security/directories/index.mdx @@ -8,15 +8,19 @@ sidebar: order: 16 --- +import { DashButton } from "~/components"; + Directories are folders to store user data. Email security allows you to manage directories from the Cloudflare dashboard. To add a directory: -1. Log in to [Cloudflare One](https://one.dash.cloudflare.com/) > **Email security**. -2. Select **Directories**. -3. Select **Add a directory** > **Connect an integration**. -4. Select either **Google Workspace CASB + EMAIL** or **Microsoft CASB+EMAIL**. -5. Refer to [Enable Gmail BCC integration](/cloudflare-one/email-security/setup/post-delivery-deployment/bcc-journaling/bcc-setup/gmail-bcc-setup/enable-gmail-integration/#enable-gmail-bcc-integration) if you choose Google Workspace. Refer to [Enable Microsoft integration](/cloudflare-one/email-security/setup/post-delivery-deployment/api/m365-api/#enable-microsoft-integration) if you choose Microsoft 365. +1. In the [Cloudflare dashboard](https://dash.cloudflare.com/), go to **Zero Trust** > **Email security** > **Directories**. + + + +2. Select **Add a directory** > **Connect an integration**. +3. Select either **Google Workspace CASB + EMAIL** or **Microsoft CASB+EMAIL**. +4. Refer to [Enable Gmail BCC integration](/cloudflare-one/email-security/setup/post-delivery-deployment/bcc-journaling/bcc-setup/gmail-bcc-setup/enable-gmail-integration/#enable-gmail-bcc-integration) if you choose Google Workspace. Refer to [Enable Microsoft integration](/cloudflare-one/email-security/setup/post-delivery-deployment/api/m365-api/#enable-microsoft-integration) if you choose Microsoft 365. To sync a directory: diff --git a/src/content/docs/cloudflare-one/email-security/directories/manage-es-directories.mdx b/src/content/docs/cloudflare-one/email-security/directories/manage-es-directories.mdx index b346156557c..c64895d0ae5 100644 --- a/src/content/docs/cloudflare-one/email-security/directories/manage-es-directories.mdx +++ b/src/content/docs/cloudflare-one/email-security/directories/manage-es-directories.mdx @@ -8,6 +8,8 @@ sidebar: order: 5 --- +import { DashButton } from "~/components"; + You can manage your Email security directory by editing and deleting added users. :::note[Registered users] @@ -16,7 +18,10 @@ The Email security directory contains registered users only. A registered user i To modify or delete users in the Email security directory: -1. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Email security** > **Directories**. +1. In [Cloudflare dashboard](https://dash.cloudflare.com/), go to **Zero Trust** > **Email security** > **Directories**. + + + 2. Select **Email security Directory**. ## Add a user diff --git a/src/content/docs/cloudflare-one/email-security/directories/manage-integrated-directories/index.mdx b/src/content/docs/cloudflare-one/email-security/directories/manage-integrated-directories/index.mdx index 7e744fd378b..6ab24952371 100644 --- a/src/content/docs/cloudflare-one/email-security/directories/manage-integrated-directories/index.mdx +++ b/src/content/docs/cloudflare-one/email-security/directories/manage-integrated-directories/index.mdx @@ -10,10 +10,13 @@ sidebar: hideIndex: true --- +import { DashButton } from "~/components"; + To manage an integrated directory: -1. Log in to [Cloudflare One](https://one.dash.cloudflare.com/). -2. Select **Email security**. -3. Select **Directories**. -4. Under **Directory name**, select your directory. -5. You will be redirected to a page where you can manage [Groups](/cloudflare-one/email-security/directories/manage-integrated-directories/manage-groups-directory/) or [Users](/cloudflare-one/email-security/directories/manage-integrated-directories/manage-users-directory/) directories. +1. In the [Cloudflare dashboard](https://dash.cloudflare.com/), go to **Zero Trust** > **Email security** > **Directories**. + + + +2. Under **Directory name**, select your directory. +3. You will be redirected to a page where you can manage [Groups](/cloudflare-one/email-security/directories/manage-integrated-directories/manage-groups-directory/) or [Users](/cloudflare-one/email-security/directories/manage-integrated-directories/manage-users-directory/) directories. diff --git a/src/content/docs/cloudflare-one/email-security/directories/manage-integrated-directories/manage-groups-directory.mdx b/src/content/docs/cloudflare-one/email-security/directories/manage-integrated-directories/manage-groups-directory.mdx index 12046078cac..41c6b60a2a3 100644 --- a/src/content/docs/cloudflare-one/email-security/directories/manage-integrated-directories/manage-groups-directory.mdx +++ b/src/content/docs/cloudflare-one/email-security/directories/manage-integrated-directories/manage-groups-directory.mdx @@ -8,11 +8,16 @@ sidebar: order: 3 --- +import { DashButton } from "~/components"; + Email security allows you to view and manage your groups directory and their [impersonation registry](/cloudflare-one/email-security/settings/detection-settings/impersonation-registry/). When a group is added to the registry, all members are registered by default. To manage a group directory: -1. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Email security** > **Directories**. +1. In [Cloudflare dashboard](https://dash.cloudflare.com/), go to **Zero Trust** > **Email security** > **Directories**. + + + 2. Locate your directory, select the three dots > **View details**. 3. Select **Groups**. diff --git a/src/content/docs/cloudflare-one/email-security/directories/manage-integrated-directories/manage-users-directory.mdx b/src/content/docs/cloudflare-one/email-security/directories/manage-integrated-directories/manage-users-directory.mdx index 639a67496e4..2e91646a728 100644 --- a/src/content/docs/cloudflare-one/email-security/directories/manage-integrated-directories/manage-users-directory.mdx +++ b/src/content/docs/cloudflare-one/email-security/directories/manage-integrated-directories/manage-users-directory.mdx @@ -8,11 +8,16 @@ sidebar: order: 4 --- +import { DashButton } from "~/components"; + Email security allows you to view and manage the [impersonation registry](/cloudflare-one/email-security/settings/detection-settings/impersonation-registry/) status of your users directory. To manage users directory: -1. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Email security** > **Directories**. +1. In [Cloudflare dashboard](https://dash.cloudflare.com/), go to **Zero Trust** > **Email security** > **Directories**. + + + 2. Locate your directory, select the three dots > **View details**. 3. Select **Users**. diff --git a/src/content/docs/cloudflare-one/email-security/index.mdx b/src/content/docs/cloudflare-one/email-security/index.mdx index ba5fbeb75d6..c6fc0dfcea4 100644 --- a/src/content/docs/cloudflare-one/email-security/index.mdx +++ b/src/content/docs/cloudflare-one/email-security/index.mdx @@ -8,7 +8,7 @@ sidebar: order: 11 --- -import { Description, Render } from "~/components"; +import { DashButton, Description, Render } from "~/components"; :::caution[Important] Refer to [Area 1](/email-security/) if you are looking for the Area 1 documentation. @@ -39,8 +39,9 @@ The Email security overview provides you with: To access the Email security overview: -1. Log in to [Cloudflare One](https://one.dash.cloudflare.com/). -2. Go to **Email security** > **Overview**. +1. In the [Cloudflare dashboard](https://dash.cloudflare.com/), go to **Zero Trust** > **Email security**. + + --- diff --git a/src/content/docs/cloudflare-one/email-security/investigation/search-email.mdx b/src/content/docs/cloudflare-one/email-security/investigation/search-email.mdx index 014c621a7fc..79c2f467e1c 100644 --- a/src/content/docs/cloudflare-one/email-security/investigation/search-email.mdx +++ b/src/content/docs/cloudflare-one/email-security/investigation/search-email.mdx @@ -8,6 +8,8 @@ sidebar: order: 1 --- +import { DashButton } from "~/components"; + With Email security, you can use different screen criteria to search through your email, reclassify and move a certain volume of messages, find similar emails, and export messages. ## Screen criteria @@ -16,10 +18,12 @@ Email security allows you to use popular, regular, and advanced screening criter To screen through your email traffic: -1. Log in to [Cloudflare One](https://one.dash.cloudflare.com/). -2. Select **Email security**. -3. Select **Investigation**, then **Run new screen**. -4. Choose between **Popular**, **Regular**, and **Advanced** screen methods. Refer to the explanation below to learn what each method does. +1. In the [Cloudflare dashboard](https://dash.cloudflare.com/), go to **Zero Trust** > **Email security** > **Investigation**. + + + +2. Select **Run new screen**. +3. Choose between **Popular**, **Regular**, and **Advanced** screen methods. Refer to the explanation below to learn what each method does. The results will be displayed on a table. The table allows you to review and take action on the messages that match your chosen screening criteria. @@ -81,7 +85,10 @@ Moving messages allows you to move messages to a specific folder. You can move u To move messages: -1. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Email security**, and select **Investigation**. +1. In [Cloudflare dashboard](https://dash.cloudflare.com/), go to **Zero Trust** > **Email security**, and select **Investigation**. + + + 2. On the Investigation page, select all the messages you want to move. 3. Select the **Action** dropdown, then select **Move**. 4. Select among one of the following folders: @@ -100,7 +107,10 @@ Each detection has an Email Detection Fingerprint (EDF) hash that Email security To find similar detection results: -1. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Email security**, and select **Investigation**. +1. In [Cloudflare dashboard](https://dash.cloudflare.com/), go to **Zero Trust** > **Email security**, and select **Investigation**. + + + 2. On the Investigation page, under **Your matching messages**, search for the **Similar emails** column. 3. Select the number of similar emails. Selecting the number will show you a list of similar emails. @@ -110,7 +120,10 @@ With Email security, you can export messages to a CSV file. To export messages: -1. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Email security**, and select **Investigation**. +1. In [Cloudflare dashboard](https://dash.cloudflare.com/), go to **Zero Trust** > **Email security**, and select **Investigation**. + + + 2. On the Investigation page, under **Your matching messages**, select **Export to CSV**. 3. Select **Export messages** on the pop-up message. You can export up to 500 messages from the dashboard. To export up to 1,000 matching messages, use the [API](/api/resources/email_security/subresources/investigate/methods/get/). @@ -122,7 +135,10 @@ Email security allows you to review the status and actions of each email. To view status and actions for each email: -1. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Email security**, and select **Investigation**. +1. In [Cloudflare dashboard](https://dash.cloudflare.com/), go to **Zero Trust** > **Email security**, and select **Investigation**. + + + 2. On the Investigation page, select the three dots. 3. Selecting the three dots will show you the following options: @@ -182,7 +198,10 @@ Browser Isolation eliminates any risk of your device being compromised by openin To open links in Security Center: -1. In [Cloudflare One](https://one.dash.cloudflare.com), go to **Email security** > **Investigation**. +1. In [Cloudflare dashboard](https://dash.cloudflare.com/), go to **Zero Trust** > **Email security** > **Investigation**. + + + 2. Locate the message you want to open links for, select the three dots, then select **View details**. 3. Under **Details**, go to **Links identified**. 4. Locate the link you want to open, and select **Open in Security Center**. @@ -192,7 +211,10 @@ To open links in Security Center: To open links in Browser Isolation: -1. In [Cloudflare One](https://one.dash.cloudflare.com), go to **Email security** > **Investigation**. +1. In [Cloudflare dashboard](https://dash.cloudflare.com/), go to **Zero Trust** > **Email security** > **Investigation**. + + + 2. Locate the message you want to open links for, select the three dots, then select **View details**. 3. Under **Details**, go to **Links identified**. 4. Locate the link you want to open, and select **Open in Browser Isolation**. @@ -208,7 +230,10 @@ If you purchased Gateway and [Browser Isolation](/cloudflare-one/remote-browser- To open and investigate a link in an external tool: -1. In [Cloudflare One](https://one.dash.cloudflare.com), go to **Email security** > **Investigation**. +1. In [Cloudflare dashboard](https://dash.cloudflare.com/), go to **Zero Trust** > **Email security** > **Investigation**. + + + 2. Locate the message you want to open links for, select the three dots, then select **View details**. 3. Under **Details**, go to **Links identified**. 4. Locate the link you want to open, and select **Copy URL**. @@ -220,7 +245,10 @@ You may encounter a `400 Bad Request` error after turning Clientless Web Isolati If you encounter this error: -1. In [Cloudflare One](https://one.dash.cloudflare.com), go to **Settings** > **Resources**. +1. In [Cloudflare dashboard](https://dash.cloudflare.com/), go to **Zero Trust** > **Settings** > **Resources**. + + + 2. Select **Generate certificate**. 3. Choose the **Expiration** (5 years is recommended), then select **Generate certificate**. Your certificate is now generated, and the dashboard will display its Deployment Status as INACTIVE. 4. Select the three dots, and then select **Activate** to activate your certificate. diff --git a/src/content/docs/cloudflare-one/email-security/monitoring/download-report.mdx b/src/content/docs/cloudflare-one/email-security/monitoring/download-report.mdx index f1a29cdbe29..294b0dcb5ed 100644 --- a/src/content/docs/cloudflare-one/email-security/monitoring/download-report.mdx +++ b/src/content/docs/cloudflare-one/email-security/monitoring/download-report.mdx @@ -8,6 +8,8 @@ sidebar: order: 3 --- +import { DashButton } from "~/components"; + Email security allows you to download three types of reports: - Disposition report @@ -18,7 +20,10 @@ Email security allows you to download three types of reports: A disposition report shows you all the email messages based on the type of disposition you selected. -1. In [Cloudflare One](https://one.dash.cloudflare.com/), select **Email security**. +1. In [Cloudflare dashboard](https://dash.cloudflare.com/), go to **Zero Trust** > **Email security**. + + + 2. Select **Monitoring** > **Download report**. 3. In **Report type**, select **Email disposition report**. 4. Under **Email disposition report**, select the **Date Range** (required), and the **Disposition**. @@ -30,7 +35,10 @@ Refer to [Dispositions and attributes](/cloudflare-one/email-security/reference/ Retro scan scans the last 14 days of your emails, and gives you a report on bulk, spam, spoof, suspicious and malicious emails. -1. In [Cloudflare One](https://one.dash.cloudflare.com/), select **Email security**. +1. In [Cloudflare dashboard](https://dash.cloudflare.com/), go to **Zero Trust** > **Email security**. + + + 2. Select **Monitoring** > **Download report**. 3. In **Report type**, select **Retro Scan report**. 4. Select **View report** to view a report of your last 14 days of emails. @@ -49,7 +57,10 @@ The reports contains: To download a security report: -1. In [Cloudflare One](https://one.dash.cloudflare.com/), select **Email security**. +1. In [Cloudflare dashboard](https://dash.cloudflare.com/), go to **Zero Trust** > **Email security**. + + + 2. Select **Monitoring** > **Download report**. 3. In **Report type**, select **Security report** and the **Date range**. 4. Select **Generate report**. diff --git a/src/content/docs/cloudflare-one/email-security/monitoring/index.mdx b/src/content/docs/cloudflare-one/email-security/monitoring/index.mdx index ea58b10a9fd..81b180893a8 100644 --- a/src/content/docs/cloudflare-one/email-security/monitoring/index.mdx +++ b/src/content/docs/cloudflare-one/email-security/monitoring/index.mdx @@ -8,7 +8,7 @@ sidebar: order: 12 --- -import { GlossaryTooltip, Render } from "~/components"; +import { DashButton, GlossaryTooltip, Render } from "~/components"; Once you have chosen a domain to scan, Email security allows you to monitor the traffic scanned from your email inboxes. @@ -18,9 +18,9 @@ With Email security, you can enable logs to send detection data to an endpoint o To monitor your inbox: -1. Log in to [Cloudflare One](https://one.dash.cloudflare.com/). -2. Select **Email security**. -3. Under **Email security**, select **Monitoring**. +1. In the [Cloudflare dashboard](https://dash.cloudflare.com/), go to **Zero Trust** > **Email security** > **Monitoring**. + + The dashboard will display the following metrics: diff --git a/src/content/docs/cloudflare-one/email-security/phishguard.mdx b/src/content/docs/cloudflare-one/email-security/phishguard.mdx index 7509b89fc68..6dc9f964f2c 100644 --- a/src/content/docs/cloudflare-one/email-security/phishguard.mdx +++ b/src/content/docs/cloudflare-one/email-security/phishguard.mdx @@ -8,6 +8,8 @@ sidebar: order: 17 --- +import { DashButton } from "~/components"; + PhishGuard is a team of analysts that routinely inspects your email environment and responds to threats that come through your email inbox. While Email security uses advanced technologies to protect your email inbox, PhishGuard offers an additional human component to protect your email environment against impersonation events, suspicious items, false negatives/false positives, and any new event that automated intelligent systems may miss due to a lack of context (for example, a compromised account activity). @@ -28,9 +30,9 @@ Additionally, PhishGuard analysts: To use PhishGuard: -1. Log in to [Cloudflare One](https://one.dash.cloudflare.com/). -2. Select **Email security**. -3. Select **PhishGuard**. +1. In the [Cloudflare dashboard](https://dash.cloudflare.com/), go to **Zero Trust** > **Email security** > **PhishGuard**. + + The dashboard will display the following metrics: diff --git a/src/content/docs/cloudflare-one/email-security/retro-scan.mdx b/src/content/docs/cloudflare-one/email-security/retro-scan.mdx index 4b91685fbaa..57720ec21e1 100644 --- a/src/content/docs/cloudflare-one/email-security/retro-scan.mdx +++ b/src/content/docs/cloudflare-one/email-security/retro-scan.mdx @@ -10,6 +10,8 @@ tags: - Microsoft --- +import { DashButton } from "~/components"; + Use Retro Scan to check whether your current email security provider has missed any threats. Cloudflare scans up to 14 days of emails in your Microsoft 365 mailbox and generates a report of malicious messages. Once the scan is complete, you will receive an email notification with a link to the report. :::note @@ -18,16 +20,18 @@ Retro Scan is only available for Microsoft 365 accounts. To start a free scan: -1. Log in to [Cloudflare One](https://one.dash.cloudflare.com/). -2. Select **Email security** > **Overview**. -3. Select **Start a free scan** > **Generate report**. -4. Enable your [Microsoft integration](/cloudflare-one/email-security/setup/post-delivery-deployment/api/m365-api/#enable-microsoft-integration). Once you have enabled your Microsoft integration, you will be redirected to a page where you will add your domains and specify your current email security system. -5. Generate Retro Scan report: +1. In the [Cloudflare dashboard](https://dash.cloudflare.com/), go to **Zero Trust** > **Email security** > **Retro Scan**. + + + +2. Select **Start a free scan** > **Generate report**. +3. Enable your [Microsoft integration](/cloudflare-one/email-security/setup/post-delivery-deployment/api/m365-api/#enable-microsoft-integration). Once you have enabled your Microsoft integration, you will be redirected to a page where you will add your domains and specify your current email security system. +4. Generate Retro Scan report: - **Connect domains**: Select at least one domain from your integration, then select **Continue**. - **Select current solution**: Select the email security tool you are currently using, then select **Continue**. - **Review details**: Confirm the domain and current solution you selected, then select **Continue**. You will receive an email notification once the report is ready. -6. When you receive the notification email, select the link to view the full report. -7. On the Cloudflare dashboard, select **View report**. +5. When you receive the notification email, select the link to view the full report. +6. On the Cloudflare dashboard, select **View report**. The dashboard will display **Overview** and **Details** pages. diff --git a/src/content/docs/cloudflare-one/email-security/settings/auto-moves.mdx b/src/content/docs/cloudflare-one/email-security/settings/auto-moves.mdx index 04516541176..06b5ea74c2c 100644 --- a/src/content/docs/cloudflare-one/email-security/settings/auto-moves.mdx +++ b/src/content/docs/cloudflare-one/email-security/settings/auto-moves.mdx @@ -14,7 +14,7 @@ Use auto-moves to enforce email security policy without relying on end users to To configure auto-move events: -1. Log in to [Cloudflare One](https://one.dash.cloudflare.com/). +1. Log in to [Cloudflare dashboard](https://dash.cloudflare.com/). 2. Select **Email security**. 3. Select **Settings**. 4. Select **Moves**. diff --git a/src/content/docs/cloudflare-one/email-security/settings/detection-settings/additional-detections.mdx b/src/content/docs/cloudflare-one/email-security/settings/detection-settings/additional-detections.mdx index 419a402e04f..756927e7163 100644 --- a/src/content/docs/cloudflare-one/email-security/settings/detection-settings/additional-detections.mdx +++ b/src/content/docs/cloudflare-one/email-security/settings/detection-settings/additional-detections.mdx @@ -17,7 +17,7 @@ Email security allows you to configure the following additional detections: To configure additional detections: -1. Log in to [Cloudflare One](https://one.dash.cloudflare.com/). +1. Log in to [Cloudflare dashboard](https://dash.cloudflare.com/). 2. Select **Email security**. 3. Select **Settings**. 4. On the **Settings** page, go to **Detection settings** > **Additional detections**, and select **Edit**. diff --git a/src/content/docs/cloudflare-one/email-security/settings/detection-settings/allow-policies.mdx b/src/content/docs/cloudflare-one/email-security/settings/detection-settings/allow-policies.mdx index d12d8110a67..d073ca80aad 100644 --- a/src/content/docs/cloudflare-one/email-security/settings/detection-settings/allow-policies.mdx +++ b/src/content/docs/cloudflare-one/email-security/settings/detection-settings/allow-policies.mdx @@ -220,7 +220,7 @@ Below you can find a list of known services you can add when configuring an Acce To configure allow policies: -1. Log in to [Cloudflare One](https://one.dash.cloudflare.com/). +1. Log in to [Cloudflare dashboard](https://dash.cloudflare.com/). 2. Select **Email security**. 3. Select **Settings**, then go to **Detection settings** > **Allow policies**. 4. On the **Detection settings** page, select **Add a policy**. diff --git a/src/content/docs/cloudflare-one/email-security/settings/detection-settings/blocked-senders.mdx b/src/content/docs/cloudflare-one/email-security/settings/detection-settings/blocked-senders.mdx index 1aa39217251..8880fa8e288 100644 --- a/src/content/docs/cloudflare-one/email-security/settings/detection-settings/blocked-senders.mdx +++ b/src/content/docs/cloudflare-one/email-security/settings/detection-settings/blocked-senders.mdx @@ -20,7 +20,7 @@ Sometimes, the same email, IP address or domain always sends malicious emails to To configure blocked senders: -1. Log in to [Cloudflare One](https://one.dash.cloudflare.com/). +1. Log in to [Cloudflare dashboard](https://dash.cloudflare.com/). 2. Select **Email security**. 3. Select **Settings**, go to **Detection settings** > **Blocked senders**. 4. On the **Detection settings** page, select **Add a sender**. diff --git a/src/content/docs/cloudflare-one/email-security/settings/detection-settings/configure-link-actions.mdx b/src/content/docs/cloudflare-one/email-security/settings/detection-settings/configure-link-actions.mdx index 8b057faa60a..212fe82a630 100644 --- a/src/content/docs/cloudflare-one/email-security/settings/detection-settings/configure-link-actions.mdx +++ b/src/content/docs/cloudflare-one/email-security/settings/detection-settings/configure-link-actions.mdx @@ -16,7 +16,7 @@ You can only configure link actions if you deploy Email security via [MX/Inline] To configure link actions: -1. Log in to [Cloudflare One](https://one.dash.cloudflare.com/). +1. Log in to [Cloudflare dashboard](https://dash.cloudflare.com/). 2. Select **Email security**. 3. Select **Settings**, then go to **Detection settings** > **Link actions** > **View**. diff --git a/src/content/docs/cloudflare-one/email-security/settings/detection-settings/configure-text-add-ons.mdx b/src/content/docs/cloudflare-one/email-security/settings/detection-settings/configure-text-add-ons.mdx index a41eb64e5d9..e41c8b98105 100644 --- a/src/content/docs/cloudflare-one/email-security/settings/detection-settings/configure-text-add-ons.mdx +++ b/src/content/docs/cloudflare-one/email-security/settings/detection-settings/configure-text-add-ons.mdx @@ -22,7 +22,7 @@ If you currently do not have text add-ons enabled, configuring text add-ons will To configure a subject prefix: -1. Log in to [Cloudflare One](https://one.dash.cloudflare.com/). +1. Log in to [Cloudflare dashboard](https://dash.cloudflare.com/). 2. Select **Email security**. 3. Select **Settings**, then go to **Detection settings** > **Text add-ons** > **View**. 4. Select **Configure** > **Subject prefix**. diff --git a/src/content/docs/cloudflare-one/email-security/settings/detection-settings/impersonation-registry.mdx b/src/content/docs/cloudflare-one/email-security/settings/detection-settings/impersonation-registry.mdx index 9e1d2c97c8b..01e19f92ed2 100644 --- a/src/content/docs/cloudflare-one/email-security/settings/detection-settings/impersonation-registry.mdx +++ b/src/content/docs/cloudflare-one/email-security/settings/detection-settings/impersonation-registry.mdx @@ -19,7 +19,7 @@ For easier tracking, the Email security team recommends syncing and structuring To add a user to the impersonation registry: -1. Log in to [Cloudflare One](https://one.dash.cloudflare.com/). +1. Log in to [Cloudflare dashboard](https://dash.cloudflare.com/). 2. Select **Email security**. 3. Select **Settings** > **Impersonation registry**. 4. Select **Add a user**. diff --git a/src/content/docs/cloudflare-one/email-security/settings/detection-settings/trusted-domains.mdx b/src/content/docs/cloudflare-one/email-security/settings/detection-settings/trusted-domains.mdx index bed68554ed1..00a5e765299 100644 --- a/src/content/docs/cloudflare-one/email-security/settings/detection-settings/trusted-domains.mdx +++ b/src/content/docs/cloudflare-one/email-security/settings/detection-settings/trusted-domains.mdx @@ -8,6 +8,8 @@ sidebar: order: 3 --- +import { DashButton } from "~/components"; + Email security allows you to exempt known partner and internal domains from typical detection scanning. Adding trusted domains helps to reduce false positives on malicious, suspicious, and spoof [dispositions](/cloudflare-one/email-security/reference/dispositions-and-attributes/). Email security only checks the date when the domain is created. ## How trusted domains work @@ -26,7 +28,10 @@ Suspicious domain age means that after 7 days (this number corresponds to the Ma To view whether a domain is malicious or suspicious: -1. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Investigation**. +1. In [Cloudflare dashboard](https://dash.cloudflare.com/), go to **Zero Trust** > **Investigation**. + + + 2. Run a screen. For example, select **Run screen** for **Malicious emails**, then select **Run screen**. 3. Under **Your matching messages**, if any message displays **Domain Age** under **Threat types**, that means that the domain age is too low, and therefore the disposition assigned is Malicious. If the domain is legitimate, you can add it as a trusted domain: - Go to **Settings** > **Trusted Domains**. @@ -36,7 +41,7 @@ To view whether a domain is malicious or suspicious: To configure a trusted domain: -1. Log in to [Cloudflare One](https://one.dash.cloudflare.com/). +1. Log in to [Cloudflare dashboard](https://dash.cloudflare.com/). 2. Select **Email security**. 3. Select **Settings**, go to **Detection settings** > **Trusted domains**. 4. On the **Detection settings** page, select **Add a domain**. diff --git a/src/content/docs/cloudflare-one/email-security/settings/phish-submissions/index.mdx b/src/content/docs/cloudflare-one/email-security/settings/phish-submissions/index.mdx index b7a8e1e860f..39930b858ed 100644 --- a/src/content/docs/cloudflare-one/email-security/settings/phish-submissions/index.mdx +++ b/src/content/docs/cloudflare-one/email-security/settings/phish-submissions/index.mdx @@ -22,7 +22,7 @@ There are three routes you can use to report an email as a phish: ## Reclassify an email -1. Log in to [Cloudflare One](https://one.dash.cloudflare.com/). +1. Log in to [Cloudflare dashboard](https://dash.cloudflare.com/). 2. Select **Email security** > **Investigation**. 3. On the **Investigation** page, under **Your matching messages**, select the message you want to reclassify. Select the three dots, then select **Submit for review**. By selecting **Submit for review**, you are requesting a new disposition for the message. 4. Select the new disposition, then select **Save**. diff --git a/src/content/docs/cloudflare-one/email-security/settings/phish-submissions/phishnet-365.mdx b/src/content/docs/cloudflare-one/email-security/settings/phish-submissions/phishnet-365.mdx index 03b7792d24a..681dd2a1c9d 100644 --- a/src/content/docs/cloudflare-one/email-security/settings/phish-submissions/phishnet-365.mdx +++ b/src/content/docs/cloudflare-one/email-security/settings/phish-submissions/phishnet-365.mdx @@ -16,7 +16,7 @@ PhishNet is an add-in button that helps users to submit directly to Email securi To set up PhishNet Microsoft 365: -1. Get the customized manifest URL from [Cloudflare One](https://one.dash.cloudflare.com/?to=/:account/email-security/settings/email-policy/phish-submission?tab=phish-submission). +1. Get the customized manifest URL from [Cloudflare One](https://dash.cloudflare.com/?to=/:account/one/email-security/settings/email-policy/phish-submission?tab=phish-submission). 2. Log in to the [Microsoft admin panel](https://admin.microsoft.com/). 3. Go to **Microsoft 365 admin center** > **Settings** > **Integrated Apps**. 4. Select **Upload custom apps**. diff --git a/src/content/docs/cloudflare-one/email-security/settings/phish-submissions/submission-addresses.mdx b/src/content/docs/cloudflare-one/email-security/settings/phish-submissions/submission-addresses.mdx index 9e049608ac6..0c2cdff46ae 100644 --- a/src/content/docs/cloudflare-one/email-security/settings/phish-submissions/submission-addresses.mdx +++ b/src/content/docs/cloudflare-one/email-security/settings/phish-submissions/submission-addresses.mdx @@ -10,7 +10,7 @@ sidebar: To view the destination addresses of user and team submissions: -1. Log in to [Cloudflare One](https://one.dash.cloudflare.com/). +1. Log in to [Cloudflare dashboard](https://dash.cloudflare.com/). 2. Select **Email security**. 3. Select **Settings**. 4. Go to **Phish submission** > **Submission addresses** > **View**. diff --git a/src/content/docs/cloudflare-one/email-security/setup/manage-domains.mdx b/src/content/docs/cloudflare-one/email-security/setup/manage-domains.mdx index 5c704f3a770..d7356172ef2 100644 --- a/src/content/docs/cloudflare-one/email-security/setup/manage-domains.mdx +++ b/src/content/docs/cloudflare-one/email-security/setup/manage-domains.mdx @@ -13,7 +13,7 @@ Once you have deployed your domain, Email security allows you to add, filter and To protect a new domain: -1. Log in to [Cloudflare One](https://one.dash.cloudflare.com) > Email security. +1. Log in to [Cloudflare dashboard](https://dash.cloudflare.com/) > Email security. 2. Select **Settings**, go to **Domains** and select **View**. 3. Select **Add a domain**. @@ -21,7 +21,7 @@ To protect a new domain: To filter your domains: -1. Log in to [Cloudflare One](https://one.dash.cloudflare.com/) > **Email security**. +1. Log in to [Cloudflare dashboard](https://dash.cloudflare.com/) > **Email security**. 2. Go to **Settings** > **Domain management** > **Domains**, then select **View**. 3. Select **Show filters** > **Configured method**. Choose among the following filters: - **MS Graph API**: To view domains connected via MS Graph API. - **BCC/Journaling**: To view domains connected via BCC/Journaling. - **MX/Inline**: To view domains connected via MX/Inline. - **Retro Scan**: To view domains scanned by Retro Scan. 4. Select **Apply filters**. @@ -30,7 +30,7 @@ To filter your domains: To edit your domains: -1. Log in to [Cloudflare One](https://one.dash.cloudflare.com/) > **Email security**. +1. Log in to [Cloudflare dashboard](https://dash.cloudflare.com/) > **Email security**. 2. Go to **Settings** > **Domain management** > **Domains**, then select **View**. 3. On the **Domains** page, locate your domain, select the three dots > **Edit**. 4. If you did not manually add your domain, you will only be able to edit **Hops**. If you manually added your domain, you will be able to edit **Domain name** and **Hops**. @@ -40,7 +40,7 @@ To edit your domains: To stop scanning domains: -1. Log in to [Cloudflare One](https://one.dash.cloudflare.com/) > **Email security**. +1. Log in to [Cloudflare dashboard](https://dash.cloudflare.com/) > **Email security**. 2. Go to **Settings** > **Domain management** > **Domains**, then select **View**. 3. On the **Domains** page, locate your domain, select the three dots > **Stop scanning**. 4. Select **Stop scanning** again to stop Cloudflare from scanning your domain. \ No newline at end of file diff --git a/src/content/docs/cloudflare-one/email-security/setup/post-delivery-deployment/api/m365-api.mdx b/src/content/docs/cloudflare-one/email-security/setup/post-delivery-deployment/api/m365-api.mdx index fdd6e5cc02d..e2d47c2a720 100644 --- a/src/content/docs/cloudflare-one/email-security/setup/post-delivery-deployment/api/m365-api.mdx +++ b/src/content/docs/cloudflare-one/email-security/setup/post-delivery-deployment/api/m365-api.mdx @@ -10,7 +10,7 @@ sidebar: order: 3 --- -import { Render } from "~/components"; +import { DashButton, Render } from "~/components"; This guide will instruct you through setting up Microsoft 365 with Email security via the Cloudflare dashboard. @@ -25,7 +25,10 @@ To use Email security, you will need to have: ## Enable Email security via the dashboard -1. Log in to [Cloudflare One](https://one.dash.cloudflare.com/) and select **Email security**.. +1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/) and go to **Zero Trust** > **Email security**. + + + 2. Select **Overview**. Select one of the following options depending on your use case: - If you have not purchased Email security, select **Contact sales**. @@ -68,7 +71,10 @@ Your domains are now connected successfully. To connect new domains: -1. In [Cloudflare One](https://one.dash.cloudflare.com/), select **Email security**. +1. In [Cloudflare dashboard](https://dash.cloudflare.com/), go to **Zero Trust** > **Email security**. + + + 2. Select **Settings** > **Domain management** > **Domains**, then select **View**. 3. Select **Add a domain**. 4. Select a method for connecting your mail environment to Email security: @@ -82,7 +88,10 @@ To connect new domains: If you want to prevent Cloudflare from scanning a domain: -1. In [Cloudflare One](https://one.dash.cloudflare.com/), select **Email security**. +1. In [Cloudflare dashboard](https://dash.cloudflare.com/), go to **Zero Trust** > **Email security**. + + + 2. Go to **Settings** > **Domain management** > **Domains**, then select **View**. 3. On the **Domain management** page, select the domain you do not want to be scanned. 4. Select the three dots > **Stop scanning**. @@ -91,7 +100,10 @@ If you want to prevent Cloudflare from scanning a domain: To view the integration for each connected domain: -1. In [Cloudflare One](https://one.dash.cloudflare.com/), select **Email security**. +1. In [Cloudflare dashboard](https://dash.cloudflare.com/), go to **Zero Trust** > **Email security**. + + + 2. Go to **Settings** > **Domain management** > **Domains**, then select **View**. 3. Select a domain. 4. Select the three dots > **View integration**. diff --git a/src/content/docs/cloudflare-one/email-security/setup/post-delivery-deployment/bcc-journaling/bcc-setup/gmail-bcc-setup/add-bcc-rules.mdx b/src/content/docs/cloudflare-one/email-security/setup/post-delivery-deployment/bcc-journaling/bcc-setup/gmail-bcc-setup/add-bcc-rules.mdx index a18a3bcf4d6..7adb26344b9 100644 --- a/src/content/docs/cloudflare-one/email-security/setup/post-delivery-deployment/bcc-journaling/bcc-setup/gmail-bcc-setup/add-bcc-rules.mdx +++ b/src/content/docs/cloudflare-one/email-security/setup/post-delivery-deployment/bcc-journaling/bcc-setup/gmail-bcc-setup/add-bcc-rules.mdx @@ -8,6 +8,8 @@ sidebar: order: 4 --- +import { DashButton } from "~/components"; + This page will show you how to add BCC rules in the Google Admin Console. BCC stands for Blind Carbon Copy. A BCC rule is a Google Workspace feature that allows you to create a secure copy of all selected outbound and inbound emails. When you allow Email security to receive a copy of your emails, Cloudflare can perform post-delivery analysis to protect your email inbox. @@ -32,7 +34,7 @@ To add BCC rules: - Ensure that **Envelope recipient** > **Change envelope recipient** is unselected, so that emails will not be dropped as an unintended consequence. You will select this option at a later stage. - Go to **Also deliver to**, select **Add more recipients** > **ADD** > Choose **Advanced**: - Under **Envelope recipient**, select **Change envelope recipient** > **Replace recipient** > Enter the service address. This is the service address you copied and pasted in step 5 when [connecting your domains](/cloudflare-one/email-security/setup/post-delivery-deployment/bcc-journaling/bcc-setup/gmail-bcc-setup/connect-domains/). - If you did not copy and paste the service address: - In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Email security**. - Go to **Settings** and locate your domain under **Your domains**. - Select the three dots > **View domain** > **Service address**. Copy and paste the service address. + If you did not copy and paste the service address: - In [Cloudflare dashboard](https://dash.cloudflare.com/), go to **Zero Trust** > **Email security**. - Go to **Settings** and locate your domain under **Your domains**. - Select the three dots > **View domain** > **Service address**. Copy and paste the service address. - Under **Spam and delivery options**, ensure **Suppress bounces from this recipient** is not enabled. - Under **Headers**, select **Add X-Gm-Spam and X-Gm-Phishy headers**. - Select **SAVE**. @@ -41,6 +43,9 @@ To add BCC rules: To verify that BCC rules have been configured successfully: -1. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Email security** > **Settings**. +1. In [Cloudflare dashboard](https://dash.cloudflare.com/), go to **Zero Trust** > **Email security** > **Settings**. + + + 2. Select **Domains** > **View**. 3. Locate your domain. Under Status, the dashboard should display **Active**. This means that the BCC rules have been configured successfully, and your mail flow is being detected. diff --git a/src/content/docs/cloudflare-one/email-security/setup/post-delivery-deployment/bcc-journaling/bcc-setup/gmail-bcc-setup/connect-domains.mdx b/src/content/docs/cloudflare-one/email-security/setup/post-delivery-deployment/bcc-journaling/bcc-setup/gmail-bcc-setup/connect-domains.mdx index 0d6916e81d6..8e51e348ef3 100644 --- a/src/content/docs/cloudflare-one/email-security/setup/post-delivery-deployment/bcc-journaling/bcc-setup/gmail-bcc-setup/connect-domains.mdx +++ b/src/content/docs/cloudflare-one/email-security/setup/post-delivery-deployment/bcc-journaling/bcc-setup/gmail-bcc-setup/connect-domains.mdx @@ -8,7 +8,7 @@ sidebar: order: 3 --- -import { GlossaryTooltip, Render } from "~/components"; +import { DashButton, GlossaryTooltip, Render } from "~/components"; To connect your domains, you will need to [enable your Gmail BCC integration](/cloudflare-one/email-security/setup/post-delivery-deployment/bcc-journaling/bcc-setup/gmail-bcc-setup/enable-gmail-integration/#enable-gmail-bcc-integration). Once you have enabled your Gmail BCC integration, the Cloudflare dashboard will redirect you to the **Set up Email security** page. @@ -31,7 +31,10 @@ Under **Source**, the dashboard will display **Google integration**, along with To add additional domains: -1. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Email security** > **Settings**. +1. In [Cloudflare dashboard](https://dash.cloudflare.com/), go to **Zero Trust** > **Email security** > **Settings**. + + + 2. Select **Connect an integration** > **BCC/Journaling** > **Integrate with Google** > **Authorize**. 3. **Connect domains**: Select the domains you want to add, then select **Next**. 4. (Optional) Select **Add manual domains**: Enter additional domains manually, then select **Next**. diff --git a/src/content/docs/cloudflare-one/email-security/setup/post-delivery-deployment/bcc-journaling/bcc-setup/gmail-bcc-setup/enable-auto-moves.mdx b/src/content/docs/cloudflare-one/email-security/setup/post-delivery-deployment/bcc-journaling/bcc-setup/gmail-bcc-setup/enable-auto-moves.mdx index a31864db847..9dde6da0a92 100644 --- a/src/content/docs/cloudflare-one/email-security/setup/post-delivery-deployment/bcc-journaling/bcc-setup/gmail-bcc-setup/enable-auto-moves.mdx +++ b/src/content/docs/cloudflare-one/email-security/setup/post-delivery-deployment/bcc-journaling/bcc-setup/gmail-bcc-setup/enable-auto-moves.mdx @@ -8,9 +8,14 @@ sidebar: order: 5 --- +import { DashButton } from "~/components"; + If you do not have an integration: -1. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Email security**. +1. In [Cloudflare dashboard](https://dash.cloudflare.com/), go to **Zero Trust** > **Email security**. + + + 2. Go to **Settings** > **Domain management** > **Domains** > select **View**. 3. Locate your domain, select the three dots > Select **Associate an integration**. 4. Select **Connect an integration**. You will then be redirected to the **Add an integration** page. diff --git a/src/content/docs/cloudflare-one/email-security/setup/post-delivery-deployment/bcc-journaling/bcc-setup/gmail-bcc-setup/enable-gmail-integration.mdx b/src/content/docs/cloudflare-one/email-security/setup/post-delivery-deployment/bcc-journaling/bcc-setup/gmail-bcc-setup/enable-gmail-integration.mdx index 5c0e77741d6..b4cd24d7931 100644 --- a/src/content/docs/cloudflare-one/email-security/setup/post-delivery-deployment/bcc-journaling/bcc-setup/gmail-bcc-setup/enable-gmail-integration.mdx +++ b/src/content/docs/cloudflare-one/email-security/setup/post-delivery-deployment/bcc-journaling/bcc-setup/gmail-bcc-setup/enable-gmail-integration.mdx @@ -10,7 +10,7 @@ sidebar: order: 2 --- -import { Render } from "~/components"; +import { DashButton, Render } from "~/components"; This guide describes the process for enabling Email security with Google Workspace. It requires setting up a [service account](https://docs.cloud.google.com/iam/docs/service-account-overview) and a JSON key in Google Cloud Platform (GCP), followed by configuring domain-wide delegation in the Google Workspace Admin Console to authorize the integration. @@ -25,7 +25,7 @@ To use Email security, you will need to have: ## Enable Gmail BCC integration: -1. Log in to [Cloudflare One](https://one.dash.cloudflare.com/). +1. Log in to [Cloudflare dashboard](https://dash.cloudflare.com/). 2. Select **Email security**. 3. Select **Overview**. Select one of the following options: @@ -62,7 +62,7 @@ On the [Google Cloud Console](https://console.cloud.google.com/welcome/new): ### 3. Upload JSON Key -On the [Cloudflare One dashboard](https://one.dash.cloudflare.com/), upload the `.json` file downloaded on step 3. +On the [Cloudflare dashboard](https://dash.cloudflare.com/), upload the `.json` file downloaded on step 3. ### 4. Enable Necessary Google Workspace APIs in GCP @@ -99,7 +99,10 @@ Enter the email associated with the Google Workspace Administrator account. Your To verify that the integration has been successful: -1. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Integrations**. +1. In [Cloudflare dashboard](https://dash.cloudflare.com/), go to **Zero Trust** > **Integrations**. + + + 2. Under **Your integrations**, locate your integration, and ensure that the integration displays **CASB+EMAIL** under **Type**. :::note diff --git a/src/content/docs/cloudflare-one/email-security/setup/post-delivery-deployment/bcc-journaling/journaling-setup/m365-journaling.mdx b/src/content/docs/cloudflare-one/email-security/setup/post-delivery-deployment/bcc-journaling/journaling-setup/m365-journaling.mdx index 8ff736556bd..cb7e7dee2cf 100644 --- a/src/content/docs/cloudflare-one/email-security/setup/post-delivery-deployment/bcc-journaling/journaling-setup/m365-journaling.mdx +++ b/src/content/docs/cloudflare-one/email-security/setup/post-delivery-deployment/bcc-journaling/journaling-setup/m365-journaling.mdx @@ -10,7 +10,7 @@ sidebar: order: 2 --- -import { GlossaryTooltip, Render } from "~/components"; +import { DashButton, GlossaryTooltip, Render } from "~/components"; Microsoft 365 journaling is a post-delivery setup method that ensures a copy of every incoming and outgoing email is forwarded to Cloudflare for analysis. When you create a [journal rule](https://learn.microsoft.com/en-us/exchange/security-and-compliance/journaling/journaling#journal-rules) in the Microsoft Purview compliance portal, Cloudflare can scan messages that have already landed in your inbox. @@ -20,7 +20,7 @@ The following diagram shows how this works: To enable Microsoft 365 journaling deployment: -1. Log in to [Cloudflare One](https://one.dash.cloudflare.com/) > **Email security**. +1. Log in to [Cloudflare dashboard](https://dash.cloudflare.com/) > **Email security**. 2. Select **Overview**. If you have not purchased Email security, select **Contact Sales**. Otherwise, select **Set up** > **BCC/Journaling**. 3. Select **Integrate with MS** > **Authorize**. 4. Continue with [Integrate with Microsoft 365](/cloudflare-one/email-security/setup/post-delivery-deployment/bcc-journaling/journaling-setup/m365-journaling/#1-integrate-with-microsoft-365) to connect your Microsoft integration. @@ -91,7 +91,10 @@ Once saved, the rule is automatically active. However, it may take a few minutes To verift that your domain has been added successfully and that your emails are being scanned: -1. In [Cloudflare One](https://one.dash.cloudflare.com/), select **Email security**. +1. In [Cloudflare dashboard](https://dash.cloudflare.com/), go to **Zero Trust** > **Email security**. + + + 2. Go to **Settings** > **Domain management** > **Domains**, then select **View**. 3. Under **Your domains**, locate your domain, and verify that **Status** is set to **Active**. The **Configured method** should be **BCC/Journaling**. diff --git a/src/content/docs/cloudflare-one/email-security/setup/post-delivery-deployment/bcc-journaling/journaling-setup/manual-add.mdx b/src/content/docs/cloudflare-one/email-security/setup/post-delivery-deployment/bcc-journaling/journaling-setup/manual-add.mdx index 4c636aa1972..7d0371dda53 100644 --- a/src/content/docs/cloudflare-one/email-security/setup/post-delivery-deployment/bcc-journaling/journaling-setup/manual-add.mdx +++ b/src/content/docs/cloudflare-one/email-security/setup/post-delivery-deployment/bcc-journaling/journaling-setup/manual-add.mdx @@ -25,7 +25,7 @@ To use Email security, you will need to have: ## Manually add domains -1. Log in to [Cloudflare One](https://one.dash.cloudflare.com/) > **Email security**. +1. Log in to [Cloudflare dashboard](https://dash.cloudflare.com/) > **Email security**. 2. Select **Overview**. If you have not purchased Email security, select **Contact Sales**. Otherwise, select **Set up** > **BCC/Journaling**. 3. Select **Manual add**. @@ -66,7 +66,7 @@ To enable auto-move events, you will have to associate an integration. To associate an integration: -1. Log in to [Cloudflare One](https://one.dash.cloudflare.com/) > **Email security**. +1. Log in to [Cloudflare dashboard](https://dash.cloudflare.com/) > **Email security**. 2. Go to **Settings** > **Domain management** > **Domains** > Select **View**. 3. On the **Domain management** page, locate your domain, select the three dots, then select **Associate an integration**. 4. Select **Connect an integration**. Follow the steps to [enable the Microsoft 365 integration](/cloudflare-one/email-security/setup/post-delivery-deployment/api/m365-api/#enable-microsoft-integration). diff --git a/src/content/docs/cloudflare-one/email-security/setup/pre-delivery-deployment/mx-inline-deployment-setup.mdx b/src/content/docs/cloudflare-one/email-security/setup/pre-delivery-deployment/mx-inline-deployment-setup.mdx index ccf3b139b35..91a529d672a 100644 --- a/src/content/docs/cloudflare-one/email-security/setup/pre-delivery-deployment/mx-inline-deployment-setup.mdx +++ b/src/content/docs/cloudflare-one/email-security/setup/pre-delivery-deployment/mx-inline-deployment-setup.mdx @@ -8,7 +8,7 @@ sidebar: order: 3 --- -import { Render } from "~/components"; +import { DashButton, Render } from "~/components"; ## Prerequisites @@ -21,7 +21,7 @@ To use Email security, you will need to have: ## Initiate MX/Inline configuration -1. Log in to [Cloudflare One](https://one.dash.cloudflare.com/). +1. Log in to [Cloudflare dashboard](https://dash.cloudflare.com/). 2. Select **Email security**. 3. Select **Overview**. Select one of the following options: @@ -42,7 +42,10 @@ MX/Inline does not require an integration for protection to be effective. Howeve To associate an integration: -1. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Integrations** > **Cloud & SaaS Integrations** > **Integrations** +1. In [Cloudflare dashboard](https://dash.cloudflare.com/), go to **Zero Trust** > **Integrations** > **Cloud & SaaS Integrations** > **Integrations** + + + 2. Select **Connect an integration**. 3. Select an application: Choose between **Google Workspace CASB + EMAIL**, or **Microsoft CASB + EMAIL**. - Refer to [Enable Gmail BCC integration](/cloudflare-one/email-security/setup/post-delivery-deployment/bcc-journaling/bcc-setup/gmail-bcc-setup/enable-gmail-integration/#1-create-a-service-account-in-your-gcp-project) if you select **Google Workspace CASB + EMAIL**. diff --git a/src/content/docs/cloudflare-one/email-security/setup/pre-delivery-deployment/partner-domain-tls.mdx b/src/content/docs/cloudflare-one/email-security/setup/pre-delivery-deployment/partner-domain-tls.mdx index d33970c1736..b30325e3f76 100644 --- a/src/content/docs/cloudflare-one/email-security/setup/pre-delivery-deployment/partner-domain-tls.mdx +++ b/src/content/docs/cloudflare-one/email-security/setup/pre-delivery-deployment/partner-domain-tls.mdx @@ -10,6 +10,8 @@ sidebar: order: 5 --- +import { DashButton } from "~/components"; + To add additional TLS (Transport Layer Security) requirements for emails coming from certain domains, you can enforce higher levels of SSL/TLS inspection. If TLS is required, mail without TLS from the specified domain will be dropped. :::note @@ -18,7 +20,10 @@ To enforce TLS across all emails, you will need to enforce TLS requirements when To set up a partner domain: -1. Log in to [Cloudflare One](https://one.dash.cloudflare.com/) and select **Email security**. +1. Log in to [Cloudflare dashboard](https://dash.cloudflare.com/) and go to **Zero Trust** > **Email security**. + + + 2. Select **Settings** > **Partner domain TLS** > **View**. 3. Select **Add a domain**. 4. Enter a valid domain name. You can also exclude subdomains by selecting **Add exclude**. diff --git a/src/content/docs/cloudflare-one/email-security/submissions/index.mdx b/src/content/docs/cloudflare-one/email-security/submissions/index.mdx index 14e7f12e83a..97d1a4ed43b 100644 --- a/src/content/docs/cloudflare-one/email-security/submissions/index.mdx +++ b/src/content/docs/cloudflare-one/email-security/submissions/index.mdx @@ -8,13 +8,18 @@ sidebar: order: 13 --- +import { DashButton } from "~/components"; + Submitting messages allows you to choose the disposition of your messages if the disposition is incorrect. This helps improve Email security's detection accuracy and ensures proper handling of email threats. ## Submit messages for review To submit a message for review: -1. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Email security** and select **Investigation**. +1. In [Cloudflare dashboard](https://dash.cloudflare.com/), go to **Zero Trust** > **Email security** and select **Investigation**. + + + 2. On the **Investigation** page, under **Your matching messages**, select the message you want to reclassify. 3. Select the three dots, then select **Submit for review**. 4. Under **New disposition**, select among the following: @@ -47,7 +52,7 @@ Once you have submitted your messages, you can access those on **Submissions**. To view submissions: -1. Log in to [Cloudflare One](https://one.dash.cloudflare.com/). +1. Log in to [Cloudflare dashboard](https://dash.cloudflare.com/). 2. Select **Email security** > **Submissions**. 3. Choose from the following submission types: - [**Team submissions**](/cloudflare-one/email-security/submissions/team-submissions/): View emails your security team submitted for submissions. diff --git a/src/content/docs/cloudflare-one/email-security/submissions/invalid-submissions.mdx b/src/content/docs/cloudflare-one/email-security/submissions/invalid-submissions.mdx index aff37d96e27..48b662e1ab2 100644 --- a/src/content/docs/cloudflare-one/email-security/submissions/invalid-submissions.mdx +++ b/src/content/docs/cloudflare-one/email-security/submissions/invalid-submissions.mdx @@ -22,7 +22,7 @@ To ensure your submission is valid: To view invalid submissions: -1. Log in to [Cloudflare One](https://one.dash.cloudflare.com/). +1. Log in to [Cloudflare dashboard](https://dash.cloudflare.com/). 2. Select **Email security** > **Submissions**. 3. Select **Invalid submissions**. @@ -34,6 +34,6 @@ You can filter based on **Date Range** and **Submitted by** (which will list ema To enable Invalid submission email notifications: -1. Log in to [Cloudflare One](https://one.dash.cloudflare.com/). +1. Log in to [Cloudflare dashboard](https://dash.cloudflare.com/). 2. Select **Email security** > **Settings**. 3. Go to **Invalid submission emails** and turn on **Invalid submission email notifications**. \ No newline at end of file diff --git a/src/content/docs/cloudflare-one/email-security/submissions/team-submissions.mdx b/src/content/docs/cloudflare-one/email-security/submissions/team-submissions.mdx index 0520ccc6a30..f89332a6031 100644 --- a/src/content/docs/cloudflare-one/email-security/submissions/team-submissions.mdx +++ b/src/content/docs/cloudflare-one/email-security/submissions/team-submissions.mdx @@ -14,7 +14,7 @@ Team submissions are the emails your security team submitted for submission. All To view team submissions: -1. Log in to [Cloudflare One](https://one.dash.cloudflare.com/). +1. Log in to [Cloudflare dashboard](https://dash.cloudflare.com/). 2. Select **Email security** > **Submissions**. 3. Select **Team submissions**. diff --git a/src/content/docs/cloudflare-one/email-security/submissions/user-submissions.mdx b/src/content/docs/cloudflare-one/email-security/submissions/user-submissions.mdx index 157f7404a08..bf4b3f4bc5f 100644 --- a/src/content/docs/cloudflare-one/email-security/submissions/user-submissions.mdx +++ b/src/content/docs/cloudflare-one/email-security/submissions/user-submissions.mdx @@ -20,7 +20,7 @@ Any email that is reported as [phish](/cloudflare-one/email-security/settings/ph To view user submissions: -1. Log in to [Cloudflare One](https://one.dash.cloudflare.com/). +1. Log in to [Cloudflare dashboard](https://dash.cloudflare.com/). 2. Select **Email security** > **Submissions**. 3. Select **User submissions**. diff --git a/src/content/docs/cloudflare-one/insights/analytics-overview.mdx b/src/content/docs/cloudflare-one/insights/analytics-overview.mdx index 94280945992..aee08b88038 100644 --- a/src/content/docs/cloudflare-one/insights/analytics-overview.mdx +++ b/src/content/docs/cloudflare-one/insights/analytics-overview.mdx @@ -10,11 +10,13 @@ tags: - Analytics --- -import { Render } from "~/components"; +import { DashButton, Render } from "~/components"; The Cloudflare One Analytics overview provides a dashboard that reports on how Cloudflare One is protecting your organization and networks. Use this page to monitor usage and potential security concerns within your organization. -To view the Analytics overview, log in to [Cloudflare One](https://one.dash.cloudflare.com) and go to **Overview**. +To view the Analytics overview, log in to [Cloudflare dashboard](https://dash.cloudflare.com/) and go to **Zero Trust** > **Overview**. + + The Analytics overview includes reports and insights across the following products and categories: diff --git a/src/content/docs/cloudflare-one/insights/dex/ip-visibility.mdx b/src/content/docs/cloudflare-one/insights/dex/ip-visibility.mdx index 5d32a72c03c..8d9265648b8 100644 --- a/src/content/docs/cloudflare-one/insights/dex/ip-visibility.mdx +++ b/src/content/docs/cloudflare-one/insights/dex/ip-visibility.mdx @@ -14,7 +14,7 @@ tags: - MacOS --- -import { Render, Details } from "~/components"; +import { DashButton, Render, Details } from "~/components";
@@ -55,7 +55,10 @@ IP information helps IT administrators troubleshoot network issues and identify To view IP information for a user device: -1. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Team & Resources** > **Devices** > **Your devices**. +1. In [Cloudflare dashboard](https://dash.cloudflare.com/), go to **Zero Trust** > **Team & Resources** > **Devices** > **Your devices**. + + + 2. Select a device, then select **View details**. 3. Go to **IP details**. 4. Review the IP details for your selected device's most recent session. @@ -64,7 +67,10 @@ To view IP information for a user device: DEX's IP visibility allows you to review an event log of a device's IP history for the last seven days. To view a device's IP history: -1. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Team & Resources** > **Devices** > **Your devices**. +1. In [Cloudflare dashboard](https://dash.cloudflare.com/), go to **Zero Trust** > **Team & Resources** > **Devices** > **Your devices**. + + + 2. Select a device > **View details** > go to **IP details**. 3. Select **View all ISPs**. diff --git a/src/content/docs/cloudflare-one/insights/dex/monitoring.mdx b/src/content/docs/cloudflare-one/insights/dex/monitoring.mdx index 056e13ea2ec..66ccbd755a8 100644 --- a/src/content/docs/cloudflare-one/insights/dex/monitoring.mdx +++ b/src/content/docs/cloudflare-one/insights/dex/monitoring.mdx @@ -8,7 +8,7 @@ sidebar: order: 2 --- -import { Render } from "~/components"; +import { DashButton, Render } from "~/components"; Monitor performance and network status for your organization's [fleet](/cloudflare-one/insights/dex/monitoring/#fleet-status) (all devices with the Cloudflare One Client installed and connected to your Zero Trust organization) or individual [user devices](/cloudflare-one/insights/dex/monitoring/#device-monitoring). @@ -20,7 +20,10 @@ A fleet is a collection of user devices. All devices in a fleet have the Cloudfl To view fleet status: -1. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Insights** > **Digital experience**. +1. In [Cloudflare dashboard](https://dash.cloudflare.com/), go to **Zero Trust** > **Insights** > **Digital experience**. + + + 2. Review the information under **Live analytics**. ### View metrics @@ -62,7 +65,10 @@ Review network and device performance for a device enrolled in your fleet. To view a device's network and device performance metrics: -1. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Team & Resources** > **Devices** > **Your devices**. +1. In [Cloudflare dashboard](https://dash.cloudflare.com/), go to **Zero Trust** > **Team & Resources** > **Devices** > **Your devices**. + + + 2. Select a device > **View details**. 3. Select the **DEX** tab. 4. In **Device Monitoring**, scroll down to **Network performance** and **Device Performance**. diff --git a/src/content/docs/cloudflare-one/insights/dex/rules.mdx b/src/content/docs/cloudflare-one/insights/dex/rules.mdx index 0823f895e22..a5586ac78f7 100644 --- a/src/content/docs/cloudflare-one/insights/dex/rules.mdx +++ b/src/content/docs/cloudflare-one/insights/dex/rules.mdx @@ -10,7 +10,7 @@ tags: - SAML --- -import { Render } from "~/components"; +import { DashButton, Render } from "~/components"; DEX rules allow you to create and manage testing policies for targeted user groups within your [fleet](/cloudflare-one/insights/dex/tests/) (all devices with the Cloudflare One Client installed and connected to your Zero Trust organization). After creating a rule, you can use it to define the scope of a [test](/cloudflare-one/insights/dex/tests/) to specific groups such as departments (like finance or sales), devices, and/or users. You can apply and reuse rules on your desired tests. @@ -20,7 +20,10 @@ Use DEX rules to scope a test to a specific group within your fleet for more pre To create a rule: -1. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Insights** > **Digital experience**. +1. In [Cloudflare dashboard](https://dash.cloudflare.com/), go to **Zero Trust** > **Insights** > **Digital experience**. + + + 2. Select the **Rules** tab. 3. Select **Add a rule**. 4. Give your rule a name and build your desired expressions. @@ -50,7 +53,10 @@ After you have created a rule, you can add it to a test. If you do not add a rul To add a rule to a test: -1. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Insights** > **Digital experience**. +1. In [Cloudflare dashboard](https://dash.cloudflare.com/), go to **Zero Trust** > **Insights** > **Digital experience**. + + + 2. Select the **Tests** tab. 3. Choose an existing test and select **Edit**, or select **Add a test** to make a new test. 4. Under **Select DEX rules**, select the rule you would like to apply. @@ -63,7 +69,10 @@ To add a rule to a test: To view which tests a rule is being applied to: -1. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Insights** > **Digital experience**. +1. In [Cloudflare dashboard](https://dash.cloudflare.com/), go to **Zero Trust** > **Insights** > **Digital experience**. + + + 2. Select the **Rules** tab. 3. Choose a rule and select **Edit**. 4. Select the **DEX tests** tab and review the list of tests that include your selected rule. @@ -74,7 +83,10 @@ You can create a new test from the [DEX test dashboard as described above](/clou To create a new test using a rule from DEX rules: -1. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Insights** > **Digital experience**. +1. In [Cloudflare dashboard](https://dash.cloudflare.com/), go to **Zero Trust** > **Insights** > **Digital experience**. + + + 2. Select the **Rules** tab. 3. Select a rule and select **Edit**. 4. Select the **DEX tests** tab. diff --git a/src/content/docs/cloudflare-one/insights/dex/tests/traceroute.mdx b/src/content/docs/cloudflare-one/insights/dex/tests/traceroute.mdx index 5b34e06f307..e821e21a9cd 100644 --- a/src/content/docs/cloudflare-one/insights/dex/tests/traceroute.mdx +++ b/src/content/docs/cloudflare-one/insights/dex/tests/traceroute.mdx @@ -12,7 +12,7 @@ tags: - Android --- -import { Details, Render } from "~/components"; +import { DashButton, Details, Render } from "~/components";
@@ -37,7 +37,10 @@ A traceroute test measures the network path of an IP packet from an end-user dev To set up a traceroute test for an application: -1. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Insights** > **Digital experience**. +1. In [Cloudflare dashboard](https://dash.cloudflare.com/), go to **Zero Trust** > **Insights** > **Digital experience**. + + + 2. Select the **Tests** tab. 3. Select **Add a Test**. 4. Fill in the following fields: diff --git a/src/content/docs/cloudflare-one/insights/dex/tests/view-results.mdx b/src/content/docs/cloudflare-one/insights/dex/tests/view-results.mdx index 49384d7583f..9bcc4b2894d 100644 --- a/src/content/docs/cloudflare-one/insights/dex/tests/view-results.mdx +++ b/src/content/docs/cloudflare-one/insights/dex/tests/view-results.mdx @@ -8,7 +8,7 @@ sidebar: order: 3 --- -import { Render } from "~/components"; +import { DashButton, Render } from "~/components"; Use the results of a Digital Experience Monitoring (DEX) test to monitor availability and performance for a specific application. DEX stores test results for 7 days on all plans, according to the [log retention policy](/cloudflare-one/insights/logs/#log-retention). @@ -21,7 +21,10 @@ Use the results of a Digital Experience Monitoring (DEX) test to monitor availab To view an overview of test results for all devices: -1. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Insights** > **Digital experience**. +1. In [Cloudflare dashboard](https://dash.cloudflare.com/), go to **Zero Trust** > **Insights** > **Digital experience**. + + + 2. Select the **Tests** tab. 3. Select a test to view detailed results. @@ -29,7 +32,10 @@ To view an overview of test results for all devices: To view analytics on a per-device level: -1. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Team & Resources** > **Devices** > **Your devices**. +1. In [Cloudflare dashboard](https://dash.cloudflare.com/), go to **Zero Trust** > **Team & Resources** > **Devices** > **Your devices**. + + + 2. Select the device you want to view, and then select **View details**. 3. Select the **Tests** tab. 4. Select a test to view detailed results. diff --git a/src/content/docs/cloudflare-one/insights/logs/dashboard-logs/gateway-logs/manage-pii.mdx b/src/content/docs/cloudflare-one/insights/logs/dashboard-logs/gateway-logs/manage-pii.mdx index 03bb75f46d2..d6405adfafa 100644 --- a/src/content/docs/cloudflare-one/insights/logs/dashboard-logs/gateway-logs/manage-pii.mdx +++ b/src/content/docs/cloudflare-one/insights/logs/dashboard-logs/gateway-logs/manage-pii.mdx @@ -10,6 +10,8 @@ sidebar: order: 1 --- +import { DashButton } from "~/components"; + Cloudflare Gateway gives you multiple ways to safely handle your employees' personally identifiable information (PII) in activity logs: - **Redact PII** (default) — PII is stored in logs but hidden from view. Only the Super Administrator and users with the [Cloudflare Zero Trust PII role](/cloudflare-one/roles-permissions/#cloudflare-zero-trust-pii) can view redacted PII. The underlying data is preserved — redaction only controls who can see it. @@ -41,5 +43,8 @@ Changes to this setting do not affect PII already stored in previous logs. To turn on the setting to exclude PII: -1. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Traffic policies** > **Traffic settings**. +1. In [Cloudflare dashboard](https://dash.cloudflare.com/), go to **Zero Trust** > **Traffic policies** > **Traffic settings**. + + + 2. In **Traffic logging**, turn on **Exclude personally identifiable information (PII) from logs**. diff --git a/src/content/docs/cloudflare-one/insights/logs/dashboard-logs/index.mdx b/src/content/docs/cloudflare-one/insights/logs/dashboard-logs/index.mdx index bc1f6d84f20..00d2caab28f 100644 --- a/src/content/docs/cloudflare-one/insights/logs/dashboard-logs/index.mdx +++ b/src/content/docs/cloudflare-one/insights/logs/dashboard-logs/index.mdx @@ -13,7 +13,7 @@ head: import { DirectoryListing } from "~/components"; -The following logs are available in the [Cloudflare One dashboard](https://one.dash.cloudflare.com/). Use these logs to review user activity, policy decisions, and connection details for your Zero Trust deployment. +The following logs are available in the [Cloudflare dashboard](https://dash.cloudflare.com/). Use these logs to review user activity, policy decisions, and connection details for your Zero Trust deployment. diff --git a/src/content/docs/cloudflare-one/insights/logs/dashboard-logs/posture-logs.mdx b/src/content/docs/cloudflare-one/insights/logs/dashboard-logs/posture-logs.mdx index 9a69bac2bfb..7a5d96b4be6 100644 --- a/src/content/docs/cloudflare-one/insights/logs/dashboard-logs/posture-logs.mdx +++ b/src/content/docs/cloudflare-one/insights/logs/dashboard-logs/posture-logs.mdx @@ -12,7 +12,7 @@ tags: Posture logs show the results of [device posture checks](/cloudflare-one/reusable-components/posture-checks/) — security requirements such as OS version, disk encryption, or endpoint protection status — reported by the Cloudflare One Client. Use these logs to identify which devices are passing or failing your organization's posture requirements and to troubleshoot individual check results. -To view device posture logs, log in to [Cloudflare One](https://one.dash.cloudflare.com/) and go to **Insights** > **Logs** > **Posture logs**. Logs will only display if you have configured [device posture checks](/cloudflare-one/reusable-components/posture-checks/) for your Zero Trust organization. +To view device posture logs, log in to [Cloudflare dashboard](https://dash.cloudflare.com/) and go to **Zero Trust** > **Insights** > **Logs** > **Posture logs**. Logs will only display if you have configured [device posture checks](/cloudflare-one/reusable-components/posture-checks/) for your Zero Trust organization. Enterprise users can generate more detailed logs with [Logpush](/cloudflare-one/insights/logs/logpush/). diff --git a/src/content/docs/cloudflare-one/insights/logs/dashboard-logs/ssh-command-logs.mdx b/src/content/docs/cloudflare-one/insights/logs/dashboard-logs/ssh-command-logs.mdx index f13bce2a545..36768873b5a 100644 --- a/src/content/docs/cloudflare-one/insights/logs/dashboard-logs/ssh-command-logs.mdx +++ b/src/content/docs/cloudflare-one/insights/logs/dashboard-logs/ssh-command-logs.mdx @@ -11,9 +11,11 @@ tags: - SSH --- +import { DashButton } from "~/components"; + SSH command logs record the commands that users run on infrastructure targets protected by [Access for Infrastructure](/cloudflare-one/networks/connectors/cloudflare-tunnel/use-cases/ssh/ssh-infrastructure-access/). Use these logs to audit user activity on your SSH servers and investigate specific sessions. -To view SSH command logs, log in to [Cloudflare One](https://one.dash.cloudflare.com/) and go to **Insights** > **Logs** > **SSH command logs**. +To view SSH command logs, log in to [Cloudflare dashboard](https://dash.cloudflare.com/) and go to **Zero Trust** > **Insights** > **Logs** > **SSH command logs**. ## Prerequisites @@ -26,7 +28,10 @@ To generate SSH command logs, you must: SSH command logs displayed in the dashboard are encrypted using the public key you provided during setup. The logs are not readable in the dashboard — you must download and decrypt them locally. To view the contents of the logs: -1. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Insights** > **Logs** > **SSH command logs**. +1. In [Cloudflare dashboard](https://dash.cloudflare.com/), go to **Zero Trust** > **Insights** > **Logs** > **SSH command logs**. + + + 2. Filter the logs using the name of your SSH application. 3. Select the SSH session for which you want to export command logs. 4. In the side panel, scroll down to **SSH logs** and select **Download**. diff --git a/src/content/docs/cloudflare-one/insights/logs/logpush/index.mdx b/src/content/docs/cloudflare-one/insights/logs/logpush/index.mdx index 375008abd65..6122bf36841 100644 --- a/src/content/docs/cloudflare-one/insights/logs/logpush/index.mdx +++ b/src/content/docs/cloudflare-one/insights/logs/logpush/index.mdx @@ -10,7 +10,7 @@ sidebar: order: 2 --- -import { GlossaryTooltip, Render, DirectoryListing, Plan } from "~/components"; +import { DashButton, GlossaryTooltip, Render, DirectoryListing, Plan } from "~/components"; @@ -20,7 +20,10 @@ With Cloudflare's [Logpush](/logs/logpush/) service, you can configure the autom To configure Logpush for Zero Trust logs: -1. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Insights** > **Logs**. +1. In [Cloudflare dashboard](https://dash.cloudflare.com/), go to **Zero Trust** > **Insights** > **Logs**. + + + 2. Select **Manage Logpush**. 3. In Logpush, select **Create a Logpush job**. A Logpush job defines which dataset to export and where to send it. 4. Choose a [Logpush destination](/logs/logpush/logpush-job/enable-destinations/). diff --git a/src/content/docs/cloudflare-one/insights/network-visibility/diagnostics/buckets.mdx b/src/content/docs/cloudflare-one/insights/network-visibility/diagnostics/buckets.mdx index b326012ef5d..4a99babe5bb 100644 --- a/src/content/docs/cloudflare-one/insights/network-visibility/diagnostics/buckets.mdx +++ b/src/content/docs/cloudflare-one/insights/network-visibility/diagnostics/buckets.mdx @@ -22,7 +22,10 @@ Learn how to set up a bucket for use with full packet captures. -1. In the [Cloudflare One](https://one.dash.cloudflare.com) dashboard, go to **Network visibility** > **Diagnostics**. +1. In the [Cloudflare dashboard](https://dash.cloudflare.com/), go to **Zero Trust** > **Network visibility** > **Diagnostics**. + + + 2. Select the **Buckets** tab > **Add a bucket**. 3. Select a bucket service and select **Next**. 4. Enter the information related to your bucket for your service provider. @@ -129,7 +132,10 @@ View a list of all buckets configured on your account. -1. In the [Cloudflare One](https://one.dash.cloudflare.com) dashboard, go to ***Insights** > *Network visibility** > **Diagnostics**. +1. In the [Cloudflare dashboard](https://dash.cloudflare.com/), go to **Zero Trust** > **Insights** > *Network visibility** > **Diagnostics**. + + + 2. Select the **Buckets** tab. The list of buckets associated with your account displays. diff --git a/src/content/docs/cloudflare-one/insights/network-visibility/diagnostics/packet-captures.mdx b/src/content/docs/cloudflare-one/insights/network-visibility/diagnostics/packet-captures.mdx index 45c45787b6a..dbc0c0e235c 100644 --- a/src/content/docs/cloudflare-one/insights/network-visibility/diagnostics/packet-captures.mdx +++ b/src/content/docs/cloudflare-one/insights/network-visibility/diagnostics/packet-captures.mdx @@ -239,7 +239,10 @@ After your request finishes processing, you can download your packet captures. -1. In the [Cloudflare One](https://one.dash.cloudflare.com) dashboard, go to **Network visibility** > **Diagnostics**. +1. In the [Cloudflare dashboard](https://dash.cloudflare.com/), go to **Zero Trust** > **Network visibility** > **Diagnostics**. + + + 2. In **Packet captures**, select **Start a capture**. 3. Locate your packet capture you want to download, and select **Download**. diff --git a/src/content/docs/cloudflare-one/integrations/cloud-and-saas/aws-s3.mdx b/src/content/docs/cloudflare-one/integrations/cloud-and-saas/aws-s3.mdx index b7f683bba09..35ab74d87da 100644 --- a/src/content/docs/cloudflare-one/integrations/cloud-and-saas/aws-s3.mdx +++ b/src/content/docs/cloudflare-one/integrations/cloud-and-saas/aws-s3.mdx @@ -12,7 +12,7 @@ sidebar: order: 6 --- -import { Render } from "~/components"; +import { DashButton, Render } from "~/components"; **Cloud & SaaS integrations**. +1. In [Cloudflare dashboard](https://dash.cloudflare.com/), go to **Zero Trust** > **Integrations** > **Cloud & SaaS integrations**. + + + 2. Find and select your AWS integration. 3. Select **Create new configuration**. 4. In **Resources**, choose the buckets you want to scan. Select **Continue**. diff --git a/src/content/docs/cloudflare-one/integrations/cloud-and-saas/findings/index.mdx b/src/content/docs/cloudflare-one/integrations/cloud-and-saas/findings/index.mdx index 81e60cf4679..0aebb6c18ce 100644 --- a/src/content/docs/cloudflare-one/integrations/cloud-and-saas/findings/index.mdx +++ b/src/content/docs/cloudflare-one/integrations/cloud-and-saas/findings/index.mdx @@ -11,7 +11,7 @@ head: content: Manage security findings --- -import { TabItem, Tabs, Details } from "~/components"; +import { DashButton, TabItem, Tabs, Details } from "~/components"; Findings are security issues detected within SaaS and cloud applications that involve users, data at rest, and other configuration settings. With Cloudflare CASB, you can review a comprehensive list of findings in Cloudflare One and immediately start taking action on the issues found. @@ -26,7 +26,10 @@ Posture findings include misconfigurations, unauthorized user activity, and othe To view details about the posture findings that CASB found: -1. In [Cloudflare One](https://one.dash.cloudflare.com), go to **Cloud & SaaS findings** > **Posture Findings**. +1. In [Cloudflare dashboard](https://dash.cloudflare.com/), go to **Zero Trust** > **Cloud & SaaS findings** > **Posture Findings**. + + + 2. Choose **SaaS** or **Cloud**. 3. To view details about a finding, select the finding's name @@ -49,7 +52,10 @@ Cloudflare CASB labels each finding with one of the following severity levels: You can change the severity level for a finding at any time in case the default assignment does not suit your environment: -1. In [Cloudflare One](https://one.dash.cloudflare.com), go to **Cloud & SaaS findings** > **Posture Findings**. +1. In [Cloudflare dashboard](https://dash.cloudflare.com/), go to **Zero Trust** > **Cloud & SaaS findings** > **Posture Findings**. + + + 2. Locate the finding you want to modify and select **Manage**. 3. In the severity level drop-down menu, choose your desired setting (_Critical_, _High_, _Medium_, or _Low_). @@ -61,7 +67,10 @@ Content findings include instances of potential data exposure as identified by [ To view details about the content findings that CASB found: -1. In [Cloudflare One](https://one.dash.cloudflare.com), go to **Cloud & SaaS findings** > **Content Findings**. +1. In [Cloudflare dashboard](https://dash.cloudflare.com/), go to **Zero Trust** > **Cloud & SaaS findings** > **Content Findings**. + + + 2. Choose **SaaS** or **Cloud**. 3. To view details about a finding, select the finding's name. @@ -75,7 +84,10 @@ File findings for some integrations (such as [Microsoft 365](/cloudflare-one/int -1. In [Cloudflare One](https://one.dash.cloudflare.com), go to **Cloud & SaaS findings** > **Posture Findings**. +1. In [Cloudflare dashboard](https://dash.cloudflare.com/), go to **Zero Trust** > **Cloud & SaaS findings** > **Posture Findings**. + + + 2. Choose **SaaS** or **Cloud**. 3. Locate the individual finding, then select **Manage**. 4. In **Active Instances**, select the file name. @@ -85,7 +97,10 @@ File findings for some integrations (such as [Microsoft 365](/cloudflare-one/int -1. In [Cloudflare One](https://one.dash.cloudflare.com), go to **Cloud & SaaS findings** > **Content Findings**. +1. In [Cloudflare dashboard](https://dash.cloudflare.com/), go to **Zero Trust** > **Cloud & SaaS findings** > **Content Findings**. + + + 2. Choose **SaaS** or **Cloud**. 3. Select the file name of the detected asset. 4. In **Sharing details**, select the linked file instance. @@ -98,7 +113,10 @@ After reviewing your findings, you may decide that certain posture findings are ### Ignore a finding -1. In [Cloudflare One](https://one.dash.cloudflare.com), go to **Cloud & SaaS findings** > **Posture Findings**. +1. In [Cloudflare dashboard](https://dash.cloudflare.com/), go to **Zero Trust** > **Cloud & SaaS findings** > **Posture Findings**. + + + 2. Locate the active finding you want to hide. 3. In the three-dot menu, select **Move to ignore**. @@ -106,7 +124,10 @@ The finding's status will change from **Active** to **Ignored**. CASB will conti ### Hide an instance of a finding -1. In [Cloudflare One](https://one.dash.cloudflare.com), go to **Cloud & SaaS findings** > **Posture Findings**. +1. In [Cloudflare dashboard](https://dash.cloudflare.com/), go to **Zero Trust** > **Cloud & SaaS findings** > **Posture Findings**. + + + 2. Choose the active finding you want to hide, then select **Manage**. 3. In **Active**, find the instance you want to hide. 4. In the three-dot menu, select **Move to hidden**. @@ -119,7 +140,10 @@ After you configure one or more [CASB webhooks](/cloudflare-one/integrations/clo CASB webhooks currently support posture finding instances only. -1. In [Cloudflare One](https://one.dash.cloudflare.com), go to **Cloud & SaaS findings** > **Posture Findings**. +1. In [Cloudflare dashboard](https://dash.cloudflare.com/), go to **Zero Trust** > **Cloud & SaaS findings** > **Posture Findings**. + + + 2. Choose **SaaS** or **Cloud**. 3. Choose the finding you want to review, then select **Manage**. 4. In **Active Instances**, select an instance. @@ -139,7 +163,10 @@ In addition to detecting and surfacing misconfigurations or issues with SaaS and Before you can remediate findings, [add a new integration](/cloudflare-one/integrations/cloud-and-saas/) and choose _Read-Write mode_ during setup. Alternatively, you can update an existing integration: -1. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Cloud & SaaS findings** > **Integrations**. +1. In [Cloudflare dashboard](https://dash.cloudflare.com/), go to **Zero Trust** > **Cloud & SaaS findings** > **Integrations**. + + + 2. Choose your integration, then select **Configure**. 3. In **Integration permissions**, choose _Read-Write mode_. 4. Select **Update integration**. CASB will redirect you to your Microsoft 365 configuration. @@ -151,7 +178,10 @@ CASB can now remediate supported findings directly. To remediate a supported finding: -1. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Cloud & SaaS findings** > **Posture Findings**. +1. In [Cloudflare dashboard](https://dash.cloudflare.com/), go to **Zero Trust** > **Cloud & SaaS findings** > **Posture Findings**. + + + 2. Choose a supported finding type, then select **Manage**. 3. In **Active Instances**, select an instance. 4. In **Remediation details**, choose a remediation action to take. @@ -196,7 +226,10 @@ Ensure that you have [enabled HTTP filtering](/cloudflare-one/traffic-policies/g To create a Gateway policy directly from a CASB finding: -1. In [Cloudflare One](https://one.dash.cloudflare.com), go to **Cloud & SaaS findings** > **Posture Findings** or **Cloud & SaaS findings** > **Content Findings**. +1. In [Cloudflare dashboard](https://dash.cloudflare.com/), go to **Zero Trust** > **Cloud & SaaS findings** > **Posture Findings** or **Cloud & SaaS findings** > **Content Findings**. + + + 2. Choose **SaaS** or **Cloud**. 3. Choose the finding you want to modify, then select **Manage**. 4. Find the instance you want to block and select its three-dot menu. diff --git a/src/content/docs/cloudflare-one/integrations/cloud-and-saas/gcp-cloud-storage.mdx b/src/content/docs/cloudflare-one/integrations/cloud-and-saas/gcp-cloud-storage.mdx index 5775f2fec20..d39a4d5e529 100644 --- a/src/content/docs/cloudflare-one/integrations/cloud-and-saas/gcp-cloud-storage.mdx +++ b/src/content/docs/cloudflare-one/integrations/cloud-and-saas/gcp-cloud-storage.mdx @@ -11,7 +11,7 @@ sidebar: order: 10 --- -import { Render } from "~/components"; +import { DashButton, Render } from "~/components"; **Cloud & SaaS integrations**. +1. In [Cloudflare dashboard](https://dash.cloudflare.com/), go to **Zero Trust** > **Integrations** > **Cloud & SaaS integrations**. + + + 2. Find and select your GCP integration. 3. Select **Open connection instructions**. 4. Follow the instructions provided to connect a new compute account. @@ -56,7 +59,10 @@ You can only connect one compute account to an integration. To remove a compute Once your GCP compute account has successfully connected to your CASB integration, you can configure where and how to scan for sensitive data: -1. In [Cloudflare One](https://one.dash.cloudflare.com), go to **Integrations** > **Cloud & SaaS integrations**. +1. In [Cloudflare dashboard](https://dash.cloudflare.com/), go to **Zero Trust** > **Integrations** > **Cloud & SaaS integrations**. + + + 2. Find and select your GCP integration. 3. Select **Create new configuration**. 4. In **Resources**, choose the buckets you want to scan. Select **Continue**. diff --git a/src/content/docs/cloudflare-one/integrations/cloud-and-saas/troubleshooting/casb.mdx b/src/content/docs/cloudflare-one/integrations/cloud-and-saas/troubleshooting/casb.mdx index 812a1a4c392..a90596cc192 100644 --- a/src/content/docs/cloudflare-one/integrations/cloud-and-saas/troubleshooting/casb.mdx +++ b/src/content/docs/cloudflare-one/integrations/cloud-and-saas/troubleshooting/casb.mdx @@ -13,6 +13,8 @@ tags: - Debugging --- +import { DashButton } from "~/components"; + Use this guide to troubleshoot common issues with Cloud Access Security Broker (CASB). This guide covers troubleshooting steps for CASB integrations and webhooks. For integration-specific issues, refer to the integration's documentation. @@ -51,7 +53,10 @@ CASB integrations do not provide real-time updates. Scans are performed periodic To trigger a new scan: -1. In [Cloudflare One](https://one.dash.cloudflare.com), go to **Cloud & SaaS findings** > **Integrations**. +1. In [Cloudflare dashboard](https://dash.cloudflare.com/), go to **Zero Trust** > **Cloud & SaaS findings** > **Integrations**. + + + 2. Find your integration and select **Configure**. 3. Turn off **Scan for findings**. 4. After a few minutes, turn on **Scan for findings** again. diff --git a/src/content/docs/cloudflare-one/integrations/cloud-and-saas/troubleshooting/troubleshoot-compute-accounts.mdx b/src/content/docs/cloudflare-one/integrations/cloud-and-saas/troubleshooting/troubleshoot-compute-accounts.mdx index 91f83026123..d5c8c5f0307 100644 --- a/src/content/docs/cloudflare-one/integrations/cloud-and-saas/troubleshooting/troubleshoot-compute-accounts.mdx +++ b/src/content/docs/cloudflare-one/integrations/cloud-and-saas/troubleshooting/troubleshoot-compute-accounts.mdx @@ -12,7 +12,7 @@ tags: - Debugging --- -import { Render } from "~/components"; +import { DashButton, Render } from "~/components"; Cloudflare CASB detects when compute accounts are unhealthy or outdated. Common compute account issues include security or functionality updates and API token misconfigurations. @@ -20,7 +20,10 @@ Cloudflare CASB detects when compute accounts are unhealthy or outdated. Common To identify unhealthy compute accounts: -1. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Integrations** > **Cloud & SaaS integrations**. +1. In [Cloudflare dashboard](https://dash.cloudflare.com/), go to **Zero Trust** > **Integrations** > **Cloud & SaaS integrations**. + + + 2. Choose the integration you created for cloud scanning. 3. Select **Manage compute accounts**. @@ -38,7 +41,10 @@ Upgrading a compute account applies the latest software features, bug fixes, and To upgrade a compute account: -1. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Integrations** > **Cloud & SaaS integrations**. +1. In [Cloudflare dashboard](https://dash.cloudflare.com/), go to **Zero Trust** > **Integrations** > **Cloud & SaaS integrations**. + + + 2. Choose the integration you created for cloud scanning. 3. Select **Open connection instructions**. 4. Follow the instructions provided to validate your local Terraform and CLI configuration. diff --git a/src/content/docs/cloudflare-one/integrations/cloud-and-saas/troubleshooting/troubleshoot-integrations.mdx b/src/content/docs/cloudflare-one/integrations/cloud-and-saas/troubleshooting/troubleshoot-integrations.mdx index 4896d3775bd..8a3051a4cf2 100644 --- a/src/content/docs/cloudflare-one/integrations/cloud-and-saas/troubleshooting/troubleshoot-integrations.mdx +++ b/src/content/docs/cloudflare-one/integrations/cloud-and-saas/troubleshooting/troubleshoot-integrations.mdx @@ -10,6 +10,8 @@ tags: - Debugging --- +import { DashButton } from "~/components"; + Cloudflare CASB detects when integrations are unhealthy or outdated. Common integration issues include changes to SaaS app or cloud environment configurations, user access, or permission scope. Integrations may need to be updated to support new features or permissions. @@ -26,7 +28,10 @@ If CASB does not support self-service repairs for an integration, you will need You can repair unhealthy CASB integrations through your list of integrations or findings. -1. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Integrations** > **Cloud & SaaS integrations**. +1. In [Cloudflare dashboard](https://dash.cloudflare.com/), go to **Zero Trust** > **Integrations** > **Cloud & SaaS integrations**. + + + 2. Choose your unhealthy integration. 3. Select **Reauthorize**. 4. In your SaaS app or cloud environment, reauthorize your account. @@ -35,7 +40,10 @@ You can repair unhealthy CASB integrations through your list of integrations or Upgrading an outdated integration will allow the integration to access new features and permissions. -1. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Integrations** > **Cloud & SaaS integrations**. +1. In [Cloudflare dashboard](https://dash.cloudflare.com/), go to **Zero Trust** > **Integrations** > **Cloud & SaaS integrations**. + + + 2. Choose your outdated integration. 3. Select **Upgrade integration**. 4. In your SaaS app or cloud environment, upgrade your app and reauthorize your account. diff --git a/src/content/docs/cloudflare-one/integrations/cloud-and-saas/webhooks.mdx b/src/content/docs/cloudflare-one/integrations/cloud-and-saas/webhooks.mdx index 52a7632c560..c2c26eb706f 100644 --- a/src/content/docs/cloudflare-one/integrations/cloud-and-saas/webhooks.mdx +++ b/src/content/docs/cloudflare-one/integrations/cloud-and-saas/webhooks.mdx @@ -8,6 +8,8 @@ sidebar: order: 2 --- +import { DashButton } from "~/components"; + :::note[Availability] Requires Cloudflare CASB. @@ -26,7 +28,10 @@ After you configure a webhook destination, you can test delivery from the **Webh ## Create a webhook -1. In [Cloudflare One](https://one.dash.cloudflare.com), go to **Integrations** > **Webhooks**. +1. In [Cloudflare dashboard](https://dash.cloudflare.com/), go to **Zero Trust** > **Integrations** > **Webhooks**. + + + 2. Select **Create webhook**. 3. Enter a **Name** for the webhook. 4. Enter the **Destination URL** for the system that will receive webhook requests. @@ -59,7 +64,10 @@ Test delivery does not send a live finding instance from your environment. To update an existing webhook: -1. In [Cloudflare One](https://one.dash.cloudflare.com), go to **Integrations** > **Webhooks**. +1. In [Cloudflare dashboard](https://dash.cloudflare.com/), go to **Zero Trust** > **Integrations** > **Webhooks**. + + + 2. Select the webhook you want to update. 3. Modify the webhook configuration. 4. Select **Save**. @@ -74,7 +82,10 @@ When you edit an existing webhook, Cloudflare does not display saved header valu After you configure one or more webhook destinations, you can send posture finding instances directly from the findings workflow. -1. In [Cloudflare One](https://one.dash.cloudflare.com), go to **Cloud & SaaS findings** > **Posture Findings**. +1. In [Cloudflare dashboard](https://dash.cloudflare.com/), go to **Zero Trust** > **Cloud & SaaS findings** > **Posture Findings**. + + + 2. Choose **SaaS** or **Cloud**. 3. Choose the finding you want to review, then select **Manage**. 4. Select an instance. diff --git a/src/content/docs/cloudflare-one/networks/resolvers-and-proxies/dns/dns-over-tls.mdx b/src/content/docs/cloudflare-one/networks/resolvers-and-proxies/dns/dns-over-tls.mdx index 225eb43a07a..487d6091135 100644 --- a/src/content/docs/cloudflare-one/networks/resolvers-and-proxies/dns/dns-over-tls.mdx +++ b/src/content/docs/cloudflare-one/networks/resolvers-and-proxies/dns/dns-over-tls.mdx @@ -11,6 +11,8 @@ sidebar: order: 2 --- +import { DashButton } from "~/components"; + By default, DNS is sent over a plaintext connection. DNS over TLS (DoT) is a standard for encrypting DNS queries to keep them secure and private. DoT uses the same security protocol, TLS, that HTTPS websites use to encrypt and authenticate communications. Cloudflare supports DoT on standard port `853` over TLS 1.2 and TLS 1.3 in compliance with [RFC7858](https://tools.ietf.org/html/rfc7858). @@ -21,7 +23,10 @@ Cloudflare supports DoT on standard port `853` over TLS 1.2 and TLS 1.3 in compl Each Gateway DNS location has a unique DoT hostname. DNS locations and corresponding DoT hostnames have policies associated with them. -1. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Networks** > **Resolvers & Proxies**. +1. In [Cloudflare dashboard](https://dash.cloudflare.com/), go to **Zero Trust** > **Networks** > **Resolvers & Proxies**. + + + 2. Under **DNS locations**, [add a new location](/cloudflare-one/networks/resolvers-and-proxies/dns/locations/) or select an existing location from the list. 3. Under **DoT endpoint**, copy the value in **DoT addresses**. diff --git a/src/content/docs/cloudflare-one/networks/resolvers-and-proxies/dns/locations/dns-resolver-ips.mdx b/src/content/docs/cloudflare-one/networks/resolvers-and-proxies/dns/locations/dns-resolver-ips.mdx index 7480922c589..2caf0f6751d 100644 --- a/src/content/docs/cloudflare-one/networks/resolvers-and-proxies/dns/locations/dns-resolver-ips.mdx +++ b/src/content/docs/cloudflare-one/networks/resolvers-and-proxies/dns/locations/dns-resolver-ips.mdx @@ -10,11 +10,16 @@ sidebar: order: 2 --- +import { DashButton } from "~/components"; + When you create a DNS location, Gateway assigns IPv4/IPv6 addresses and DoT/DoH hostnames to that location. These are the IP addresses and hostnames you send your DNS queries to for Gateway to resolve. To view the resolver endpoint IP addresses and hostnames for a DNS location: -1. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Networks** > **Resolvers & Proxies**. +1. In [Cloudflare dashboard](https://dash.cloudflare.com/), go to **Zero Trust** > **Networks** > **Resolvers & Proxies**. + + + 2. Select the DNS location, then select **Edit**. 3. Go to **Setup instructions**. The addresses and hostnames will appear in **Your configuration**. diff --git a/src/content/docs/cloudflare-one/networks/resolvers-and-proxies/proxy-endpoints/index.mdx b/src/content/docs/cloudflare-one/networks/resolvers-and-proxies/proxy-endpoints/index.mdx index bae11b92839..185340985c7 100644 --- a/src/content/docs/cloudflare-one/networks/resolvers-and-proxies/proxy-endpoints/index.mdx +++ b/src/content/docs/cloudflare-one/networks/resolvers-and-proxies/proxy-endpoints/index.mdx @@ -11,6 +11,7 @@ tags: --- import { + DashButton, Details, GlossaryDefinition, TabItem, @@ -98,7 +99,10 @@ All devices you add to the proxy endpoint can access your Cloudflare Tunnel appl To add an [authorization endpoint](#authorization-endpoint): -1. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Networks** > **Resolvers & Proxies**, then go to **Proxy endpoints**. +1. In [Cloudflare dashboard](https://dash.cloudflare.com/), go to **Zero Trust** > **Networks** > **Resolvers & Proxies**, then go to **Proxy endpoints**. + + + 2. In **Proxy endpoints**, select **Add an endpoint**. 3. Choose **Add an authorization endpoint**. 4. Name your endpoint. @@ -113,7 +117,10 @@ To add an [authorization endpoint](#authorization-endpoint): To add a [source IP endpoint](#source-ip-endpoint): -1. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Networks** > **Resolvers & Proxies**, then go to **Proxy endpoints**. +1. In [Cloudflare dashboard](https://dash.cloudflare.com/), go to **Zero Trust** > **Networks** > **Resolvers & Proxies**, then go to **Proxy endpoints**. + + + 2. In **Proxy endpoints**, select **Add an endpoint**. 3. Choose **Add a source IP endpoint**. 4. Name your endpoint. @@ -254,7 +261,10 @@ When you create a PAC file in Cloudflare One, Cloudflare will host it in a publi To create a hosted PAC file: -1. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Networks** > **Resolvers & Proxies**. +1. In [Cloudflare dashboard](https://dash.cloudflare.com/), go to **Zero Trust** > **Networks** > **Resolvers & Proxies**. + + + 2. Select **Proxy endpoints**. 3. [Create a proxy endpoint](#1-create-a-proxy-endpoint) or select an existing one, then select **Edit**. 4. Select **Add PAC files**. @@ -356,7 +366,10 @@ To get the domain of a proxy endpoint: -1. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Networks** > **Resolvers & Proxies** > **Proxy endpoints**. +1. In [Cloudflare dashboard](https://dash.cloudflare.com/), go to **Zero Trust** > **Networks** > **Resolvers & Proxies** > **Proxy endpoints**. + + + 2. Choose the proxy endpoint. Select **Edit**. 3. In **Proxy Endpoint**, copy the domain. @@ -464,7 +477,10 @@ You can modify proxy endpoint settings after creation. ### Edit authorization endpoint -1. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Networks** > **Resolvers & Proxies** > **Proxy endpoints**. +1. In [Cloudflare dashboard](https://dash.cloudflare.com/), go to **Zero Trust** > **Networks** > **Resolvers & Proxies** > **Proxy endpoints**. + + + 2. Locate your authorization endpoint (indicated by **Authorization** under **Type**). 3. Select the three dots, then select **Configure**. 4. Choose what to edit: @@ -475,7 +491,10 @@ You can modify proxy endpoint settings after creation. ### Edit source IP endpoint -1. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Networks** > **Resolvers & Proxies** > **Proxy endpoints**. +1. In [Cloudflare dashboard](https://dash.cloudflare.com/), go to **Zero Trust** > **Networks** > **Resolvers & Proxies** > **Proxy endpoints**. + + + 2. Locate your source IP endpoint (indicated by **Source IP** under **Type**). 3. Select the three dots, then select **Configure**. 4. Update the endpoint name or modify the allowed source IP addresses. diff --git a/src/content/docs/cloudflare-one/remote-browser-isolation/setup/clientless-browser-isolation.mdx b/src/content/docs/cloudflare-one/remote-browser-isolation/setup/clientless-browser-isolation.mdx index c0e775d854e..a150d41f3df 100644 --- a/src/content/docs/cloudflare-one/remote-browser-isolation/setup/clientless-browser-isolation.mdx +++ b/src/content/docs/cloudflare-one/remote-browser-isolation/setup/clientless-browser-isolation.mdx @@ -10,7 +10,7 @@ tags: - TLS --- -import { GlossaryTooltip, Render } from "~/components"; +import { DashButton, 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 One Client on their device. Use Clientless Web Isolation when you need to provide isolated browsing to unmanaged devices (for example, contractor laptops or personal phones) where you cannot install software. @@ -40,7 +40,10 @@ Your application will now be served in an isolated browser for users matching yo To open links using Browser Isolation: -1. In [Cloudflare One](https://one.dash.cloudflare.com), go to **Browser isolation** > **Browser isolation settings**. +1. In [Cloudflare dashboard](https://dash.cloudflare.com/), go to **Zero Trust** > **Browser isolation** > **Browser isolation settings**. + + + 2. Turn on **Allow users to open a remote browser without the device client**. 3. In **Launch browser**, enter the URL link, and then select **Launch**. Your URL will open in a secure isolated browser. diff --git a/src/content/docs/cloudflare-one/remote-browser-isolation/setup/index.mdx b/src/content/docs/cloudflare-one/remote-browser-isolation/setup/index.mdx index c45a25eaf8d..af0740f474d 100644 --- a/src/content/docs/cloudflare-one/remote-browser-isolation/setup/index.mdx +++ b/src/content/docs/cloudflare-one/remote-browser-isolation/setup/index.mdx @@ -9,6 +9,8 @@ sidebar: label: Get started --- +import { DashButton } from "~/components"; + Browser Isolation is enabled through [Secure Web Gateway HTTP policies](/cloudflare-one/traffic-policies/http-policies/). By default, no traffic is isolated until you have added an Isolate policy to your HTTP policies. ## 1. Connect devices to Cloudflare @@ -29,7 +31,10 @@ Setup instructions vary depending on how you want to connect your devices to Clo To configure Browser Isolation policies: -1. In [Cloudflare One](https://one.dash.cloudflare.com), go to **Traffic policies** > **Firewall policies** > **HTTP**. +1. In [Cloudflare dashboard](https://dash.cloudflare.com/), go to **Zero Trust** > **Traffic policies** > **Firewall policies** > **HTTP**. + + + 2. Select **Add a policy** and enter a name for the policy. 3. Use the HTTP policy [selectors](/cloudflare-one/traffic-policies/http-policies/#selectors) and [operators](/cloudflare-one/traffic-policies/http-policies/#comparison-operators) to specify the websites or content you want to isolate. 4. For **Action**, choose either [_Isolate_](/cloudflare-one/remote-browser-isolation/isolation-policies/#isolate) or [_Do not Isolate_](/cloudflare-one/remote-browser-isolation/isolation-policies/#do-not-isolate). diff --git a/src/content/docs/cloudflare-one/remote-browser-isolation/setup/non-identity.mdx b/src/content/docs/cloudflare-one/remote-browser-isolation/setup/non-identity.mdx index 81deb161780..e007905e586 100644 --- a/src/content/docs/cloudflare-one/remote-browser-isolation/setup/non-identity.mdx +++ b/src/content/docs/cloudflare-one/remote-browser-isolation/setup/non-identity.mdx @@ -8,6 +8,8 @@ sidebar: order: 5 --- +import { DashButton } from "~/components"; + On-ramps are the methods used to route traffic from your network to Cloudflare for inspection. With Cloudflare One, you can isolate HTTP traffic from on-ramps such as [proxy endpoints](/cloudflare-one/networks/resolvers-and-proxies/proxy-endpoints/) (which your browser connects to via PAC files to send traffic through Gateway) or [Cloudflare WAN](/cloudflare-wan/zero-trust/cloudflare-gateway/) (formerly Magic WAN, which connects your network to Cloudflare through GRE or IPsec tunnels). Since these on-ramps do not require users to log in to the Cloudflare One Client, [identity-based policies](/cloudflare-one/traffic-policies/identity-selectors/) are not supported. :::note @@ -22,6 +24,9 @@ If you want to apply Isolate policies based on user identity, you will need to e - Configure your browser to forward traffic to a Gateway proxy endpoint with [PAC files](/cloudflare-one/networks/resolvers-and-proxies/proxy-endpoints/) (Proxy Auto-Configuration files that tell the browser which traffic to route through the proxy). - Connect your enterprise site router to Gateway with the [anycast GRE or IPsec tunnel on-ramp to Cloudflare WAN](/cloudflare-wan/zero-trust/cloudflare-gateway/) (site-to-site encrypted tunnels between your network and Cloudflare). 3. Enable non-identity browser isolation: - 1. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Browser isolation** > **Browser isolation settings**. + 1. In [Cloudflare dashboard](https://dash.cloudflare.com/), go to **Zero Trust** > **Browser isolation** > **Browser isolation settings**. + + + 2. Turn on **Allow isolated HTTP traffic when user identity is unknown**. 4. Build a non-identity [HTTP policy](/cloudflare-one/remote-browser-isolation/isolation-policies/) to isolate websites in a remote browser. diff --git a/src/content/docs/cloudflare-one/reusable-components/custom-pages/gateway-block-page.mdx b/src/content/docs/cloudflare-one/reusable-components/custom-pages/gateway-block-page.mdx index f0ab810ee25..7365a18f8ce 100644 --- a/src/content/docs/cloudflare-one/reusable-components/custom-pages/gateway-block-page.mdx +++ b/src/content/docs/cloudflare-one/reusable-components/custom-pages/gateway-block-page.mdx @@ -8,7 +8,7 @@ sidebar: order: 1 --- -import { Render, Tabs, TabItem } from "~/components"; +import { DashButton, Render, Tabs, TabItem } from "~/components"; When Gateway blocks traffic with a [DNS](/cloudflare-one/traffic-policies/dns-policies/#block) or [HTTP Block policy](/cloudflare-one/traffic-policies/http-policies/#block), you can configure a block page to display in your users' browsers. You can provide a descriptive reason for blocking traffic and contact information, or you can redirect your users' browsers to another page. You can apply these customizations globally for every Block policy, or override the settings on a per-policy basis. @@ -22,7 +22,10 @@ Gateway will display a global block page in the browser of any user whose traffi To configure the global block page: -1. In [Cloudflare One](https://one.dash.cloudflare.com), go to **Reusable components** > **Custom pages**. +1. In [Cloudflare dashboard](https://dash.cloudflare.com/), go to **Zero Trust** > **Reusable components** > **Custom pages**. + + + 2. Under **Account Gateway block page**, Gateway will display the current block page setting. Select **Manage**. 3. Choose whether to use the [default Gateway block page](#use-the-default-block-page), a [URL redirect](#redirect-to-a-block-page), or a [custom Gateway block page](#customize-the-block-page). 4. Select **Save**. @@ -37,7 +40,10 @@ Instead of displaying the Cloudflare block page, you can configure Gateway to re To redirect users to a non-Cloudflare block page: -1. In [Cloudflare One](https://one.dash.cloudflare.com), go to **Reusable components** > **Custom pages**. +1. In [Cloudflare dashboard](https://dash.cloudflare.com/), go to **Zero Trust** > **Reusable components** > **Custom pages**. + + + 2. Under **Account Gateway block page**, select **Manage**. 3. Choose **URL redirect**. 4. Enter the URL you want to redirect blocked traffic to. diff --git a/src/content/docs/cloudflare-one/setup/index.mdx b/src/content/docs/cloudflare-one/setup/index.mdx index e781c09dd87..27034874ccf 100644 --- a/src/content/docs/cloudflare-one/setup/index.mdx +++ b/src/content/docs/cloudflare-one/setup/index.mdx @@ -26,7 +26,7 @@ Sign up for a [Cloudflare account](https://dash.cloudflare.com/sign-up) and enab ## What would you like to do? -These use cases match the guided onboarding in the [Cloudflare One dashboard](https://one.dash.cloudflare.com). To follow along in the dashboard, select **Get Started**. +These use cases match the guided onboarding in the [Cloudflare dashboard](https://dash.cloudflare.com/). To follow along in the dashboard, select **Get Started**. diff --git a/src/content/docs/cloudflare-one/setup/replace-vpn/device-to-network.mdx b/src/content/docs/cloudflare-one/setup/replace-vpn/device-to-network.mdx index fd94785b410..93c9a6c5279 100644 --- a/src/content/docs/cloudflare-one/setup/replace-vpn/device-to-network.mdx +++ b/src/content/docs/cloudflare-one/setup/replace-vpn/device-to-network.mdx @@ -17,7 +17,7 @@ Connect a remote device to a private network so your users can securely access i To explore other connection scenarios, refer to [Replace your VPN](/cloudflare-one/setup/replace-vpn/). -This guide follows the same steps as the **Get Started** onboarding wizard in the [Cloudflare One dashboard](https://one.dash.cloudflare.com). +This guide follows the same steps as the **Get Started** onboarding wizard in the [Cloudflare dashboard](https://dash.cloudflare.com/). ## How it works @@ -35,7 +35,7 @@ The [Cloudflare One Client](/cloud Cloudflare Tunnel establishes an outbound connection between your resources and Cloudflare. This is how new devices can reach your private network. You can install Tunnel on any Windows, Mac, or Linux device currently in your private network. -1. In [Cloudflare One](https://one.dash.cloudflare.com), select the **Get Started** tab. +1. In [Cloudflare dashboard](https://dash.cloudflare.com/), select the **Get Started** tab. 2. For **Replace my client-based or site-to-site VPN**, select **Get started**. 3. For **Device to network**, select **Continue**. 4. On the **Connect a remote device to a private network** screen, select **Continue**. @@ -104,7 +104,7 @@ After verifying your connection, consider securing your private network with pol - **Set up Gateway policies**: By default, all enrolled devices can reach your entire private network. Gateway policies let you scan, filter, and log traffic between your devices and your private network. For more information, refer to [DNS policies](/cloudflare-one/traffic-policies/dns-policies/), [Network policies](/cloudflare-one/traffic-policies/network-policies/), and [HTTP policies](/cloudflare-one/traffic-policies/http-policies/). - **Create an Access application**: Restrict access to specific applications or hostnames on your private network with identity-based rules. For more information, refer to [Secure a private IP or hostname](/cloudflare-one/access-controls/applications/non-http/self-hosted-private-app/). -- **Explore more with Zero Trust**: Review your tunnel, policies, and connected devices in the [Cloudflare One dashboard](https://one.dash.cloudflare.com). +- **Explore more with Zero Trust**: Review your tunnel, policies, and connected devices in the [Cloudflare dashboard](https://dash.cloudflare.com/). For in-depth guidance on policy design and device posture checks, refer to the [Replace your VPN learning path](/learning-paths/replace-vpn/concepts/). diff --git a/src/content/docs/cloudflare-one/setup/secure-private-apps/clientless-ssh.mdx b/src/content/docs/cloudflare-one/setup/secure-private-apps/clientless-ssh.mdx index 5fda8fec1cd..84451b653ea 100644 --- a/src/content/docs/cloudflare-one/setup/secure-private-apps/clientless-ssh.mdx +++ b/src/content/docs/cloudflare-one/setup/secure-private-apps/clientless-ssh.mdx @@ -17,7 +17,7 @@ Provide secure, in-browser command line access to an internal server without SSH To explore other access scenarios, refer to [Secure private apps](/cloudflare-one/setup/secure-private-apps/). -This guide follows the same steps as the **Get Started** experience in the [Cloudflare One dashboard](https://one.dash.cloudflare.com). +This guide follows the same steps as the **Get Started** experience in the [Cloudflare dashboard](https://dash.cloudflare.com/). ## How it works @@ -38,7 +38,7 @@ For details on connection methods and advanced configuration, refer to [Connect In this step, you describe the internal server you want to make available through Cloudflare. -1. In [Cloudflare One](https://one.dash.cloudflare.com), select the **Get Started** tab. +1. In [Cloudflare dashboard](https://dash.cloudflare.com/), select the **Get Started** tab. 2. For **Set up secure access to private apps from any browser**, select **Get started**. 3. For **Configure clientless SSH access to an internal service**, select **Continue**. 4. On the **Zero Trust SSH terminal directly from your browser** screen, select **Continue**. diff --git a/src/content/docs/cloudflare-one/setup/secure-private-apps/in-browser-rdp.mdx b/src/content/docs/cloudflare-one/setup/secure-private-apps/in-browser-rdp.mdx index 6b3c59e897f..8014fb540e6 100644 --- a/src/content/docs/cloudflare-one/setup/secure-private-apps/in-browser-rdp.mdx +++ b/src/content/docs/cloudflare-one/setup/secure-private-apps/in-browser-rdp.mdx @@ -18,7 +18,7 @@ Provide secure, in-browser remote desktop access to Windows hosts without Remote To explore other access scenarios, refer to [Secure private apps](/cloudflare-one/setup/secure-private-apps/). -This guide follows the same steps as the **Get Started** experience in the [Cloudflare One dashboard](https://one.dash.cloudflare.com). +This guide follows the same steps as the **Get Started** experience in the [Cloudflare dashboard](https://dash.cloudflare.com/). ## How it works @@ -39,7 +39,7 @@ For details on supported operating systems, connection methods, and known limita In this step, you describe the Windows host you want to make available through Cloudflare. -1. In [Cloudflare One](https://one.dash.cloudflare.com), select the **Get Started** tab. +1. In [Cloudflare dashboard](https://dash.cloudflare.com/), select the **Get Started** tab. 2. For **Set up secure access to private apps from any browser**, select **Get started**. 3. For **Enable in-browser remote desktop sessions to Windows hosts**, select **Continue**. 4. On the **Zero Trust RDP client directly from your browser** screen, select **Continue**. diff --git a/src/content/docs/cloudflare-one/setup/secure-private-apps/private-web-app.mdx b/src/content/docs/cloudflare-one/setup/secure-private-apps/private-web-app.mdx index b764ff1e34a..4b8078adf28 100644 --- a/src/content/docs/cloudflare-one/setup/secure-private-apps/private-web-app.mdx +++ b/src/content/docs/cloudflare-one/setup/secure-private-apps/private-web-app.mdx @@ -17,7 +17,7 @@ Connect a self-hosted web application to Cloudflare so authorized users can acce To explore other access scenarios, refer to [Secure private apps](/cloudflare-one/setup/secure-private-apps/). -This guide follows the same steps as the **Get Started** experience in the [Cloudflare One dashboard](https://one.dash.cloudflare.com). +This guide follows the same steps as the **Get Started** experience in the [Cloudflare dashboard](https://dash.cloudflare.com/). ## How it works @@ -36,7 +36,7 @@ This guide follows the same steps as the **Get Started** experience in the [Clou In this step, you describe the internal application you want to make available through Cloudflare. -1. In [Cloudflare One](https://one.dash.cloudflare.com), select the **Get Started** tab. +1. In [Cloudflare dashboard](https://dash.cloudflare.com/), select the **Get Started** tab. 2. For **Set up secure access to private apps from any browser**, select **Get started**. 3. For **Connect a private web application**, select **Continue**. 4. On the **Connect and access private web applications** screen, select **Continue**. diff --git a/src/content/docs/cloudflare-one/tutorials/entra-id-risky-users.mdx b/src/content/docs/cloudflare-one/tutorials/entra-id-risky-users.mdx index fbfa9dc10b8..a3a8b65cc50 100644 --- a/src/content/docs/cloudflare-one/tutorials/entra-id-risky-users.mdx +++ b/src/content/docs/cloudflare-one/tutorials/entra-id-risky-users.mdx @@ -13,7 +13,7 @@ tags: - SCIM --- -import { WranglerConfig } from "~/components"; +import { DashButton, WranglerConfig } from "~/components"; Microsoft Entra ID (formerly Azure Active Directory) calculates a user's [risk level](https://learn.microsoft.com/entra/id-protection/howto-identity-protection-investigate-risk) based on the probability that their account has been compromised. With Cloudflare Zero Trust, you can synchronize the Entra ID risky users list with Cloudflare Access and apply more stringent Zero Trust policies to users at higher risk. @@ -158,7 +158,9 @@ Cloudflare Access will now synchronize changes in group membership with Entra ID Finally, create a [Gateway HTTP policy](/cloudflare-one/traffic-policies/http-policies/) to isolate traffic for risky user groups. -1. In [Cloudflare One](https://one.dash.cloudflare.com), go to **Traffic policies** > **Firewall policies** > **HTTP**. +1. In [Cloudflare dashboard](https://dash.cloudflare.com/), go to **Zero Trust** > **Traffic policies** > **Firewall policies** > **HTTP**. + + 2. Select **Add a policy**. diff --git a/src/content/docs/cloudflare-one/tutorials/integrate-microsoft-mcas-teams.mdx b/src/content/docs/cloudflare-one/tutorials/integrate-microsoft-mcas-teams.mdx index ab595a65b90..e42435a96fd 100644 --- a/src/content/docs/cloudflare-one/tutorials/integrate-microsoft-mcas-teams.mdx +++ b/src/content/docs/cloudflare-one/tutorials/integrate-microsoft-mcas-teams.mdx @@ -12,6 +12,8 @@ tags: - Microsoft --- +import { DashButton } from "~/components"; + Many security teams rely on Microsoft MCAS (Microsoft Cloud App Security), Microsoft's CASB solution, to identify and block threats on the Internet, as well as allow or block access to cloud applications. This tutorial covers how to integrate MCAS with Cloudflare Zero Trust, and create Gateway HTTP policies to ensure visibility and control over data. Microsoft provides an MCAS API endpoint to allow queries to see which applications have been marked as blocked or allowed. With an MCAS API call, you can manage a URL category that contains the blocked URLs returned by the API query, and use the output to create a Hostname List that can be used by Gateway HTTP policies to block them. @@ -67,7 +69,10 @@ curl -v "https:///api/discovery_block_scripts/?format=120&type=all ## Adding a hostname list in Cloudflare One -1. In [Cloudflare One](https://one.dash.cloudflare.com), go to **Reusable components** > **Lists** +1. In [Cloudflare dashboard](https://dash.cloudflare.com/), go to **Zero Trust** > **Reusable components** > **Lists** + + + 2. Select **Upload CSV**. Even though the hostname list is not in CSV format, it will work with no issues. 3. Add a name for the list, specify _Hostnames_ as the list type, and give it a description. 4. Drag and drop your MCAS output file created via the API call, or you can select **Select a file**. diff --git a/src/content/docs/cloudflare-one/tutorials/m365-dedicated-egress-ips.mdx b/src/content/docs/cloudflare-one/tutorials/m365-dedicated-egress-ips.mdx index 20be140548c..1bf5fb6d1e5 100644 --- a/src/content/docs/cloudflare-one/tutorials/m365-dedicated-egress-ips.mdx +++ b/src/content/docs/cloudflare-one/tutorials/m365-dedicated-egress-ips.mdx @@ -14,6 +14,8 @@ tags: - IPv6 --- +import { DashButton } from "~/components"; + :::note Only available on Zero Trust Enterprise plans. @@ -33,7 +35,9 @@ Make sure you have: ## Create an egress policy in Cloudflare Gateway -1. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Traffic policies** > **Egress policies**. +1. In [Cloudflare dashboard](https://dash.cloudflare.com/), go to **Zero Trust** > **Traffic policies** > **Egress policies**. + + 2. Select **Add a policy**. diff --git a/src/content/docs/cloudflare-one/tutorials/r2-logs.mdx b/src/content/docs/cloudflare-one/tutorials/r2-logs.mdx index a78c2233c32..daa0e27d248 100644 --- a/src/content/docs/cloudflare-one/tutorials/r2-logs.mdx +++ b/src/content/docs/cloudflare-one/tutorials/r2-logs.mdx @@ -45,7 +45,10 @@ This tutorial covers how to build a [Cloudflare R2 bucket](/r2/buckets/) to stor ## Connect a Zero Trust Logpush job -1. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Insights** > **Logs**. Select **Manage Logpush**. +1. In [Cloudflare dashboard](https://dash.cloudflare.com/), go to **Zero Trust** > **Insights** > **Logs**. Select **Manage Logpush**. + + + 2. Select **Connect a service**. 3. Choose which data sets and fields you want to send to your bucket. Select **Next**. 4. Select **S3 Compatible**. diff --git a/src/content/docs/dns/internal-dns/get-started.mdx b/src/content/docs/dns/internal-dns/get-started.mdx index b760d0ce037..404c7972b87 100644 --- a/src/content/docs/dns/internal-dns/get-started.mdx +++ b/src/content/docs/dns/internal-dns/get-started.mdx @@ -143,7 +143,10 @@ Besides selecting an internal DNS view when setting up your resolver policies, y -1. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Traffic policies** > **Firewall policies** > **Resolver policies**. +1. In [Cloudflare dashboard](https://dash.cloudflare.com/), go to **Zero Trust** > **Traffic policies** > **Firewall policies** > **Resolver policies**. + + + 2. Select **Add a policy** and enter a name and description. 3. Create an expression for the traffic you wish to route. For guidance about selectors, operators, and values, refer to [Gateway resolver policies](/cloudflare-one/traffic-policies/resolver-policies/#selectors). 4. Select **Use Internal DNS**. Choose the view that queries matching the expression should be sent to. diff --git a/src/content/docs/email-security/migrate-to-email-security.mdx b/src/content/docs/email-security/migrate-to-email-security.mdx index 0f8848970f5..dbadcb2d71e 100644 --- a/src/content/docs/email-security/migrate-to-email-security.mdx +++ b/src/content/docs/email-security/migrate-to-email-security.mdx @@ -39,7 +39,7 @@ In Area 1, you [invite users](/email-security/account-setup/manage-account-membe To invite users in Zero Trust Email security: -1. Log in to [Cloudflare One](https://one.dash.cloudflare.com/). +1. Log in to [Cloudflare dashboard](https://dash.cloudflare.com/). 2. Go to **Manage Account**. 3. Select **Members** > **Invite** > [Add account members](/fundamentals/manage-members/manage/#add-account-members). diff --git a/src/content/docs/learning-paths/clientless-access/terraform/publish-apps-with-terraform.mdx b/src/content/docs/learning-paths/clientless-access/terraform/publish-apps-with-terraform.mdx index 4b572dc13e5..c705ccf22da 100644 --- a/src/content/docs/learning-paths/clientless-access/terraform/publish-apps-with-terraform.mdx +++ b/src/content/docs/learning-paths/clientless-access/terraform/publish-apps-with-terraform.mdx @@ -161,7 +161,7 @@ You can view your new tunnel in the Cloudflare dashboard under **Networking** > -Your Access application and policy are under **Zero Trust** > **Access controls** > **[Applications](https://dash.cloudflare.com/?to=/:account/one/access/apps)**. +Your Access application and policy are under **Zero Trust** > **Access controls** > **[Applications](https://dash.cloudflare.com/?to=/:account/one/access-controls/apps)**. :::note diff --git a/src/content/docs/learning-paths/secure-your-email/configure-email-security/active-directory-sync.mdx b/src/content/docs/learning-paths/secure-your-email/configure-email-security/active-directory-sync.mdx index a017783809f..75295be1a81 100644 --- a/src/content/docs/learning-paths/secure-your-email/configure-email-security/active-directory-sync.mdx +++ b/src/content/docs/learning-paths/secure-your-email/configure-email-security/active-directory-sync.mdx @@ -14,7 +14,7 @@ Directories are folders to store user data. Email security allows you to manage To manage your Microsoft 365 directory: -1. Log in to [Zero Trust ](https://one.dash.cloudflare.com/). +1. Log in to [Cloudflare dashboard](https://dash.cloudflare.com/). 2. Select **Email security**. 3. Select **Directories**. 4. Under **Directory name**, select **MS directory**. @@ -24,7 +24,7 @@ To manage your Microsoft 365 directory: To manage your Google Workspace Directory: -1. Log in to [Zero Trust ](https://one.dash.cloudflare.com/). +1. Log in to [Cloudflare dashboard](https://dash.cloudflare.com/). 2. Select **Email security**. 3. Select **Directories**. 4. Under **Directory name**, select **Google Workspace Directory**. diff --git a/src/content/docs/learning-paths/secure-your-email/configure-email-security/create-allow-policies.mdx b/src/content/docs/learning-paths/secure-your-email/configure-email-security/create-allow-policies.mdx index ce5a674615d..21a966e5e85 100644 --- a/src/content/docs/learning-paths/secure-your-email/configure-email-security/create-allow-policies.mdx +++ b/src/content/docs/learning-paths/secure-your-email/configure-email-security/create-allow-policies.mdx @@ -20,7 +20,7 @@ You can choose how Email security will handle messages that match your criteria: To configure allow policies: -1. Log in to [Cloudflare One](https://one.dash.cloudflare.com/). +1. Log in to [Cloudflare dashboard](https://dash.cloudflare.com/). 2. Select **Email security**. 3. Select **Settings**, then go to **Detection settings** > **Allow policies**. 4. On the **Detection settings** page, select **Add a policy**. diff --git a/src/content/docs/learning-paths/secure-your-email/configure-email-security/impersonation-registry.mdx b/src/content/docs/learning-paths/secure-your-email/configure-email-security/impersonation-registry.mdx index 0378058f8d8..6ac10f8965b 100644 --- a/src/content/docs/learning-paths/secure-your-email/configure-email-security/impersonation-registry.mdx +++ b/src/content/docs/learning-paths/secure-your-email/configure-email-security/impersonation-registry.mdx @@ -14,7 +14,7 @@ The impersonation registry protects against these attacks by looking for spoofs To add a user to the impersonation registry: -1. Log in to [Cloudflare One](https://one.dash.cloudflare.com/). +1. Log in to [Cloudflare dashboard](https://dash.cloudflare.com/). 2. Select **Email security**. 3. Select **Settings** > **Impersonation registry**. 4. Select **Add a user**. diff --git a/src/content/docs/learning-paths/secure-your-email/configure-email-security/set-additional-detections.mdx b/src/content/docs/learning-paths/secure-your-email/configure-email-security/set-additional-detections.mdx index ad7c97fb428..10e87e417b6 100644 --- a/src/content/docs/learning-paths/secure-your-email/configure-email-security/set-additional-detections.mdx +++ b/src/content/docs/learning-paths/secure-your-email/configure-email-security/set-additional-detections.mdx @@ -17,7 +17,7 @@ Email security allows you to configure the following additional detections: To configure additional detections: -1. Log in to [Cloudflare One](https://one.dash.cloudflare.com/). +1. Log in to [Cloudflare dashboard](https://dash.cloudflare.com/). 2. Select **Email security**. 3. Select **Settings**. 4. On the Settings page, go to **Detection settings** > **Additional detections**, and select **Edit**. diff --git a/src/content/docs/learning-paths/secure-your-email/enable-auto-moves/configure-auto-moves.mdx b/src/content/docs/learning-paths/secure-your-email/enable-auto-moves/configure-auto-moves.mdx index 0182e9c8c20..4b87c1ec001 100644 --- a/src/content/docs/learning-paths/secure-your-email/enable-auto-moves/configure-auto-moves.mdx +++ b/src/content/docs/learning-paths/secure-your-email/enable-auto-moves/configure-auto-moves.mdx @@ -10,7 +10,7 @@ products: To configure auto-move events: -1. Log in to [Cloudflare One](https://one.dash.cloudflare.com/). +1. Log in to [Cloudflare dashboard](https://dash.cloudflare.com/). 2. Select **Email security**. 3. Select **Settings**. 4. Select **Moves**. diff --git a/src/content/docs/learning-paths/secure-your-email/get-started/setup-google-workspace.mdx b/src/content/docs/learning-paths/secure-your-email/get-started/setup-google-workspace.mdx index 28bf9247f9c..fee4b91d3af 100644 --- a/src/content/docs/learning-paths/secure-your-email/get-started/setup-google-workspace.mdx +++ b/src/content/docs/learning-paths/secure-your-email/get-started/setup-google-workspace.mdx @@ -8,7 +8,7 @@ products: - email-security --- -1. Log in to [Cloudflare One](https://one.dash.cloudflare.com/). +1. Log in to [Cloudflare dashboard](https://dash.cloudflare.com/). 2. Select **Email security** > **Settings**. 3. Select **Connect an integration**, choose **Google Workspace CASB + EMAIL**, then select **Select Integration**. 4. Follow the wizard to create an integration, then select **Create Integration**. Refer to [Enable Gmail BCC integration](/cloudflare-one/email-security/setup/post-delivery-deployment/bcc-journaling/bcc-setup/gmail-bcc-setup/enable-gmail-integration/) for further instructions. \ No newline at end of file diff --git a/src/content/docs/learning-paths/secure-your-email/get-started/setup-ms-graph-api.mdx b/src/content/docs/learning-paths/secure-your-email/get-started/setup-ms-graph-api.mdx index 447dea2119c..26533e79825 100644 --- a/src/content/docs/learning-paths/secure-your-email/get-started/setup-ms-graph-api.mdx +++ b/src/content/docs/learning-paths/secure-your-email/get-started/setup-ms-graph-api.mdx @@ -8,7 +8,7 @@ products: - email-security --- -1. Log in to [Cloudflare One](https://one.dash.cloudflare.com/). +1. Log in to [Cloudflare dashboard](https://dash.cloudflare.com/). 2. Select **Email security** > **Settings**. 3. Select **Connect an integration**, choose **Microsoft CASB + EMAIL**, then select **Select Integration**. 4. Enable **Microsoft Integration**: diff --git a/src/content/docs/learning-paths/secure-your-email/monitor-your-inbox/index.mdx b/src/content/docs/learning-paths/secure-your-email/monitor-your-inbox/index.mdx index 99194b1606d..187330616c3 100644 --- a/src/content/docs/learning-paths/secure-your-email/monitor-your-inbox/index.mdx +++ b/src/content/docs/learning-paths/secure-your-email/monitor-your-inbox/index.mdx @@ -10,7 +10,7 @@ products: To access an overview of your account, the total number of emails processed, a breakdown of types of threads detected, and other useful information: -1. Log in to [Zero Trust.](https://one.dash.cloudflare.com/) +1. Log in to the [Cloudflare dashboard.](https://dash.cloudflare.com/) 2. Select **Email security**. Under **Email security**, select **Monitoring**. diff --git a/src/content/docs/reference-architecture/architectures/sase.mdx b/src/content/docs/reference-architecture/architectures/sase.mdx index 7c326f5a387..d0c4211a7b7 100644 --- a/src/content/docs/reference-architecture/architectures/sase.mdx +++ b/src/content/docs/reference-architecture/architectures/sase.mdx @@ -684,7 +684,7 @@ The dashboard shows a comprehensive summary of the entire device fleet, displayi Having acquired a comprehensive understanding of Cloudflare's SASE platform, you are now well-equipped to integrate it with existing infrastructure. This system efficiently secures access to applications for both employees and external users, starting from the initial request on the device and extending across every network to the application, regardless of its location. This powerful new model for securing networks, applications, devices, and users is built on the massive Cloudflare network and managed through an intuitive management interface. -It's worth noting that many of the capabilities described in this document can be used for free, without any time constraints, for up to 50 users. [Sign up](https://dash.cloudflare.com/sign-up) for an account and head to the [Cloudflare One](https://one.dash.cloudflare.com/) section. While this document has provided an overview of the platform as a whole, for those interested in delving deeper into specific areas, we recommend exploring the following resources. +It's worth noting that many of the capabilities described in this document can be used for free, without any time constraints, for up to 50 users. [Sign up](https://dash.cloudflare.com/sign-up) for an account and head to the [Cloudflare dashboard](https://dash.cloudflare.com/) section. While this document has provided an overview of the platform as a whole, for those interested in delving deeper into specific areas, we recommend exploring the following resources. | Topic | Content | | ------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | diff --git a/src/content/docs/security-center/indicator-feeds.mdx b/src/content/docs/security-center/indicator-feeds.mdx index 5340e416b2f..f562c322dcb 100644 --- a/src/content/docs/security-center/indicator-feeds.mdx +++ b/src/content/docs/security-center/indicator-feeds.mdx @@ -10,7 +10,7 @@ sidebar: order: 8 --- -import { Render } from "~/components"; +import { DashButton, Render } from "~/components"; Cloudflare's threat intelligence team crowdsources attack trends and protects users automatically, such as from zero-day vulnerabilities like the [HTTP/2 Rapid Reset attack](https://blog.cloudflare.com/technical-breakdown-http2-rapid-reset-ddos-attack/). However, in some cases, Cloudflare will partner with external entities that have their own feeds which can be shared with eligible Cloudflare users. @@ -137,7 +137,10 @@ Providers can create and manage a Custom Indicator Feed with the [Custom Indicat Once an account is granted access to a feed, it will be available to match traffic as a [selector in Gateway DNS policies](/cloudflare-one/traffic-policies/dns-policies/#indicator-feeds). -1. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Traffic policies** > **Firewall policies**. Select **DNS**. +1. In [Cloudflare dashboard](https://dash.cloudflare.com/), go to **Zero Trust** > **Traffic policies** > **Firewall policies**. Select **DNS**. + + + 2. To create a new DNS policy, select **Add a policy**. 3. Name your policy. 4. In **Traffic**, add a condition with the **Indicator Feeds** selector. If your account has been granted access to a Custom Indicator Feed, Gateway will list the feed in **Value**. For example, you can block sites that appear in a feed: diff --git a/src/content/partials/cloudflare-one/casb/aws-compute-account.mdx b/src/content/partials/cloudflare-one/casb/aws-compute-account.mdx index c4c2c368508..c48399e2b85 100644 --- a/src/content/partials/cloudflare-one/casb/aws-compute-account.mdx +++ b/src/content/partials/cloudflare-one/casb/aws-compute-account.mdx @@ -2,9 +2,14 @@ {} --- +import { DashButton } from "~/components"; + To connect a compute account to your AWS integration: -1. In [Cloudflare One](https://one.dash.cloudflare.com), go to **Cloud & SaaS findings** > **Integrations**. +1. In [Cloudflare dashboard](https://dash.cloudflare.com/), go to **Zero Trust** > **Cloud & SaaS findings** > **Integrations**. + + + 2. Find and select your AWS integration. 3. Select **Open connection instructions**. 4. Follow the instructions provided to connect a new compute account. diff --git a/src/content/partials/cloudflare-one/casb/manage-integrations.mdx b/src/content/partials/cloudflare-one/casb/manage-integrations.mdx index e4eec357f4d..acdb2ec499d 100644 --- a/src/content/partials/cloudflare-one/casb/manage-integrations.mdx +++ b/src/content/partials/cloudflare-one/casb/manage-integrations.mdx @@ -2,6 +2,8 @@ {} --- +import { DashButton } from "~/components"; + When you integrate a third-party SaaS application or cloud environment with Cloudflare CASB, you allow CASB to make API calls to its endpoint and read relevant data on your behalf. The CASB integration permissions are read-only and follow the least privileged model. In other words, only the minimum access required to perform a scan is granted. ### Prerequisites @@ -10,7 +12,10 @@ Before you can integrate a SaaS application or cloud environment with CASB, your ### Add an integration -1. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Cloud & SaaS findings** > **Integrations**. +1. In [Cloudflare dashboard](https://dash.cloudflare.com/), go to **Zero Trust** > **Cloud & SaaS findings** > **Integrations**. + + + 2. Select **Connect an integration** or **Add integration**. 3. Browse the available integrations and select the application you would like to add. 4. Follow the step-by-step integration instructions in the UI. @@ -22,7 +27,10 @@ Once CASB detects at least one finding, you can [view and manage your findings]( ### Pause an integration -1. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Cloud & SaaS findings** > **Integrations**. +1. In [Cloudflare dashboard](https://dash.cloudflare.com/), go to **Zero Trust** > **Cloud & SaaS findings** > **Integrations**. + + + 2. Find the integration you would like to pause and select **Configure**. 3. To stop scanning the application, turn off **Scan for findings**. 4. Select **Save integration**. @@ -35,7 +43,10 @@ You can resume CASB scanning at any time by turning on **Scan for findings**. When you delete an integration, all keys and OAuth data will be deleted. This means you cannot restore a deleted integration or its scanned data. ::: -1. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Cloud & SaaS findings** > **Integrations**. +1. In [Cloudflare dashboard](https://dash.cloudflare.com/), go to **Zero Trust** > **Cloud & SaaS findings** > **Integrations**. + + + 2. Find the integration you would like to delete and select **Configure**. 3. Select **Disenroll**. diff --git a/src/content/partials/cloudflare-one/clientless-browser-isolation.mdx b/src/content/partials/cloudflare-one/clientless-browser-isolation.mdx index fe7557d4765..5a01ed5ea89 100644 --- a/src/content/partials/cloudflare-one/clientless-browser-isolation.mdx +++ b/src/content/partials/cloudflare-one/clientless-browser-isolation.mdx @@ -3,5 +3,10 @@ --- -1. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Browser isolation** > **Browser isolation settings**. +import { DashButton } from "~/components"; + +1. In [Cloudflare dashboard](https://dash.cloudflare.com/), go to **Zero Trust** > **Browser isolation** > **Browser isolation settings**. + + + 2. Turn on **Allow users to open a remote browser without the device client**. \ No newline at end of file diff --git a/src/content/partials/cloudflare-one/dex/http-test-create-steps.mdx b/src/content/partials/cloudflare-one/dex/http-test-create-steps.mdx index 708d43bafc7..28154a88fdc 100644 --- a/src/content/partials/cloudflare-one/dex/http-test-create-steps.mdx +++ b/src/content/partials/cloudflare-one/dex/http-test-create-steps.mdx @@ -1,6 +1,11 @@ +import { DashButton } from "~/components"; + To set up an HTTP test for an application: -1. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Insights** > **Digital experience**. +1. In [Cloudflare dashboard](https://dash.cloudflare.com/), go to **Zero Trust** > **Insights** > **Digital experience**. + + + 2. Select the **Tests** tab. 3. Select **Add a Test**. 4. Fill in the following fields: diff --git a/src/content/partials/cloudflare-one/dex/pcaps-download.mdx b/src/content/partials/cloudflare-one/dex/pcaps-download.mdx index d12598c7476..5c2b4ae18cb 100644 --- a/src/content/partials/cloudflare-one/dex/pcaps-download.mdx +++ b/src/content/partials/cloudflare-one/dex/pcaps-download.mdx @@ -2,7 +2,12 @@ {} --- -1. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **DEX** > **Remote captures**. +import { DashButton } from "~/components"; + +1. In [Cloudflare dashboard](https://dash.cloudflare.com/), go to **Zero Trust** > **DEX** > **Remote captures**. + + + 2. Find a successful capture. 3. Select the three-dot menu and select **Download**. diff --git a/src/content/partials/cloudflare-one/dex/pcaps-run.mdx b/src/content/partials/cloudflare-one/dex/pcaps-run.mdx index 65a8f00486b..e4edb61a2ff 100644 --- a/src/content/partials/cloudflare-one/dex/pcaps-run.mdx +++ b/src/content/partials/cloudflare-one/dex/pcaps-run.mdx @@ -2,13 +2,16 @@ inputParameters: bestPractice --- -import { Render } from "~/components"; +import { DashButton, Render } from "~/components"; Devices must be actively connected to the Internet for remote captures to run. To capture data from a remote device: -1. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **DEX** > **Remote captures**. +1. In [Cloudflare dashboard](https://dash.cloudflare.com/), go to **Zero Trust** > **DEX** > **Remote captures**. + + + 2. Select up to 10 devices that you want to run a capture on. Devices must be [registered](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/deployment/) in your Zero Trust organization. 3. Configure the types of captures to run. - **Packet captures (PCAP)**: Performs packet captures for traffic outside of the WARP tunnel (default network interface) and traffic inside of the WARP tunnel ([virtual interface](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/route-traffic/client-architecture/#ip-traffic)). diff --git a/src/content/partials/cloudflare-one/dex/pcaps-view-warp-diag.mdx b/src/content/partials/cloudflare-one/dex/pcaps-view-warp-diag.mdx index 079d435bdb3..9979f000097 100644 --- a/src/content/partials/cloudflare-one/dex/pcaps-view-warp-diag.mdx +++ b/src/content/partials/cloudflare-one/dex/pcaps-view-warp-diag.mdx @@ -2,13 +2,16 @@ {} --- -import { Details } from "~/components"; +import { DashButton, Details } from "~/components"; The diagnostics analyzer highlights what Cloudflare determines to be the most important detection events in a `warp-diag` log. You can use the detection report to help parse your [log files](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/troubleshooting/diagnostic-logs/#warp-diag-logs) and identify the root cause of client issues. The diagnostics analyzer is only available for logs [collected via the dashboard](#collect-logs-via-the-dashboard). To access the diagnostics analyzer: -1. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **DEX** > **Remote captures**. +1. In [Cloudflare dashboard](https://dash.cloudflare.com/), go to **Zero Trust** > **DEX** > **Remote captures**. + + + 2. Locate an existing `warp-diag` log from the list or select **Run diagnostics** to generate a new `warp-diag` log. 3. Select the three dots for the `warp-diag` log that you want to analyze, then select **View Device Diag**. diff --git a/src/content/partials/cloudflare-one/email-security/domain-information.mdx b/src/content/partials/cloudflare-one/email-security/domain-information.mdx index 23143351441..8de17da944e 100644 --- a/src/content/partials/cloudflare-one/email-security/domain-information.mdx +++ b/src/content/partials/cloudflare-one/email-security/domain-information.mdx @@ -11,7 +11,7 @@ When you configure your domain, the Cloudflare dashboard will display you the fo - **Service address**: This is the email address you will use to send a copy of your email. - **Source**: Depending on how you added the domains, the dashboard will display **MS integration**, **Google**, **CF zones**, or **Manual add**. - **Integration name**: Name of the integration. This field will only be displayed for Microsoft integrations. To rename your integration: - 1. Log in to [Cloudflare One](https://one.dash.cloudflare.com/) > **Integrations** > **Cloud & SaaS**. + 1. Log in to [Cloudflare dashboard](https://dash.cloudflare.com/) > **Integrations** > **Cloud & SaaS**. 2. Locate your integration, select **Configure**, then select **Edit**. 3. Rename your integration, then select **Save**. - **Hops**: The number of hops. This will not be displayed if the configuration method is Microsoft Graph API. Hop count will be visible only if it has been configured. diff --git a/src/content/partials/cloudflare-one/email-security/post-verification-setup.mdx b/src/content/partials/cloudflare-one/email-security/post-verification-setup.mdx index 0b8d43681a9..ab4fbd8163c 100644 --- a/src/content/partials/cloudflare-one/email-security/post-verification-setup.mdx +++ b/src/content/partials/cloudflare-one/email-security/post-verification-setup.mdx @@ -2,10 +2,15 @@ {} --- +import { DashButton } from "~/components"; + ## Verify successful deployment To verify that the deployment has been successful and that your emails are being scanned: -1. In [Cloudflare One](https://one.dash.cloudflare.com/), select **Email security**. +1. In [Cloudflare dashboard](https://dash.cloudflare.com/), go to **Zero Trust** > **Email security**. + + + 2. Go to **Settings** > **Domain management** > **Domains**, then select **View**. 3. Under **Your domains**, locate your domain, and verify that **Status** (which describes the state of the configuration) displays **Active**. diff --git a/src/content/partials/networking-services/analytics/site-analytics.mdx b/src/content/partials/networking-services/analytics/site-analytics.mdx index 5f9269dba90..4a2cb5309d7 100644 --- a/src/content/partials/networking-services/analytics/site-analytics.mdx +++ b/src/content/partials/networking-services/analytics/site-analytics.mdx @@ -41,7 +41,7 @@ To start using network overview: <> **${props.networkOverviewPageName}**. `} inline={false} diff --git a/src/content/partials/networking-services/analytics/traceroutes.mdx b/src/content/partials/networking-services/analytics/traceroutes.mdx index b8299a5be86..91a67bb37be 100644 --- a/src/content/partials/networking-services/analytics/traceroutes.mdx +++ b/src/content/partials/networking-services/analytics/traceroutes.mdx @@ -14,7 +14,7 @@ You can run traceroutes to analyze the hop-by-hop Internet path and latency betw text={` To run a traceroute from a specific Cloudflare data center to your network: -1. Log in to [Cloudflare One](https://one.dash.cloudflare.com/) > **Insights**. +1. Log in to [Cloudflare dashboard](https://dash.cloudflare.com/) > **Insights**. 2. Go to **Network health** > **WAN connector health**. 3. Find the tunnel for the traceroute. 4. Select the three dots > **Traceroute details**. diff --git a/src/content/partials/networking-services/cloudflare-wan/third-party/ubiquiti.mdx b/src/content/partials/networking-services/cloudflare-wan/third-party/ubiquiti.mdx index 8ef69b83eb2..92ff8d3f27f 100644 --- a/src/content/partials/networking-services/cloudflare-wan/third-party/ubiquiti.mdx +++ b/src/content/partials/networking-services/cloudflare-wan/third-party/ubiquiti.mdx @@ -31,7 +31,7 @@ Connect a Ubiquiti UniFi Gateway to Cloudflare's network using Cloudflare WAN (f ) : ( Cloudflare One, and go to **Networks**. + text={`1. Log in to Cloudflare dashboard, and go to **Networks**. 2. Go to **Connectors** > **Cloudflare WAN**, and select **Create**.`} inline={false} /> @@ -99,7 +99,7 @@ Connect a Ubiquiti UniFi Gateway to Cloudflare's network using Cloudflare WAN (f ) : ( Cloudflare One, and go to **Networks**. + text={`1. Log in to Cloudflare dashboard, and go to **Networks**. 2. In **Cloudflare WAN**, find the IPsec tunnel you have just created.`} inline={false} /> @@ -129,7 +129,7 @@ Connect a Ubiquiti UniFi Gateway to Cloudflare's network using Cloudflare WAN (f ) : ( Cloudflare One, and go to **Networks**. + text={`1. Log in to Cloudflare dashboard, and go to **Networks**. 2. Go to **Routes** > **WAN routes** > **Create**.`} inline={false} /> @@ -161,7 +161,7 @@ Wait a few minutes, then access both Cloudflare and UniFi to verify the tunnel's ) : ( Cloudflare One, and go to **Insights**. + text={`1. Log in to Cloudflare dashboard, and go to **Insights**. 2. Go to **Network visibility** > **WAN connector health**. 3. Find the tunnel you have just created and make sure its status shows **Up**. Refer to [Check tunnel health in the dashboard](/cloudflare-one/networks/connectors/cloudflare-wan/configuration/common-settings/check-tunnel-health-dashboard/) for more information.`} inline={false} diff --git a/src/content/partials/networking-services/mconn/configure-connectors.mdx b/src/content/partials/networking-services/mconn/configure-connectors.mdx index d9f3d01c6d0..0da4ba863b8 100644 --- a/src/content/partials/networking-services/mconn/configure-connectors.mdx +++ b/src/content/partials/networking-services/mconn/configure-connectors.mdx @@ -346,7 +346,7 @@ To create a profile: { props.dashName === "CF1 Cloudflare WAN" && ( <>
    -
  1. Log in to Cloudflare One, and go to Networks.
    2. +
  2. Log in to Cloudflare dashboard, and go to Networks.
  3. Go to Connectors > Appliances > Create a profile.
@@ -580,7 +580,7 @@ When you are ready to connect your { props.magicWord === "virtual" ? props.produ <> Cloudflare One, and go to **Networks**. + 1. Log in to Cloudflare dashboard, and go to **Networks**. 2. Go to **Connectors** > **Appliances**. 3. Find the ${ props.magicWord === "virtual" ? props.productNameVirtual : props.productName } you want to activate, select the three dots next to it > **Edit**. Make sure you verify the serial number to choose the right ${ props.magicWord === "virtual" ? props.productNameVirtual : props.productName } you want to activate. 4. In the new window, the **Status** dropdown will show as **Deactivated**. Select it to change the status to **Activated**. @@ -862,7 +862,7 @@ To check the IPsec tunnels and static routes created by your { props.magicWord = <> Cloudflare One, and go to **Connectors**. + 1. Log in to Cloudflare dashboard, and go to **Connectors**. 2. In **Cloudflare WAN** you can inspect the IPsec tunnels created by your ${props.magicWord === "virtual" ? props.productNameVirtual : props.productName }. 3. In **Routes** you can inspect the static routes created by your ${props.magicWord === "virtual" ? props.productNameVirtual : props.productName }. diff --git a/src/content/partials/networking-services/mconn/maintenance/deactivate-connector.mdx b/src/content/partials/networking-services/mconn/maintenance/deactivate-connector.mdx index abb2c35e51b..21ad188c784 100644 --- a/src/content/partials/networking-services/mconn/maintenance/deactivate-connector.mdx +++ b/src/content/partials/networking-services/mconn/maintenance/deactivate-connector.mdx @@ -9,7 +9,7 @@ import { DashButton, Markdown } from '~/components'; <> Cloudflare One, and go to **Networks**. + 1. Log in to Cloudflare dashboard, and go to **Networks**. 2. Go to **Connectors** > **Appliances** > **Appliances**. 3. Find the Cloudflare One Appliance you want to deactivate, select the three dots next to it > **Edit**. `} diff --git a/src/content/partials/networking-services/mconn/maintenance/edit-basic-info.mdx b/src/content/partials/networking-services/mconn/maintenance/edit-basic-info.mdx index b11277c02a7..f7b4a1c3974 100644 --- a/src/content/partials/networking-services/mconn/maintenance/edit-basic-info.mdx +++ b/src/content/partials/networking-services/mconn/maintenance/edit-basic-info.mdx @@ -11,7 +11,7 @@ In **Basic information**, you can change the name and description of your Cloudf <> Cloudflare One, and go to **Networks**. + 1. Log in to Cloudflare dashboard, and go to **Networks**. 2. Go to **Connectors** > **Appliances** > **Appliances**. `} inline={false} diff --git a/src/content/partials/networking-services/mconn/maintenance/edit-network-settings.mdx b/src/content/partials/networking-services/mconn/maintenance/edit-network-settings.mdx index f71c11c0de5..68aea6b8773 100644 --- a/src/content/partials/networking-services/mconn/maintenance/edit-network-settings.mdx +++ b/src/content/partials/networking-services/mconn/maintenance/edit-network-settings.mdx @@ -9,7 +9,7 @@ import { DashButton, Markdown } from "~/components"; <> Cloudflare One, and go to **Networks**. + 1. Log in to Cloudflare dashboard, and go to **Networks**. 2. Go to **Connectors** > **Appliances** > **Profiles**. `} inline={false} diff --git a/src/content/partials/networking-services/mconn/maintenance/edit-sites.mdx b/src/content/partials/networking-services/mconn/maintenance/edit-sites.mdx index 7a5e68df4e8..d4ee39c3f08 100644 --- a/src/content/partials/networking-services/mconn/maintenance/edit-sites.mdx +++ b/src/content/partials/networking-services/mconn/maintenance/edit-sites.mdx @@ -9,7 +9,7 @@ import { DashButton, Markdown } from "~/components"; <> Cloudflare One > **Insights**. + 1. Log in to Cloudflare dashboard > **Insights**. 2. Go to **Network visibility** > **Traffic overview**, and find the site you want to make changes on. 3. Select the three dots next to it > **Edit**. 4. In **Basic information**, make changes to the site's name, description, and geographic coordinates. diff --git a/src/content/partials/networking-services/mconn/maintenance/edit-traffic-steering.mdx b/src/content/partials/networking-services/mconn/maintenance/edit-traffic-steering.mdx index 267156ca7a1..795b5729e3f 100644 --- a/src/content/partials/networking-services/mconn/maintenance/edit-traffic-steering.mdx +++ b/src/content/partials/networking-services/mconn/maintenance/edit-traffic-steering.mdx @@ -11,7 +11,7 @@ You can only add or remove applications to Breakout traffic and Prioritized traf <> Cloudflare One, and go to **Networks**. + 1. Log in to Cloudflare dashboard, and go to **Networks**. 2. Go to **Connectors** > **Appliances** > **Profiles**. `} inline={false} diff --git a/src/content/partials/networking-services/mconn/maintenance/heartbeat.mdx b/src/content/partials/networking-services/mconn/maintenance/heartbeat.mdx index c8f54f97a75..d62f43182ac 100644 --- a/src/content/partials/networking-services/mconn/maintenance/heartbeat.mdx +++ b/src/content/partials/networking-services/mconn/maintenance/heartbeat.mdx @@ -21,7 +21,7 @@ There are three symbols for the heartbeat signal that allow you to quickly check <> Cloudflare One, and go to **Networks**. + 1. Log in to Cloudflare dashboard, and go to **Networks**. 2. Go to **Connectors** > **Appliances** > **Appliances**. 3. Find your Cloudflare One Appliance, and place your cursor over the icon on the **Status** column to check the timestamp. The timestamp displays the last time Cloudflare One Appliance successfully contacted Cloudflare. `} diff --git a/src/content/partials/networking-services/mconn/maintenance/register-hardware-appliance.mdx b/src/content/partials/networking-services/mconn/maintenance/register-hardware-appliance.mdx index ad72dcbe7fe..e189034cf92 100644 --- a/src/content/partials/networking-services/mconn/maintenance/register-hardware-appliance.mdx +++ b/src/content/partials/networking-services/mconn/maintenance/register-hardware-appliance.mdx @@ -11,7 +11,7 @@ To set up and use the hardware version of Cloudflare One Appliance (formerly Mag { props.dashName === "CF1 Cloudflare WAN" && ( <>
    -
  1. Log in to Cloudflare One, and go to Networks.
    2. +
  2. Log in to Cloudflare dashboard, and go to Networks.
  3. Go to Connectors > Appliances, and select Register an appliance.
diff --git a/src/content/partials/networking-services/mconn/maintenance/remove-connectors.mdx b/src/content/partials/networking-services/mconn/maintenance/remove-connectors.mdx index fa154fec8ac..1744477984b 100644 --- a/src/content/partials/networking-services/mconn/maintenance/remove-connectors.mdx +++ b/src/content/partials/networking-services/mconn/maintenance/remove-connectors.mdx @@ -17,7 +17,7 @@ You can have more than one Cloudflare One Appliance in one profile if you initia <> Cloudflare One, and go to **Networks**. + 1. Log in to Cloudflare dashboard, and go to **Networks**. 2. Go to **Connectors** > **Appliances** > **Profiles**. `} inline={false} @@ -52,7 +52,7 @@ To remove a Cloudflare One Appliance from your account: <> Cloudflare One, and go to **Networks**. + 1. Log in to Cloudflare dashboard, and go to **Networks**. 2. Go to **Connectors** > **Appliances** > **Appliances**. `} inline={false} diff --git a/src/content/partials/networking-services/mconn/network-options/app-aware-policies/breakout-prioritized.mdx b/src/content/partials/networking-services/mconn/network-options/app-aware-policies/breakout-prioritized.mdx index 7eb868cf827..95ed4584984 100644 --- a/src/content/partials/networking-services/mconn/network-options/app-aware-policies/breakout-prioritized.mdx +++ b/src/content/partials/networking-services/mconn/network-options/app-aware-policies/breakout-prioritized.mdx @@ -99,7 +99,7 @@ You need to configure {props.featureName} applications for each of your existing <> Cloudflare One dashboard, and go to **Networks**. + 1. Log in to the Cloudflare dashboard, and go to **Networks**. 2. Go to **Connectors** > **Appliances** > **Profiles**. `} inline={false} @@ -228,7 +228,7 @@ The traffic for the application you chose ${props.whatHappensApp}. <> Cloudflare One dashboard, and go to **Networks**. + 1. Log in to the Cloudflare dashboard, and go to **Networks**. 2. Go to **Connectors** > **Appliances** > **Profiles**. `} inline={false} @@ -333,7 +333,7 @@ To pin applications to a WAN port: <> Cloudflare One dashboard, and go to **Networks**. + 1. Log in to the Cloudflare dashboard, and go to **Networks**. 2. Go to **Connectors** > **Appliances** > **Profiles**. 3. Select the Cloudflare One Appliance you want to configure > **Edit**. `} diff --git a/src/content/partials/networking-services/mconn/network-options/dhcp/dhcp-relay.mdx b/src/content/partials/networking-services/mconn/network-options/dhcp/dhcp-relay.mdx index a00df213960..44a048d5b10 100644 --- a/src/content/partials/networking-services/mconn/network-options/dhcp/dhcp-relay.mdx +++ b/src/content/partials/networking-services/mconn/network-options/dhcp/dhcp-relay.mdx @@ -43,7 +43,7 @@ To configure DHCP relay: <> Cloudflare One, and go to **Networks**. + 1. Log in to Cloudflare dashboard, and go to **Networks**. 2. Go to **Connectors** > **Appliances** > **Profiles**. `} inline={false} diff --git a/src/content/partials/networking-services/mconn/network-options/dhcp/dhcp-server.mdx b/src/content/partials/networking-services/mconn/network-options/dhcp/dhcp-server.mdx index 94056a78a61..d0bcb4ed259 100644 --- a/src/content/partials/networking-services/mconn/network-options/dhcp/dhcp-server.mdx +++ b/src/content/partials/networking-services/mconn/network-options/dhcp/dhcp-server.mdx @@ -13,7 +13,7 @@ When you use a static IP address, Cloudflare One Appliance (formerly Magic WAN C <> Cloudflare One, and go to **Networks**. + 1. Log in to Cloudflare dashboard, and go to **Networks**. 2. Go to **Connectors** > **Appliances** > **Profiles**. `} inline={false} diff --git a/src/content/partials/networking-services/mconn/network-options/network-segmentation.mdx b/src/content/partials/networking-services/mconn/network-options/network-segmentation.mdx index 6243e2b3a08..7eaf3c9d334 100644 --- a/src/content/partials/networking-services/mconn/network-options/network-segmentation.mdx +++ b/src/content/partials/networking-services/mconn/network-options/network-segmentation.mdx @@ -52,7 +52,7 @@ Follow these steps to create a new LAN policy to segment your network. Only the <> Cloudflare One, and go to **Networks**. + 1. Log in to Cloudflare dashboard, and go to **Networks**. 2. Go to **Connectors** > **Appliances** > **Profiles**. `} inline={false} @@ -203,7 +203,7 @@ The new policy will ensure that traffic between the specified LANs flows locally <> Cloudflare One, and go to **Networks**. + 1. Log in to Cloudflare dashboard, and go to **Networks**. 2. Go to **Connectors** > **Appliances** > **Profiles**. `} inline={false} @@ -315,7 +315,7 @@ Example: <> Cloudflare One, and go to **Networks**. + 1. Log in to Cloudflare dashboard, and go to **Networks**. 2. Go to **Connectors** > **Appliances** > **Profiles**. `} inline={false} diff --git a/src/content/partials/networking-services/routing/configure-routes.mdx b/src/content/partials/networking-services/routing/configure-routes.mdx index 892df6d2a1c..0f3b75e1afe 100644 --- a/src/content/partials/networking-services/routing/configure-routes.mdx +++ b/src/content/partials/networking-services/routing/configure-routes.mdx @@ -64,7 +64,7 @@ The dashboard **Routes** page shows the routes for all of your connectors — in <> Cloudflare One, and go to **Networks**. + 1. Log in to Cloudflare dashboard, and go to **Networks**. 2. Go to **Routes** > **WAN Routes**, and select **Create** to add a new route. `} inline={false} @@ -433,7 +433,7 @@ To set this ASN: <> Cloudflare One, and go to **Networks**. + 1. Log in to Cloudflare dashboard, and go to **Networks**. 2. Go to **Routes** > **WAN configuration**. 3. In **Border Gateway Protocol (BGP) configuration**, select **Edit** and enter your ASN. 4. Select **Save**. @@ -520,7 +520,7 @@ BGP over CNI is in closed beta and is not currently available to new customers. <> Cloudflare One, and go to **Networks**. + 1. Log in to Cloudflare dashboard, and go to **Networks**. 2. Go to **Routes** > **WAN configuration**. 3. In **Border Gateway Protocol (BGP) configuration**, select **Edit ASN** and enter your ASN. 4. Go to **Networks** > **Connectors** > **Interconnects**. @@ -574,7 +574,7 @@ BGP over CNI is in closed beta and is not currently available to new customers. <> Cloudflare One, and go to **Networks**. + 1. Log in to Cloudflare dashboard, and go to **Networks**. 2. Go to **Routes** > **WAN configuration**. 3. In **Border Gateway Protocol (BGP) configuration**, select **Edit ASN** and enter your ASN. 4. Go to **Networks** > **Connectors** > **Cloudflare WAN**. diff --git a/src/content/partials/networking-services/routing/configure-tunnels.mdx b/src/content/partials/networking-services/routing/configure-tunnels.mdx index 4ebe94c3499..40975fd147e 100644 --- a/src/content/partials/networking-services/routing/configure-tunnels.mdx +++ b/src/content/partials/networking-services/routing/configure-tunnels.mdx @@ -94,7 +94,7 @@ Beyond GRE and IPsec tunnels, you can also use Network Interconnect (CNI) to onb <> Cloudflare One, and go to **Networks**. + 1. Log in to Cloudflare dashboard, and go to **Networks**. 2. Go to **Connectors** > **Cloudflare WAN**, and select **Create**. 3. On the **Add Tunnel** page, choose either a **GRE tunnel** or **IPsec tunnel**. `} diff --git a/src/content/partials/networking-services/sites/sites.mdx b/src/content/partials/networking-services/sites/sites.mdx index e49acf781ff..a544e465fe8 100644 --- a/src/content/partials/networking-services/sites/sites.mdx +++ b/src/content/partials/networking-services/sites/sites.mdx @@ -25,7 +25,7 @@ Before creating a site, ensure you have set up at least one on-ramp. Then, follo <> **Network visibility**. 3. In **Network overview**, select **Add site**. 4. Add a name and description for your new site. Optionally, you can also add the geographical coordinates for your site in **Latitude** and **Longitude**. If you add geographical coordinates, your site's location will appear in the map once created. @@ -98,7 +98,7 @@ Your site is now set up. If you have other sites you need to set up, repeat the <> **Network visibility**. 3. In **Network overview** > **Traffic overview**, find your site > select the three dots in front of it > **Edit**. 4. Select **On-ramps**. diff --git a/src/content/partials/networking-services/tunnel-health/check-tunnel-healthchecks-dash.mdx b/src/content/partials/networking-services/tunnel-health/check-tunnel-healthchecks-dash.mdx index 33f16ff7be3..1ab8e127be1 100644 --- a/src/content/partials/networking-services/tunnel-health/check-tunnel-healthchecks-dash.mdx +++ b/src/content/partials/networking-services/tunnel-health/check-tunnel-healthchecks-dash.mdx @@ -26,7 +26,7 @@ Not all data centers are relevant to you at all times. You can refer to the **Tr <> **Insights**. 2. Go to **Network health** > **WAN connector health**. 3. In this view you can access a list of your tunnels and their current health status. You can also check the amount of health checks passed in the last hour as well as traffic volume for each tunnel. 4. Find the tunnel you want to inspect, select the three dots next to it, and choose: @@ -72,7 +72,7 @@ You can drill down into a specific tunnel to check its health status and other i <> **Insights**. 2. Go to **Network health** > **WAN connector health**. `} inline={false} diff --git a/src/content/partials/networking-services/tunnel-health/update-tunnel-health-checks-frequency.mdx b/src/content/partials/networking-services/tunnel-health/update-tunnel-health-checks-frequency.mdx index 62940d5dfcc..c8a7a0d861e 100644 --- a/src/content/partials/networking-services/tunnel-health/update-tunnel-health-checks-frequency.mdx +++ b/src/content/partials/networking-services/tunnel-health/update-tunnel-health-checks-frequency.mdx @@ -96,7 +96,7 @@ The following example adjusts tunnel health check frequency to `low`. Note that ) : ( **Networks**. +1. Log in to [Cloudflare dashboard](https://dash.cloudflare.com/) > **Networks**. 2. Go to **Connectors** > **Appliances**. 3. In **Profiles**, find the Connector profile you want to edit > select the three dots > **Edit**. 4. In **Network Configuration** > **WAN configuration** > select your WAN > **Edit**.