Skip to content

Commit 4f0f0da

Browse files
patriciasantaanapatriciasantaana
authored
[Bots] New dash (#23375)
* new dash * missing commas * fix faq * toggle language * edits * edits
1 parent 10344ce commit 4f0f0da

23 files changed

+338
-130
lines changed

‎src/content/docs/bots/additional-configurations/ai-labyrinth.mdx‎

Lines changed: 20 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -5,22 +5,30 @@ sidebar:
55
order: 7
66
---
77

8-
import { Render, Tabs, TabItem } from "~/components"
8+
import { Render, Tabs, TabItem, Steps } from "~/components"
99

1010
The AI Labyrinth adds invisible links on your webpage with specific `Nofollow` tags to block AI crawlers that do not adhere to the recommended guidelines and crawl without permission. AI crawlers that scrape your website content without permission will be stuck in a maze of never-ending links, and their details are recorded and used by all Cloudflare customers who choose to block [AI bots](/bots/concepts/bot/#ai-bots).
1111

1212
These links do not impact your search engine optimization (SEO) or your website's appearance, and are only seen by bots. AI bots that respect no-crawl instructions will safely ignore this honeypot.
1313

14-
To enable [AI Labyrinth](/bots/additional-configurations/ai-labyrinth) based on your plan:
14+
To enable [AI Labyrinth](/bots/additional-configurations/ai-labyrinth):
1515

16-
<Tabs>
17-
<TabItem label="Bot Fight Mode">
18-
<Render file="ai-labyrinth-enable" params={{ one: "Bot Fight Mode" }} />
19-
</TabItem>
20-
<TabItem label="Super Bot Fight Mode">
21-
<Render file="ai-labyrinth-enable" params={{ one: "Super Bot Fight Mode" }} />
22-
</TabItem>
23-
<TabItem label="Bot Management for Enterprise">
24-
<Render file="ai-labyrinth-enable" params={{ one: "Bot Management" }} />
25-
</TabItem>
16+
<Tabs syncKey="dashNewNav">
17+
<TabItem label="Old dashboard">
18+
<Steps>
19+
<Render
20+
file="ai-labyrinth-enable"
21+
params={{ one: "Bot Fight Mode" }}
22+
/>
23+
</Steps>
24+
</TabItem>
25+
<TabItem label="New dashboard" icon="rocket">
26+
<Steps>
27+
1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/login), and select your account and domain.
28+
2. Go to **Security** > **Settings**.
29+
3. Filter by **Bot traffic**.
30+
4. Go to **AI Labyrinth**.
31+
4. Turn **AI Labyrinth** on.
32+
</Steps>
33+
</TabItem>
2634
</Tabs>

‎src/content/docs/bots/additional-configurations/block-ai-bots.mdx‎

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ sidebar:
66
label: Block AI Bots
77
---
88

9-
import { Render, Tabs, TabItem } from "~/components"
9+
import { Render, Steps } from "~/components"
1010

1111
:::note[Block AI bots availability]
1212
Note that **Block AI bots** feature is only available in the new application security dashboard (beta).
@@ -18,7 +18,8 @@ You can choose to block AI bots by activating **Block AI bots**. Activating this
1818

1919
To block [AI bots](/bots/concepts/bot/#ai-bots):
2020

21-
1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/) and select your account and domain.
21+
<Steps>
22+
1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/), and select your account and domain.
2223
2. Go to **Security** > **Settings**.
2324
3. Filter by **Bot traffic**.
2425
4. Go to **Block AI bots**.
@@ -27,5 +28,6 @@ To block [AI bots](/bots/concepts/bot/#ai-bots):
2728
- **Block on all pages**: Use this option if you wish to block AI bots on all your pages.
2829
- **Do not block (off)**: Use this option if you wish to allow AI bots on all your pages.
2930
6. Select **Save** to save your configuration.
31+
</Steps>
3032

3133
To block individual AI crawlers (rather than blocking all crawlers), use [AI Audit](/ai-audit/).

‎src/content/docs/bots/additional-configurations/detection-ids.mdx‎

Lines changed: 64 additions & 17 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ sidebar:
55
order: 2
66
---
77

8-
import { Render } from "~/components"
8+
import { Render, Tabs, TabItem, Steps } from "~/components"
99

1010
<Render file="detection-ids" />
1111

@@ -40,26 +40,43 @@ You can create or edit existing Logpush jobs to include the new Bot Detection ID
4040

4141
### Via the Cloudflare dashboard
4242

43-
1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/) and select your account and domain.
43+
<Steps>
44+
1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/), and select your account and domain.
4445
2. Go to **Analytics & Logs** > **Logs**.
4546
3. Select **Add Logpush Job**.
4647
4. Select **HTTP Requests** as the dataset.
4748
5. Select **BotDetectionIDs** under the General data field category.
4849
6. Select and enter the destination information.
4950
7. Prove the ownership.
5051
8. Select **Save**.
52+
</Steps>
5153

