Skip to content
This repository has been archived by the owner on Aug 7, 2020. It is now read-only.

Latest commit

 

History

History
105 lines (78 loc) · 5.39 KB

rules.rst

File metadata and controls

105 lines (78 loc) · 5.39 KB

What's In The Rules

REQUEST-00-LOCAL-WHITELIST.conf.example
Configuration Path: owasp-modsecurity-crs/rules/REQUEST-00-LOCAL-WHITELIST.conf.example
This file is used to add LOCAL exceptions for your site. Often in this file we would see rules that short-circuit inspection and allow certain transactions to skip through inspection.
Example: SecRule REMOTE_ADDR "@ipMatch 192.168.1.100" "phase:1,id:'981033',t:none,nolog,pass,ctl:ruleEngine=Off"
REQUEST-01-COMMON-EXCEPTIONS
Configuration Path: owasp-modsecurity-crs/rules/REQUEST-01-COMMON-EXCEPTIONS.conf

Some rules are quite prone to causing false positives in well established software, such as Apache callbacks or Google Analytics tracking cookie. This file offers rules that will allow the transactions to avoid triggering these false positives.
REQUEST-10-IP-REPUTATION
Configuration Path: owasp-modsecurity-crs/rules/REQUEST-10-IP-REPUTATION.conf

These rules deal with detecting traffic from IPs that have previously been involved with malicious activity, either on our local site or globally.
REQUEST-12-DOS-PROTECTION
Configuration Path: owasp-modsecurity-crs/rules/REQUEST-12-DOS-PROTECTION.conf

The rules in this file will attempt to detect some level 7 DoS (Denial of Service) attacks against your server.
REQUEST-13-SCANNER-DETECTION
Configuration Path: owasp-modsecurity-crs/rules/REQUEST-13-SCANNER-DETECTION.conf

These rules are concentrated around detecting security tools and scanners.
REQUEST-20-PROTOCOL-ENFORCEMENT
Configuration Path: owasp-modsecurity-crs/rules/REQUEST-20-PROTOCOL-ENFORCEMENT.conf

The rules in this file center around detecting requests that either violate HTTP or represent a request that no modern browser would generate, for instance missing a user-agent.
REQUEST-21-PROTOCOL-ATTACK

Configuration Path: owasp-modsecurity-crs/rules/REQUEST-21-PROTOCOL-ATTACK.conf
The rules in this file focus on specific attacks against the HTTP protocol itself such as HTTP Request Smuggling and Response Splitting.
REQUEST-30-APPLICATION-ATTACK-LFI

Configuration Path: owasp-modsecurity-crs/rules/REQUEST-30-APPLICATION-ATTACK-LFI.conf
These rules attempt to detect when a user is trying to include a file that would be local to the webserver that they should not have access to. Exploiting this type of attack can lead to the web application or server being compromised.
REQUEST-31-APPLICATION-ATTACK-RFI
Configuration Path: owasp-modsecurity-crs/rules/REQUEST-31-APPLICATION-ATTACK-RFI.conf

These rules attempt to detect when a user is trying to include a remote resource into the web application that will be executed. Exploiting this type of attack can lead to the web application or server being compromised.
REQUEST-41-APPLICATION-ATTACK-SQLI
Configuration Path: owasp-modsecurity-crs/rules/REQUEST-41-APPLICATION-ATTACK-SQLI.conf

Within this configuration file we provide rules that protect against SQL injection attacks. SQLi attackers occur when an attacker passes crafted control characters to parameters to an area of the application that is expecting only data. The application will then pass the control characters to the database. This will end up changing the meaning of the expected SQL query.
REQUEST-43-APPLICATION-ATTACK-SESSION-FIXATION
Configuration Path: owasp-modsecurity-crs/rules/REQUEST-43-APPLICATION-ATTACK-SESSION-FIXATION.conf

These rules focus around providing protection against Session Fixation attacks.
REQUEST-49-BLOCKING-EVALUATION
Configuration Path: owasp-modsecurity-crs/rules/REQUEST-49-BLOCKING-EVALUATION.conf

These rules provide the anomaly based blocking for a given request. If you are in anomaly detection mode this file must not be deleted.
RESPONSE-50-DATA-LEAKAGES-IIS
Configuration Path: owasp-modsecurity-crs/rules/RESPONSE-50-DATA-LEAKAGES-IIS.conf

These rules provide protection against data leakages that may occur because of Microsoft IIS
RESPONSE-50-DATA-LEAKAGES-JAVA
Configuration Path: owasp-modsecurity-crs/rules/RESPONSE-50-DATA-LEAKAGES-JAVA.conf

These rules provide protection against data leakages that may occur because of Java
RESPONSE-50-DATA-LEAKAGES-PHP
Configuration Path: owasp-modsecurity-crs/rules/RESPONSE-50-DATA-LEAKAGES-PHP.conf

These rules provide protection against data leakages that may occur because of PHP
RESPONSE-50-DATA-LEAKAGES
Configuration Path: owasp-modsecurity-crs/rules/RESPONSE-50-DATA-LEAKAGES.conf

These rules provide protection against data leakages that may occur genericly
RESPONSE-51-DATA-LEAKAGES-SQL
Configuration Path: owasp-modsecurity-crs/rules/RESPONSE-51-DATA-LEAKAGES-SQL.conf

These rules provide protection against data leakages that may occur from backend SQL servers. Often these are indicative of SQL injection issues being present.
RESPONSE-59-BLOCKING-EVALUATION
Configuration Path: owasp-modsecurity-crs/rules/RESPONSE-59-BLOCKING-EVALUATION.conf

These rules provide the anomaly based blocking for a given response. If you are in anomaly detection mode this file must not be deleted.
RESPONSE-80-CORRELATION
Configuration Path: owasp-modsecurity-crs/rules/RESPONSE-80-CORRELATION.conf

The rules in this configuration file facilitate the gathering of data about successful and unsuccessful attacks on the server.