Skip to content

docs: document engine-specific rule-range behavior for ById exclusions #302

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
Copilot wants to merge 2 commits into
base: main
Choose a base branch
from
Open

docs: document engine-specific rule-range behavior for ById exclusions #302

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
5e7a378
Initial plan
Copilot Sep 14, 2026
03d37c1
docs: clarify rule-range support across engines
Copilot Sep 14, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 10 additions & 1 deletion content/2-how-crs-works/2-3-false-positives-and-tuning.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -116,7 +116,7 @@ The different rule exclusion types and methods are summarized in the table below

*\*Can also exclude ranges of rules or multiple space separated rules.*

*\*\*Can also exclude ranges of rules (not currently supported in ModSecurity v3).*
*\*\*Can also exclude ranges of rules.*

{{% notice style="tip" icon="file-arrow-down" %}}
This table is available as a well presented, downloadable [Rule Exclusion Cheatsheet](https://www.netnea.com/cms/rule-exclusion-cheatsheet-download) from Christian Folini.
Expand Down Expand Up @@ -154,6 +154,15 @@ SecRuleRemoveById "913000-913999"

Excluding rules using rule ranges may be more useful than excluding using tags in situations where tags are less relevant or where tags vary across the rules in question. For example, a rule range may be the most appropriate solution if the goal is to remove all rules contained in a single file, regardless of how the rules are tagged.

Support for rule ranges is not identical across all directives/actions and engines. The table below summarizes current behavior when a rule **range** is used with `ById` exclusions:

| Directive / action | ModSecurity v2 | ModSecurity v3 | Coraza |
| ------------------------------ | -------------- | -------------- | ------ |
| `SecRuleRemoveById` | ✅ Full range | ✅ Full range | ✅ Full range |
| `ctl:ruleRemoveById` | ✅ Full range | ✅ Full range | ✅ Full range |
| `SecRuleUpdateTargetById` | ⚠️ First ID only | ⚠️ First ID only | ✅ Full range |
| `ctl:ruleRemoveTargetById` | ⚠️ First ID only | ⚠️ First ID only | ✅ Full range |

#### Support for Regular Expressions

Most of the configure-time rule exclusion directives feature some level of support for using regular expressions. This makes it possible, for example, to exclude a dynamically named variable from a rule. The directives with support for regular expressions are:
Expand Down
Loading