Currently, this is more than enough space, however, ifĪt some point this becomes a problem we’ll cross that bridge when weĬome to it. This means that each rule file in CRS 3.x has 1000 IDs List above notes, the OWASP Core Rule Set is assigned ID’s from 900,000 RulesĪre assigned an ID based on their location within the ruleset. ID’s within the OWASP Core Rule Set (CRS) have special meaning.

9,000,000-9,999,999 reserved for the OWASP ModSecurity Core Rule Set project.

2,000,000-2,999,999 reserved for rules from Trustwave's SpiderLabs.

1,000,000-1,009,999 reserved for rules published by Redhat Security.900,000-999,999 reserved for the OWASP ModSecurity Core Rule Set.430,000–439,999: reserved for rules published by Flameeyes.200,000–299,999 reserved for rules published Comodo.100,000–199,999 reserved for rules published by Oracle.Use as you see fit butĭo not use this range for rules that are distributed to others. 1-99,999 reserved for local (internal) use.If you are planning on publishing rules or a ruleset please To aid in this process the project maintains a list of reserved (in fact it is designed to be used with the Trustwave commercial rules,įor instance) it is important that no two rulesets have overlapping ID Because CRS can be used with other rule sets This becomes particularly important when it comes to As a result of this it is important that IDsīe generated in a preplanned way such that they don't overlap with Why do rule IDs matter?Įach rule added to a ModSecurity instance must have a unique ID (in We are currently in the process of rewriting all of our documentation: please bear with us while we update our older content. The content on this page may be outdated.

Comodo waf rules