Skip to content

Commit 432abc8

Browse files
authored
[Security, WAF] Small updates (#23952)
1 parent 54f38c1 commit 432abc8

File tree

13 files changed

+48
-42
lines changed

13 files changed

+48
-42
lines changed

src/content/docs/ddos-protection/managed-rulesets/http/http-overrides/configure-dashboard.mdx

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -26,7 +26,7 @@ If you cannot deploy any additional overrides, consider editing an existing over
2626

2727
## Access
2828

29-
<Tabs syncKey="dashNewNav">
29+
<Tabs syncKey="dashNewNav">
3030
<TabItem label="Old dashboard">
3131
<Steps>
3232
1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/), and select your account and website.
@@ -37,8 +37,8 @@ If you cannot deploy any additional overrides, consider editing an existing over
3737
<TabItem label="New dashboard" icon="rocket">
3838
<Steps>
3939
1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/), and select your account and domain.
40-
2. Go to **Security** > **Security rules**.
41-
3. On **HTTP DDoS Attack Protection**, select **Create override**.
40+
2. Go to **Security** > **Security rules** > **DDoS protection** tab.
41+
3. On **HTTP DDoS attack protection**, select **Create override**.
4242
</Steps>
4343
</TabItem>
4444
</Tabs>

src/content/docs/page-shield/get-started.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -26,7 +26,7 @@ If you do not have access to Page Shield in the Cloudflare dashboard, check if y
2626
</TabItem> <TabItem label="New dashboard" icon="rocket">
2727

2828
1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/), and select your account and domain.
29-
2. Go to **Security** > **Settings** and filter by **Client side abuse**.
29+
2. Go to **Security** > **Settings** and filter by **Client-side abuse**.
3030
3. Turn on **Continuous script monitoring**.
3131

3232
If you do not have access to resource monitoring in the Cloudflare dashboard, check if your user has one of the [necessary roles](/page-shield/reference/roles-and-permissions/).

src/content/docs/page-shield/reference/settings.mdx

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -44,7 +44,7 @@ To configure the CSP reporting endpoint:
4444
</TabItem> <TabItem label="New dashboard" icon="rocket">
4545

4646
1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/), and select your account and domain.
47-
2. Go to **Security** > **Settings** and filter by **Client side abuse**.
47+
2. Go to **Security** > **Settings** and filter by **Client-side abuse**.
4848
3. Under **Continuous script monitoring** > **Configurations**, select the edit icon next to **Reporting endpoint**.
4949
4. Select **Cloudflare-owned endpoint** or **Same hostname**.
5050
5. Select **Save**.
@@ -69,7 +69,7 @@ By default, Page Shield will only check the domain against malicious threat inte
6969
</TabItem> <TabItem label="New dashboard" icon="rocket">
7070

7171
1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/), and select your account and domain.
72-
2. Go to **Security** > **Settings** and filter by **Client side abuse**.
72+
2. Go to **Security** > **Settings** and filter by **Client-side abuse**.
7373
3. Under **Continuous script monitoring** > **Configurations**, select the edit icon next to **Data processing**.
7474
4. Select **Log host only** to analyze only the hostname or **Log full URI** to use the full URI.
7575
5. Select **Save**.
@@ -91,7 +91,7 @@ To turn off client-side resource monitoring:
9191
</TabItem> <TabItem label="New dashboard" icon="rocket">
9292

9393
1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/), and select your account and domain.
94-
2. Go to **Security** > **Settings** and filter by **Client side abuse**.
94+
2. Go to **Security** > **Settings** and filter by **Client-side abuse**.
9595
3. Next to **Continuous script monitoring**, set the toggle to **Off**.
9696

9797
</TabItem> </Tabs>

src/content/docs/security/rules.mdx

Lines changed: 6 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -12,7 +12,7 @@ Security rules are available in the new security dashboard in **Security** > **S
1212

1313
## Security rules
1414

15-
The **Security rules** tab includes a list of different types of rules configured in your domain / zone to protect your applications and resources.
15+
The **Security rules** tab includes a list of different types of rules configured in your domain/zone to protect your applications and resources.
1616

1717
To create a security rule:
1818

@@ -29,6 +29,8 @@ To create a security rule:
2929

3030
:::note[Notes]
3131

