ddos protection dashbutton

patriciasantaana · patriciasantaana · commit 06e8852eb709 · 2025-09-02T13:44:11.000-07:00
diff --git a/src/content/docs/ddos-protection/advanced-ddos-systems/how-to/add-prefix-allowlist.mdx b/src/content/docs/ddos-protection/advanced-ddos-systems/how-to/add-prefix-allowlist.mdx
@@ -8,17 +8,18 @@ head:
     content: Add an IP address/prefix to the Advanced DDoS Protection allowlist
 ---
 
-import { Render, Steps } from "~/components";
+import { Render, Steps, DashButton } from "~/components";
 
 To add an IP address or prefix to the Advanced DDoS Protection [allowlist](/ddos-protection/advanced-ddos-systems/concepts/#allowlist):
 
 <Steps>
-	1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com) and
-	select your account. 2. Go to **L3/4 DDoS** > **Advanced Protection**. 3.
-	Under **General settings** > **Allowlist**, select **Edit**. 4. Enter a prefix
-	and (optionally) a description in **Prefix** and **Description**,
-	respectively. 5. To exclude the current prefix from the allowlist instead of
-	including it, uncheck the **Enabled** checkbox. 6. Select **Add**.
+	1. In the Cloudflare dashboard, go to the **L3/4 DDoS** page.
+ 
+		<DashButton url="/?to=/:account/network-security/ddos" />
+	2. Go to **Advanced Protection**. 
+	3. Under **General settings** > **Allowlist**, select **Edit**.
+	4. Enter a prefix and (optionally) a description in **Prefix** and **Description**, respectively.
+	5. To exclude the current prefix from the allowlist instead of including it, uncheck the **Enabled** checkbox. 6. Select **Add**.
 </Steps>
 
 <Render file="allowlist-ip-spoofing" product="ddos-protection" />
diff --git a/src/content/docs/ddos-protection/advanced-ddos-systems/how-to/add-prefix.mdx b/src/content/docs/ddos-protection/advanced-ddos-systems/how-to/add-prefix.mdx
@@ -8,16 +8,18 @@ head:
     content: Add a prefix to Advanced DDoS Protection
 
 ---
-import { Steps } from "~/components"
+import { Steps, DashButton } from "~/components"
 
 To add a [prefix](/ddos-protection/advanced-ddos-systems/concepts/#prefixes) to Advanced DDoS Protection:
 
 <Steps>
-1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com) and select your account.
-2. Go to **L3/4 DDoS** > **Advanced Protection**.
-3. Under **General settings** > **Prefixes**, select **Edit**.
-4. Expand the **Add existing prefix** section and select **Add** next to the prefix you wish to add.<br/>
-   Alternatively, enter a prefix and (optionally) a description in **Prefix** and **Description**, respectively, and select **Add**.
+	1. In the Cloudflare dashboard, go to the **L3/4 DDoS** page.
+ 
+		<DashButton url="/?to=/:account/network-security/ddos" />
+	2. Go to **Advanced Protection**. 
+  3. Under **General settings** > **Prefixes**, select **Edit**.
+  4. Expand the **Add existing prefix** section and select **Add** next to the prefix you wish to add.<br/>
+    Alternatively, enter a prefix and (optionally) a description in **Prefix** and **Description**, respectively, and select **Add**.
 </Steps>
 
 :::note[Note]