5254
### Via the API
5355

5456
[Update your logpush job](/logs/reference/log-output-options/) by adding `BotDetectionIDs` to the `output_options:` parameters.
5557

5658
## Create or edit an expression
5759

58-
1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/) and select your account and domain.
59-
2. Go to **Security** > **Bots**, apply filters and select **Create custom rule** to create a [custom rule](/waf/custom-rules/create-dashboard/) based on those filters.
60-
- Alternatively, if you already created a custom rule, go to **Security** > **WAF** > **Custom rules** and edit the expression of an existing custom rule.
61-
3. Use the `cf.bot_management.detection_ids` field in the rule expression.
62-
4. Select **Save**.
60+
<Tabs syncKey="dashNewNav">
61+
<TabItem label="Old dashboard">
62+
<Steps>
63+
1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/), and select your account and domain.
64+
2. Go to **Security** > **Bots**, apply filters and select **Create custom rule** to create a [custom rule](/waf/custom-rules/create-dashboard/) based on those filters. Alternatively, if you already created a custom rule, go to **Security** > **WAF** > **Custom rules** and edit the expression of an existing custom rule.
65+
3. Use the `cf.bot_management.detection_ids` field in the rule expression.
66+
4. Select **Save**.
67+
</Steps>
68+
</TabItem>
69+
<TabItem label="New dashboard" icon="rocket">
70+
<Steps>
71+
1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/login), and select your account and domain.
72+
2. Go to **Security** > **Analytics**.
73+
3. Apply filters and select **Create custom security rule** to create a custom rule based on your filters. Alternatively, if you have already created a custom rule, you can go to the existing rule in **Security** > **Security rules** and edit the expression based on your filters.
74+
4. Use the `cf.bot_management.detection_ids` field in the rule expression.
75+
5. Select **Deploy**.
76+
</Steps>
77+
</TabItem>
78+
</Tabs>
79+
6380

6481
## Use cases
6582

@@ -92,11 +109,26 @@ Cloudflare's [Managed Challenge](/cloudflare-challenges/challenge-types/challeng
92109

93110
To access account takeover detections:
94111

95-
1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/) and select your account and domain.
96-
2. Go to **Security** > **WAF**.
97-
3. Under **Custom Rules**, select **Create rule**.
98-
4. Fill out the form using **Bot Detection IDs** along with other necessary information.
99-
5. Select **Save as draft** to return to it later, or **Deploy** to deploy the rule.
112+
<Tabs syncKey="dashNewNav">
113+
<TabItem label="Old dashboard">
114+
<Steps>
115+
1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/), and select your account and domain.
116+
2. Go to **Security** > **WAF**.
117+
3. Under **Custom Rules**, select **Create rule**.
118+
4. Fill out the form using **Bot Detection IDs** along with other necessary information.
119+
5. Select **Save as draft** to return to it later, or **Deploy** to deploy the rule.
120+
</Steps>
121+
</TabItem>
122+
<TabItem label="New dashboard" icon="rocket">
123+
<Steps>
124+
1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/login), and select your account and domain.
125+
2. Go to **Security** > **Security rules**.
126+
3. Select **Create rule** and choose **Custom rule**.
127+
4. Fill out the form using **Bot Detection IDs** along with other necessary information.
128+
5. Select **Save as draft** to return to it later, or **Deploy** to deploy the rule.
129+
</Steps>
130+
</TabItem>
131+
</Tabs>
100132

