Skip to content

Commit 9f8d544

Browse files
patriciasantaanapatriciasantaana
committed
spacing
1 parent 2d9d569 commit 9f8d544

File tree

3 files changed

+26
-24
lines changed

3 files changed

+26
-24
lines changed

‎src/content/docs/ddos-protection/advanced-ddos-systems/how-to/create-rule.mdx‎

Lines changed: 2 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -17,9 +17,8 @@ To create a [SYN flood rule](/ddos-protection/advanced-ddos-systems/overview/adv
1717
{/* prettier-ignore */}
1818
<Steps>
1919
1. In the Cloudflare dashboard, go to the **L3/4 DDoS protection** page.
20-
20+
2121
<DashButton url="/?to=/:account/network-security/ddos" />
22-
2322
2. Go to **Advanced Protection** > **Advanced TCP Protection**.
2423
3. Depending on the rule you are creating, do one of the following:
2524
- Under **SYN Flood Protection**, select **Create SYN flood rule**.
@@ -42,7 +41,7 @@ To create a [SYN flood rule](/ddos-protection/advanced-ddos-systems/overview/adv
4241
2. Go to **Advanced Protection** > **General settings**.
4342
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.
4443
:::note
45-
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.
44+
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.
4645
:::
4746
4. Go to **Advanced DNS Protection**.
4847
5. Select **Create Advanced DNS Protection rule**.

‎src/content/docs/ddos-protection/advanced-ddos-systems/how-to/exclude-prefix.mdx‎

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -12,6 +12,7 @@ To exclude a prefix or a prefix subset from Advanced DDoS Protection:
1212

1313
<Steps>
1414
1. In the Cloudflare dashboard, go to the **L3/4 DDoS protection** page.
15+
1516
<DashButton url="/?to=/:account/network-security/ddos" />
1617
2. Go to **Advanced Protection**.
1718
3. [Add the prefix](/ddos-protection/advanced-ddos-systems/how-to/add-prefix/) you previously onboarded to Magic Transit to Advanced TCP Protection.

‎src/content/docs/ddos-protection/managed-rulesets/http/http-overrides/override-examples.mdx‎

Lines changed: 23 additions & 21 deletions
Original file line numberDiff line numberDiff line change
@@ -37,16 +37,17 @@ To remedy a false positive:
3737
<Tabs syncKey="dashNewNav"> <TabItem label="Old dashboard">
3838

3939
1. In the Cloudflare dashboard, go to the Network analytics page.
40+
4041
<DashButton url="/?to=/:account/network-analytics" />
4142
2. Apply filters to the displayed data.
4243
<Details header="For WAF/CDN customers">
43-
1. Select the zone that is experiencing DDoS attack false positives.
44-
2. Go to **Security** > **Events**.
45-
3. Select **Add filter** and filter by `Service equals HTTP DDoS`.
44+
1. Select the zone that is experiencing DDoS attack false positives.
45+
2. Go to **Security** > **Events**.
46+
3. Select **Add filter** and filter by `Service equals HTTP DDoS`.
4647
</Details>
4748
<Details header="For Magic Transit and Spectrum customers">
48-
1. Go to Account Home > **Analytics & Logs** > **Network Analytics**.
49-
2. Identify the legitimate traffic that is causing the false positives. Use the Attack ID number included in the DDoS alert (if you received one), or apply dashboard filters such as destination IP address and port.
49+
1. Go to Account Home > **Analytics & Logs** > **Network Analytics**.
50+
2. Identify the legitimate traffic that is causing the false positives. Use the Attack ID number included in the DDoS alert (if you received one), or apply dashboard filters such as destination IP address and port.
5051
</Details>
5152
3. Scroll down to **Top events by source** > **HTTP DDoS rules**.
5253
4. Copy the rule name.
@@ -57,17 +58,18 @@ To remedy a false positive:
5758

5859
</TabItem> <TabItem label="New dashboard" icon="rocket">
5960

60-
1. In the Cloudflare dashboard), go to the Network analytics page.
61+
1. In the Cloudflare dashboard, go to the Network analytics page.
62+
6163
<DashButton url="/?to=/:account/network-analytics" />
6264
2. Apply filters to the displayed data.
6365
<Details header="For WAF/CDN customers">
64-
1. Select the zone that is experiencing DDoS attack false positives.
65-
2. Go to **Security** > **Analytics** > **Events** tab.
66-
3. Select **Add filter** and filter by `Service equals HTTP DDoS`.
66+
1. Select the zone that is experiencing DDoS attack false positives.
67+
2. Go to **Security** > **Analytics** > **Events** tab.
68+
3. Select **Add filter** and filter by `Service equals HTTP DDoS`.
6769
</Details>
6870
<Details header="For Magic Transit and Spectrum customers">
69-
1. Go to Account Home > **Analytics & Logs** > **Network Analytics**.
70-
1. Identify the legitimate traffic that is causing the false positives. Use the Attack ID number included in the DDoS alert (if you received one), or apply dashboard filters such as destination IP address and port.
71+
1. Go to Account Home > **Analytics & Logs** > **Network Analytics**.
72+
2. Identify the legitimate traffic that is causing the false positives. Use the Attack ID number included in the DDoS alert (if you received one), or apply dashboard filters such as destination IP address and port.
7173
</Details>
7274
3. Scroll down to **Top events by source** > **HTTP DDoS rules**.
7375
4. Copy the rule name.
@@ -123,13 +125,13 @@ If you are experiencing a DDoS attack detected by Cloudflare and the applied mit
123125
<DashButton url="/?to=/:account/network-analytics" />
124126
2. Apply filters to the displayed data.
125127
<Details header="For WAF/CDN customers">
126-
1. Select the zone that is experiencing an incomplete mitigation of a DDoS attack.
127-
2. Go to **Security** > **Events**.
128-
3. Select **Add filter** and filter by `Service equals HTTP DDoS`.
128+
1. Select the zone that is experiencing an incomplete mitigation of a DDoS attack.
129+
2. Go to **Security** > **Events**.
130+
3. Select **Add filter** and filter by `Service equals HTTP DDoS`.
129131
</Details>
130132
<Details header="For Magic Transit and Spectrum customers">
131-
1. Go to Account Home > **Analytics & Logs** > **Network Analytics**.
132-
2. Identify the DDoS attack that is having incomplete mitigations. Use the Attack ID number included in the DDoS alert (if you received one), or apply dashboard filters such as destination IP address and port.
133+
1. Go to Account Home > **Analytics & Logs** > **Network Analytics**.
134+
2. Identify the DDoS attack that is having incomplete mitigations. Use the Attack ID number included in the DDoS alert (if you received one), or apply dashboard filters such as destination IP address and port.
133135
</Details>
134136
3. Scroll down to **Top events by source** > **HTTP DDoS rules**.
135137
4. Copy the rule name.
@@ -144,13 +146,13 @@ If you are experiencing a DDoS attack detected by Cloudflare and the applied mit
144146
<DashButton url="/?to=/:account/network-analytics" />
145147
2. Apply filters to the displayed data.
146148
<Details header="For WAF/CDN customers">
147-
1. Select the zone that is experiencing an incomplete mitigation of a DDoS attack.
148-
2. Go to **Security** > **Analytics** > **Events** tab.
149-
3. Select **Add filter** and filter by `Service equals HTTP DDoS`.
149+
1. Select the zone that is experiencing an incomplete mitigation of a DDoS attack.
150+
2. Go to **Security** > **Analytics** > **Events** tab.
151+
3. Select **Add filter** and filter by `Service equals HTTP DDoS`.
150152
</Details>
151153
<Details header="For Magic Transit and Spectrum customers">
152-
1. Go to Account Home > **Analytics & Logs** > **Network Analytics**.
153-
2. Identify the DDoS attack that is having incomplete mitigations. Use the Attack ID number included in the DDoS alert (if you received one), or apply dashboard filters such as destination IP address and port.
154+
1. Go to Account Home > **Analytics & Logs** > **Network Analytics**.
155+
2. Identify the DDoS attack that is having incomplete mitigations. Use the Attack ID number included in the DDoS alert (if you received one), or apply dashboard filters such as destination IP address and port.
154156
</Details>
155157
3. Scroll down to **Top events by source** > **HTTP DDoS rules**.
156158
4. Copy the rule name.

0 commit comments

Comments
 (0)