diff --git a/src/content/docs/ddos-protection/advanced-ddos-systems/how-to/create-filter.mdx b/src/content/docs/ddos-protection/advanced-ddos-systems/how-to/create-filter.mdx
@@ -24,15 +24,16 @@ To create a [filter](/ddos-protection/advanced-ddos-systems/concepts/#filter) fo
 
 {/* prettier-ignore */}
 <Steps>
-1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com) and
-	select your account.
-2. Go to **L3/4 DDoS** > **Advanced Protection** > **Advanced TCP Protection**.
-3. Under the system component for which you are creating the filter (**SYN Flood Protection** or **Out-of-state TCP Protection**), select **Create** next to the type of filter you want to create:
-	- **Mitigation Filter**: The protection system will drop <GlossaryTooltip term="data packet">packets</GlossaryTooltip> matching the filter expression. - **Monitoring Filter**: The protection system will log
-	packets matching the filter expression.
-	- **Off Filter**: The protection system will ignore packets matching the filter expression.
-4. Under **When incoming packets match**, define a filter expression using the Expression Builder (specifying one or more values for **Field**, **Operator**, and **Value**), or manually enter an expression using the Expression Editor. For more information, refer to [Edit rule expressions](/ruleset-engine/rules-language/expressions/edit-expressions/).
-5. Select **Save**.
+		1. In the Cloudflare dashboard, go to the **L3/4 DDoS** page.
+ 
+		<DashButton url="/?to=/:account/network-security/ddos" />
+	2. Go to **Advanced Protection** > **Advanced TCP Protection**.
+	3. Under the system component for which you are creating the filter (**SYN Flood Protection** or **Out-of-state TCP Protection**), select **Create** next to the type of filter you want to create:
+		- **Mitigation Filter**: The protection system will drop <GlossaryTooltip term="data packet">packets</GlossaryTooltip> matching the filter expression. - **Monitoring Filter**: The protection system will log
+		packets matching the filter expression.
+		- **Off Filter**: The protection system will ignore packets matching the filter expression.
+	4. Under **When incoming packets match**, define a filter expression using the Expression Builder (specifying one or more values for **Field**, **Operator**, and **Value**), or manually enter an expression using the Expression Editor. For more information, refer to [Edit rule expressions](/ruleset-engine/rules-language/expressions/edit-expressions/).
+	5. Select **Save**.
 </Steps>
 
 <Render file="atp-filters-rules-precedence" product="ddos-protection" />
diff --git a/src/content/docs/ddos-protection/advanced-ddos-systems/how-to/create-rule.mdx b/src/content/docs/ddos-protection/advanced-ddos-systems/how-to/create-rule.mdx
@@ -8,16 +8,19 @@ head:
     content: Create an Advanced DDoS Protection rule
 ---
 
-import { Render, Steps } from "~/components";
+import { Render, Steps, DashButton } from "~/components";
 
 ## Create an Advanced TCP Protection rule
 
 To create a [SYN flood rule](/ddos-protection/advanced-ddos-systems/overview/advanced-tcp-protection/#syn-flood-protection) or an [out-of-state TCP](/ddos-protection/advanced-ddos-systems/overview/advanced-tcp-protection/#out-of-state-tcp-protection) rule:
 
 {/* prettier-ignore */}
 <Steps>
-	1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com) and 	select your account.
-	2. Go to **L3/4 DDoS** > **Advanced Protection** > 	**Advanced TCP Protection**.
+	1. In the Cloudflare dashboard, go to the **L3/4 DDoS** page.
+ 
+		<DashButton url="/?to=/:account/network-security/ddos" />
+		
+	2. Go to **Advanced Protection** > **Advanced TCP Protection**.
 	3. Depending on the rule you are creating, do one of the following:
 		- Under **SYN Flood Protection**, select **Create SYN flood rule**.
 		- Under **Out-of-state TCP Protection**, select **Create out-of-state TCP rule**.
@@ -33,8 +36,10 @@ To create a [SYN flood rule](/ddos-protection/advanced-ddos-systems/overview/adv
 
 {/* prettier-ignore */}
 <Steps>
-1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/login) and select your account.
-2. Go to **L3/4 DDoS** > **Advanced Protection** > **General settings**.
+1. In the Cloudflare dashboard, go to the **L3/4 DDoS** page.
+
+	<DashButton url="/?to=/:account/network-security/ddos" />
+2. Go to **Advanced Protection** > **General settings**.
 3. Add the prefixes you wish to onboard. Advanced DNS Protection will only be applied to the prefixes you onboard. If you already onboarded the desired prefixes when you configured Advanced TCP Protection, you do not need to take any other action.
    :::note
 		Currently, the list of onboarded prefixes is shared with Advanced TCP Protection. Any onboarded prefixes will be subject to both Advanced TCP Protection and Advanced DNS Protection, assuming that your account team has done the initial configuration of both systems. However, you can leave Advanced TCP Protection in monitoring mode.
