Skip to content

Commit 1842086

Browse files
feedback
1 parent c7c39c8 commit 1842086

File tree

5 files changed

+18
-9
lines changed

5 files changed

+18
-9
lines changed

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
@@ -24,7 +24,7 @@ Rules built using these custom rules are different from sequence mitigation rule
2424

2525
<Render file="sequence-rules-availability" product="bots" />
2626

27-
## Create a sequence custom rule
27+
## Build a sequence custom rule
2828

2929
<Render file="sequence-custom-rules" />
3030

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

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -12,6 +12,10 @@ head:
1212
---
1313
import { Steps, Tabs, TabItem } from "~/components"
1414

15+
:::note
16+
Cloudflare recommends creating sequence rules using WAF custom rules. Refer to the [sequence custom rules documentation](/api-shield/security/sequence-mitigation/custom-rules/) for more information.
17+
:::
18+
1519
## Create a sequence rule
1620

1721
<Tabs syncKey="dashNewNav">

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -26,7 +26,7 @@ You can [create a sequence custom rule via the Cloudflare dashboard](#create-a-s
2626

2727
---
2828

29-
## Create a sequence custom rule via the Cloudflare dashboard
29+
## Build a sequence custom rule via the Cloudflare dashboard
3030

3131
<Render file="sequence-custom-rules" product="api-shield" />
3232

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,10 +1,10 @@
11
---
22
pcx_content_type: configuration
3-
title: Create a sequence rule within custom rules
3+
title: Build a sequence rule within custom rules
44
---
55

66
import { Render } from "~/components";
77

8-
You can create an [API sequence rule](/api-shield/security/sequence-mitigation/custom-rules/) via the Cloudflare dashboard.
8+
You can build an [API sequence rule](/api-shield/security/sequence-mitigation/custom-rules/) via the Cloudflare dashboard.
99

1010
<Render file="sequence-custom-rules" product="api-shield" />

src/content/partials/api-shield/sequence-custom-rules.mdx

Lines changed: 10 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -32,18 +32,23 @@ import { Steps, Tabs, TabItem } from "~/components"
3232
2. Go to **Security** > **Security rules**.
3333
3. To create a new empty rule, select **Create rule** > **Custom rules**.
3434
4. Enter a descriptive name for the rule in **Rule name**.
35-
5. Under **When incoming requests match**, use the **Field** drop-down list to filter by **Sequences** and select:
35+
5. Under **When incoming requests match**, use the **Field** drop-down list to filter by **Sequences** and select from:
3636
- Current Operation
3737
- Previous Operations
3838
- Elapsed time
39-
6. Under **Value**, build a sequence by selecting a hostname for the sequence.
40-
7. Select the checkbox for each endpoint in the order that you want them to appear in the sequence.
39+
6. Under **Value**, select the edit icon to use Builder and build a sequence on the side panel.
40+
7. Under **Select a hostname for this sequence**, choose all or a specific hostname from the dropdown list. Optionally, you can use the search bar to search for a specific hostname.
41+
8. From the **Methods** dropdown list, choose all methods or a specific request method.
42+
8. Select the checkbox for each endpoint in the order that you want them to appear in the sequence.
4143
8. Set the time to complete.
4244
9. Select **Save**.
4345
10. Under **Then take action**, select the rule action in the **Choose action** dropdown. For example, selecting *Block* tells Cloudflare to refuse requests that match the conditions you specified.
44-
11. (Optional) If you selected the Block action, you can configure a custom response.
46+
11. (Optional) If you selected the *Block* action, you can configure a custom response.
4547
12. Under **Place at**, select the order of when the rule will fire.
4648
13. To save and deploy your rule, select **Deploy**. If you are not ready to deploy your rule, select **Save as Draft**.
4749
</Steps>
50+
:::note
51+
The fields in the custom rule are populated as a grouped sequence based on the values that you entered on Builder.
52+
:::
4853
</TabItem>
49-
</Tabs>
54+
</Tabs>

0 commit comments

Comments
 (0)