Skip to content

Commit 3afc819

Browse files
Update application-gateway-crs-rulegroups-rules.md
1 parent 8f80531 commit 3afc819

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

articles/web-application-firewall/ag/application-gateway-crs-rulegroups-rules.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -19,7 +19,7 @@ You also have the option of using rules that are defined based on the OWASP core
1919
You can disable rules individually, or set specific actions for each rule. This article lists the current rules and rule sets available. If a published rule set requires an update, we'll document it here.
2020

2121
> [!NOTE]
22-
> When a new ruleset version is assigned to a WAF, existing customizations of the previously assigned ruleset version will be set to the default for the new ruleset that is being assigned. See: [Upgrading or changing ruleset version](#upgrading-or-changing-ruleset-version).
22+
> When a ruleset version is changed in a WAF Policy, any existing customizations you made to your ruleset will be reset to the defaults for the new ruleset. See: [Upgrading or changing ruleset version](#upgrading-or-changing-ruleset-version).
2323
2424
## Default rule sets
2525

@@ -103,7 +103,7 @@ For example, a single *Critical* rule match is enough for the WAF to block a req
103103

104104
### Upgrading or changing ruleset version
105105

106-
When assigning a new managed ruleset to a WAF policy, all the previous customizations from the existing managed rulesets such as rule state, rule actions and rule level exclusions will be reset to the new managed ruleset's defaults. However, any custom rules, policy settings, and global exclusions will remain unaffected during the new ruleset assignment. You will need to redefine rule overrides and validate changes before deploying in a production environment.
106+
When a ruleset version is changed in a WAF Policy, all the previous customizations from the existing managed rulesets such as rule state, rule actions and rule level exclusions will be reset to the new managed ruleset's defaults. However, any custom rules, policy settings, and global exclusions will remain unaffected during the new ruleset assignment. You will need to redefine rule overrides and validate changes before deploying in a production environment.
107107

108108
### DRS 2.1
109109

0 commit comments

Comments
 (0)