diff --git a/src/content/docs/ddos-protection/advanced-ddos-systems/how-to/exclude-prefix.mdx b/src/content/docs/ddos-protection/advanced-ddos-systems/how-to/exclude-prefix.mdx
@@ -6,13 +6,14 @@ sidebar:
 
 ---
 
-import { Steps } from "~/components"
+import { Steps, DashButton } from "~/components"
 
 To exclude a prefix or a prefix subset from Advanced DDoS Protection:
 
 <Steps>
-1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com) and select your account.
-2. Go to **L3/4 DDoS** > **Advanced Protection**.
+1. In the Cloudflare dashboard, go to the **L3/4 DDoS** page.
+    <DashButton url="/?to=/:account/network-security/ddos" />
+2. Go to **Advanced Protection**.
 3. [Add the prefix](/ddos-protection/advanced-ddos-systems/how-to/add-prefix/) you previously onboarded to Magic Transit to Advanced TCP Protection.
 4. [Add the prefix](/ddos-protection/advanced-ddos-systems/how-to/add-prefix/) (or subset) you wish to exclude as a new, separate prefix in Advanced TCP Protection.
 5. For the prefix you added in the previous step, select **Exclude Subset** in the **Enrolled Prefixes** list.
diff --git a/src/content/docs/ddos-protection/advanced-ddos-systems/overview/index.mdx b/src/content/docs/ddos-protection/advanced-ddos-systems/overview/index.mdx
@@ -9,7 +9,7 @@ head:
     content: Advanced DDoS Protection systems
 ---
 
-import { GlossaryTooltip, Render, Steps } from "~/components";
+import { GlossaryTooltip, Render, Steps, DashButton } from "~/components";
 
 The Advanced DDoS Protection system includes [Advanced TCP Protection](/ddos-protection/advanced-ddos-systems/overview/advanced-tcp-protection/) and [Advanced DNS Protection](/ddos-protection/advanced-ddos-systems/overview/advanced-dns-protection/). Both systems are configured using the general settings, but also comprise of their own dedicated settings.
 
@@ -115,8 +115,9 @@ Optionally, you can create [filters](/ddos-protection/advanced-ddos-systems/conc
 Enable the Advanced DDoS system and begin routing traffic through it.
 
 <Steps>
-	1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/) and
-	select your account.
-  2. Go to **L3/4 DDoS** > **Advanced Protection** > **General settings**.
+	1. In the Cloudflare dashboard, go to the **L3/4 DDoS** page.
+ 
+		<DashButton url="/?to=/:account/network-security/ddos" />	
+	2. Go to **Advanced Protection** > **General settings**.
   3. Under **General settings**, toggle the feature status **On**.
 </Steps>
diff --git a/src/content/docs/ddos-protection/botnet-threat-feed.mdx b/src/content/docs/ddos-protection/botnet-threat-feed.mdx
@@ -11,7 +11,7 @@ learning_center:
   link: https://www.cloudflare.com/learning/ddos/what-is-a-ddos-botnet/
 
 ---
-import { Steps, APIRequest } from "~/components"
+import { Steps, APIRequest, DashButton } from "~/components"
 
 The Cloudflare DDoS Botnet Threat Feed is a threat intelligence feed for service providers (SPs) such as hosting providers and Internet service providers (ISPs) that provides information about their own IP addresses that have participated in HTTP DDoS attacks as observed from Cloudflare's global network. The feed aims to help service providers stop the abuse and reduce DDoS attacks originating from within their networks.
 
@@ -46,11 +46,12 @@ Make sure that:
 ### 1. Authenticate your ASN via PeeringDB
 
 <Steps>
