Skip to content

Commit c8e45c7

Browse files
committed
Review asides
1 parent 071d75d commit c8e45c7

File tree

1 file changed

+4
-2
lines changed

1 file changed

+4
-2
lines changed

src/content/docs/waf/account/custom-rulesets/create-dashboard.mdx

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -22,6 +22,8 @@ You can create and deploy custom rulesets at the account or zone level. However,
2222

2323
## Create and deploy a custom ruleset
2424

25+
To create and deploy a custom ruleset at the account level:
26+
2527
<Steps>
2628

2729
1. In the Cloudflare dashboard, go to the **WAF** page.
@@ -41,7 +43,7 @@ You can create and deploy custom rulesets at the account or zone level. However,
4143
- Select **Custom filter expression** to define a custom expression that defines when to execute the custom ruleset. Use the **Field** drop-down list to choose an HTTP property. For each request, the value of the property you choose for **Field** is compared to the value you specify for **Value** using the operator selected in **Operator**. Alternatively, select **Edit expression** to define your expression using the [Expression Editor](/ruleset-engine/rules-language/expressions/edit-expressions/#expression-editor).
4244

4345
:::caution
44-
Deployed custom rulesets will only apply to incoming traffic of Enterprise domains. The Expression Builder will automatically include this filter. If you define a custom expression for the ruleset using the Expression Editor, you must use parentheses to enclose any custom conditions and end your expression with `and cf.zone.plan eq "ENT"` so that the rule only applies to domains on an Enterprise plan.
46+
Custom rulesets deployed at the account level only apply to incoming traffic of Enterprise domains. The Expression Builder will automatically include this filter. If you define a custom expression for the ruleset using the Expression Editor, you must use parentheses to enclose any custom conditions and end your expression with `and cf.zone.plan eq "ENT"` so that the rule only applies to domains on an Enterprise plan.
4547
:::
4648

4749
6. To create a new rule, select **Add rule**.
@@ -83,7 +85,7 @@ You can create and deploy custom rulesets at the account or zone level. However,
8385
</Steps>
8486

8587
:::caution
86-
Deployed custom rulesets will only apply to incoming traffic of Enterprise domains. The Expression Builder will automatically include this filter. If you define a custom expression for the ruleset using the Expression Editor, you must use parentheses to enclose any custom conditions and end your expression with `and cf.zone.plan eq "ENT"` so that the rule only applies to domains on an Enterprise plan.
88+
Custom rulesets deployed at the account level only apply to incoming traffic of Enterprise domains. The Expression Builder in the Cloudflare dashboard will automatically include this filter. If you define a custom expression for the ruleset using the Expression Editor, you must use parentheses to enclose any custom conditions and end your expression with `and cf.zone.plan eq "ENT"` so that the rule only applies to domains on an Enterprise plan.
8789
:::
8890

8991
## Delete a custom ruleset

0 commit comments

Comments
 (0)