32+
To deploy a managed ruleset, go to **Security** > **Settings** and filter by **Web application exploits**. For more information, refer to [Deploy a managed ruleset](/waf/managed-rules/deploy-zone-dashboard/#deploy-a-managed-ruleset).
33+
3234
The **Security rules** tab includes functionality available in different products in the previous dashboard navigation structure, such as the [WAF](/waf/), [API Shield](/api-shield/), and [Page Shield](/page-shield/).
3335

3436
The tab may show additional rule types if you have configured at least one of the following:
@@ -41,12 +43,12 @@ The tab may show additional rule types if you have configured at least one of th
4143

4244
## DDoS protection
4345

44-
The **DDoS Protection** tab shows the multiple DDoS mitigation services provided by Cloudflare. You can create rules to override these mitigation tools. DDoS attack protection overrides are only available to Enterprise customers with the Advanced DDoS Protection subscription.
46+
The **DDoS protection** tab shows the multiple DDoS mitigation services provided by Cloudflare. You can create rules to override these mitigation tools. DDoS attack protection overrides are only available to Enterprise customers with the Advanced DDoS Protection subscription.
4547

4648
To learn more about DDoS protection overrides, refer to the following resources:
4749

48-
- [HTTP DDoS attack protection overrides](/ddos-protection/managed-rulesets/http/http-overrides/override-expressions/)
49-
- [Network-layer DDoS attack protection overrides](/ddos-protection/managed-rulesets/network/network-overrides/override-expressions/)
50+
- [HTTP DDoS attack protection overrides](/ddos-protection/managed-rulesets/http/http-overrides/)
51+
- [Network-layer DDoS attack protection overrides](/ddos-protection/managed-rulesets/network/network-overrides/)
5052

5153
:::note
5254
You define overrides for the Network-layer DDoS attack protection managed ruleset at the account level in Account Home > **L3/4 DDoS** > **Network-layer DDoS Protection**.

src/content/docs/security/settings.mdx

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -41,8 +41,8 @@ You can create rules to override DDoS attack protection tools. DDoS attack prote
4141

4242
To learn more about DDoS protection overrides, refer to the following resources:
4343

44-
- [HTTP DDoS attack protection overrides](/ddos-protection/managed-rulesets/http/http-overrides/override-expressions/)
45-
- [Network-layer DDoS attack protection overrides](/ddos-protection/managed-rulesets/network/network-overrides/override-expressions/)
44+
- [HTTP DDoS attack protection overrides](/ddos-protection/managed-rulesets/http/http-overrides/)
45+
- [Network-layer DDoS attack protection overrides](/ddos-protection/managed-rulesets/network/network-overrides/)
4646

4747
:::note
4848
You define overrides for the Network-layer DDoS attack protection managed ruleset at the account level in Account Home > **L3/4 DDoS** > **Network-layer DDoS Protection**.
@@ -61,7 +61,7 @@ Additionally, you can manage the following settings:
6161
- [Under Attack mode](/fundamentals/reference/under-attack-mode/) (under Security Level)
6262
- SSL/TLS DDoS attack protection
6363

64-
### Bot traffic
64+
### Bot traffic
6565

6666
In the **Bot traffic** security category you can manage the following settings:
6767

src/content/docs/waf/account/managed-rulesets/deploy-dashboard.mdx

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -15,7 +15,7 @@ import { Render } from "~/components";
1515
This feature requires an Enterprise plan with a paid add-on.
1616
:::
1717

18-
You deploy managed rulesets for an account in Account Home > **WAF** > **Managed rulesets**.
18+
You deploy managed rulesets for an account in Account Home > **WAF** > **Managed rulesets** tab.
1919

2020
![Example WAF Managed Rules configuration in the Managed rulesets tab under Account Home > WAF.](~/assets/images/waf/account/managed-rulesets-dashboard.png)
2121

@@ -25,7 +25,7 @@ To deploy a managed ruleset for a single zone, refer to [Deploy a managed rulese
2525

2626
1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/) and select your account.
2727

28-
2. Go to Account Home > **WAF** > **Managed rulesets**.
28+
2. Go to Account Home > **WAF** > **Managed rulesets** tab.
2929

3030
3. Select **Deploy** > **Deploy managed ruleset**.
3131

@@ -70,7 +70,7 @@ To configure an entire managed ruleset:
7070

7171
1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/) and select your account.
7272

73-
2. Go to Account Home > **WAF** > **Managed rulesets**.
73+
2. Go to Account Home > **WAF** > **Managed rulesets** tab.
7474

7575
3. Select the rule description of the _Execute_ rule that deploys the managed ruleset you want to configure. Alternatively, select the three dots > **Edit**.
7676

@@ -105,7 +105,7 @@ You can browse the available rules in a managed ruleset and search for individua
105105