-1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/) and select your account.
-2. Go to **Manage Account** > **Configurations**.
-3. Select **DDoS Threat Feed ASNs**.
-4. On the list of ASNs configured for your threat feed, select **Add ASN**.
-5. You will be redirected to the PeeringDB authentication page, where you can log in and consent to share the affiliation data with us. You will be redirected back to the configuration page once it is successful.
+1. In the Cloudflare dashboard, go to your account settings page.
+    
+    <DashButton url="/?to=/:account/configurations" />
+2. Select **DDoS Threat Feed ASNs**.
+3. On the list of ASNs configured for your threat feed, select **Add ASN**.
+4. You will be redirected to the PeeringDB authentication page, where you can log in and consent to share the affiliation data with us. You will be redirected back to the configuration page once it is successful.
 </Steps>
 
 :::note
diff --git a/src/content/docs/ddos-protection/get-started.mdx b/src/content/docs/ddos-protection/get-started.mdx
@@ -51,9 +51,8 @@ The _Log_ action is only available to Enterprise customers.
 :::
 
 <Steps>
-1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/), and select your account.
-2. [Configure all the rules in the HTTP DDoS Attack Protection managed ruleset](/ddos-protection/managed-rulesets/http/http-overrides/configure-dashboard/#create-a-ddos-override), setting their action to _Log_.
-3. [Configure all the rules in the Network-layer DDoS Attack Protection managed ruleset](/ddos-protection/managed-rulesets/network/network-overrides/configure-dashboard/#create-a-ddos-override), setting the action to _Log_.
+1. [Configure all the rules in the HTTP DDoS Attack Protection managed ruleset](/ddos-protection/managed-rulesets/http/http-overrides/configure-dashboard/#access), setting their action to _Log_.
+2. [Configure all the rules in the Network-layer DDoS Attack Protection managed ruleset](/ddos-protection/managed-rulesets/network/network-overrides/configure-dashboard/#create-a-ddos-override), setting the action to _Log_.
 </Steps>
 
 Alternatively, if you are using the API, define an override at the ruleset level to set the action of all managed ruleset rules to `log` by following these instructions:
diff --git a/src/content/docs/ddos-protection/managed-rulesets/adaptive-protection.mdx b/src/content/docs/ddos-protection/managed-rulesets/adaptive-protection.mdx
@@ -7,7 +7,7 @@ sidebar:
 
 ---
 
-import { Tabs, TabItem, Steps } from "~/components"
+import { Tabs, TabItem, Steps, DashButton } from "~/components"
 
 Adaptive DDoS Protection learns your unique traffic patterns and adapts to them to provide better protection against sophisticated DDoS attacks on layer 7 and layers 3/4, depending on your subscribed Cloudflare services.
 
@@ -71,9 +71,10 @@ To view traffic flagged by L3/4 Adaptive DDoS Protection rules:
 <Tabs syncKey="dashNewNav"> 
   <TabItem label="Old dashboard">
     <Steps>
-      1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/) and select your account.
-      2. Go to Account Home > **Analytics & Logs** > **Network Analytics**.
-      3. Filter by rule ID.
+      1. In the [Cloudflare dashboard](https://dash.cloudflare.com), go to the Network analytics page.
+
+      <DashButton url="/?to=/:account/network-analytics" />
+      2. Filter by rule ID.
     </Steps>
   </TabItem>
   <TabItem label="New dashboard" icon="rocket">
diff --git a/src/content/docs/ddos-protection/managed-rulesets/http/http-overrides/override-examples.mdx b/src/content/docs/ddos-protection/managed-rulesets/http/http-overrides/override-examples.mdx
@@ -8,7 +8,7 @@ head:
     content: Override examples for HTTP DDoS Attack Protection
 ---
 
-import { Details, GlossaryTooltip, Tabs, TabItem } from "~/components"
+import { Details, GlossaryTooltip, Tabs, TabItem, DashButton } from "~/components"
 
 ## Use cases
 
@@ -36,8 +36,9 @@ To remedy a false positive:
 
 <Tabs syncKey="dashNewNav"> <TabItem label="Old dashboard">
 
-1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com) and select your account.
-2. Go to the analytics dashboard and apply filters to the displayed data.
+1. In the [Cloudflare dashboard](https://dash.cloudflare.com), go to the Network analytics page.
+      <DashButton url="/?to=/:account/network-analytics" />
+ 2. Apply filters to the displayed data.
   <Details header="For WAF/CDN customers">
   1. Select the zone that is experiencing DDoS attack false positives.
   2. Go to **Security** > **Events**.
@@ -56,8 +57,9 @@ To remedy a false positive:
 
 </TabItem> <TabItem label="New dashboard" icon="rocket">
 
-1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com) and select your account.
-2. Go to the analytics dashboard and apply filters to the displayed data.
+1. In the [Cloudflare dashboard](https://dash.cloudflare.com), go to the Network analytics page.
+      <DashButton url="/?to=/:account/network-analytics" />
+2. Apply filters to the displayed data.
   <Details header="For WAF/CDN customers">
   1. Select the zone that is experiencing DDoS attack false positives.
   2. Go to **Security** > **Analytics** > **Events** tab.
@@ -117,8 +119,9 @@ If you are experiencing a DDoS attack detected by Cloudflare and the applied mit
 
 <Tabs syncKey="dashNewNav"> <TabItem label="Old dashboard">
 
-1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com) and select your account.
-2. Go to the analytics dashboard and apply filters to the displayed data.
+1. In the [Cloudflare dashboard](https://dash.cloudflare.com), go to the Network analytics page.
+      <DashButton url="/?to=/:account/network-analytics" />
+2. Apply filters to the displayed data.
   <Details header="For WAF/CDN customers">
   1. Select the zone that is experiencing an incomplete mitigation of a DDoS attack.
   2. Go to **Security** > **Events**.
@@ -137,8 +140,9 @@ If you are experiencing a DDoS attack detected by Cloudflare and the applied mit
 
 </TabItem> <TabItem label="New dashboard" icon="rocket">
 
-1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com) and select your account.
-2. Go to the analytics dashboard and apply filters to the displayed data.
+1. In the [Cloudflare dashboard](https://dash.cloudflare.com), go to the Network analytics page.
+      <DashButton url="/?to=/:account/network-analytics" />
+2. Apply filters to the displayed data.
   <Details header="For WAF/CDN customers">
   1. Select the zone that is experiencing an incomplete mitigation of a DDoS attack.
   2. Go to **Security** > **Analytics** > **Events** tab.
diff --git a/src/content/partials/ddos-protection/create-notification.mdx b/src/content/partials/ddos-protection/create-notification.mdx
@@ -8,10 +8,11 @@ import { Steps } from "~/components";
 To set up a notification:
 
 <Steps>
-1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/) and select your account.
-2. Select **Notifications**.
-3. Under **Notifications**, select **Add**.
-4. Select one of the [available DDoS alerts](/ddos-protection/reference/alerts/#alert-types) (depending on your plan and services):
+1. In the Cloudflare dashboard, go to the **NotificationS** page.
+
+	<DashButton url="/?to=/:account/notifications" />
+2. Under **Notifications**, select **Add**.
+3. Select one of the [available DDoS alerts](/ddos-protection/reference/alerts/#alert-types) (depending on your plan and services:
    
    - HTTP DDoS Attack Alert
    - Layer 3/4 DDoS Attack Alert
diff --git a/src/content/partials/ddos-protection/managed-rulesets/create-override.mdx b/src/content/partials/ddos-protection/managed-rulesets/create-override.mdx
@@ -5,8 +5,10 @@
 import { Details, Render, Steps } from "~/components"
 
 <Steps>
-  1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/) and select your account.
-  2. Go to Account Home > **L3/4 DDoS** > **Network-layer DDoS Protection**.
+  1. In the Cloudflare dashboard, go to the **L3/4 DDoS** page.
+
+	<DashButton url="/?to=/:account/network-security/ddos" />
+  2. Go to **Network-layer DDoS Protection**.
   3. Select **Deploy a DDoS override**.
   4. In **Set scope**, specify if you wish to apply the override to all incoming packets or to a subset of the packets.
   5. If you are creating an override for a subset of the incoming packets, define the [custom expression](/ddos-protection/managed-rulesets/network/network-overrides/override-expressions/) that matches the incoming packets you wish to target in the override, using either the Rule Builder or the Expression Editor.
