Wednesday, August 31, 2011

OWASP AppSensor Detection Points in the OWASP ModSecurity Core Rule Set

(from Ryan Barnett)

I have begun the process of implementing the OWASP AppSensor Detection Points ( within the OWASP ModSecurity Core Rule Set (

I am pleased to announce that I have just made an update to the OWASP CRS SVN repository that fully implements the Request Exception (RE) category - See the following blog post for more details -

The major change in this version vs. the earlier one outlined in this blog post ( is that both the profiling and detection logic has been moved to Lua scripts. With the increased logic capabilities of Lua, we are now able to more accurately profile the application in real-time by analyzing traffic and automatically generating profiles for the following resource characteristics -
  • Enforcing the expected Request Method(s)
  • Enforce the number of expected parameters (min-max range)
  • Enforce parameter names
  • Enforce parameter lengths (min-max range)
  • Enforce Character Classes
    • Flag (e.g. - /path/to/foo.php?param)
    • Digits (e.g. - /path/to/foo.php?param=1234)
    • Alpha (e.g. - /path/to/foo.php?param=abcd)
    • AlphaNumeric (e.g. - /path/to/foo.php?param=abcd1234)
    • Email (e.g. - /path/to/foo.php?
    • Path (e.g. - /path/to/foo.php?param=/dir/somefile.txt)
    • URL (e.g. - /path/to/foo.php?param=http://somehost/dir/file.txt)
    • SafeText (e.g. - /path/to/foo.php?param=some_data-12)
The updated rules files are in the /experimental_rules directory -

I encourage people to test out these new rules and to report back their experiences – both good and bad.

FYI – I also wanted to thank Josh Zlatin for assisting with the initial Lua script creation.


Ryan Barnett
OWASP ModSecurity Core Rule Set Project Leader


Post a Comment

Subscribe to Post Comments [Atom]

<< Home