106106
1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/) and select your account.
107107

108-
2. Go to Account Home > **WAF** > **Managed rulesets**.
108+
2. Go to Account Home > **WAF** > **Managed rulesets** tab.
109109

110110
3. Select the rule description of the _Execute_ rule that deploys the managed ruleset you want to configure. Alternatively, select the three dots > **Edit**.
111111

@@ -121,5 +121,5 @@ You can browse the available rules in a managed ruleset and search for individua
121121
### Delete a managed ruleset deployment rule or an exception
122122

123123
1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/) and select your account.
124-
2. Go to Account Home > **WAF** > **Managed rulesets**.
124+
2. Go to Account Home > **WAF** > **Managed rulesets** tab.
125125
3. Under **Deployed managed rulesets** and next to the rule you want to delete, select the three dots > **Delete** and confirm the operation.

src/content/docs/waf/managed-rules/check-for-exposed-credentials/upgrade-to-leaked-credentials-detection.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -26,7 +26,7 @@ If you had deployed the Cloudflare Exposed Credentials Check managed ruleset:
2626
<Tabs syncKey="dashNewNav"> <TabItem label="Old dashboard">
2727

2828
1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/), and select your account and domain.
29-
2. Go to **Security** > **WAF** > **Managed rules**.
29+
2. Go to **Security** > **WAF** > **Managed rules** tab.
3030
3. Under **Managed rules**, edit the rule that executes the Cloudflare Exposed Credentials Check Ruleset and take note of the current configuration (namely the performed action). Next, delete (or turn off) that rule.
3131

3232
</TabItem> <TabItem label="New dashboard" icon="rocket">

src/content/docs/waf/managed-rules/deploy-zone-dashboard.mdx

Lines changed: 10 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -23,7 +23,7 @@ To deploy a managed ruleset with the default configuration:
2323

2424
1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/), and select your account and domain.
2525

26-
2. Go to **Security** > **WAF** > **Managed rules**.
26+
2. Go to **Security** > **WAF** > **Managed rules** tab.
2727

2828
3. Under **Managed Rulesets**, select **Deploy** next to a managed ruleset.
2929

@@ -34,7 +34,7 @@ This operation deploys the managed ruleset for the current zone, creating a new
3434
</TabItem> <TabItem label="New dashboard" icon="rocket">
3535

3636
1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com), and select your account and domain.
37-
2. Go to **Security** > **Settings** and filter by **Detections**.
37+
2. Go to **Security** > **Settings** and filter by **Web application exploits**.
3838
3. Turn on the managed ruleset you want to deploy.
3939

4040
</TabItem> </Tabs>
@@ -43,11 +43,15 @@ This operation deploys the managed ruleset for the current zone, creating a new
4343

4444
<Tabs syncKey="dashNewNav"> <TabItem label="Old dashboard">
4545

46-
In the **Managed rules** tab, next to the managed ruleset you want to turn on or off, switch the **Enabled** toggle.
46+
1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/), and select your account and domain.
47+
2. Go to **Security** > **WAF** > **Managed rules** tab.
48+
3. Next to the managed ruleset you want to turn on or off, switch the **Enabled** toggle.
4749

4850
</TabItem> <TabItem label="New dashboard" icon="rocket">
4951

50-
In the **Settings** page, next to the managed ruleset you want to turn on or off, set the toggle to **On** or **Off**, respectively.
52+
1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com), and select your account and domain.
53+
2. Go to **Security** > **Settings** and filter by **Web application exploits**.
54+
3. Next to the managed ruleset you want to turn on or off, set the toggle to **On** or **Off**, respectively.
5155

5256
</TabItem> </Tabs>
5357

@@ -72,7 +76,7 @@ To configure rule field values for all the rules in a managed ruleset:
7276

7377
1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/), and select your account and domain.
7478

75-
2. Go to **Security** > **WAF** > **Managed rules**.
79+
2. Go to **Security** > **WAF** > **Managed rules** tab.
7680

7781
3. Next to the _Execute_ rule deploying the managed ruleset you want to configure, select the managed ruleset name.<br/> If you have not deployed the managed ruleset yet, select the managed ruleset name under **Managed Rulesets**.
7882

@@ -159,7 +163,7 @@ You can browse the available rules in a managed ruleset and search for individua
159163
<Tabs syncKey="dashNewNav"> <TabItem label="Old dashboard">
160164

