Difference between revisions of "ModSecurity: Core Rule Set"
Onnowpurbo (talk | contribs) |
Onnowpurbo (talk | contribs) |
||
| Line 2: | Line 2: | ||
| + | OWASP ModSecurity Core Rule Set (CRS) adalah sekumpulan generic attack detection rules untuk digunakan dengan ModSecurity atau compatible web application firewall. CRS bertujuan untuk protect web applicatio dari berbagai serangan, termasuk OWASP Top Ten, dengan minimum false alert. | ||
| + | The Core Rule Set provides protection against many common attack categories, including: | ||
| + | SQL Injection (SQLi) | ||
| + | Cross Site Scripting (XSS) | ||
| + | Local File Inclusion (LFI) | ||
| + | Remote File Inclusion (RFI) | ||
| + | Remote Code Execution (RCE) | ||
| + | PHP Code Injection | ||
| + | HTTP Protocol Violations HTTPoxy | ||
| + | Shellshock | ||
| + | Session Fixation | ||
| + | Scanner Detection | ||
| + | Metadata/Error Leakages | ||
| + | Project Honey Pot Blacklist | ||
| + | GeoIP Country Blocking | ||
| − | The | + | The Core Rule Set is free software, distributed under Apache Software License version 2. |
| − | + | ==New Features in CRS 3== | |
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | + | CRS 3 includes many coverage improvements, plus the following new features: | |
| − | |||
| − | |||
| − | + | Over 90% reduction of false alerts in a default install | |
| − | + | A user-defined Paranoia Level to enable additional strict checks | |
| − | + | Application-specific exclusions for WordPress Core and Drupal | |
| − | + | Sampling mode runs the CRS on a user-defined percentage of traffic | |
| − | + | SQLi/XSS parsing using libinjection embedded in ModSecurity | |
For a full list of changes in this release, see the CHANGES document. | For a full list of changes in this release, see the CHANGES document. | ||
| − | Installation | + | |
| + | ==Installation== | ||
CRS 3 requires an Apache/IIS/Nginx web server with ModSecurity 2.8.0 or higher. | CRS 3 requires an Apache/IIS/Nginx web server with ModSecurity 2.8.0 or higher. | ||
Our GitHub repository is the preferred way to download and update CRS. | Our GitHub repository is the preferred way to download and update CRS. | ||
| − | HTTPS git clone https://github.com/SpiderLabs/owasp-modsecurity-crs.git | + | |
| − | SSH git clone git@github.com:SpiderLabs/owasp-modsecurity-crs.git | + | HTTPS git clone https://github.com/SpiderLabs/owasp-modsecurity-crs.git |
| + | SSH git clone git@github.com:SpiderLabs/owasp-modsecurity-crs.git | ||
After download, copy crs-setup.conf.example to crs-setup.conf. Optionally edit this file to configure your CRS settings. Then include the files in your webserver configuration: | After download, copy crs-setup.conf.example to crs-setup.conf. Optionally edit this file to configure your CRS settings. Then include the files in your webserver configuration: | ||
| − | Include /.../crs-setup.conf | + | Include /.../crs-setup.conf |
| − | + | I nclude /.../rules/*.conf | |
For detailed installation instructions, see the INSTALL document. Also review the CHANGES and KNOWN_BUGS documents. | For detailed installation instructions, see the INSTALL document. Also review the CHANGES and KNOWN_BUGS documents. | ||
You can update the rule set using the included script util/upgrade.py. | You can update the rule set using the included script util/upgrade.py. | ||
| − | Handling False Positives and Advanced Features | + | |
| + | ==Handling False Positives and Advanced Features== | ||
Advanced features are explained in the crs-setup.conf and the rule files themselves. The crs-setup.conf file is generally a very good entry point to explore the features of the CRS. | Advanced features are explained in the crs-setup.conf and the rule files themselves. The crs-setup.conf file is generally a very good entry point to explore the features of the CRS. | ||
| Line 56: | Line 59: | ||
Christian Folini's tutorials on installing ModSecurity, configuring the CRS and handling false positives provide in-depth information on these topics. | Christian Folini's tutorials on installing ModSecurity, configuring the CRS and handling false positives provide in-depth information on these topics. | ||
| − | Community | + | |
| + | ==Community== | ||
We strive to make the OWASP ModSecurity CRS accessible to a wide audience of beginner and experienced users. We are interested in hearing any bug reports, false positive alert reports, evasions, usability issues, and suggestions for new detections. | We strive to make the OWASP ModSecurity CRS accessible to a wide audience of beginner and experienced users. We are interested in hearing any bug reports, false positive alert reports, evasions, usability issues, and suggestions for new detections. | ||
| Line 65: | Line 69: | ||
Join the #modsecurity channel on Freenode IRC to chat about the CRS. | Join the #modsecurity channel on Freenode IRC to chat about the CRS. | ||
| − | |||
| − | + | ==Core Team== | |
| − | + | ||
| − | + | Chaim Sanders (csanders-git) - Project Lead | |
| + | Walter Hop (lifeforms) - Core Developer | ||
| + | Christian Folini (Twitter: @ChrFolini, GitHub: dune73) - Core Developer | ||
Revision as of 11:09, 28 March 2020
sumber: http://modsecurity.org/crs/
OWASP ModSecurity Core Rule Set (CRS) adalah sekumpulan generic attack detection rules untuk digunakan dengan ModSecurity atau compatible web application firewall. CRS bertujuan untuk protect web applicatio dari berbagai serangan, termasuk OWASP Top Ten, dengan minimum false alert.
The Core Rule Set provides protection against many common attack categories, including:
SQL Injection (SQLi) Cross Site Scripting (XSS) Local File Inclusion (LFI) Remote File Inclusion (RFI) Remote Code Execution (RCE) PHP Code Injection HTTP Protocol Violations HTTPoxy Shellshock Session Fixation Scanner Detection Metadata/Error Leakages Project Honey Pot Blacklist GeoIP Country Blocking
The Core Rule Set is free software, distributed under Apache Software License version 2.
New Features in CRS 3
CRS 3 includes many coverage improvements, plus the following new features:
Over 90% reduction of false alerts in a default install A user-defined Paranoia Level to enable additional strict checks Application-specific exclusions for WordPress Core and Drupal Sampling mode runs the CRS on a user-defined percentage of traffic SQLi/XSS parsing using libinjection embedded in ModSecurity
For a full list of changes in this release, see the CHANGES document.
Installation
CRS 3 requires an Apache/IIS/Nginx web server with ModSecurity 2.8.0 or higher.
Our GitHub repository is the preferred way to download and update CRS.
HTTPS git clone https://github.com/SpiderLabs/owasp-modsecurity-crs.git SSH git clone git@github.com:SpiderLabs/owasp-modsecurity-crs.git
After download, copy crs-setup.conf.example to crs-setup.conf. Optionally edit this file to configure your CRS settings. Then include the files in your webserver configuration:
Include /.../crs-setup.conf
I nclude /.../rules/*.conf
For detailed installation instructions, see the INSTALL document. Also review the CHANGES and KNOWN_BUGS documents.
You can update the rule set using the included script util/upgrade.py.
Handling False Positives and Advanced Features
Advanced features are explained in the crs-setup.conf and the rule files themselves. The crs-setup.conf file is generally a very good entry point to explore the features of the CRS.
We are trying hard to reduce the number of false positives (false alerts) in the default installation. But sooner or later, you may encounter false positives nevertheless.
Christian Folini's tutorials on installing ModSecurity, configuring the CRS and handling false positives provide in-depth information on these topics.
Community
We strive to make the OWASP ModSecurity CRS accessible to a wide audience of beginner and experienced users. We are interested in hearing any bug reports, false positive alert reports, evasions, usability issues, and suggestions for new detections.
Create an issue on GitHub to report a false positive or false negative (evasion). Please include your installed version and the relevant portions of your ModSecurity audit log.
Sign up for the mailing list to ask general usage questions and participate in discussions on the CRS.
Join the #modsecurity channel on Freenode IRC to chat about the CRS.
Core Team
Chaim Sanders (csanders-git) - Project Lead Walter Hop (lifeforms) - Core Developer Christian Folini (Twitter: @ChrFolini, GitHub: dune73) - Core Developer