Skip to content

Commit 82708b9

Browse files
authored
[AI Audit] Update WAF instructions (#23835)
1 parent 3837af4 commit 82708b9

File tree

1 file changed

+20
-6
lines changed

1 file changed

+20
-6
lines changed

src/content/docs/ai-audit/configuration/ai-audit-with-waf.mdx

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

77
---
88

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

1111
AI Audit works alongside other Cloudflare products, such as Cloudflare [Web Application Firewall (WAF)](/waf/). WAF checks incoming web and API requests, and filters undesired traffic based on rules. [WAF custom rules](/waf/custom-rules/) allow you to perform certain actions such as enforcing <GlossaryTooltip term="robots.txt">`robots.txt`</GlossaryTooltip>.
1212

@@ -53,9 +53,9 @@ You may have both of the following features enabled:
5353
- [WAF custom rule to allow search engine bots](/waf/custom-rules/use-cases/allow-traffic-from-verified-bots/)
5454
- AI Audit's [pay per crawl](/ai-audit/features/pay-per-crawl/what-is-pay-per-crawl/) to charge all AI crawlers when they request access to your content (including search engine bots).
5555

56-
Since WAF custom rules are enforced before pay per crawl:
56+
Since custom rules are enforced before pay per crawl:
5757

58-
- Only search engine bots will be able to access your site (enforced by WAF custom rule).
58+
- Only search engine bots will be able to access your site (enforced by custom rule).
5959
- The search engine bots will then be charged for access to your content (enforced by AI Audit's pay per crawl).
6060

6161
:::note
@@ -71,11 +71,25 @@ You may have both of the following features enabled:
7171
- A WAF custom rule which blocks all bots.
7272
- AI Audit selection which allows certain AI crawlers.
7373

74-
In this scenario, you have two WAF custom rules, each directing a different logic for handling AI crawlers. To resolve this issue:
74+
In this scenario, you have two custom rules, each directing a different logic for handling AI crawlers. To resolve this issue:
75+
76+
<Tabs syncKey="dashNewNav"> <TabItem label="Old dashboard">
7577

7678
<Steps>
7779
1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/), and select your account and domain.
78-
2. Go to **Rules** > **Overview**.
80+
2. Go to **Security** > **WAF** > **Custom rules** tab.
7981
3. Identify your WAF custom rule and the AI Audit rule.
8082
4. Drag the rule you wish to prioritize to the top, or modify your WAF custom rule to ensure it does not conflict with your AI Audit configurations.
81-
</Steps>
83+
</Steps>
84+
85+
</TabItem> <TabItem label="New dashboard" icon="rocket">
86+
87+
<Steps>
88+
1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/), and select your account and domain.
89+
2. Go to **Security** > **Security rules** and filter by **Custom rules**.
90+
3. Identify your custom rule and the AI Audit rule.
91+
4. Drag the rule you wish to prioritize to the top, or modify your custom rule to ensure it does not conflict with your AI Audit configurations.
92+
</Steps>
93+
94+
</TabItem> </Tabs>
95+

0 commit comments

Comments
 (0)