101133
```js title="Rule example"
102134

@@ -109,11 +141,26 @@ Rate limiting rules can limit the number of logins from a particular IP, JA4 Fin
109141

110142
To use rate limiting rules with account takeover detections:
111143

112-
1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/) and select your account and domain.
113-
2. Go to ***Security** > **WAF**.
114-
3. Under **Rate limiting rules**, select **Create rule**.
115-
4. Fill out the form using the **Custom expression builder** and `cf.bot_management_detection_ids` along with other necessary information.
116-
5. Select **Save as draft** to return to it later, or **Deploy** to deploy the rule.
144+
<Tabs syncKey="dashNewNav">
145+
<TabItem label="Old dashboard">
146+
<Steps>
147+
1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/), and select your account and domain.
148+
2. Go to **Security** > **WAF**.
149+
3. Under **Rate limiting rules**, select **Create rule**.
150+
4. Fill out the form using the **Custom expression builder** and `cf.bot_management_detection_ids` along with other necessary information.
151+
5. Select **Save as draft** to return to it later, or **Deploy** to deploy the rule.
152+
</Steps>
153+
</TabItem>
154+
<TabItem label="New dashboard" icon="rocket">
155+
<Steps>
156+
1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/login), and select your account and domain.
157+
2. Go to **Security** > **Security rules**.
158+
3. Select **Create rule** and choose **Rate limiting rule**.
159+
4. Fill out the form using the **Custom expression builder** and `cf.bot_management_detection_ids` along with other necessary information.
160+
5. Select **Save as draft** to return to it later, or **Deploy** to deploy the rule.
161+
</Steps>
162+
</TabItem>
163+
</Tabs>
117164

118165
:::note
119166
The rule can be enhanced with Leaked Credential Checks. Refer to the [WAF documentation](/waf/detections/leaked-credentials/) for more information on how to include leaked credentials and account takeover detections in a rate limiting rule.

‎src/content/docs/bots/additional-configurations/managed-robots-txt.mdx‎

Lines changed: 21 additions & 22 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ sidebar:
66
label: Managed robots.txt
77
---
88

9-
import { Render, Tabs, TabItem } from "~/components";
9+
import { Render, Tabs, TabItem, Steps } from "~/components";
1010

1111
Protect your website or application from AI crawlers by implementing a `robots.txt` file on your domain to direct AI bot operators on what content they can and cannot scrape for AI model training.
1212

@@ -45,27 +45,26 @@ If your website does not have a `robots.txt` file, Cloudflare creates a new file
4545

4646
## Implementation
4747

48-
To implement a `robots.txt` file on your domain based on your plan:
49-
50-
<Tabs>
51-
<TabItem label="Bot Fight Mode">
52-
<Render
53-
file="enable-managed-robots-txt"
54-
params={{ one: "Bot Fight Mode" }}
55-
/>
56-
</TabItem>
57-
<TabItem label="Super Bot Fight Mode">
58-
<Render
59-
file="enable-managed-robots-txt"
60-
params={{ one: "Super Bot Fight Mode" }}
61-
/>
62-
</TabItem>
63-
<TabItem label="Bot Management for Enterprise">
64-
<Render
65-
file="enable-managed-robots-txt"
66-
params={{ one: "Bot Management" }}
67-
/>
68-
</TabItem>
48+
To implement a `robots.txt` file on your domain:
49+
50+
<Tabs syncKey="dashNewNav">
51+
<TabItem label="Old dashboard">
52+
<Steps>
53+
<Render
54+
file="enable-managed-robots-txt"
55+
params={{ one: "Bot Fight Mode" }}
56+
/>
57+
</Steps>
58+
</TabItem>
59+
<TabItem label="New dashboard" icon="rocket">
60+
<Steps>
61+
1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/login), and select your account and domain.
62+
2. Go to **Security** > **Settings**.
63+
3. Filter by **Bot traffic**.
64+
4. Go to **Managed robots.txt**.
65+
5. Turn **Managed robots.txt** on.
66+
</Steps>
67+
</TabItem>
6968
</Tabs>
7069

7170
## Availability

‎src/content/docs/bots/additional-configurations/sequence-rules.mdx‎

Lines changed: 14 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ sidebar:
55
order: 4
66
---
77

8-
import { Render } from "~/components"
8+
import { Render, Steps } from "~/components"
99

1010
<Render file="sequence-rules" product="bots" params={{ one: "Sequence rules", two: "/bots/additional-configurations/sequence-rules/" }} />
1111

@@ -20,14 +20,17 @@ Sequence rules is currently in private beta. If you would like to be included in
2020

2121
## Enable sequence rules via the API
2222

23+
<Steps>
2324
1. [Create an API token](/fundamentals/api/get-started/create-token/) if you do not already have one. The API token must include the _Zone_ > _Fraud Detection_ > _Edit_ permission.
2425
2. [Get the zone ID](/fundamentals/account/find-account-and-zone-ids/) for the zone(s) where you want to enable sequence rules.
2526
3. [Add the endpoints](/api-shield/management-and-monitoring/) that you want to track in your sequence rules using API Shield's Endpoint Management and make note of the short ID.
26-
:::note
27-
28-
The short ID will not be visible until our account team has enabled this feature for you.
29-
:::
3027
4. Enable the sequence cookie by adding your API token and zone ID to the following API call.
28+
</Steps>
29+
30+
:::note
31+
32+
The short ID will not be visible until your account team has enabled this feature for you.
33+
:::
3134

3235
```bash title="API call"
3336
curl --request PUT \
@@ -40,7 +43,6 @@ https://api.cloudflare.com/client/v4/zones/{zone_id}/fraud_detection/sequence_co
4043
5. Use the expression editor to write sequence or timing based rules via [custom rules](/waf/custom-rules/), [rate limiting rules](/waf/rate-limiting-rules/), or [transform rules](/rules/transform/). You can put these rules in log only mode to monitor.
4144

