Slashdot Mirror
OWASP ModSecurity Core Rule Set Version 3.0 Released (modsecurity.org)
Need a new set of generic attack detection rules for your web application firewall? Try the new OWASP ModSecurity Core Rule Set version 3.0.0! Long-time Slashdot reader dune73 writes: The OWASP CRS is a widely-used Open Source set of generic rules designed to protect users against threats like the OWASP Top 10. The rule set is most often deployed in conjunction with an existing Web Application Firewall like ModSecurity. Four years in the making, this release comes with dozens of new features including reduced false positives (by over 90% in the default setup), improved detection of SQLi, XSS, RCE and PHP injections, the introduction of a Paranoia Mode which allows assigning a certain security level to a site, and better documentation that takes the pain out of ModSecurity.
There's rumors this new rule set is even being made into a movie
There's rumors this new rule set is even being made into a movie
It's for web hosts and other people running code they didn't write -- in other words, the 99.998% of websites that aren't custom-built from scratch. Unfortunately, the false positives are a major headache which make me loathe modsecurity.
This space intentionally left blank
false sense of security. Build proper code
Oh, the irony.
"Proper code?" Do tell me about your stunning insights into software security engineering.
My God, it's Full of Source!
OUTSIDE_IP=$(dig +short my.ip @outsideip.net)
[project committer here]
The ModSec Core Rule Set 3.0 (CRS3) comes with a reduction of at least 90% of false positives (more like 99% on my servers). The base setups of Wordpress and Drupal can be run without any FPs.
If you see FPs with a default install of the Core Rules, please report. The idea is to have next to no FPs in the standard deployment mode.
There is a series of tutorials, which explains the installation of ModSec, the inclusion of the Core Rule Set and the handling of False Positives (still important at higher Paranoia Levels).
Several components of the application stack used by this system have had known serious security vulnerabilities in the past.
Could you elaborate, please?
The stack I see Apache/NginX/IIS + ModSecurity + Libinjection + Core Rule Set. What am I missing? Apache has certainly had it's share of weaknesses, but with ModSec the track records seems quite clean; as is the case of Libinjection and the CRS.