Skip to content

Commit acb1fbf

Browse files
[Bots] Navigation refresh (#21348)
* navigation refresh * broken links * broken link * redirects * fix redirect
1 parent c54f12d commit acb1fbf

File tree

77 files changed

+269
-313
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

77 files changed

+269
-313
lines changed

public/__redirects

Lines changed: 13 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -178,16 +178,27 @@
178178
/api-shield/security/sequential-abuse-detection/ /api-shield/security/sequence-analytics/ 301
179179

180180
# bots
181-
/bots/about/javascript-detections/ /bots/reference/javascript-detections/ 301
182181
/bots/about/plans/ /bots/plans/ 301
183182
/bots/about/plans/biz-and-ent/ /bots/plans/biz-and-ent/ 301
184183
/bots/about/plans/bm-subscription/ /bots/plans/bm-subscription/ 301
185184
/support/firewall/tools/cloudflare-bot-products-faqs/ /bots/troubleshooting/ 301
186185
/support/other-languages/deutsch/cloudflare-bot/ /bots/troubleshooting/ 301
187-
/bots/concepts/ja3-fingerprint/ /bots/concepts/ja3-ja4-fingerprint/ 301
188186
/bots/reference/verified-bot-categories/ /bots/concepts/bot/verified-bots/categories/ 301
189187
/bots/reference/verified-bot-policy/ /bots/concepts/bot/verified-bots/policy/ 301
190188
/bots/concepts/challenge-solve-rate/ /fundamentals/security/cloudflare-challenges/challenge-solve-rate/ 301
189+
/bots/concepts/detection-ids/ /bots/additional-configurations/detection-ids/ 301
190+
/bots/concepts/ja3-ja4-fingerprint/ /bots/additional-configurations/ja3-ja4-fingerprint/ 301
191+
/bots/concepts/signals-intelligence/ /bots/additional-configurations/ja3-ja4-fingerprint/signals-intelligence/ 301
192+
/bots/reference/javascript-detections/ /bots/additional-configurations/javascript-detections/ 301
193+
/bots/concepts/sequence-rules/ /bots/additional-configurations/sequence-rules/ 301
194+
/bots/reference/static-resources/ /bots/additional-configurations/static-resources/ 301
195+
/bots/bot-analytics/biz-and-ent/ /bots/bot-analytics/ 301
196+
/bots/bot-analytics/bm-subscription/ /bots/bot-analytics/ 301
197+
/bots/concepts/cloudflare-bot-tags/ /bots/concepts/bot-tags/ 301
198+
/bots/get-started/biz-and-ent/ /bots/get-started/super-bot-fight-mode/ 301
199+
/bots/get-started/free/ /bots/get-started/bot-fight-mode/ 301
200+
/bots/get-started/bm-subscription/ /bots/get-started/bot-management/ 301
201+
/bots/get-started/pro/ /bots/get-started/super-bot-fight-mode/ 301
191202

192203
#browser-rendering
193204
/browser-rendering/get-started/browser-rendering-with-do/ /browser-rendering/workers-binding-api/browser-rendering-with-do/ 301

src/content/docs/api-shield/security/sequence-mitigation/custom-rules.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -10,7 +10,7 @@ import { GlossaryTooltip, Render } from "~/components"
1010

1111
API Shield sequence custom rules use the configured API Shield <GlossaryTooltip term="session identifier">session identifier</GlossaryTooltip> to track the order of requests a user has made and the time between requests, and makes them available via [Cloudflare Rules](/rules). This allows you to write rules that match valid or invalid sequences.
1212

13-
These rules are different from [cookie sequence rules](/bots/concepts/sequence-rules/) in a few ways:
13+
These rules are different from [cookie sequence rules](/bots/additional-configurations/sequence-rules/) in a few ways:
1414

1515
- They only require an API Shield subscription.
1616
- They require [session identifiers](/api-shield/get-started/#session-identifiers) to be set in API Shield.

src/content/docs/bots/concepts/detection-ids.mdx renamed to src/content/docs/bots/additional-configurations/detection-ids.mdx

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,8 @@
11
---
22
pcx_content_type: concept
33
title: Detection IDs
4-
4+
sidebar:
5+
order: 2
56
---
67

78
import { Render } from "~/components"
Lines changed: 16 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,16 @@
1+
---
2+
title: Additional configurations
3+
pcx_content_type: navigation
4+
sidebar:
5+
order: 5
6+
group:
7+
hideIndex: true
8+
head:
9+
- tag: title
10+
content: Additional Bots configurations
11+
12+
---
13+
14+
import { DirectoryListing } from "~/components"
15+
16+
<DirectoryListing />

src/content/docs/bots/concepts/ja3-ja4-fingerprint.mdx renamed to src/content/docs/bots/additional-configurations/ja3-ja4-fingerprint/index.mdx

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,8 @@
11
---
22
pcx_content_type: concept
33
title: JA3/JA4 fingerprint
4+
sidebar:
5+
order: 1
46

57
---
68

@@ -78,7 +80,7 @@ This sample was generated using [Workers' Cloudflare Object script](/workers/exa
7880

7981
To get more information about potential bot requests, use these JA3 and JA4 fingerprints in:
8082

81-
- [Bot Analytics](/bots/bot-analytics/bm-subscription/)
83+
- [Bot Analytics](/bots/bot-analytics/#enterprise-bot-management)
8284
- [Security Events](/waf/analytics/security-events/) and [Security Analytics](/waf/analytics/security-analytics/)
8385
- [Analytics GraphQL API](/analytics/graphql-api/), specifically the **HTTP Requests** dataset
8486
- [Logs](/logs/reference/log-fields/zone/http_requests/)

src/content/docs/bots/concepts/signals-intelligence.mdx renamed to src/content/docs/bots/additional-configurations/ja3-ja4-fingerprint/signals-intelligence.mdx

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,12 +1,13 @@
11
---
22
pcx_content_type: concept
33
title: Signals Intelligence
4-
4+
sidebar:
5+
order: 1
56
---
67

78
import { Render } from "~/components"
89

9-
For every available [JA4 fingerprint](/bots/concepts/ja3-ja4-fingerprint/), Bot Management customers can view how Cloudflare sees it on the Internet and what behavior we view with the fingerprint. This data can help you understand why a request is scored in a particular fashion or allow you to use the aggregate data in your own ML models, run in either [Cloudflare Workers](/workers/) or at the origin location.
10+
For every available [JA4 fingerprint](/bots/additional-configurations/ja3-ja4-fingerprint/), Bot Management customers can view how Cloudflare sees it on the Internet and what behavior we view with the fingerprint. This data can help you understand why a request is scored in a particular fashion or allow you to use the aggregate data in your own ML models, run in either [Cloudflare Workers](/workers/) or at the origin location.
1011

1112
Specifically, for each JA4 fingerprint, you will be able to access the following information:
1213

src/content/docs/bots/reference/javascript-detections.mdx renamed to src/content/docs/bots/additional-configurations/javascript-detections.mdx

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -2,8 +2,8 @@
22
type: overview
33
pcx_content_type: reference
44
title: JavaScript detections
5-
weight: 0
6-
5+
sidebar:
6+
order: 6
77
---
88

99
import { Render } from "~/components"

src/content/docs/bots/concepts/sequence-rules.mdx renamed to src/content/docs/bots/additional-configurations/sequence-rules.mdx

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,12 +1,13 @@
11
---
22
pcx_content_type: reference
33
title: Sequence rules
4-
4+
sidebar:
5+
order: 4
56
---
67

78
import { Render } from "~/components"
89

9-
<Render file="sequence-rules" product="bots" params={{ one: "Sequence rules", two: "/bots/concepts/sequence-rules/" }} />
10+
<Render file="sequence-rules" product="bots" params={{ one: "Sequence rules", two: "/bots/additional-configurations/sequence-rules/" }} />
1011

1112
Sequence rules is currently in private beta. If you would like to be included in the beta, contact your account team.
1213

src/content/docs/bots/reference/static-resources.mdx renamed to src/content/docs/bots/additional-configurations/static-resources.mdx

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,8 @@
11
---
22
pcx_content_type: reference
33
title: Static resource protection
4-
weight: 0
4+
sidebar:
5+
order: 7
56

67
---
78

Lines changed: 41 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -1,25 +1,27 @@
11
---
2-
title: Business
3-
pcx_content_type: reference
2+
title: Bot Analytics
3+
pcx_content_type: navigation
44
sidebar:
5-
order: 3
5+
order: 5
66
head:
77
- tag: title
8-
content: Super Bot Fight Mode (Business) Analytics
8+
content: Cloudflare Bot Analytics
99

1010
---
1111

1212
import { GlossaryTooltip, Render } from "~/components"
1313

14+
## Business and Enterprise
15+
1416
Business and Enterprise customers without Bot Management can use **Bot Analytics** to dynamically examine bot traffic. These dashboards offer less functionality than Bot Management for Enterprise but still help you understand bot traffic on your domain.
1517

16-
## Access
18+
### Access
1719

1820
To use Bot Analytics, open the Cloudflare dashboard and select **Security** > **Bots**.
1921

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

22-
## Features
24+
### Features
2325

2426
For a full tour of Bot Analytics, see [our blog post](https://blog.cloudflare.com/introducing-bot-analytics/). At a high level, the tool includes:
2527

@@ -31,12 +33,43 @@ Bot Analytics shows up to 72 hours of data at a time and can display data up to
3133

3234
<Render file="analytics-features" />
3335

34-
## Common uses
36+
### Common uses
3537

3638
Business and Enterprise customers without Bot Management can use Bot Analytics to:
3739

3840
- Understand <GlossaryTooltip term="bot">bot</GlossaryTooltip> traffic
3941
- Study recent attacks to find trends and detailed information
4042
- Learn more about Cloudflare’s detection engines with real data
4143

42-
For more details and granular control over bot traffic, consider upgrading to [Bot Management for Enterprise](/bots/bot-analytics/bm-subscription/).
44+
For more details and granular control over bot traffic, consider upgrading to [Bot Management for Enterprise](/bots/bot-analytics/#enterprise-bot-management).
45+
46+
## Enterprise Bot Management
47+
48+
Enterprise customers with Bot Management can use **Bot Analytics** to dynamically examine bot traffic.
49+
50+
### Access
51+
52+
To use Bot Analytics, open the Cloudflare dashboard and select **Security** > **Bots**.
53+
54+
![View Bot Analytics in the Cloudflare dashboard. For more details, keep reading.](~/assets/images/bots/bot-analytics-dashboard-ent.png)
55+
56+
### Features
57+
58+
<Render file="bm-analytics-features" />
59+
60+
<Render file="analytics-features" />
61+
62+
### Common uses
63+
64+
Bot Management customers can use Bot Analytics to:
65+
66+
- Understand traffic during [your onboarding phase](/bots/get-started/bot-management/).
67+
- Tune WAF custom rules to be effective but not overly aggressive.
68+
- Study recent attacks to find trends and detailed information.
69+
- Learn more about Cloudflare’s detection engines with real data.
70+
71+
### API
72+
73+
Data from Bot Analytics is also available via the GraphQL API. You can access <GlossaryTooltip term="bot score">bot scores</GlossaryTooltip>, bot sources, <GlossaryTooltip term="bot tags" link="/bots/concepts/bot-tags/">bot tags</GlossaryTooltip>, and bot _decisions_ (_automated_, _likely automated_, etc.), and more.
74+
75+
Read the [GraphQL Analytics API documentation](/analytics/graphql-api/) for more information about GraphQL and basic querying.

0 commit comments

Comments
 (0)