4245
:::note
43-
4446
When you enable sequence rules, Cloudflare will start setting cookies for all requests that match your endpoints.
4547
:::
4648

@@ -92,16 +94,16 @@ Disabling sequence rules will stop the rules fields from being populated. If you
9294

9395
To disable sequence rules:
9496

97+
<Steps>
9598
1. [Create an API token](/fundamentals/api/get-started/create-token/) if you do not already have one. The API token must include the _Zone_ > _Fraud Detection_ > _Edit_ permission.
9699
2. [Get the zone ID](/fundamentals/account/find-account-and-zone-ids/) for the zone(s) where you want to enable sequence rules.
97100
3. [Add the endpoints](/api-shield/management-and-monitoring/) that you want to track in your sequence rules using API Shield's Endpoint Management and make note of the short ID.
98-
99-
:::note
100-
101-
The short ID will not be visible until our account team has enabled this feature for you.
102-
:::
103-
104101
4. Disable the sequence cookie using your API token, zone ID, and by setting `enabled` to `false` on the following API call.
102+
</Steps>
103+
104+
:::note
105+
The short ID will not be visible until your account team has enabled this feature for you.
106+
:::
105107

106108
```bash title="API call"
107109
curl --request PUT https://api.cloudflare.com/client/v4/zones/{zone_id}/fraud_detection/sequence_cookies \

‎src/content/docs/bots/additional-configurations/static-resources.mdx‎

Lines changed: 20 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ sidebar:
66

77
---
88

9-
import { GlossaryTooltip, Render } from "~/components"
9+
import { Render, Tabs, TabItem, Steps, GlossaryTooltip } from "~/components";
1010

1111
Pro, Business, and Enterprise customers can use Cloudflare's bot solutions to protect their <GlossaryTooltip term="static content">static resources</GlossaryTooltip> from bots.
1212

@@ -19,9 +19,25 @@ If you enable static resource protection, you may block good bots — like mail
1919

2020
To enable this feature as a Pro or Business customer or an Enterprise customer without Bot Management:
2121

22-
1. Go to **Security** > **Bots**.
23-
2. Select **Configure Super Bot Fight Mode**.
24-
3. For **Static resource protection**, select **On**.
22+
<Tabs syncKey="dashNewNav">
23+
<TabItem label="Old dashboard">
24+
<Steps>
25+
1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/login), and select your account and domain.
26+
2. Go to **Security** > **Bots**.
27+
3. Select **Configure Super Bot Fight Mode**.
28+
4. For **Static resource protection**, select **On**.
29+
</Steps>
30+
</TabItem>
31+
<TabItem label="New dashboard" icon="rocket">
32+
<Steps>
33+
1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/login), and select your account and domain.
34+
2. Go to **Security** > **Settings**.
35+
3. Filter by **Bot traffic**.
36+
4. Go to **Super Bot Fight Mode**.
37+
5. Under **Configurations**, select the edit icon for **Static resource protection** and turn it on.
38+
</Steps>
39+
</TabItem>
40+
</Tabs>
2541

2642
:::caution
2743

‎src/content/docs/bots/bot-analytics.mdx‎

Lines changed: 10 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -17,7 +17,11 @@ Business and Enterprise customers without Bot Management can use **Bot Analytics
1717

1818
### Access
1919

20-
To use Bot Analytics, open the Cloudflare dashboard and select **Security** > **Bots**.
20+
You can access Bot Analytics by going to the [Cloudflare dashboard](https://dash.cloudflare.com/login), and selecting your account and domain.
21+
22+
Old dashboard: **Security** > **Bots**.
23+
24+
New dashboard: **Security** > **Analytics** > **Bot analysis**.
2125

2226
![View Bot Analytics in the Cloudflare dashboard. For more details, keep reading.](~/assets/images/bots/bot-analytics-dashboard-biz.png)
2327

@@ -49,7 +53,11 @@ Enterprise customers with Bot Management can use **Bot Analytics** to dynamicall
4953

5054
### Access
5155

52-
To use Bot Analytics, open the Cloudflare dashboard and select **Security** > **Bots**.
56+
You can access Bot Analytics by going to the [Cloudflare dashboard](https://dash.cloudflare.com/login), and selecting your account and domain.
57+
58+
Old dashboard: **Security** > **Bots**.
59+
60+
New dashboard: **Security** > **Analytics** > **Bot analysis**.
5361

5462
![View Bot Analytics in the Cloudflare dashboard. For more details, keep reading.](~/assets/images/bots/bot-analytics-dashboard-ent.png)
5563

‎src/content/docs/bots/concepts/bot/verified-bots/policy.mdx‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -15,7 +15,7 @@ In order to be listed by Cloudflare as a <GlossaryTooltip term="verified bot" li
1515

1616
### Minimum Traffic
1717

18-
A bot or proxy must have a minimum amount of traffic for Cloudflare to be able find it in the sampled data. The minimum traffic should have more than 1000 requests per day across multiple domains.
18+
A bot or proxy must have a minimum amount of traffic for Cloudflare to be able to find it in the sampled data. The minimum traffic should have more than 1,000 requests per day across multiple domains.
1919

2020
### Minimum Zones
2121

0 commit comments

Comments
 (0)