ModSecurity CRS Rule Description Template
- This is a template for submitting or documenting ModSecurity CRS rule/signature descriptions to the OWASP ModSecurity Core Rule Set (CRS) Project. - Project participants are encouraged to copy this template and create landing pages for each CRS rule - Use this template and create a new page using the following format - http://www.owasp.org/index.php?title=ModSecurity_CRS_RuleID-XXXXX (where XXXXX is the CRS ruleID)
Rule ID: XXXXX
Place Rule ID Here
Place Rule Message Here
Provide rule background. What is the rule looking for? What attack is trying to identify or prevent.
This should be the Severity rating specified in the rule. (Example: 4 - Warning)
|Detailed Rule Information||
Provide detailed information about the rule construction such as:
A description of the regular expression used - what is is looking for in plain english (Example RegEx analysis from Expresso tool)
Provide an example payload that will trigger this rule.
Example Apache log entry or HTTP payload captured by another tool
|Example Audit Log Entry||
Include an example ModSecurity Audit Log Entry for when this rule matchs.
Audit Log Entry
Provide any data around "how" the attack is carried out.
|Ease of Attack||
How easy is it for an attacker to carry out the attack?
|Ease of Detection||
How easy is it for a defender to use ModSecurity to accurately detect this attack?
If there are any known false positives - specify them here Also sign-up for the Reporting False Positives mail-list here: https://lists.sourceforge.net/lists/listinfo/mod-security-report-false-positives
Are there any know issues with evasions or how an attacker might bypass detection?
|Rule Accuracy Level||
5 point scale where:
|Rule Documentation Contributor(s)|
Provide any external reference links (e.g. - if this is a virtual patch for a known vuln link to the Bugtraq or CVE page).