Skip to content

Commit b176646

Browse files
sequence rules new dash
1 parent 9bdb537 commit b176646

File tree

1 file changed

+51
-24
lines changed

1 file changed

+51
-24
lines changed

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

Lines changed: 51 additions & 24 deletions
Original file line numberDiff line numberDiff line change
@@ -10,33 +10,60 @@ head:
1010
content: Manage sequence rules
1111

1212
---
13-
import { Steps } from "~/components"
13+
import { Steps, Tabs, TabItem } from "~/components"
1414

1515
## Create a sequence rule
1616

17-
<Steps>
18-
1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/), and select your account and domain.
19-
2. Go to **Security** > **API Shield** > **API Rules**.
20-
3. Select **Create sequence rule**.
21-
4. <a id="rule-form"/>
22-
Name your rule.
23-
5. Select a starting endpoint. This is the endpoint that you expect users to hit first in their request flow when using your API.
24-
- Choose a hostname to display the list of endpoints for that hostname.
25-
- Choose an endpoint.
26-
- Select **Set as starting endpoint**.
27-
6. Select a final endpoint. This is the endpoint you are targeting for protection.
28-
- Choose a hostname to display the list of endpoints for that hostname.
29-
- Choose an endpoint.
30-
- Select **Set as ending endpoint**.
31-
7. Choose an action that corresponds to the security model type:
32-
- **Allow**: This will create a positive security model by defining approved sequences on your API.
33-
- **Log** / **Block**: This will test or enforce a negative security model defining known bad sequences on your API.
34-
:::note
35-
36-
If you chose **Allow**, select whether to log or block the request to the final endpoint when users do not first request the starting endpoint in the sequence.
37-
:::
38-
8. Select **Create rule**.
39-
</Steps>
17+
<Tabs syncKey="dashNewNav">
18+
<TabItem label="Old dashboard">
19+
<Steps>
20+
1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/), and select your account and domain.
21+
2. Go to **Security** > **API Shield** > **API Rules**.
22+
3. Select **Create sequence rule**.
23+
4. Name your rule.
24+
5. Select a starting endpoint. This is the endpoint that you expect users to hit first in their request flow when using your API.
25+
- Choose a hostname to display the list of endpoints for that hostname.
26+
- Choose an endpoint.
27+
- Select **Set as starting endpoint**.
28+
6. Select a final endpoint. This is the endpoint you are targeting for protection.
29+
- Choose a hostname to display the list of endpoints for that hostname.
30+
- Choose an endpoint.
31+
- Select **Set as ending endpoint**.
32+
7. Choose an action that corresponds to the security model type:
33+
- **Allow**: This will create a positive security model by defining approved sequences on your API.
34+
- **Log** / **Block**: This will test or enforce a negative security model defining known bad sequences on your API.
35+
:::note
36+
37+
If you chose **Allow**, select whether to log or block the request to the final endpoint when users do not first request the starting endpoint in the sequence.
38+
:::
39+
8. Select **Create rule**.
40+
</Steps>
41+
</TabItem>
42+
<TabItem label="New dashboard" icon="rocket">
43+
<Steps>
44+
1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/), and select your account and domain.
45+
2. Go to **Security** > **Security rules**.
46+
3. Select **Create rule** and choose **API sequence rules**.
47+
4. Name your rule.
48+
5. Select a starting endpoint. This is the endpoint that you expect users to hit first in their request flow when using your API.
49+
- Choose a hostname to display the list of endpoints for that hostname.
50+
- Choose an endpoint.
51+
- Select **Set as starting endpoint**.
52+
6. Select a final endpoint. This is the endpoint you are targeting for protection.
53+
- Choose a hostname to display the list of endpoints for that hostname.
54+
- Choose an endpoint.
55+
- Select **Set as ending endpoint**.
56+
7. Choose an action that corresponds to the security model type:
57+
- **Allow**: This will create a positive security model by defining approved sequences on your API.
58+
- **Log** / **Block**: This will test or enforce a negative security model defining known bad sequences on your API.
59+
:::note
60+
61+
If you chose **Allow**, select whether to log or block the request to the final endpoint when users do not first request the starting endpoint in the sequence.
62+
:::
63+
8. Select **Create rule**.
64+
</Steps>
65+
</TabItem>
66+
</Tabs>
4067

4168
## Edit a sequence rule
4269

0 commit comments

Comments
 (0)