161165
1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/) and select your account and domain.
162-
2. Go to **Security** > **WAF** > **Managed rules**.
166+
2. Go to **Security** > **WAF** > **Managed rules** tab.
163167
3. Next to the rule or exception (skip rule) you want to delete, select the three dots > **Delete** and confirm the operation.
164168

165169
</TabItem> <TabItem label="New dashboard" icon="rocket">

src/content/docs/waf/managed-rules/payload-logging/configure.mdx

Lines changed: 10 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -17,27 +17,28 @@ Only users with the [Super Administrator role](/fundamentals/manage-members/role
1717

1818
<Tabs syncKey="dashNewNav"> <TabItem label="Old dashboard">
1919

20-
1. Open **Security** > **WAF** > **Managed rules**.
20+
1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com), and select your account and domain.
2121

22-
![Example Managed Rules configuration in the Managed rules tab under Security > WAF](~/assets/images/waf/waf-managed-rules-tab.png)
22+
2. Go to **Security** > **WAF** > **Managed rules** tab.
2323

24-
2. To configure payload logging for a ruleset you had already deployed in the WAF, select the managed ruleset name.
24+
![Example Managed Rules configuration in the Managed rules tab under Security > WAF](~/assets/images/waf/waf-managed-rules-tab.png)
2525

26-
3. At the bottom of the page, select **Configure payload logging**.
26+
3. To configure payload logging for a ruleset you had already deployed in the WAF, select the managed ruleset name.
2727

28-
4. After reading and understanding the implications of enabling payload logging, select one of the available options:
28+
4. At the bottom of the page, select **Configure payload logging**.
2929

30+
5. After reading and understanding the implications of enabling payload logging, select one of the available options:
3031
- **Generate key pair using your web browser**: Generates a key pair (a private and a public key) in your browser and configures payload logging with the generated public key.
3132

3233
- **Use my own public key**: Enter a public key [generated by the `matched-data-cli` command-line tool](/waf/managed-rules/payload-logging/command-line/generate-key-pair/).
3334

34-
5. Select **Next**.
35+
6. Select **Next**.
3536

36-
6. If you generated a key pair in the browser, copy the displayed private key and **store it safely**. You will use this private key later to [view the decrypted payload content](/waf/managed-rules/payload-logging/view/).
37+
7. If you generated a key pair in the browser, copy the displayed private key and **store it safely**. You will use this private key later to [view the decrypted payload content](/waf/managed-rules/payload-logging/view/).
3738

38-
7. Select **Done**.
39+
8. Select **Done**.
3940

40-
8. If you are deploying the managed ruleset where you configured payload logging, select **Deploy**. If you configured payload logging for a ruleset you had already deployed, select **Save**.
41+
9. If you are deploying the managed ruleset where you configured payload logging, select **Deploy**. If you configured payload logging for a ruleset you had already deployed, select **Save**.
4142

4243
</TabItem> <TabItem label="New dashboard" icon="rocket">
4344

@@ -52,7 +53,6 @@ Only users with the [Super Administrator role](/fundamentals/manage-members/role
5253
5. At the bottom of the page, select **Configure payload logging**.
5354

5455
6. After reading and understanding the implications of enabling payload logging, select one of the available options:
55-
5656
- **Generate key pair using your web browser**: Generates a key pair (a private and a public key) in your browser and configures payload logging with the generated public key.
5757

5858
- **Use my own public key**: Enter a public key [generated by the `matched-data-cli` command-line tool](/waf/managed-rules/payload-logging/command-line/generate-key-pair/).

src/content/docs/waf/managed-rules/waf-exceptions/define-dashboard.mdx

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -19,7 +19,7 @@ To add an exception at the zone level:
1919
<Tabs syncKey="dashNewNav"> <TabItem label="Old dashboard">
2020

2121
1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com), and select your account and domain.
22-
2. Go to **Security** > **WAF** > **Managed rules**.
22+
2. Go to **Security** > **WAF** > **Managed rules** tab.
2323
3. Select **Add exception**.
2424

2525
</TabItem> <TabItem label="New dashboard" icon="rocket">
@@ -33,7 +33,7 @@ To add an exception at the zone level:
3333
To add an exception at the account level (Enterprise plans only):
3434

3535
1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com), and select your account.
36-
2. Go to Account Home > **WAF** > **Managed rulesets**.
36+
2. Go to Account Home > **WAF** > **Managed rulesets** tab.
3737
3. Select **Deploy** > **Deploy managed exception**.
3838

3939
## 2. Define basic exception parameters

0 commit comments

Comments
 (0)