From 54903c08551b7199cb79e10ceec4c99be4d7a0a7 Mon Sep 17 00:00:00 2001 From: brenosilva Date: Sat, 20 Oct 2012 08:10:20 -0700 Subject: [PATCH] Updated Reference Manual (mediawiki) --- Reference-Manual.mediawiki | 6571 ++++++++++++++++-------------------- 1 file changed, 2977 insertions(+), 3594 deletions(-) diff --git a/Reference-Manual.mediawiki b/Reference-Manual.mediawiki index e6b8f3e..dac9ff5 100644 --- a/Reference-Manual.mediawiki +++ b/Reference-Manual.mediawiki @@ -1,940 +1,256 @@ - - - - - - - - - - += ModSecurity® Reference Manual = +== Current as of v2.5.13 v2.6 and v2.7 == +=== Copyright © 2004-2011 [https://www.trustwave.com/ Trustwave Holdings, Inc.] === - - - - SourceForge.net: Reference Manual - mod-security - - - - += Table of Contents = += Introduction = +ModSecurity is a web application firewall (WAF). With over 70% of attacks now carried out over the web application level, organisations need all the help they can get in making their systems secure. WAFs are deployed to establish an increased external security layer to detect and/or prevent attacks before they reach web applications. ModSecurity provides protection from a range of attacks against web applications and allows for HTTP traffic monitoring and real-time analysis with little or no changes to existing infrastructure. - - - - - - - - +== HTTP Traffic Logging == +Web servers are typically well-equipped to log traffic in a form useful for marketing analyses, but fall short logging traffic to web applications. In particular, most are not capable of logging the request bodies. Your adversaries know this, and that is why most attacks are now carried out via POST requests, rendering your systems blind. ModSecurity makes full HTTP transaction logging possible, allowing complete requests and responses to be logged. Its logging facilities also allow fine-grained decisions to be made about exactly what is logged and when, ensuring only the relevant data is recorded. As some of the request and/or response may contain sensitive data in certain fields, ModSecurity can be configured to mask these fields before they are written to the audit log. - +== Real-Time Monitoring and Attack Detection == +In addition to providing logging facilities, ModSecurity can monitor the HTTP traffic in real time in order to detect attacks. In this case, ModSecurity operates as a web intrusion detection tool, allowing you to react to suspicious events that take place at your web systems. - - - - - +== Attack Prevention and Virtual Patching == +ModSecurity can also act immediately to prevent attacks from reaching your web applications. There are three commonly used approaches: +#Negative security model. A negative security model monitors requests for anomalies, unusual behaviour, and common web application attacks. It keeps anomaly scores for each request, IP addresses, application sessions, and user accounts. Requests with high anomaly scores are either logged or rejected altogether. +#Positive security model. When a positive security model is deployed, only requests that are known to be valid are accepted, with everything else rejected. This model requires knownledge of the web applications you are protecting. Therefore a positive security model works best with applications that are heavily used but rarely updated so that maintenance of the model is minimized. +#Known weaknesses and vulnerabilities. Its rule language makes ModSecurity an ideal external patching tool. External patching (sometimes referred to as Virtual Patching) is about reducing the window of opportunity. Time needed to patch application vulnerabilities often runs to weeks in many organisations. With ModSecurity, applications can be patched from the outside, without touching the application source code (and even without any access to it), making your systems secure until a proper patch is applied to the application. - - +== Flexible Rule Engine == +A flexible rule engine sits in the heart of ModSecurity. It implements the ModSecurity Rule Language, which is a specialised programming language designed to work with HTTP transaction data. The ModSecurity Rule Language is designed to be easy to use, yet flexible: common operations are simple while complex operations are possible. Certified ModSecurity Rules, included with ModSecurity, contain a comprehensive set of rules that implement general-purpose hardening, protocol validation and detection of common web application security issues. Heavily commented, these rules can be used as a learning tool. - - - - - - +== Embedded-mode Deployment == +ModSecurity is an embeddable web application firewall, which means it can be deployed as part of your existing web server infrastructure provided your web servers are Apache-based. This deployment method has certain advantages: - - +#No changes to existing network. It only takes a few minutes to add ModSecurity to your existing web servers. And because it was designed to be completely passive by default, you are free to deploy it incrementally and only use the features you need. It is equally easy to remove or deactivate it if required. +#No single point of failure. Unlike with network-based deployments, you will not be introducing a new point of failure to your system. +#Implicit load balancing and scaling. Because it works embedded in web servers, ModSecurity will automatically take advantage of the additional load balancing and scalability features. You will not need to think of load balancing and scaling unless your existing system needs them. +#Minimal overhead. Because it works from inside the web server process there is no overhead for network communication and minimal overhead in parsing and data exchange. +#No problem with encrypted or compressed content. Many IDS systems have difficulties analysing SSL traffic. This is not a problem for ModSecurity because it is positioned to work when the traffic is decrypted and decompressed. - +== Network-based Deployment == +ModSecurity works equally well when deployed as part of an Apache-based reverse proxy server, and many of our customers choose to do so. In this scenario, one installation of ModSecurity can protect any number of web servers (even the non-Apache ones). - -
-
-
    -
    2. -
  2. Summary
    3. +== Portability == +ModSecurity is known to work well on a wide range of operating systems. Our customers are successfully running it on Linux, Windows, Solaris, FreeBSD, OpenBSD, NetBSD, AIX, Mac OS X, and HP-UX. -
  3. Files
  4. Support
    5. -
  5. Report Spam
    6. -
  6. Log out
    7. -
  7. Account
    8. -
  8. Welcome brenosilva
    9. +== Licensing == +ModSecurity is available under the Apache Software License v2 [http://www.apache.org/licenses/LICENSE-2.0.txt] -
-
-
-
- -
- +; Note : ModSecurity, mod_security, ModSecurity Pro, and ModSecurity Core Rules are trademarks or registered trademarks of Trustwave Holdings, Inc. -
-
-
- += OWASP ModSecurity Core Rule Set (CRS) Project = +== Overview == +ModSecurity is a web application firewall engine that provides very little protection on its own. In order to become useful, ModSecurity must be configured with rules. In order to enable users to take full advantage of ModSecurity out of the box, Trustwave's SpiderLabs created the OWASP ModSecurity Core Rule Set (CRS) Project. Unlike intrusion detection and prevention systems, which rely on signatures specific to known vulnerabilities, the CRS provide generic protection from unknown vulnerabilities often found in web applications, which are in most cases custom coded. The CRS is heavily commented to allow it to be used as a step-by-step deployment guide for ModSecurity. The latest rules packages can be found at the [http://www.owasp.org/index.php/Category:OWASP_ModSecurity_Core_Rule_Set_Project OWASP ModSecurity CRS Project Site]. -

Reference Manual

-
-

From mod-security

-
-
Jump to: navigation, search
+== Core Rules Content == +In order to provide generic web applications protection, the CRS use some of the following example techniques: -

Contents

- -
-

[edit] ModSecurity® Reference Manual

- -

[edit] Current as of v2.5.13 v2.6 and v2.7

-

[edit] Copyright © 2004-2011 Trustwave Holdings, Inc.

- -

[edit] Table of Contents

-

[edit] Introduction

-

ModSecurity is a web application firewall (WAF). With over 70% of attacks now carried out over the web application level, organisations need all the help they can get in making their systems secure. WAFs are deployed to establish an increased external security layer to detect and/or prevent attacks before they reach web applications. ModSecurity provides protection from a range of attacks against web applications and allows for HTTP traffic monitoring and real-time analysis with little or no changes to existing infrastructure. -

-

[edit] HTTP Traffic Logging

- -

Web servers are typically well-equipped to log traffic in a form useful for marketing analyses, but fall short logging traffic to web applications. In particular, most are not capable of logging the request bodies. Your adversaries know this, and that is why most attacks are now carried out via POST requests, rendering your systems blind. ModSecurity makes full HTTP transaction logging possible, allowing complete requests and responses to be logged. Its logging facilities also allow fine-grained decisions to be made about exactly what is logged and when, ensuring only the relevant data is recorded. As some of the request and/or response may contain sensitive data in certain fields, ModSecurity can be configured to mask these fields before they are written to the audit log. -

-

[edit] Real-Time Monitoring and Attack Detection

-

In addition to providing logging facilities, ModSecurity can monitor the HTTP traffic in real time in order to detect attacks. In this case, ModSecurity operates as a web intrusion detection tool, allowing you to react to suspicious events that take place at your web systems. -

-

[edit] Attack Prevention and Virtual Patching

- -

ModSecurity can also act immediately to prevent attacks from reaching your web applications. There are three commonly used approaches: -

-
  1. Negative security model. A negative security model monitors requests for anomalies, unusual behaviour, and common web application attacks. It keeps anomaly scores for each request, IP addresses, application sessions, and user accounts. Requests with high anomaly scores are either logged or rejected altogether. -
  2. Positive security model. When a positive security model is deployed, only requests that are known to be valid are accepted, with everything else rejected. This model requires knownledge of the web applications you are protecting. Therefore a positive security model works best with applications that are heavily used but rarely updated so that maintenance of the model is minimized. -
  3. Known weaknesses and vulnerabilities. Its rule language makes ModSecurity an ideal external patching tool. External patching (sometimes referred to as Virtual Patching) is about reducing the window of opportunity. Time needed to patch application vulnerabilities often runs to weeks in many organisations. With ModSecurity, applications can be patched from the outside, without touching the application source code (and even without any access to it), making your systems secure until a proper patch is applied to the application. -
-

[edit] Flexible Rule Engine

-

A flexible rule engine sits in the heart of ModSecurity. It implements the ModSecurity Rule Language, which is a specialised programming language designed to work with HTTP transaction data. The ModSecurity Rule Language is designed to be easy to use, yet flexible: common operations are simple while complex operations are possible. Certified ModSecurity Rules, included with ModSecurity, contain a comprehensive set of rules that implement general-purpose hardening, protocol validation and detection of common web application security issues. Heavily commented, these rules can be used as a learning tool. -

-

[edit] Embedded-mode Deployment

- -

ModSecurity is an embeddable web application firewall, which means it can be deployed as part of your existing web server infrastructure provided your web servers are Apache-based. This deployment method has certain advantages: -

-
  1. No changes to existing network. It only takes a few minutes to add ModSecurity to your existing web servers. And because it was designed to be completely passive by default, you are free to deploy it incrementally and only use the features you need. It is equally easy to remove or deactivate it if required. -
  2. No single point of failure. Unlike with network-based deployments, you will not be introducing a new point of failure to your system. -
  3. Implicit load balancing and scaling. Because it works embedded in web servers, ModSecurity will automatically take advantage of the additional load balancing and scalability features. You will not need to think of load balancing and scaling unless your existing system needs them. -
  4. Minimal overhead. Because it works from inside the web server process there is no overhead for network communication and minimal overhead in parsing and data exchange. -
  5. No problem with encrypted or compressed content. Many IDS systems have difficulties analysing SSL traffic. This is not a problem for ModSecurity because it is positioned to work when the traffic is decrypted and decompressed. -
-

[edit] Network-based Deployment

-

ModSecurity works equally well when deployed as part of an Apache-based reverse proxy server, and many of our customers choose to do so. In this scenario, one installation of ModSecurity can protect any number of web servers (even the non-Apache ones). -

- -

[edit] Portability

-

ModSecurity is known to work well on a wide range of operating systems. Our customers are successfully running it on Linux, Windows, Solaris, FreeBSD, OpenBSD, NetBSD, AIX, Mac OS X, and HP-UX. -

-

[edit] Licensing

-

ModSecurity is available under the Apache Software License v2 [1] - -

-
Note 
ModSecurity, mod_security, ModSecurity Pro, and ModSecurity Core Rules are trademarks or registered trademarks of Trustwave Holdings, Inc. -
-

[edit] OWASP ModSecurity Core Rule Set (CRS) Project

-

[edit] Overview

- -

ModSecurity is a web application firewall engine that provides very little protection on its own. In order to become useful, ModSecurity must be configured with rules. In order to enable users to take full advantage of ModSecurity out of the box, Trustwave's SpiderLabs created the OWASP ModSecurity Core Rule Set (CRS) Project. Unlike intrusion detection and prevention systems, which rely on signatures specific to known vulnerabilities, the CRS provide generic protection from unknown vulnerabilities often found in web applications, which are in most cases custom coded. The CRS is heavily commented to allow it to be used as a step-by-step deployment guide for ModSecurity. The latest rules packages can be found at the OWASP ModSecurity CRS Project Site. -

-

[edit] Core Rules Content

-

In order to provide generic web applications protection, the CRS use some of the following example techniques: -

-
  • HTTP protection - detecting violations of the HTTP protocol and a locally defined usage policy. -
  • Common Web Attacks Protection - detecting common web application security attack. -
  • Automation detection - Detecting bots, crawlers, scanners and other surface malicious activity. -
  • Trojan Protection - Detecting access to Trojans horses. - -
  • Error Hiding - Disguising error messages sent by the server. -
-

[edit] Installation for Apache

-

[edit] Prerequisites

-

[edit] ModSecurity 2.x works only with Apache 2.0.x or higher

- -

Version 2.2.x is highly recommended. -

-

[edit] mod_uniqueid

-

Make sure you have mod_unique_id installed. +=== ModSecurity 2.x works only with Apache 2.0.x or higher === +Version 2.2.x is highly recommended. +=== mod_uniqueid === +Make sure you have mod_unique_id installed. mod_unique_id is packaged with Apache httpd. -

-

[edit] libapr and libapr-util

-

libapr and libapr-util - http://apr.apache.org/ -

-

[edit] libpcre

-

http://www.pcre.org/ -

-

[edit] libxml2

+=== libapr and libapr-util === +libapr and libapr-util - http://apr.apache.org/ -

http://xmlsoft.org/downloads.html -

-

[edit] liblua v5.1.x

-

This library is optional and only needed if you will be using the new Lua engine - http://www.lua.org/download.html -

-
Note 
that ModSecurity requires the dynamic libraries. These are not built by default in the source distribution, so the binary distribution is recommended. +=== libpcre === +http://www.pcre.org/ -
-

[edit] libcurl v7.15.1 or higher

-

If you will be using the ModSecurity Log Collector (mlogc) to send audit logs to a central repository, then you will also need the curl library. -

http://curl.haxx.se/libcurl/ -

-
Note 
Many have had issues with libcurl linked with the GnuTLS library for SSL/TLS support. It is recommended that the openssl library be used for SSL/TLS support in libcurl. -
+=== libxml2 === +http://xmlsoft.org/downloads.html -

[edit] Installation Methods

-

Before you begin with installation you will need to choose your preferred installation method. First you need to choose whether to install the latest version of ModSecurity directly from CVS (best features, but possibly unstable) or use the latest stable release (recommended). If you choose a stable release, it might be possible to install ModSecurity from binary. It is always possible to compile it from source code. -

The following few pages will give you more information on benefits of choosing one method over another. -

-

[edit] SVN Access

+=== liblua v5.1.x === +This library is optional and only needed if you will be using the new Lua engine - http://www.lua.org/download.html -

If you want to access the latest version of the module you need to get it from the svn repository. The list of changes made since the last stable release is normally available on the web site (and in the file CHANGES). The SVN repository for ModSecurity is hosted by SourceForge (http://www.sf.net). You can access it directly or view if through web using this address: http://mod-security.svn.sourceforge.net/viewvc/mod-security/ -

To download the lastest TRUNK source code to your computer you need to execute the following command: -

git -

+; Note : that ModSecurity requires the dynamic libraries. These are not built by default in the source distribution, so the binary distribution is recommended. + +=== libcurl v7.15.1 or higher === + +If you will be using the ModSecurity Log Collector (mlogc) to send audit logs to a central repository, then you will also need the curl library. + +http://curl.haxx.se/libcurl/ + +; Note : Many have had issues with libcurl linked with the GnuTLS library for SSL/TLS support. It is recommended that the openssl library be used for SSL/TLS support in libcurl. + +== Installation Methods == +Before you begin with installation you will need to choose your preferred installation method. First you need to choose whether to install the latest version of ModSecurity directly from CVS (best features, but possibly unstable) or use the latest stable release (recommended). If you choose a stable release, it might be possible to install ModSecurity from binary. It is always possible to compile it from source code. + +The following few pages will give you more information on benefits of choosing one method over another. + +== SVN Access == + +If you want to access the latest version of the module you need to get it from the svn repository. The list of changes made since the last stable release is normally available on the web site (and in the file CHANGES). The SVN repository for ModSecurity is hosted by SourceForge (http://www.sf.net). You can access it directly or view if through web using this address: http://mod-security.svn.sourceforge.net/viewvc/mod-security/ + +To download the lastest TRUNK source code to your computer you need to execute the following command: + +'''git''' 
 $git svn clone --prefix=svn/ https://mod-security.svn.sourceforge.net/svnroot/mod-security/m2/trunk
-

svn -

+'''svn''' 
 svn co https://mod-security.svn.sourceforge.net/svnroot/mod-security/m2/trunk modsecurity
-
-

For v2.6.0 and above, the installation process has changed. Follow these steps: -

-
  1. cd into the directory - $cd modsecurity -
  2. Run autogen.sh script - $./autogen.sh -
  3. Run configure script - $./configure -
  4. Run make - $make -
  5. Run make install - $make install -
  6. Copy the new mod_security2.so file into the proper Apache modules directory - $cp /usr/local/modsecurity/lib/mod_security2.so /usr/local/apache/modules/ -
-

[edit] Stable Release Download

-

To download the stable release go to http://www.modsecurity.org/download/. Binary distributions are sometimes available. If they are, they are listed on the download page. If not download the source code distribution. -

-

[edit] Installation Steps

+For v2.6.0 and above, the installation process has changed. Follow these steps: +#cd into the directory - $cd modsecurity +#Run autogen.sh script - $./autogen.sh +#Run configure script - $./configure +#Run make - $make +#Run make install - $make install +#Copy the new mod_security2.so file into the proper Apache modules directory - $cp /usr/local/modsecurity/lib/mod_security2.so /usr/local/apache/modules/ -
  • Stop Apache httpd -
  • Unpack the ModSecurity archive -
  • Build -
-

Building differs for UNIX (or UNIX-like) operating systems and Windows. -

-

[edit] UNIX

-

Run the configure script to generate a Makefile. Typically no options are needed. -

+== Stable Release Download == +To download the stable release go to http://www.modsecurity.org/download/. Binary distributions are sometimes available. If they are, they are listed on the download page. If not download the source code distribution. + +== Installation Steps == + +*Stop Apache httpd +*Unpack the ModSecurity archive +*Build +Building differs for UNIX (or UNIX-like) operating systems and Windows. +=== UNIX === +Run the configure script to generate a Makefile. Typically no options are needed. 
./configure
- -

Options are available for more customization (use ./configure --help for a full list), but typically you will only need to specify the location of the apxs command installed by Apache httpd with the --with-apxs option. -

+Options are available for more customization (use ./configure --help for a full list), but typically you will only need to specify the location of the apxs command installed by Apache httpd with the --with-apxs option. 
./configure --with-apxs=/path/to/httpd-2.x.y/bin/apxs
-
Note 
There are certain configure options that are meant for debugging an other development use. If enabled, these options can substantially impact performance. These options include all --debug-* options as well as the --enable-performance-measurements options. -
-

Compile with: -

+; Note : There are certain configure options that are meant for debugging an other development use. If enabled, these options can substantially impact performance. These options include all --debug-* options as well as the --enable-performance-measurements options. +Compile with: 
make
-

Optionally test with: -

+Optionally test with: 
make CFLAGS=-DMSC_TEST test
- -
Note 
This is step is still a bit experimental. If you have problems, please send the full output and error from the build to the support list. Most common issues are related to not finding the required headers and/or libraries. -
-

Optionally build the ModSecurity Log Collector with: -

+; Note : This is step is still a bit experimental. If you have problems, please send the full output and error from the build to the support list. Most common issues are related to not finding the required headers and/or libraries. +Optionally build the ModSecurity Log Collector with: 
make mlogc
-

Optionally install mlogc: Review the INSTALL file included in the apache2/mlogc-src directory in the distribution. +Optionally install mlogc: Review the INSTALL file included in the apache2/mlogc-src directory in the distribution. Install the ModSecurity module with: -

make install
-

[edit] Windows (MS VC++ 8)

-

Edit Makefile.win to configure the Apache base and library paths. +=== Windows (MS VC++ 8) === +Edit Makefile.win to configure the Apache base and library paths. Compile with: nmake -f Makefile.win Install the ModSecurity module with: nmake -f Makefile.win install Copy the libxml2.dll and lua5.1.dll to the Apache bin directory. Alternatively you can follow the step below for using LoadFile to load these libraries. -

-
Note 
Users should follow the steps present in README_WINDOWS.txt into ModSecurity tarball. -
-

[edit] Edit the main Apache httpd config file (usually httpd.conf)

+; Note : Users should follow the steps present in README_WINDOWS.txt into ModSecurity tarball. -

On UNIX (and Windows if you did not copy the DLLs as stated above) you must load libxml2 and lua5.1 before ModSecurity with something like this: -

+=== Edit the main Apache httpd config file (usually httpd.conf) === +On UNIX (and Windows if you did not copy the DLLs as stated above) you must load libxml2 and lua5.1 before ModSecurity with something like this: 
 LoadFile /usr/lib/libxml2.so
 LoadFile /usr/lib/liblua5.1.so
-

Load the ModSecurity module with: -

+Load the ModSecurity module with: 
 LoadModule security2_module modules/mod_security2.so
-

[edit] Configure ModSecurity

+=== Configure ModSecurity === +=== Start Apache httpd === +You should now have ModSecurity 2.x up and running. -

[edit] Start Apache httpd

-

You should now have ModSecurity 2.x up and running. -

-
Note 
If you have compiled Apache yourself you might experience problems compiling ModSecurity against PCRE. This is because Apache bundles PCRE but this library is also typically provided by the operating system. I would expect most (all) vendor-packaged Apache distributions to be configured to use an external PCRE library (so this should not be a problem). -
-
You want to avoid Apache using the bundled PCRE library and ModSecurity linking against the one provided by the operating system. The easiest way to do this is to compile Apache against the PCRE library provided by the operating system (or you can compile it against the latest PCRE version you downloaded from the main PCRE distribution site). You can do this at configure time using the --with-pcre switch. If you are not in a position to recompile Apache, then, to compile ModSecurity successfully, you'd still need to have access to the bundled PCRE headers (they are available only in the Apache source code) and change the include path for ModSecurity (as you did in step 7 above) to point to them (via the --with-pcre ModSecurity configure option). +; Note : If you have compiled Apache yourself you might experience problems compiling ModSecurity against PCRE. This is because Apache bundles PCRE but this library is also typically provided by the operating system. I would expect most (all) vendor-packaged Apache distributions to be configured to use an external PCRE library (so this should not be a problem). -
-
Do note that if your Apache is using an external PCRE library you can compile ModSecurity with WITH_PCRE_STUDY defined,which would possibly give you a slight performance edge in regular expression processing. -
-
Non-gcc compilers may have problems running out-of-the-box as the current build system was designed around the gcc compiler and some compiler/linker flags may differ. To use a non-gcc compiler you may need some manual Makefile tweaks if issues cannot be solved by exporting custom CFLAGS and CPPFLAGS environment variables. -
-
If you are upgrading from ModSecurity 1.x, please refer to the migration matrix at http://www.modsecurity.org/documentation/ModSecurity-Migration-Matrix.pdf -
-
Starting with ModSecurity 2.7.0 there are a few important configuration options -
-
  1. --enable-pcre-jit - Enables JIT support from pcre >= 8.20 that can improve regex performance. +: You want to avoid Apache using the bundled PCRE library and ModSecurity linking against the one provided by the operating system. The easiest way to do this is to compile Apache against the PCRE library provided by the operating system (or you can compile it against the latest PCRE version you downloaded from the main PCRE distribution site). You can do this at configure time using the --with-pcre switch. If you are not in a position to recompile Apache, then, to compile ModSecurity successfully, you'd still need to have access to the bundled PCRE headers (they are available only in the Apache source code) and change the include path for ModSecurity (as you did in step 7 above) to point to them (via the --with-pcre ModSecurity configure option). -
  2. --enable-lua-cache - Enables lua vm caching that can improve lua script performance. Difference just appears if ModSecurity must run more than one script per transaction. -
  3. --enable-request-early - On ModSecuricy 2.6 phase one has been moved to phase 2 hook, if you want to play around it use this option. -
-

[edit] Installation for NGINX

-

The extensibility model of the nginx server does not include dynamically loaded modules, thus ModSecurity must be compiled with the source code of the main server. Since nginx is available on multiple Unix-based platforms (and also on Windows), for now the recommended way of obtaining ModSecurity for nginx is compilation in the designated environment. -

-

[edit] Manually Installing ModSecurity Module on NGINX

+: Do note that if your Apache is using an external PCRE library you can compile ModSecurity with WITH_PCRE_STUDY defined,which would possibly give you a slight performance edge in regular expression processing. -

The first step in obtaining nginx server with built-in ModSecurity module is building of standalone library containing full ModSecurity with a set of intermediate API (this layer is a common base for IIS version, nginx version, and server-less command line version of ModSecurity). It is recommended to follow the general steps of preparing build environment for ModSecurity and then follow with two simple commands -

-

[edit] Installation Steps

-

1 - Compile standalone module: -

+: Non-gcc compilers may have problems running out-of-the-box as the current build system was designed around the gcc compiler and some compiler/linker flags may differ. To use a non-gcc compiler you may need some manual Makefile tweaks if issues cannot be solved by exporting custom CFLAGS and CPPFLAGS environment variables. + +: If you are upgrading from ModSecurity 1.x, please refer to the migration matrix at http://www.modsecurity.org/documentation/ModSecurity-Migration-Matrix.pdf + +: Starting with ModSecurity 2.7.0 there are a few important configuration options +#'''--enable-pcre-jit''' - Enables JIT support from pcre >= 8.20 that can improve regex performance. +#'''--enable-lua-cache''' - Enables lua vm caching that can improve lua script performance. Difference just appears if ModSecurity must run more than one script per transaction. +#'''--enable-request-early''' - On ModSecuricy 2.6 phase one has been moved to phase 2 hook, if you want to play around it use this option. + += Installation for NGINX = +The extensibility model of the nginx server does not include dynamically loaded modules, thus ModSecurity must be compiled with the source code of the main server. Since nginx is available on multiple Unix-based platforms (and also on Windows), for now the recommended way of obtaining ModSecurity for nginx is compilation in the designated environment. +== Manually Installing ModSecurity Module on NGINX == +The first step in obtaining nginx server with built-in ModSecurity module is building of standalone library containing full ModSecurity with a set of intermediate API (this layer is a common base for IIS version, nginx version, and server-less command line version of ModSecurity). It is recommended to follow the general steps of preparing build environment for ModSecurity and then follow with two simple commands +=== Installation Steps === +1 - Compile standalone module: 
 ~/mod_security$ ./configure --enable-standalone-module
 ~/mod_security$ make
-

2 - Once the standalone library is built successfully, one can follow with building the nginx server, following the steps from the nginx build tutorial: -

-
 
+2 - Once the standalone library is built successfully, one can follow with building the nginx server, following the steps from the nginx build tutorial:
+
 ~/nginx-1.2.0$ ./configure --add-module=../mod_security/nginx/modsecurity
 ~/nginx-1.2.0$ make
 ~/nginx-1.2.0$ sudo make install
 

-
The last command performs server installation on the local machine, which can be either customized or omitted with built binaries packaged or moved to alternative server.
-

-
[edit]  Installation for Microsoft IIS 

-
The source code of ModSecurity’s IIS components is fully published and the binary building process is described (see mod_security/iis/winbuild/howto.txt). For quick installation it is highly recommended to use standard MSI installer available from SourceForge files repository of ModSecurity project or use binary package and follow the manual installation steps.
-

-
[edit]  Manually Installing and Troubleshooting Setup of ModSecurity Module on IIS 

-
-
[edit]  Prerequisites 

-
Before installing ModSecurity one has to install Visual Studio 2010 Runtime:
-

-
-
[edit]  Installation Steps 

-
-
Download binary package and unzip the content to a separate folder:
-

-
-
 The installation process of ModSecurity module on IIS consists of three parts:
-

-


-

-
1. Copying of binaries: copyfiles.bat
-
 The following binary files are required by ModSecurity module and by default should be copied to %windir%\system32\ (32-bit binaries) and/or %windir%\SysWOW64\ (64-bit binaries):
-

-
-
  • libapr-1.dll
-
  • libapriconv-1.dll
-
  • libaprutil-1.dll
-
  • libxml2.dll
-
  • lua5.1.dll
-
  • ModSecurityIIS.dll
-
  • pcre.dll
-
  • zlib1.dll
-

-
 The mlogc tool can be copied to any place, together with libcurl.dll:
-

-
  • libcurl.dll
-
  • mlogc.exe
-

-


-

-
-
2. Registering of the module: register.bat
-
 An IIS module must be properly registered before it can be used by web applications. The following command, executed in %windir%\system32\inetsrv, performs the registration:
-

+The last command performs server installation on the local machine, which can be either customized or omitted with built binaries packaged or moved to alternative server.
+= Installation for Microsoft IIS =
+The source code of ModSecurity’s IIS components is fully published and the binary building process is described (see mod_security/iis/winbuild/howto.txt). For quick installation it is highly recommended to use standard MSI installer available from SourceForge files repository of ModSecurity project or use binary package and follow the manual installation steps.
+== Manually Installing and Troubleshooting Setup of ModSecurity Module on IIS ==
+=== Prerequisites ===
+Before installing ModSecurity one has to install Visual Studio 2010 Runtime:
+*32-bit OS: http://www.microsoft.com/en-us/download/details.aspx?id=5555
+*64-bit OS: http://www.microsoft.com/en-us/download/details.aspx?id=14632
+=== Installation Steps ===
+Download binary package and unzip the content to a separate folder:
+*http://sourceforge.net/projects/mod-security/files/modsecurity-iis/2.7.0-rc2/ModSecurityIIS_2.7.0-rc2_debug.zip/download
+: The installation process of ModSecurity module on IIS consists of three parts:
+

+:'''1. Copying of binaries: copyfiles.bat'''
+: The following binary files are required by ModSecurity module and by default should be copied to %windir%\system32\ (32-bit binaries) and/or %windir%\SysWOW64\ (64-bit binaries):
+*libapr-1.dll
+*libapriconv-1.dll
+*libaprutil-1.dll
+*libxml2.dll
+*lua5.1.dll
+*ModSecurityIIS.dll
+*pcre.dll
+*zlib1.dll
+: The mlogc tool can be copied to any place, together with libcurl.dll:
+*libcurl.dll
+*mlogc.exe
+

+:'''2. Registering of the module: register.bat'''
+: An IIS module must be properly registered before it can be used by web applications. The following command, executed in %windir%\system32\inetsrv, performs the registration:
 
appcmd.exe install module /name:ModSecurityIIS /image:%windir%\system32\inetsrv\modsecurityiis.dll

-
 The registration process itself is described with details in the following articles:
-

-
-


-
-

-
3. Extending of the configuration schema.
-
 The last step extends IIS configuration schema with ModSecurity entities, using ModSecurity.xml file provided in the binary:
-

+: The registration process itself is described with details in the following articles:
+*http://technet.microsoft.com/en-us/library/cc771133(v=ws.10)
+*http://learn.iis.net/page.aspx/121/iis-modules-overview/
+

+:'''3. Extending of the configuration schema.'''
+: The last step extends IIS configuration schema with ModSecurity entities, using ModSecurity.xml file provided in the binary:
 
iisschema.exe /install ModSecurity.xml

-
 and iisschema.exe tool. More information about the tool and this step is available here:
-

-
-
[edit]  Configuration 

+: and iisschema.exe tool. More information about the tool and this step is available here:
+*http://mvolo.com/iisschemaexe-a-tool-to-register-iis7-configuration-sections
+=== Configuration ===
+: After the installation the module will be running in all websites by default. To remove it from a website add to web.config:
+

+    
+

+: To configure module in a website add to web.config:
+

+
+    
+        
+    
+

+: where configFile is standard ModSecurity config file.
+

+: Events from the module will show up in "Application" Windows log.
 
-
 After the installation the module will be running in all websites by default. To remove it from a website add to web.config:
-

-
<modules>
-    <remove name="ModSecurityIIS" />
-</modules>

-
 To configure module in a website add to web.config:
-

-
<?xml version="1.0" encoding="UTF-8"?>
+== Common Problems ==
 
-<configuration>
-    <system.webServer>
-        <ModSecurity enabled="true" configFile="c:\inetpub\wwwroot\xss.conf" />
-    </system.webServer>
+: If after installation protected website responds with HTTP 503 error and event ID 2280 keeps getting logged in the application event log:
 
-</configuration>

-
 where configFile is standard ModSecurity config file.
-

-


-

-
 Events from the module will show up in "Application" Windows log.
-

-
[edit]  Common Problems 

-
-
 If after installation protected website responds with HTTP 503 error and event ID 2280 keeps getting logged in the application event log:
-

 
 Log Name:      Application
 Source:        Microsoft-Windows-IIS-W3SVC-WP
@@ -946,57 +262,64 @@ User:          N/A
 Description:
 The Module DLL C:\Windows\system32\inetsrv\modsecurityiis.dll failed to load.  The data is the error.
 

-
most likely it means that the installation process has failed and the ModSecurityIIS.dll module is missing one or more libraries that it depends on. Repeating installation of the prerequisites and the module files should fix the problem. The dependency walker tool:
-

-
-
can be used to figure out which library is missing or cannot be loaded.
-

-
[edit]  Configuration Directives 

 
-
The following section outlines all of the ModSecurity directives. Most of the ModSecurity directives can be used inside the various Apache Scope Directives such as VirtualHost, Location, LocationMatch, Directory, etc... There are others, however, that can only be used once in the main configuration file. This information is specified in the Scope sections below. The first version to use a given directive is given in the Version sections below.
-
These rules, along with the Core rules files, should be contained is files outside of the httpd.conf file and called up with Apache "Include" directives. This allows for easier updating/migration of the rules. If you create your own custom rules that you would like to use with the Core rules, you should create a file called - modsecurity_crs_15_customrules.conf and place it in the same directory as the Core rules files. By using this file name, your custom rules will be called up after the standard ModSecurity Core rules configuration file but before the other Core rules. This allows your rules to be evaluated first which can be useful if you need to implement specific "allow" rules or to correct any false positives in the Core rules as they are applied to your site.
-

-
 Note 
 It is highly encouraged that you do not edit the Core rules files themselves but rather place all changes (such as SecRuleRemoveByID, etc...) in your custom rules file. This will allow for easier upgrading as newer Core rules are released by Breach Security on the ModSecurity website.
-

-
[edit]  SecAction 

-
Description: Unconditionally processes the action list it receives as the first and only parameter. The syntax of the parameter is identical to that of the third parameter of SecRule.
+most likely it means that the installation process has failed and the ModSecurityIIS.dll module is missing one or more libraries that it depends on. Repeating installation of the prerequisites and the module files should fix the problem. The dependency walker tool:
 
-
Syntax: SecAction "action1,action2,action3,...“
-
Scope: Any
-
Version: 2.0.0
-
This directive is commonly used to set variables and initialize persistent collections using the initcol action. For example:
-

+* http://www.dependencywalker.com/
+
+can be used to figure out which library is missing or cannot be loaded.
+
+= Configuration Directives =
+The following section outlines all of the ModSecurity directives. Most of the ModSecurity directives can be used inside the various Apache Scope Directives such as VirtualHost, Location, LocationMatch, Directory, etc... There are others, however, that can only be used once in the main configuration file. This information is specified in the Scope sections below. The first version to use a given directive is given in the Version sections below.
+
+These rules, along with the Core rules files, should be contained is files outside of the httpd.conf file and called up with Apache "Include" directives. This allows for easier updating/migration of the rules. If you create your own custom rules that you would like to use with the Core rules, you should create a file called - modsecurity_crs_15_customrules.conf and place it in the same directory as the Core rules files. By using this file name, your custom rules will be called up after the standard ModSecurity Core rules configuration file but before the other Core rules. This allows your rules to be evaluated first which can be useful if you need to implement specific "allow" rules or to correct any false positives in the Core rules as they are applied to your site.
+
+; Note : It is highly encouraged that you do not edit the Core rules files themselves but rather place all changes (such as SecRuleRemoveByID, etc...) in your custom rules file. This will allow for easier upgrading as newer Core rules are released by Breach Security on the ModSecurity website.
+== SecAction == 
+'''Description:''' Unconditionally processes the action list it receives as the first and only parameter. The syntax of the parameter is identical to that of the third parameter of SecRule.
+
+'''Syntax:''' SecAction "action1,action2,action3,...“
+
+'''Scope:''' Any
+
+'''Version:''' 2.0.0
+
+This directive is commonly used to set variables and initialize persistent collections using the initcol action. For example:
 
SecAction nolog,phase:1,initcol:RESOURCE=%{REQUEST_FILENAME}

-
[edit]  SecArgumentSeparator 

+== SecArgumentSeparator ==
+'''Description:''' Specifies which character to use as the separator for application/x-www-form- urlencoded content.
 
-
Description: Specifies which character to use as the separator for application/x-www-form- urlencoded content.
-
Syntax: SecArgumentSeparator character
-
Default: & 
-
Scope: Main(< 2.7.0), Any(2.7.0)
-
Version: 2.0.0
+'''Syntax:''' SecArgumentSeparator character
 
-
This directive is needed if a backend web application is using a nonstandard argument separator. Applications are sometimes (very rarely) written to use a semicolon separator. You should not change the default setting unless you establish that the application you are working with requires a different separator. If this directive is not set properly for each web application, then ModSecurity will not be able to parse the arguments appropriately and the effectiveness of the rule matching will be significantly decreased.
-

-
[edit]  SecAuditEngine 

-
Description: Configures the audit logging engine. 
-
Syntax: SecAuditEngine RelevantOnly 
-
Default: Off 
+'''Default:''' & 
 
-
Scope: Any
-
Version: 2.0.0
-
The SecAuditEngine directive is used to configure the audit engine, which logs complete transactions. ModSecurity is currently able to log most, but not all transactions. Transactions involving errors (e.g., 400 and 404 transactions) use a different execution path, which ModSecurity does not support.
-
The possible values for the audit log engine are as follows:
-

-
  • On: log all transactions
-
  • Off: do not log any transactions
-
  • RelevantOnly: only the log transactions that have triggered a warning or an error, or have a status code that is considered to be relevant (as determined by the SecAuditLogRelevantStatus directive)
-

-
 Note 
 If you need to change the audit log engine configuration on a per-transaction basis (e.g., in response to some transaction data), use the ctl action.
+'''Scope:''' Main(< 2.7.0), Any(2.7.0)
 
-

-
The following example demonstrates how SecAuditEngine is used:
-

+'''Version:''' 2.0.0
+
+This directive is needed if a backend web application is using a nonstandard argument separator. Applications are sometimes (very rarely) written to use a semicolon separator. You should not change the default setting unless you establish that the application you are working with requires a different separator. If this directive is not set properly for each web application, then ModSecurity will not be able to parse the arguments appropriately and the effectiveness of the rule matching will be significantly decreased.
+
+== SecAuditEngine ==
+'''Description:''' Configures the audit logging engine. 
+
+'''Syntax:''' SecAuditEngine RelevantOnly 
+
+'''Default:''' Off 
+
+'''Scope:''' Any
+
+'''Version:''' 2.0.0
+
+The SecAuditEngine directive is used to configure the audit engine, which logs complete transactions. ModSecurity is currently able to log most, but not all transactions. Transactions involving errors (e.g., 400 and 404 transactions) use a different execution path, which ModSecurity does not support.
+
+The possible values for the audit log engine are as follows:
+*'''On''': log all transactions
+*'''Off''': do not log any transactions
+*'''RelevantOnly''': only the log transactions that have triggered a warning or an error, or have a status code that is considered to be relevant (as determined by the SecAuditLogRelevantStatus directive)
+
+; Note : If you need to change the audit log engine configuration on a per-transaction basis (e.g., in response to some transaction data), use the ctl action.
+
+The following example demonstrates how SecAuditEngine is used:
 
 SecAuditEngine RelevantOnly
 SecAuditLog logs/audit/audit.log
@@ -1005,730 +328,914 @@ SecAuditLogType concurrent
 SecAuditLogStorageDir logs/audit 
 SecAuditLogRelevantStatus ^(?:5|4(?!04))
 

-
[edit]  SecAuditLog 

-
Description: Defines the path to the main audit log file (serial logging format) or the concurrent logging index file (concurrent logging format). When used in combination with mlogc (only possible with concurrent logging), this directive defines the mlogc location and command line.
-
Syntax: SecAuditLog /path/to/audit.log 
 
-
Scope: Any Version: 2.0.0
-
This file will be used to store the audit log entries if serial audit logging format is used. If concurrent audit logging format is used this file will be used as an index, and contain a record of all audit log files created. If you are planning to use concurrent audit logging to send your audit log data off to a remote server you will need to deploy the ModSecurity Log Collector (mlogc), like this:
-

+== SecAuditLog ==
+'''Description:''' Defines the path to the main audit log file (serial logging format) or the concurrent logging index file (concurrent logging format). When used in combination with mlogc (only possible with concurrent logging), this directive defines the mlogc location and command line.
+
+'''Syntax:''' SecAuditLog /path/to/audit.log 
+
+'''Scope:''' Any Version: 2.0.0
+
+This file will be used to store the audit log entries if serial audit logging format is used. If concurrent audit logging format is used this file will be used as an index, and contain a record of all audit log files created. If you are planning to use concurrent audit logging to send your audit log data off to a remote server you will need to deploy the ModSecurity Log Collector (mlogc), like this:
 
-SecAuditLog "|/path/to/mlogc /path/to/mlogc.conf"
+SecAuditLog "|/path/to/mlogc /path/to/mlogc.conf"
 

-
 Note 
 This audit log file is opened on startup when the server typically still runs as root. You should not allow non-root users to have write privileges for this file or for the directory.
-

-
[edit]  SecAuditLog2 

+; Note : This audit log file is opened on startup when the server typically still runs as root. You should not allow non-root users to have write privileges for this file or for the directory.
 
-
Description: Defines the path to the secondary audit log index file when concurrent logging is enabled. See SecAuditLog for more details.
-
Syntax: SecAuditLog2 /path/to/audit.log 
-
Scope: Any 
-
Version: 2.1.2
-
The purpose of SecAuditLog2 is to make logging to two remote servers possible, which is typically achieved by running two instances of the mlogc tool, each with a different configuration (in addition, one of the instances will need to be instructed not to delete the files it submits). This directive can be used only if SecAuditLog was previously configured and only if concurrent logging format is used.
-

-
[edit]  SecAuditLogDirMode

+== SecAuditLog2 ==
+'''Description:''' Defines the path to the secondary audit log index file when concurrent logging is enabled. See SecAuditLog for more details.
 
-
Description: Configures the mode (permissions) of any directories created for the concurrent audit logs, using an octal mode value as parameter (as used in chmod).
-
Syntax: SecAuditLogDirMode octal_mode|"default" 
-
Default: 0600 
-
Scope: Any 
-
Version: 2.5.10
-
The default mode for new audit log directories (0600) only grants read/write access to the owner (typically the account under which Apache is running, for example apache). If access from other accounts is needed (e.g., for use with mpm-itk), then you may use this directive to grant additional read and/or write privileges. You should use this directive with caution to avoid exposing potentially sensitive data to unauthorized users. Using the value default as parameter reverts the configuration back to the default setting. This feature is not available on operating systems not supporting octal file modes.
+'''Syntax:''' SecAuditLog2 /path/to/audit.log 
 
-
Example:
-

+'''Scope:''' Any 
+
+'''Version:''' 2.1.2
+
+The purpose of SecAuditLog2 is to make logging to two remote servers possible, which is typically achieved by running two instances of the mlogc tool, each with a different configuration (in addition, one of the instances will need to be instructed not to delete the files it submits). This directive can be used only if SecAuditLog was previously configured and only if concurrent logging format is used.
+
+== SecAuditLogDirMode==
+'''Description:''' Configures the mode (permissions) of any directories created for the concurrent audit logs, using an octal mode value as parameter (as used in chmod).
+
+'''Syntax:''' SecAuditLogDirMode octal_mode|"default" 
+
+'''Default:''' 0600 
+
+'''Scope:''' Any 
+
+'''Version:''' 2.5.10
+
+The default mode for new audit log directories (0600) only grants read/write access to the owner (typically the account under which Apache is running, for example apache). If access from other accounts is needed (e.g., for use with mpm-itk), then you may use this directive to grant additional read and/or write privileges. You should use this directive with caution to avoid exposing potentially sensitive data to unauthorized users. Using the value default as parameter reverts the configuration back to the default setting. This feature is not available on operating systems not supporting octal file modes.
+
+Example:
 
SecAuditLogDirMode 02750

-
 Note 
 The process umask may still limit the mode if it is being more restrictive than the mode set using this directive.
-

-
[edit]  SecAuditLogFileMode 

-
Description: Configures the mode (permissions) of any files created for concurrent audit logs using an octal mode (as used in chmod). See SecAuditLogDirMode for controlling the mode of created audit log directories.
+; Note : The process umask may still limit the mode if it is being more restrictive than the mode set using this directive.
 
-
Syntax: SecAuditLogFileMode octal_mode|"default" 
-
Default: 0600
-
Scope: Any 
-
Version: 2.5.10
-
Example Usage: SecAuditLogFileMode 00640 
+== SecAuditLogFileMode ==
+'''Description:''' Configures the mode (permissions) of any files created for concurrent audit logs using an octal mode (as used in chmod). See SecAuditLogDirMode for controlling the mode of created audit log directories.
 
-
This feature is not available on operating systems not supporting octal file modes. The default mode (0600) only grants read/write access to the account writing the file. If access from another account is needed (using mpm-itk is a good example), then this directive may be required. However, use this directive with caution to avoid exposing potentially sensitive data to unauthorized users. Using the value “default” will revert back to the default setting.
-

-
 Note 
 The process umask may still limit the mode if it is being more restrictive than the mode set using this directive.
-

-
[edit]  SecAuditLogParts 

-
Description: Defines which parts of each transaction are going to be recorded in the audit log. Each part is assigned a single letter; when a letter appears in the list then the equivalent part will be recorded. See below for the list of all parts.
+'''Syntax:''' SecAuditLogFileMode octal_mode|"default" 
 
-
Syntax: SecAuditLogParts PARTLETTERS
-
Example Usage: SecAuditLogParts ABCFHZ 
-
Scope: Any Version: 2.0.0
-
Default: ABCFHZ Note
-
The format of the audit log format is documented in detail in the Audit Log Data Format Documentation.
-
Available audit log parts:
-

+'''Default:''' 0600
 
-
  • A: Audit log header (mandatory).
-
  • B: Request headers.
-
  • C: Request body (present only if the request body exists and ModSecurity is configured to intercept it).
-
  • D: Reserved for intermediary response headers; not implemented yet.
-
  • E: Intermediary response body (present only if ModSecurity is configured to intercept response bodies, and if the audit log engine is configured to record it). Intermediary response body is the same as the actual response body unless ModSecurity intercepts the intermediary response body, in which case the actual response body will contain the error message (either the Apache default error message, or the ErrorDocument page).
-
  • F: Final response headers (excluding the Date and Server headers, which are always added by Apache in the late stage of content delivery).
-
  • G: Reserved for the actual response body; not implemented yet.
-
  • H: Audit log trailer.
-
  • I: This part is a replacement for part C. It will log the same data as C in all cases except when multipart/form-data encoding in used. In this case, it will log a fake application/x-www-form-urlencoded body that contains the information about parameters but not about the files. This is handy if you don’t want to have (often large) files stored in your audit logs.
-
  • J: This part contains information about the files uploaded using multipart/form-data encoding.
-
  • K: This part contains a full list of every rule that matched (one per line) in the order they were matched. The rules are fully qualified and will thus show inherited actions and default operators. Supported as of v2.5.0.
-
  • Z: Final boundary, signifies the end of the entry (mandatory).
-

-
[edit]  SecAuditLogRelevantStatus 

+'''Scope:''' Any 
 
-
Description: Configures which response status code is to be considered relevant for the purpose of audit logging.
-
Syntax: SecAuditLogRelevantStatus REGEX 
-
Example Usage: SecAuditLogRelevantStatus "^(?:5|4(?!04))" 
-
Scope: Any 
-
Version: 2.0.0
+'''Version:''' 2.5.10
 
-
Dependencies/Notes: Must have SecAuditEngine set to RelevantOnly. 
-
The main purpose of this directive is to allow you to configure audit logging for only the transactions that have the status code that matches the supplied regular expression. The example provided would log all 5xx and 4xx level status codes, except for 404s. Although you could achieve the same effect with a rule in phase 5, SecAuditLogRelevantStatus is sometimes better, because it continues to work even when SecRuleEngine is disabled.
-

-
[edit]  SecAuditLogStorageDir 

-
Description: Configures the directory where concurrent audit log entries are to be stored. 
-
Syntax: SecAuditLogStorageDir /path/to/storage/dir
+'''Example Usage:''' SecAuditLogFileMode 00640 
 
-
Example Usage: SecAuditLogStorageDir /usr/local/apache/logs/audit 
-
Scope: Any
-
Version: 2.0.0
-
This directive is only needed when concurrent audit logging is used. The directory must already exist and must be writable by the web server user. Audit log entries are created at runtime, after Apache switches to a non-root account.
+This feature is not available on operating systems not supporting octal file modes. The default mode (0600) only grants read/write access to the account writing the file. If access from another account is needed (using mpm-itk is a good example), then this directive may be required. However, use this directive with caution to avoid exposing potentially sensitive data to unauthorized users. Using the value “default” will revert back to the default setting.
+
+; Note : The process umask may still limit the mode if it is being more restrictive than the mode set using this directive.
+
+== SecAuditLogParts ==
+'''Description:''' Defines which parts of each transaction are going to be recorded in the audit log. Each part is assigned a single letter; when a letter appears in the list then the equivalent part will be recorded. See below for the list of all parts.
+
+'''Syntax:''' SecAuditLogParts PARTLETTERS
+
+'''Example Usage:''' SecAuditLogParts ABCFHZ 
+
+'''Scope:''' Any Version: 2.0.0
+
+'''Default:''' ABCFHZ Note
+
+The format of the audit log format is documented in detail in the Audit Log Data Format Documentation.
+
+Available audit log parts:
+*A: Audit log header (mandatory).
+*B: Request headers.
+*C: Request body (present only if the request body exists and ModSecurity is configured to intercept it).
+*D: Reserved for intermediary response headers; not implemented yet.
+*E: Intermediary response body (present only if ModSecurity is configured to intercept response bodies, and if the audit log engine is configured to record it). Intermediary response body is the same as the actual response body unless ModSecurity intercepts the intermediary response body, in which case the actual response body will contain the error message (either the Apache default error message, or the ErrorDocument page).
+*F: Final response headers (excluding the Date and Server headers, which are always added by Apache in the late stage of content delivery).
+*G: Reserved for the actual response body; not implemented yet.
+*H: Audit log trailer.
+*I: This part is a replacement for part C. It will log the same data as C in all cases except when multipart/form-data encoding in used. In this case, it will log a fake application/x-www-form-urlencoded body that contains the information about parameters but not about the files. This is handy if you don’t want to have (often large) files stored in your audit logs.
+*J: This part contains information about the files uploaded using multipart/form-data encoding.
+*K: This part contains a full list of every rule that matched (one per line) in the order they were matched. The rules are fully qualified and will thus show inherited actions and default operators. Supported as of v2.5.0.
+*Z: Final boundary, signifies the end of the entry (mandatory).
+
+== SecAuditLogRelevantStatus ==
+'''Description:''' Configures which response status code is to be considered relevant for the purpose of audit logging.
+
+'''Syntax:''' SecAuditLogRelevantStatus REGEX 
+
+'''Example Usage:''' SecAuditLogRelevantStatus "^(?:5|4(?!04))" 
+
+'''Scope:''' Any 
+
+'''Version:''' 2.0.0
+
+'''Dependencies/Notes:''' Must have SecAuditEngine set to RelevantOnly. 
+
+The main purpose of this directive is to allow you to configure audit logging for only the transactions that have the status code that matches the supplied regular expression. The example provided would log all 5xx and 4xx level status codes, except for 404s. Although you could achieve the same effect with a rule in phase 5, SecAuditLogRelevantStatus is sometimes better, because it continues to work even when SecRuleEngine is disabled.
+
+== SecAuditLogStorageDir ==
+'''Description:''' Configures the directory where concurrent audit log entries are to be stored. 
+
+'''Syntax''': SecAuditLogStorageDir /path/to/storage/dir
+
+'''Example Usage:''' SecAuditLogStorageDir /usr/local/apache/logs/audit 
+
+'''Scope:''' Any
+
+'''Version:''' 2.0.0
+
+This directive is only needed when concurrent audit logging is used. The directory must already exist and must be writable by the web server user. Audit log entries are created at runtime, after Apache switches to a non-root account.
 As with all logging mechanisms, ensure that you specify a file system location that has adequate disk space and is not on the main system partition.
-

-
[edit]  SecAuditLogType 

 
-
Description: Configures the type of audit logging mechanism to be used. 
-
Syntax: SecAuditLogType Serial|Concurrent 
-
Example Usage: SecAuditLogType Serial
-
Scope: Any
-
Version: 2.0.0 
+== SecAuditLogType ==
+'''Description:''' Configures the type of audit logging mechanism to be used. 
 
-
The possible values are:
-

-
 Serial 
 Audit log entries will be stored in a single file, specified by SecAuditLog. This is conve- nient for casual use, but it can slow down the server, because only one audit log entry can be written to the file at any one time.
-
 Concurrent 
 One file per transaction is used for audit logging. This approach is more scalable when heavy logging is required (multiple transactions can be recorded in parallel). It is also the only choice if you need to use remote logging.
-

-
[edit]  SecCacheTransformations 

+'''Syntax:''' SecAuditLogType Serial|Concurrent 
 
-
Description: Controls the caching of transformations, which may speed up the processing of complex rule sets. Caching is off by default starting with 2.5.6, when it was deprecated and downgraded back to experimental.
-
Syntax: SecCacheTransformations On|Off [options] 
-
Example Usage: SecCacheTransformations On "minlen:64,maxlen:0" 
-
Scope: Any 
-
Version: 2.5.0; deprecated in 2.5.6. 
+'''Example Usage:''' SecAuditLogType Serial
 
-
The first directive parameter can be one of the following:
-

-
  • On: Cache transformations (per transaction, per phase) allowing identical transforma- tions to be performed only once.
-
  • Off: Do not cache any transformations, leaving all transformations to be performed every time they are needed.
-

-
The following options are allowed (multiple options must be comma-separated): 
-

-
  • incremental:on|off: Enabling this option will cache every transformation instead of just the final transformation. The default is off.
-
  • maxitems:N: Do not allow more than N transformations to be cached. Cache will be disabled once this number is reached. A zero value is interpreted as unlimited. This option may be useful to limit caching for a form with a large number of variables. The default value is 512.
-
  • minlen:N: Do not cache the transformation if the variable’s length is less than N bytes. The default setting is 32.
-
  • maxlen:N: Do not cache the transformation if the variable’s length is more than N bytes. A zero value is interpreted as unlimited. The default setting is 1024.
+'''Scope:''' Any
 
-

-
[edit]  SecChrootDir 

-
Description: Configures the directory path that will be used to jail the web server process. 
-
Syntax: SecChrootDir /path/to/chroot/dir 
-
Example Usage: SecChrootDir /chroot 
+'''Version:''' 2.0.0 
 
-
Scope: Main
-
Version: 2.0.0
-
This feature is not available on Windows builds. The internal chroot functionality provided by ModSecurity works great for simple setups. One example of a simple setup is Apache serving only static files, or running applications using built-in modules. Some problems you might encounter with more complex setups:
-

-
  1. DNS lookups do not work (this is because this feature requires a shared library that is loaded on demand, after chroot takes place).
-
  2. You cannot send email from PHP, because it wants to use sendmail and sendmail re- sides outside the jail.
-
  3. In some cases, when you separate Apache from its configuration, restarts and graceful reloads no longer work.
-

-
The best way to use SecChrootDir is the following: 
-

-
  1. Create /chroot to be your main jail directory.
-
  2. Create /chroot/opt/apache inside jail.
-
  3. Create a symlink from /opt/apache to /chroot/opt/apache. 
+The possible values are:
+; Serial : Audit log entries will be stored in a single file, specified by SecAuditLog. This is conve- nient for casual use, but it can slow down the server, because only one audit log entry can be written to the file at any one time.
+; Concurrent : One file per transaction is used for audit logging. This approach is more scalable when heavy logging is required (multiple transactions can be recorded in parallel). It is also the only choice if you need to use remote logging.
 
-
  4. Now install Apache into /chroot/opt/apache.
-

-
You should be aware that the internal chroot feature might not be 100% reliable. Due to the large number of default and third-party modules available for the Apache web server, it is not possible to verify the internal chroot works reliably with all of them. A module, working from within Apache, can do things that make it easy to break out of the jail. In particular, if you are using any of the modules that fork in the module initialisation phase (e.g., mod_fastcgi, mod_fcgid, mod_cgid), you are advised to examine each Apache process and observe its current working directory, process root, and the list of open files. Consider what your options are and make your own decision.
-

-
[edit]  SecComponentSignature 

-
Description: Appends component signature to the ModSecurity signature. 
-
Syntax: SecComponentSignature "COMPONENT_NAME/X.Y.Z (COMMENT)" 
+== SecCacheTransformations ==
+'''Description:''' Controls the caching of transformations, which may speed up the processing of complex rule sets. Caching is off by default starting with 2.5.6, when it was deprecated and downgraded back to experimental.
 
-
Example usage: SecComponentSignature "core ruleset/2.1.3"
-
Scope: Main 
-
Version: 2.5.0
-
This directive should be used to make the presence of significant rule sets known. The entire signature will be recorded in the transaction audit log.
-

-
[edit]  SecContentInjection 

+'''Syntax:''' SecCacheTransformations On|Off [options] 
 
-
Description: Enables content injection using actions append and prepend. 
-
Syntax: SecContentInjection On|Off 
-
Example Usage: SecContentInjection On 
-
Scope: Any
-
Version: 2.5.0
+'''Example Usage:''' SecCacheTransformations On "minlen:64,maxlen:0" 
 
-
This directive provides an easy way to control content injection, no matter what the rules want to do. It is not necessary to have response body buffering enabled in order to use content injection.
-

-
 Note 
 This directive must ben enabled if you want to use @rsub + the STREAM_ variables to manipulate live transactional data.
-

-
[edit]  SecCookieFormat 

-
Description: Selects the cookie format that will be used in the current configuration context. 
+'''Scope:''' Any 
 
-
Syntax: SecCookieFormat 0|1 
-
Example Usage: SecCookieFormat 0 
-
Scope: Any
-
Version: 2.0.0 
-
The possible values are:
-

-
  • 0: Use version 0 (Netscape) cookies. This is what most applications use. It is the default value.
+'''Version:''' 2.5.0; deprecated in 2.5.6. 
 
-
  • 1: Use version 1 cookies.
-

-
[edit]  SecDataDir 

-
Description: Path where persistent data (e.g., IP address data, session data, and so on) is to be stored.
-
Syntax: SecDataDir /path/to/dir 
+The first directive parameter can be one of the following:
+*'''On''': Cache transformations (per transaction, per phase) allowing identical transforma- tions to be performed only once.
+*'''Off''': Do not cache any transformations, leaving all transformations to be performed every time they are needed.
 
-
Example Usage: SecDataDir /usr/local/apache/logs/data 
-
Scope: Main
-
Version: 2.0.0
-
This directive must be provided before initcol, setsid, and setuid can be used. The directory to which the directive points must be writable by the web server user.
-

-
[edit]  SecDebugLog 

+The following options are allowed (multiple options must be comma-separated): 
+*'''incremental:on|off''': Enabling this option will cache every transformation instead of just the final transformation. The default is off.
+*'''maxitems:N''': Do not allow more than N transformations to be cached. Cache will be disabled once this number is reached. A zero value is interpreted as unlimited. This option may be useful to limit caching for a form with a large number of variables. The default value is 512.
+*'''minlen:N''': Do not cache the transformation if the variable’s length is less than N bytes. The default setting is 32.
+*'''maxlen:N''': Do not cache the transformation if the variable’s length is more than N bytes. A zero value is interpreted as unlimited. The default setting is 1024.
 
-
Description: Path to the ModSecurity debug log file. 
-
Syntax: SecDebugLog /path/to/modsec-debug.log 
-
Example Usage: SecDebugLog /usr/local/apache/logs/modsec-debug.log 
-
Scope: Any 
-
Version: 2.0.0
-

+== SecChrootDir ==
+'''Description:''' Configures the directory path that will be used to jail the web server process. 
 
-
[edit]  SecDebugLogLevel 

-
Description: Configures the verboseness of the debug log data. 
-
Syntax: SecDebugLogLevel 0|1|2|3|4|5|6|7|8|9
-
Example Usage: SecDebugLogLevel 4 
+'''Syntax:''' SecChrootDir /path/to/chroot/dir 
 
-
Scope: Any
-
Version: 2.0.0
-
Messages at levels 1–3 are always copied to the Apache error log. Therefore you can always use level 0 as the default logging level in production if you are very concerned with performance. Having said that, the best value to use is 3. Higher logging levels are not recommended in production, because the heavy logging affects performance adversely.
-
The possible values for the debug log level are: 
-

-
  • 0: no logging 
-
  • 1: errors (intercepted requests) only 
-
  • 2: warnings
-
  • 3: notices 
-
  • 4: details of how transactions are handled 
-
  • 5: as above, but including information about each piece of information handled 
-
  • 9: log everything, including very detailed debugging information
-

+'''Example Usage:''' SecChrootDir /chroot 
 
-
[edit]  SecDefaultAction 

-
Description: Defines the default list of actions, which will be inherited by the rules in the same configuration context.
-
Syntax: SecDefaultAction "action1,action2,action3“ 
-
Example Usage: SecDefaultAction "phase:2,log,auditlog,deny,status:403“ 
+'''Scope:''' Main
 
-
Scope: Any 
-
Version: 2.0.0 
-
Default: phase:2,log,auditlog,pass
-
Every rule following a previous SecDefaultAction directive in the same configuration context will inherit its settings unless more specific actions are used. Every SecDefaultAction directive must specify a disruptive action and a processing phase and cannot contain metadata actions.
-

+'''Version:''' 2.0.0
 
-
 Warning 
 SecDefaultAction is not inherited across configuration contexts. (For an example of why this may be a problem, read the following ModSecurity Blog entry http://blog.spiderlabs.com/2008/07/three-modsecurity-rule-language-annoyances.html.)
-

-
[edit]  SecDisableBackendCompression 

-
Description: Disables backend compression while leaving the frontend compression enabled. 
+This feature is not available on Windows builds. The internal chroot functionality provided by ModSecurity works great for simple setups. One example of a simple setup is Apache serving only static files, or running applications using built-in modules. Some problems you might encounter with more complex setups:
+#DNS lookups do not work (this is because this feature requires a shared library that is loaded on demand, after chroot takes place).
+#You cannot send email from PHP, because it wants to use sendmail and sendmail re- sides outside the jail.
+#In some cases, when you separate Apache from its configuration, restarts and graceful reloads no longer work.
 
-
Syntax: SecDisableBackendCompression On|Off 
-
Scope: Any 
-
Version: 2.6.0 
-
Default: Off
-
This directive is necessary in reverse proxy mode when the backend servers support response compression, but you wish to inspect response bodies. Unless you disable backend compression, ModSecurity will only see compressed content, which is not very useful. This directive is not necessary in embedded mode, because ModSecurity performs inspection before response compression takes place.
-

-
[edit]  SecEncryptionEngine 

+The best way to use SecChrootDir is the following: 
+#Create /chroot to be your main jail directory.
+#Create /chroot/opt/apache inside jail.
+#Create a symlink from /opt/apache to /chroot/opt/apache. 
+#Now install Apache into /chroot/opt/apache.
 
-
Description: Configures the encryption engine. 
-
Syntax: SecEncryptionEngine On|Off
-
Example Usage: SecEncryptionEngine On 
-
Scope: Any 
-
Version: 2.7
-
Default: Off
+You should be aware that the internal chroot feature might not be 100% reliable. Due to the large number of default and third-party modules available for the Apache web server, it is not possible to verify the internal chroot works reliably with all of them. A module, working from within Apache, can do things that make it easy to break out of the jail. In particular, if you are using any of the modules that fork in the module initialisation phase (e.g., mod_fastcgi, mod_fcgid, mod_cgid), you are advised to examine each Apache process and observe its current working directory, process root, and the list of open files. Consider what your options are and make your own decision.
 
-
The possible values are: 
-

-
  • On: Encryption engine can process the request/response data.
-
  • Off: Encryption engine will not process any data. 
-

-
 Note 
 Users must enable stream output variables and content injection.
-

-
[edit]  SecEncryptionKey 

+== SecComponentSignature ==
+'''Description:''' Appends component signature to the ModSecurity signature. 
 
-
Description: Define the key that will be used by HMAC. 
-
Syntax: SecEncryptionKey rand|TEXT KeyOnly|SessionID|RemoteIP
-
Example Usage: SecEncryptionKey "this_is_my_key" KeyOnly
-
Scope: Any 
-
Version: 2.7
-
ModSecurity encryption engine will append, if specified, the user's session id or remote ip to the key before the MAC operation. If the first parameter is "rand" then a random key will be generated and used by the engine.
+'''Syntax:''' SecComponentSignature "COMPONENT_NAME/X.Y.Z (COMMENT)" 
 
-


-

-
[edit]  SecEncryptionParam 

-
Description: Define the parameter name that will receive the MAC hash. 
-
Syntax: SecEncryptionParam TEXT
-
Example Usage: SecEncryptionKey "hmac"
+'''Example usage''': SecComponentSignature "core ruleset/2.1.3"
 
-
Scope: Any 
-
Version: 2.7
-
ModSecurity encryption engine will add a new parameter to protected HTML elements containing the MAC hash.
-

-
[edit]  SecEncryptionMethodRx 

-
Description: Configures what kind of HTML data the encryption engine should sign based on regular expression.
+'''Scope:''' Main 
 
-
Syntax: SecEncryptionMethodRx TYPE REGEX 
-
Example Usage: SecEncryptionMethodRx HashHref "product_info|list_product"
-
Scope: Any
-
Version: 2.7.0
-
As a initial support is possible to protect HREF, FRAME, IFRAME and FORM ACTION html elements as well response Location header when http redirect code are sent.
-
The possible values for TYPE are:
-

+'''Version:''' 2.5.0
 
-
  • HashHref: Used to sign href= html elements
-
  • HashFormAction: Used to sign form action= html elements
-
  • HashIframeSrc: Used to sign iframe src= html elements
-
  • HashframeSrc: Used to sign frame src= html elements 
-
  • HashLocation: Used to sign Location response header
-

-
 Note 
 This directive is used to sign the elements however user must use the @validateEncryption operator to enforce data integrity.
-

-


+This directive should be used to make the presence of significant rule sets known. The entire signature will be recorded in the transaction audit log.
 
-

-
[edit]  SecEncryptionMethodPm 

-
Description: Configures what kind of HTML data the encryption engine should sign based on string search algoritm.
-
Syntax: SecEncryptionMethodRx TYPE "string1 string2 string3..." 
-
Example Usage: SecEncryptionMethodRx HashHref "product_info list_product"
+== SecContentInjection ==
+'''Description:''' Enables content injection using actions append and prepend. 
 
-
Scope: Any
-
Version: 2.7.0
-
As a initial support is possible to protect HREF, FRAME, IFRAME and FORM ACTION html elements as well response Location header when http redirect code are sent.
-
The possible values for TYPE are:
-

-
  • HashHref: Used to sign href= html elements
-
  • HashFormAction: Used to sign form action= html elements
-
  • HashIframeSrc: Used to sign iframe src= html elements
-
  • HashframeSrc: Used to sign frame src= html elements 
+'''Syntax:''' SecContentInjection On|Off 
 
-
  • HashLocation: Used to sign Location response header
-

-
 Note 
 This directive is used to sign the elements however user must use the @validateEncryption operator to enforce data integrity.
-

-
[edit]  SecGeoLookupDb 

-
Description: Defines the path to the database that will be used for geolocation lookups. 
+'''Example Usage:''' SecContentInjection On 
 
-
Syntax: SecGeoLookupDb /path/to/db 
-
Example Usage: SecGeoLookupDb /path/to/GeoLiteCity.dat
-
Scope: Any
-
Version: 2.5.0 
-
ModSecurity relies on the free geolocation databases (GeoLite City and GeoLite Country) that can be obtained from MaxMind [2].
+'''Scope:''' Any
 
-

-
[edit]  SecGsbLookupDb 

-
Description: Defines the path to the database that will be used for Google Safe Browsing (GSB) lookups. 
-
Syntax: SecGsbLookupDb /path/to/db 
-
Example Usage: SecGsbLookupDb /path/to/GsbMalware.dat
+'''Version:''' 2.5.0
 
-
Scope: Any
-
Version: 2.6.0 
-
ModSecurity relies on the free Google Safe Browsing database that can be obtained from the Google GSB API [3].
-

-
 Note 
 Deprecated in 2.7.0 after Google dev team decided to not allow the database download anymore. After registering and obtaining a Safe Browsing API key, you can automatically download the GSB using a tool like wget (where KEY is your own API key):
+This directive provides an easy way to control content injection, no matter what the rules want to do. It is not necessary to have response body buffering enabled in order to use content injection.
 
-

-
wget http://sb.google.com/safebrowsing/update?client=api&apikey=KEY&version=goog-malware-hash:1:-1
-

-
[edit]  SecGuardianLog 

-
Description: Configures an external program that will receive the information about every transaction via piped logging.
+; Note : This directive must ben enabled if you want to use @rsub + the STREAM_ variables to manipulate live transactional data.
 
-
Syntax: SecGuardianLog |/path/to/httpd-guardian 
-
Example Usage: SecGuardianLog |/usr/local/apache/bin/httpd-guardian 
-
Scope: Main 
-
Version: 2.0.0
-
Guardian logging is designed to send the information about every request to an external program. Because Apache is typically deployed in a multiprocess fashion, which makes information sharing between processes difficult, the idea is to deploy a single external process to observe all requests in a stateful manner, providing additional protection.
-
Currently the only tool known to work with guardian logging is httpd-guardian, which is part of the Apache httpd tools project [4]. The httpd-guardian tool is designed to defend against denial of service attacks. It uses the blacklist tool (from the same project) to interact with an iptables-based (on a Linux system) or pf-based (on a BSD system) firewall, dynamically blacklisting the offending IP addresses. It can also interact with SnortSam [5]. Assuming httpd-guardian is already configured (look into the source code for the detailed instructions), you only need to add one line to your Apache configuration to deploy it:
+== SecCookieFormat ==
+'''Description:''' Selects the cookie format that will be used in the current configuration context. 
 
-

+'''Syntax:''' SecCookieFormat 0|1 
+
+'''Example Usage:''' SecCookieFormat 0 
+
+'''Scope:''' Any
+
+'''Version:''' 2.0.0 
+
+The possible values are:
+*'''0''': Use version 0 (Netscape) cookies. This is what most applications use. It is the default value.
+*'''1''': Use version 1 cookies.
+
+== SecDataDir ==
+'''Description:''' Path where persistent data (e.g., IP address data, session data, and so on) is to be stored.
+
+'''Syntax:''' SecDataDir /path/to/dir 
+
+'''Example Usage:''' SecDataDir /usr/local/apache/logs/data 
+
+'''Scope:''' Main
+
+'''Version:''' 2.0.0
+
+This directive must be provided before initcol, setsid, and setuid can be used. The directory to which the directive points must be writable by the web server user.
+
+== SecDebugLog ==
+'''Description''': Path to the ModSecurity debug log file. 
+
+'''Syntax:''' SecDebugLog /path/to/modsec-debug.log 
+
+'''Example Usage:''' SecDebugLog /usr/local/apache/logs/modsec-debug.log 
+
+'''Scope:''' Any 
+
+'''Version:''' 2.0.0
+
+== SecDebugLogLevel ==
+'''Description:''' Configures the verboseness of the debug log data. 
+
+'''Syntax''': SecDebugLogLevel 0|1|2|3|4|5|6|7|8|9
+
+'''Example Usage:''' SecDebugLogLevel 4 
+
+'''Scope:''' Any
+
+'''Version:''' 2.0.0
+
+Messages at levels 1–3 are always copied to the Apache error log. Therefore you can always use level 0 as the default logging level in production if you are very concerned with performance. Having said that, the best value to use is 3. Higher logging levels are not recommended in production, because the heavy logging affects performance adversely.
+
+The possible values for the debug log level are: 
+*0: no logging 
+*1: errors (intercepted requests) only 
+*2: warnings
+*3: notices 
+*4: details of how transactions are handled 
+*5: as above, but including information about each piece of information handled 
+*9: log everything, including very detailed debugging information
+
+== SecDefaultAction ==
+'''Description''': Defines the default list of actions, which will be inherited by the rules in the same configuration context.
+
+'''Syntax:''' SecDefaultAction "action1,action2,action3“ 
+
+'''Example Usage:''' SecDefaultAction "phase:2,log,auditlog,deny,status:403“ 
+
+'''Scope:''' Any 
+
+'''Version:''' 2.0.0 
+
+'''Default:''' phase:2,log,auditlog,pass
+
+Every rule following a previous SecDefaultAction directive in the same configuration context will inherit its settings unless more specific actions are used. Every SecDefaultAction directive must specify a disruptive action and a processing phase and cannot contain metadata actions.
+
+; Warning : SecDefaultAction is not inherited across configuration contexts. (For an example of why this may be a problem, read the following ModSecurity Blog entry http://blog.spiderlabs.com/2008/07/three-modsecurity-rule-language-annoyances.html.)
+
+== SecDisableBackendCompression ==
+'''Description:''' Disables backend compression while leaving the frontend compression enabled. 
+
+'''Syntax:''' SecDisableBackendCompression On|Off 
+
+'''Scope:''' Any 
+
+'''Version:''' 2.6.0 
+
+'''Default:''' Off
+
+This directive is necessary in reverse proxy mode when the backend servers support response compression, but you wish to inspect response bodies. Unless you disable backend compression, ModSecurity will only see compressed content, which is not very useful. This directive is not necessary in embedded mode, because ModSecurity performs inspection before response compression takes place.
+
+== SecEncryptionEngine ==
+'''Description:''' Configures the encryption engine. 
+
+'''Syntax:''' SecEncryptionEngine On|Off
+
+'''Example Usage:''' SecEncryptionEngine On 
+
+'''Scope''': Any 
+
+'''Version:''' 2.7
+
+'''Default:''' Off
+
+The possible values are: 
+*'''On''': Encryption engine can process the request/response data.
+*'''Off''': Encryption engine will not process any data. 
+
+; Note : Users must enable stream output variables and content injection.
+
+== SecEncryptionKey ==
+'''Description:''' Define the key that will be used by HMAC. 
+
+'''Syntax:''' SecEncryptionKey rand|TEXT KeyOnly|SessionID|RemoteIP
+
+'''Example Usage:''' SecEncryptionKey "this_is_my_key" KeyOnly
+
+'''Scope''': Any 
+
+'''Version:''' 2.7
+
+ModSecurity encryption engine will append, if specified, the user's session id or remote ip to the key before the MAC operation. If the first parameter is "rand" then a random key will be generated and used by the engine.
+
+
+== SecEncryptionParam ==
+'''Description:''' Define the parameter name that will receive the MAC hash. 
+
+'''Syntax:''' SecEncryptionParam TEXT
+
+'''Example Usage:''' SecEncryptionKey "hmac"
+
+'''Scope''': Any 
+
+'''Version:''' 2.7
+
+ModSecurity encryption engine will add a new parameter to protected HTML elements containing the MAC hash.
+
+== SecEncryptionMethodRx ==
+'''Description:''' Configures what kind of HTML data the encryption engine should sign based on regular expression.
+
+'''Syntax:''' SecEncryptionMethodRx TYPE REGEX 
+
+'''Example Usage''': SecEncryptionMethodRx HashHref "product_info|list_product"
+
+'''Scope:''' Any
+
+'''Version:''' 2.7.0
+
+As a initial support is possible to protect HREF, FRAME, IFRAME and FORM ACTION html elements as well response Location header when http redirect code are sent.
+
+The possible values for TYPE are:
+*'''HashHref''': Used to sign href= html elements
+*'''HashFormAction''': Used to sign form action= html elements
+*'''HashIframeSrc''': Used to sign iframe src= html elements
+*'''HashframeSrc''': Used to sign frame src= html elements 
+*'''HashLocation''': Used to sign Location response header
+
+; Note : This directive is used to sign the elements however user must use the @validateEncryption operator to enforce data integrity.
+
+
+== SecEncryptionMethodPm ==
+'''Description:''' Configures what kind of HTML data the encryption engine should sign based on string search algoritm.
+
+'''Syntax:''' SecEncryptionMethodRx TYPE "string1 string2 string3..." 
+
+'''Example Usage''': SecEncryptionMethodRx HashHref "product_info list_product"
+
+'''Scope:''' Any
+
+'''Version:''' 2.7.0
+
+As a initial support is possible to protect HREF, FRAME, IFRAME and FORM ACTION html elements as well response Location header when http redirect code are sent.
+
+The possible values for TYPE are:
+*'''HashHref''': Used to sign href= html elements
+*'''HashFormAction''': Used to sign form action= html elements
+*'''HashIframeSrc''': Used to sign iframe src= html elements
+*'''HashframeSrc''': Used to sign frame src= html elements 
+*'''HashLocation''': Used to sign Location response header
+
+; Note : This directive is used to sign the elements however user must use the @validateEncryption operator to enforce data integrity.
+
+== SecGeoLookupDb ==
+'''Description''': Defines the path to the database that will be used for geolocation lookups. 
+
+'''Syntax:''' SecGeoLookupDb /path/to/db 
+
+'''Example Usage''': SecGeoLookupDb /path/to/GeoLiteCity.dat
+
+'''Scope:''' Any
+
+'''Version:''' 2.5.0 
+
+ModSecurity relies on the free geolocation databases (GeoLite City and GeoLite Country) that can be obtained from MaxMind [http://www.maxmind.com].
+
+== SecGsbLookupDb ==
+'''Description''': Defines the path to the database that will be used for Google Safe Browsing (GSB) lookups. 
+
+'''Syntax:''' SecGsbLookupDb /path/to/db 
+
+'''Example Usage''': SecGsbLookupDb /path/to/GsbMalware.dat
+
+'''Scope:''' Any
+
+'''Version:''' 2.6.0 
+
+ModSecurity relies on the free Google Safe Browsing database that can be obtained from the Google GSB API [http://code.google.com/apis/safebrowsing/].
+
+; Note : Deprecated in 2.7.0 after Google dev team decided to not allow the database download anymore. After registering and obtaining a Safe Browsing API key, you can automatically download the GSB using a tool like wget (where '''''KEY''''' is your own API key):
+wget http://sb.google.com/safebrowsing/update?client=api&apikey=KEY&version=goog-malware-hash:1:-1
+
+== SecGuardianLog ==
+'''Description:''' Configures an external program that will receive the information about every transaction via piped logging.
+
+'''Syntax:''' SecGuardianLog |/path/to/httpd-guardian 
+
+'''Example Usage:''' SecGuardianLog |/usr/local/apache/bin/httpd-guardian 
+
+'''Scope:''' Main 
+
+'''Version:''' 2.0.0
+
+Guardian logging is designed to send the information about every request to an external program. Because Apache is typically deployed in a multiprocess fashion, which makes information sharing between processes difficult, the idea is to deploy a single external process to observe all requests in a stateful manner, providing additional protection.
+
+Currently the only tool known to work with guardian logging is httpd-guardian, which is part of the Apache httpd tools project [http://apache-tools.cvs.sourceforge.net/viewvc/apache-tools/apache-tools/]. The httpd-guardian tool is designed to defend against denial of service attacks. It uses the blacklist tool (from the same project) to interact with an iptables-based (on a Linux system) or pf-based (on a BSD system) firewall, dynamically blacklisting the offending IP addresses. It can also interact with SnortSam [http://www.snortsam.net]. Assuming httpd-guardian is already configured (look into the source code for the detailed instructions), you only need to add one line to your Apache configuration to deploy it:
 
SecGuardianLog |/path/to/httpd-guardian

-
[edit]  SecHttpBlKey 

-
Description: Configures the user's registered Honeypot Project HTTP BL API Key to use with @rbl.
-
Syntax: SecHttpBlKey [12 char access key] 
 
-
Example Usage: SecHttpBlKey whdkfieyhtnf 
-
Scope: Main 
-
Version: 2.7.0
-
If the @rbl operator uses the dnsbl.httpbl.org RBL (http://www.projecthoneypot.org/httpbl_api.php) you must provide an API key.  This key is registered to individual users and is included within the RBL DNS requests.
-

-
[edit]  SecInterceptOnError 

+== SecHttpBlKey ==
+'''Description:''' Configures the user's registered Honeypot Project HTTP BL API Key to use with @rbl.
 
-
Description: Configures how to respond when rule processing fails.
-
Syntax: SecInterceptOnError On|Off 
-
Example Usage: SecInterceptOnError On 
-
Scope: Main 
-
Version: 2.6
+'''Syntax:''' SecHttpBlKey [12 char access key] 
 
-
When an operator execution fails (ie returns <0), this directive configures how to react.  When set to "Off", the rule is just ignored and the engine will continue executing the rules in phase.  When set to "On", the rule will be just dropped and no more rules will be executed in the same phase, also no interception is made.
-

-
[edit]  SecMarker 

-
Description: Adds a fixed rule marker that can be used as a target in a skipAfter action. A SecMarker directive essentially creates a rule that does nothing and whose only purpose is to carry the given ID.
-
Syntax: SecMarker ID|TEXT 
+'''Example Usage:''' SecHttpBlKey whdkfieyhtnf 
 
-
Example Usage: SecMarker 9999 
-
Scope: Any 
-
Version: 2.5.0
-
The value can be either a number or a text string.  The SecMarker directive is available to allow you to choose the best way to implement a skip-over. Here is an example used from the Core Rule Set:
-

+'''Scope:''' Main 
+
+'''Version:''' 2.7.0
+
+If the @rbl operator uses the dnsbl.httpbl.org RBL (http://www.projecthoneypot.org/httpbl_api.php) you must provide an API key.  This key is registered to individual users and is included within the RBL DNS requests.
+
+== SecInterceptOnError ==
+'''Description:''' Configures how to respond when rule processing fails.
+
+'''Syntax:''' SecInterceptOnError On|Off 
+
+'''Example Usage:''' SecInterceptOnError On 
+
+'''Scope:''' Main 
+
+'''Version:''' 2.6
+
+When an operator execution fails (ie returns <0), this directive configures how to react.  When set to "Off", the rule is just ignored and the engine will continue executing the rules in phase.  When set to "On", the rule will be just dropped and no more rules will be executed in the same phase, also no interception is made.
+
+== SecMarker ==
+'''Description:''' Adds a fixed rule marker that can be used as a target in a skipAfter action. A SecMarker directive essentially creates a rule that does nothing and whose only purpose is to carry the given ID.
+
+'''Syntax:''' SecMarker ID|TEXT 
+
+'''Example Usage''': SecMarker 9999 
+
+'''Scope:''' Any 
+
+'''Version:''' 2.5.0
+
+The value can be either a number or a text string.  The SecMarker directive is available to allow you to choose the best way to implement a skip-over. Here is an example used from the Core Rule Set:
 
 SecMarker BEGIN_HOST_CHECK
 
-        SecRule &REQUEST_HEADERS:Host "@eq 0" \
-                "skipAfter:END_HOST_CHECK,phase:2,rev:'2.1.1',t:none,block,msg:'Request Missing a Host Header',id:'960008',tag:'PROTOCOL_VIOLATION/MISSING_HEADER_HOST',tag:'WASCTC/WASC-21',tag:'OWASP_TOP_10/A7',tag:'PCI/6.5.10',severity:'5',setvar:'tx.msg=%{rule.msg}',setvar:tx.anomaly_score=+%{tx.notice_anomaly_score},setvar:tx.protocol_violation_score=+%{tx.notice_anomaly_score},setvar:tx.%{rule.id}-PROTOCOL_VIOLATION/MISSING_HEADER-%{matched_var_name}=%{matched_var}"
-
-        SecRule REQUEST_HEADERS:Host "^$" \
-                "phase:2,rev:'2.1.1',t:none,block,msg:'Request Missing a Host Header',id:'960008',tag:'PROTOCOL_VIOLATION/MISSING_HEADER_HOST',tag:'WASCTC/WASC-21',tag:'OWASP_TOP_10/A7',tag:'PCI/6.5.10',severity:'5',setvar:'tx.msg=%{rule.msg}',setvar:tx.anomaly_score=+%{tx.notice_anomaly_score},setvar:tx.protocol_violation_score=+%{tx.notice_anomaly_score},setvar:tx.%{rule.id}-PROTOCOL_VIOLATION/MISSING_HEADER-%{matched_var_name}=%{matched_var}"
+        SecRule &REQUEST_HEADERS:Host "@eq 0" \
+                "skipAfter:END_HOST_CHECK,phase:2,rev:'2.1.1',t:none,block,msg:'Request Missing a Host Header',id:'960008',tag:'PROTOCOL_VIOLATION/MISSING_HEADER_HOST',tag:'WASCTC/WASC-21',tag:'OWASP_TOP_10/A7',tag:'PCI/6.5.10',severity:'5',setvar:'tx.msg=%{rule.msg}',setvar:tx.anomaly_score=+%{tx.notice_anomaly_score},setvar:tx.protocol_violation_score=+%{tx.notice_anomaly_score},setvar:tx.%{rule.id}-PROTOCOL_VIOLATION/MISSING_HEADER-%{matched_var_name}=%{matched_var}"
+        SecRule REQUEST_HEADERS:Host "^$" \
+                "phase:2,rev:'2.1.1',t:none,block,msg:'Request Missing a Host Header',id:'960008',tag:'PROTOCOL_VIOLATION/MISSING_HEADER_HOST',tag:'WASCTC/WASC-21',tag:'OWASP_TOP_10/A7',tag:'PCI/6.5.10',severity:'5',setvar:'tx.msg=%{rule.msg}',setvar:tx.anomaly_score=+%{tx.notice_anomaly_score},setvar:tx.protocol_violation_score=+%{tx.notice_anomaly_score},setvar:tx.%{rule.id}-PROTOCOL_VIOLATION/MISSING_HEADER-%{matched_var_name}=%{matched_var}"
 
 SecMarker END_HOST_CHECK
 

-
[edit]  SecPcreMatchLimit 

 
-
Description: Sets the match limit in the PCRE library. 
-
Syntax: SecPcreMatchLimit value 
-
Example Usage: SecPcreMatchLimit 1500 
-
Scope: Main
-
Version: 2.5.12
-
Default: 1500
+== SecPcreMatchLimit ==
+'''Description''': Sets the match limit in the PCRE library. 
 
-
The default can be changed when ModSecurity is prepared for compilation: the --enable-pcre-match-limit=val configure option will set a custom default and the --disable-pcre-match-limit option will revert back to the default of the PCRE library.
+'''Syntax:''' SecPcreMatchLimit value 
+
+'''Example Usage''': SecPcreMatchLimit 1500 
+
+'''Scope:''' Main
+
+'''Version''': 2.5.12
+
+'''Default:''' 1500
+
+The default can be changed when ModSecurity is prepared for compilation: the --enable-pcre-match-limit=val configure option will set a custom default and the --disable-pcre-match-limit option will revert back to the default of the PCRE library.
 For more information, refer to the pcre_extra field in the pcreapi man page.
-

-
[edit]  SecPcreMatchLimitRecursion 

-
Description: Sets the match limit recursion in the PCRE library. 
-
Syntax: SecPcreMatchLimitRecursion value 
-
Example Usage: SecPcreMatchLimitRecursion 1500 
 
-
Scope: Main
-
Version: 2.5.12
-
Default: 1500
-
The default can be changed when ModSecurity is prepared for compilation: the --enable-pcre-match-limit-recursion=val configure option will set a custom default and the --disable-pcre-match-limit-recursion option will revert back to the default of the PCRE library.
+== SecPcreMatchLimitRecursion ==
+'''Description:''' Sets the match limit recursion in the PCRE library. 
+
+'''Syntax:''' SecPcreMatchLimitRecursion value 
+
+'''Example Usage:''' SecPcreMatchLimitRecursion 1500 
+
+'''Scope:''' Main
+
+'''Version:''' 2.5.12
+
+'''Default:''' 1500
+
+The default can be changed when ModSecurity is prepared for compilation: the --enable-pcre-match-limit-recursion=val configure option will set a custom default and the --disable-pcre-match-limit-recursion option will revert back to the default of the PCRE library.
 For more information, refer to the pcre_extra field in the pcreapi man page.
-

-
[edit]  SecPdfProtect 

 
-
Description: Enables the PDF XSS protection functionality. 
-
Syntax: SecPdfProtect On|Off 
-
Example Usage: SecPdfProtect On 
-
Scope: Any 
-
Version: 2.5.0; removed from trunk
+== SecPdfProtect ==
+'''Description:''' Enables the PDF XSS protection functionality. 
 
-
Once enabled access to PDF files is tracked. Direct access attempts are redirected to links that contain one-time tokens. Requests with valid tokens are allowed through, unmodified. Requests with invalid tokens are also allowed through, but with forced download of the PDF files. This implementation uses response headers to detect PDF files and thus can be used with dynamically generated PDF files that do not have the .pdf extension in the request URI.
-

-
[edit]  SecPdfProtectMethod 

-
Description: Configure desired protection method to be used when requests for PDF files are detected. 
-
Syntax: SecPdfProtectMethod method 
-
Example Usage: SecPdfProtectMethod TokenRedirection 
+'''Syntax:''' SecPdfProtect On|Off 
 
-
Scope: Any 
-
Version: 2.5.0; removed from trunk 
-
Default: TokenRedirection
-
Possible values are TokenRedirection and ForcedDownload. The token redirection approach will attempt to redirect with tokens where possible. This allows PDF files to continue to be opened inline but works only for GET requests. Forced download always causes PDF files to be delivered as opaque binaries and attachments. The latter will always be used for non-GET requests. Forced download is considered to be more secure but may cause usability problems for users (“This PDF won’t open anymore!”).
-

-
[edit]  SecPdfProtectSecret 

+'''Example Usage:''' SecPdfProtect On 
 
-
Description: Defines the secret that will be used to construct one-time tokens. 
-
Syntax: SecPdfProtectSecret secret 
-
Example Usage: SecPdfProtectSecret MyRandomSecretString
-
Scope: Any 
-
Version: 2.5.0; removed from trunk
+'''Scope:''' Any 
 
-
You should use a reasonably long value for the secret (e.g., 16 characters is good). Once selected, the secret should not be changed, as it will break the tokens that were sent prior to change. But it’s not a big deal even if you change it. It will just force download of PDF files with tokens that were issued in the last few seconds.
-

-
[edit]  SecPdfProtectTimeout 

-
Description: Defines the token timeout. 
-
Syntax: SecPdfProtectTimeout timeout 
-
Example Usage: SecPdfProtectTimeout 10 
+'''Version:''' 2.5.0; removed from trunk
 
-
Scope: Any 
-
Version: 2.5.0; removed from trunk 
-
Default: 10
-
After token expires, it can no longer be used to allow access to a PDF file. Request will be allowed through but the PDF will be delivered as an attachment.
-

-
[edit]  SecPdfProtectTokenName 

+Once enabled access to PDF files is tracked. Direct access attempts are redirected to links that contain one-time tokens. Requests with valid tokens are allowed through, unmodified. Requests with invalid tokens are also allowed through, but with forced download of the PDF files. This implementation uses response headers to detect PDF files and thus can be used with dynamically generated PDF files that do not have the .pdf extension in the request URI.
 
-
Description: Defines the name of the token. 
-
Syntax: SecPdfProtectTokenName name 
-
Example Usage: SecPdfProtectTokenName PDFTOKEN 
-
Scope: Any 
-
Version: 2.5.0; removed from trunk 
-
Default: PDFTOKEN
+== SecPdfProtectMethod ==
+'''Description''': Configure desired protection method to be used when requests for PDF files are detected. 
 
-
The only reason you would want to change the name of the token is if you wanted to hide the fact that you are running ModSecurity. It’s a good reason, but it won’t really help, as the adversary can look into the algorithm used for PDF protection and figure it out anyway. It does raise the bar slightly, so go ahead if you want to.
-

-
[edit]  SecReadStateLimit 

-
Description: Establishes a per-IP address limit of how many connections are allowed to be in SERVER_BUSY_READ state. 
-
Syntax: SecReadStateLimit LIMIT 
+'''Syntax:''' SecPdfProtectMethod method 
 
-
Example Usage: SecReadStateLimit 50 
-
Scope: Main 
-
Version: 2.5.13 
-
Default: 0 (no limit)
-
This measure is effective against Slowloris-style attacks from a single IP address, but it may not be as good against modified attacks that work by slowly sending request body content. This is because Apache to switches state to SERVER_BUSY_WRITE once request headers have been read. As an alternative, consider mod_reqtimeout (part of Apache as of 2.2.15), which is expected be effective against both attack types.  See Blog post on mitigating slow DoS attacks - http://blog.spiderlabs.com/2010/11/advanced-topic-of-the-week-mitigating-slow-http-dos-attacks.html
-

-
[edit]  SecSensorId 

+'''Example Usage''': SecPdfProtectMethod TokenRedirection 
 
-
Description: Define a sensor ID that will be present into log part H. 
-
Syntax: SecSensorId TEXT 
-
Example Usage: SecSensorId WAFSensor01 
-
Scope: Main 
-
Version: 2.7.0 
-

-
[edit]  SecWriteStateLimit 

+'''Scope''': Any 
 
-
Description: Establishes a per-IP address limit of how many connections are allowed to be in SERVER_BUSY_WRITE state. 
-
Syntax: SecWriteStateLimit LIMIT 
-
Example Usage: SecWriteStateLimit 50 
-
Scope: Main 
-
Version: 2.6.0 
-
Default: 0 (no limit)
+'''Version:''' 2.5.0; removed from trunk 
 
-
This measure is effective against Slow DoS request body attacks.
-

-
[edit]  SecRequestBodyAccess 

-
Description: Configures whether request bodies will be buffered and processed by ModSecurity.
-
Syntax: SecRequestBodyAccess On|Off 
-
Example Usage: SecRequestBodyAccess On
+'''Default:''' TokenRedirection
 
-
Scope: Any 
-
Version: 2.0.0
-
This directive is required if you want to inspect the data transported request bodies (e.g., POST parameters). Request buffering is also required in order to make reliable blocking possible.  The possible values are:
-

-
  • On: buffer request bodies
-
  • Off: do not buffer request bodies
-

-
[edit]  SecRequestBodyInMemoryLimit 

+Possible values are TokenRedirection and ForcedDownload. The token redirection approach will attempt to redirect with tokens where possible. This allows PDF files to continue to be opened inline but works only for GET requests. Forced download always causes PDF files to be delivered as opaque binaries and attachments. The latter will always be used for non-GET requests. Forced download is considered to be more secure but may cause usability problems for users (“This PDF won’t open anymore!”).
 
-
Description: Configures the maximum request body size that ModSecurity will store in mem- ory.
-
Syntax: SecRequestBodyInMemoryLimit LIMIT_IN_BYTES 
-
Example Usage: SecRequestBodyInMemoryLimit 131072 
-
Scope: Any 
-
Version: 2.0.0
-
Default: 131072 (128 KB) 
+== SecPdfProtectSecret ==
+'''Description:''' Defines the secret that will be used to construct one-time tokens. 
 
-
When a multipart/form-data request is being processed, once the in-memory limit is reached, the request body will start to be streamed into a temporary file on disk.
-

-
[edit]  SecRequestBodyLimit 

-
Description: Configures the maximum request body size ModSecurity will accept for buffering.
-
Syntax: SecRequestBodyLimit LIMIT_IN_BYTES 
-
Example Usage: SecRequestBodyLimit 134217728 
+'''Syntax:''' SecPdfProtectSecret secret 
 
-
Scope: Any 
-
Version: 2.0.0
-
Default: 134217728 (131072 KB) 
-
Anything over the limit will be rejected with status code 413 (Request Entity Too Large). There is a hard limit of 1 GB.
-

-
 Note 
 In ModSecurity 2.5.x and earlier, SecRequestBodyLimit works only when used in the main server configuration, or a VirtualHost container. In these versions, request body limit is enforced immediately after phase 1, but before phase 2 configuration (i.e. whatever is placed in a Location container) is resolved.  You can work around this limitation by using a phase 1 rule that changes the request body limit dynamically, using the ctl:requestBodyLimit action. ModSecurity 2.6.x (currently in the trunk only) and better do not have this limitation.
-

-
[edit]  SecRequestBodyNoFilesLimit 

+'''Example Usage:''' SecPdfProtectSecret MyRandomSecretString
 
-
Description: Configures the maximum request body size ModSecurity will accept for buffering, excluding the size of any files being transported in the request. This directive is useful to reduce susceptibility to DoS attacks when someone is sending request bodies of very large sizes. Web applications that require file uploads must configure SecRequestBodyLimit to a high value, but because large files are streamed to disk, file uploads will not increase memory consumption. However, it’s still possible for someone to take advantage of a large request body limit and send non-upload requests with large body sizes. This directive eliminates that loophole.
-
Syntax: SecRequestBodyNoFilesLimit NUMBER_IN_BYTES 
-
Example Usage: SecRequestBodyLimit 131072 
-
Scope: Any 
-
Version: 2.5.0
-
Default: 1048576 (1 MB)
+'''Scope:''' Any 
 
-
Generally speaking, the default value is not small enough. For most applications, you should be able to reduce it down to 128 KB or lower. Anything over the limit will be rejected with status code 413 (Request Entity Too Large). There is a hard limit of 1 GB.
-

-
[edit]  SecRequestBodyLimitAction 

-
Description: Controls what happens once a request body limit, configured with SecRequestBodyLimit, is encountered
-
Syntax: SecRequestBodyLimitAction Reject|ProcessPartial 
-
Example Usage: SecRequestBodyLimitAction ProcessPartial
+'''Version:''' 2.5.0; removed from trunk
 
-
Scope: Any 
-
Version: 2.6.0
-
By default, ModSecurity will reject a request body that is longer than specified.  This is problematic especially when ModSecurity is being run in DetectionOnly mode and the intent is to be totally passive and not take any disruptive actions against the transaction. With the ability to choose what happens once a limit is reached, site administrators can choose to inspect only the first part of the request, the part that can fit into the desired limit, and let the rest through.  This is not ideal from a possible evasion issue perspective, however it may be acceptable under certain circumstances.
-

-
 Note 
 When the SecRuleEngine is set to DetectionOnly, SecRequestBodyLimitAction is automatically set to ProcessPartial in order to not cause any disruptions.  If you want to know if/when a request body size is over your limit, you can create a rule to check for the existence of the INBOUND_ERROR_DATA variable.
-

-
[edit]  SecResponseBodyLimit 

+You should use a reasonably long value for the secret (e.g., 16 characters is good). Once selected, the secret should not be changed, as it will break the tokens that were sent prior to change. But it’s not a big deal even if you change it. It will just force download of PDF files with tokens that were issued in the last few seconds.
 
-
Description: Configures the maximum response body size that will be accepted for buffering.
-
Syntax: SecResponseBodyLimit LIMIT_IN_BYTES 
-
Example Usage: SecResponseBodyLimit 524228 
-
Scope: Any 
-
Version: 2.0.0
+== SecPdfProtectTimeout ==
+'''Description''': Defines the token timeout. 
 
-
Default: 524288 (512 KB)
-
Anything over this limit will be rejected with status code 500 (Internal Server Error). This setting will not affect the responses with MIME types that are not selected for buffering. There is a hard limit of 1 GB.
-

-
[edit]  SecResponseBodyLimitAction 

-
Description: Controls what happens once a response body limit, configured with SecResponseBodyLimit, is encountered. 
-
Syntax: SecResponseBodyLimitAction Reject|ProcessPartial 
+'''Syntax:''' SecPdfProtectTimeout timeout 
 
-
Example Usage: SecResponseBodyLimitAction ProcessPartial 
-
Scope: Any 
-
Version: 2.5.0
-
By default, ModSecurity will reject a response body that is longer than specified. Some web sites, however, will produce very long responses, making it difficult to come up with a reasonable limit. Such sites would have to raise the limit significantly to function properly, defying the purpose of having the limit in the first place (to control memory consumption). With the ability to choose what happens once a limit is reached, site administrators can choose to inspect only the first part of the response, the part that can fit into the desired limit, and let the rest through. Some could argue that allowing parts of responses to go uninspected is a weakness. This is true in theory, but applies only to cases in which the attacker controls the output (e.g., can make it arbitrary long). In such cases, however, it is not possible to prevent leakage anyway. The attacker could compress, obfuscate, or even encrypt data before it is sent back, and therefore bypass any monitoring device.
-

-
[edit]  SecResponseBodyMimeType 

+'''Example Usage''': SecPdfProtectTimeout 10 
 
-
Description: Configures which MIME types are to be considered for response body buffering. 
-
Syntax: SecResponseBodyMimeType MIMETYPE MIMETYPE ... 
-
Example Usage: SecResponseBodyMimeType text/plain text/html text/xml
-
Scope: Any
-
Version: 2.0.0 
+'''Scope:''' Any 
 
-
Default: text/plain text/html
-
Multiple SecResponseBodyMimeType directives can be used to add MIME types. Use SecResponseBodyMimeTypesClear to clear previously configured MIME types and start over.
-

-
[edit]   SecResponseBodyMimeTypesClear 

-
Description: Clears the list of MIME types considered for response body buffering, allowing you to start populating the list from scratch.
-
Syntax: SecResponseBodyMimeTypesClear 
+'''Version:''' 2.5.0; removed from trunk 
 
-
Example Usage: SecResponseBodyMimeTypesClear 
-
Scope: Any 
-
Version: 2.0.0
-

-
[edit]  SecResponseBodyAccess 

+'''Default:''' 10
 
-
Description: Configures whether response bodies are to be buffered. 
-
Syntax: SecResponseBodyAccess On|Off 
-
Example Usage: SecResponseBodyAccess On 
-
Scope: Any
-
Version: 2.0.0 
+After token expires, it can no longer be used to allow access to a PDF file. Request will be allowed through but the PDF will be delivered as an attachment.
 
-
Default: Off
-
This directive is required if you plan to inspect HTML responses and implement response blocking.  Possible values are: 
-

-
  • On: buffer response bodies (but only if the response MIME type matches the list configured with SecResponseBodyMimeType). 
-
  • Off: do not buffer response bodies.
-

-
[edit]  SecRule 

-
Description: Creates a rule that will analyze the selected variables using the selected operator. 
+== SecPdfProtectTokenName ==
+'''Description''': Defines the name of the token. 
 
-
Syntax: SecRule VARIABLES OPERATOR [ACTIONS] 
-
Example Usage: SecRule ARGS "@rx attack" "phase:1,log,deny,id:1" 
-
Scope: Any
-
Version: 2.0.0
-
Every rule must provide one or more variables along with the operator that should be used to inspect them. If no actions are provided, the default list will be used. (There is always a default list, even if one was not explicitly set with SecDefaultAction.) If there are actions specified in a rule, they will be merged with the default list to form the final actions that will be used. (The actions in the rule will overwrite those in the default list.) Refer to SecDefaultAction for more information.
-

-
[edit]  SecRuleInheritance 

+'''Syntax''': SecPdfProtectTokenName name 
 
-
Description: Configures whether the current context will inherit the rules from the parent context.
-
Syntax: SecRuleInheritance On|Off 
-
Example Usage: SecRuleInheritance Off 
-
Scope: Any 
-
Version: 2.0.0 
+'''Example Usage''': SecPdfProtectTokenName PDFTOKEN 
 
-
Default: On
-
Sometimes when you create a more specific configuration context (for example using the <Location> container), you may wish to use a different set of rules than those used in the parent context. By setting SecRuleInheritance to Off, you prevent the parent rules to be inherited, which allows you to start from scratch. In ModSecurity 2.5.x it is not possible to override phase 1 rules from a <Location> configuration context. There are no limitations in that respect in the current development version (and there won’t be in the next major version).
-
The possible values are: 
-

-
  • On: inherit rules from the parent context 
-
  • Off: do not inherit rules from the parent context
-

-
 Note 
 Configuration contexts are an Apache concept. Directives <Directory>, <Files>, <Location>, and <VirtualHost> are all used to create configuration contexts. For more information, please go to the Apache documentation, under Configuration Sections [6]. This directive does not affect how configuration options are inherited.
+'''Scope''': Any 
 
-

-
[edit]  SecRuleEngine 

-
Description: Configures the rules engine. 
-
Syntax: SecRuleEngine On|Off|DetectionOnly
-
Example Usage: SecRuleEngine On 
+'''Version''': 2.5.0; removed from trunk 
 
-
Scope: Any 
-
Version: 2.0.0 
-
Default: Off
-
The possible values are: 
-

-
  • On: process rules
-
  • Off: do not process rules 
-
  • DetectionOnly: process rules but never executes any disruptive actions (block, deny, drop, allow, proxy and redirect)
-

+'''Default:''' PDFTOKEN
 
-
[edit]  SecRulePerfTime 

-
Description: Set a performance threshold for rules. Rules that spends too much time will be logged into audit log Part H in the format id=usec. 
-
Syntax: SecRulePerfTime USECS 
-
Example Usage: SecRulePerfTime 1000 
+The only reason you would want to change the name of the token is if you wanted to hide the fact that you are running ModSecurity. It’s a good reason, but it won’t really help, as the adversary can look into the algorithm used for PDF protection and figure it out anyway. It does raise the bar slightly, so go ahead if you want to.
 
-
Scope: Any
-
Version: 2.7 
-

-
[edit]  SecRuleRemoveById 

-
Description: Removes the matching rules from the current configuration context. 
+== SecReadStateLimit ==
+'''Description:''' Establishes a per-IP address limit of how many connections are allowed to be in SERVER_BUSY_READ state. 
 
-
Syntax: SecRuleRemoveById ID ID RANGE ... 
-
Example Usage: SecRuleRemoveByID 1 2 "9000-9010" 
-
Scope: Any
-
Version: 2.0.0 
-
This directive supports multiple parameters, each of which can be a rule ID or a range. Parameters that contain spaces must be delimited using double quotes.
-

-
 Note 
 This directive must be specified after the rule in which it is disabling.  This should be used within local custom rule files that are processed after third party rule sets.  Example file - modsecurity_crs_60_customrules.conf.
+'''Syntax:''' SecReadStateLimit LIMIT 
 
-

-
[edit]  SecRuleRemoveByMsg 

-
Description: Removes the matching rules from the current configuration context. 
-
Syntax: SecRuleRemoveByMsg REGEX 
-
Example Usage: SecRuleRemoveByMsg "FAIL" 
+'''Example Usage''': SecReadStateLimit 50 
 
-
Scope: Any
-
Version: 2.0.0
-
Normally, you would use SecRuleRemoveById to remove rules, but that requires the rules to have IDs defined. If they don’t, then you can remove them with SecRuleRemoveByMsg, which matches a regular expression against rule messages.
-

-
 Note 
 This directive must be specified after the rule in which it is disabling. This should be used within local custom rule files that are processed after third party rule sets. Example file - modsecurity_crs_60_customrules.conf.
-

-
[edit]  SecRuleRemoveByTag 

+'''Scope''': Main 
 
-
Description: Removes the matching rules from the current configuration context. 
-
Syntax: SecRuleRemoveByTab REGEX 
-
Example Usage: SecRuleRemoveByTag "WEB_ATTACK/XSS" 
-
Scope: Any
-
Version: 2.6
+'''Version''': 2.5.13 
 
-
Normally, you would use SecRuleRemoveById to remove rules, but that requires the rules to have IDs defined. If they don’t, then you can remove them with SecRuleRemoveByTag, which matches a regular expression against rule tag data.  This is useful if you want to disable entire groups of rules based on tag data.  Example tags used in the OWASP ModSecurity CRS include:
-

-
  • AUTOMATION/MALICIOUS
-
  • AUTOMATION/MISC
-
  • AUTOMATION/SECURITY_SCANNER
-
  • LEAKAGE/SOURCE_CODE_ASP_JSP
-
  • LEAKAGE/SOURCE_CODE_CF
-
  • LEAKAGE/SOURCE_CODE_PHP
-
  • WEB_ATTACK/CF_INJECTION
-
  • WEB_ATTACK/COMMAND_INJECTION
-
  • WEB_ATTACK/FILE_INJECTION
-
  • WEB_ATTACK/HTTP_RESPONSE_SPLITTING
-
  • WEB_ATTACK/LDAP_INJECTION
-
  • WEB_ATTACK/PHP_INJECTION
-
  • WEB_ATTACK/REQUEST_SMUGGLING
-
  • WEB_ATTACK/SESSION_FIXATION
-
  • WEB_ATTACK/SQL_INJECTION
+'''Default:''' 0 (no limit)
 
-
  • WEB_ATTACK/SSI_INJECTION
-
  • WEB_ATTACK/XSS
-

-
 Note 
 This directive must be specified after the rule in which it is disabling. This should be used within local custom rule files that are processed after third party rule sets. Example file - modsecurity_crs_60_customrules.conf.
-

-
[edit]  SecRuleScript 

-
Description: This directive creates a special rule that executes a Lua script to decide whether to match or not. The main difference from SecRule is that there are no targets nor operators. The script can fetch any variable from the ModSecurity context and use any (Lua) operator to test them. The second optional parameter is the list of actions whose meaning is identical to that of SecRule.
-
Syntax: SecRuleScript /path/to/script.lua [ACTIONS]
+This measure is effective against Slowloris-style attacks from a single IP address, but it may not be as good against modified attacks that work by slowly sending request body content. This is because Apache to switches state to SERVER_BUSY_WRITE once request headers have been read. As an alternative, consider mod_reqtimeout (part of Apache as of 2.2.15), which is expected be effective against both attack types.  See Blog post on mitigating slow DoS attacks - http://blog.spiderlabs.com/2010/11/advanced-topic-of-the-week-mitigating-slow-http-dos-attacks.html
 
-
Example Usage: SecRuleScript "/path/to/file.lua" "block"
-
Scope: Any
-
Version: 2.5.0
-

-
 Note 
 All Lua scripts are compiled at configuration time and cached in memory. To reload scripts you must reload the entire ModSecurity configuration by restarting Apache.
-

-
Example script:
+== SecSensorId ==
+'''Description:''' Define a sensor ID that will be present into log part H. 
 
-

+'''Syntax:''' SecSensorId TEXT 
+
+'''Example Usage''': SecSensorId WAFSensor01 
+
+'''Scope''': Main 
+
+'''Version''': 2.7.0 
+
+== SecWriteStateLimit ==
+'''Description:''' Establishes a per-IP address limit of how many connections are allowed to be in SERVER_BUSY_WRITE state. 
+
+'''Syntax:''' SecWriteStateLimit LIMIT 
+
+'''Example Usage''': SecWriteStateLimit 50 
+
+'''Scope''': Main 
+
+'''Version''': 2.6.0 
+
+'''Default:''' 0 (no limit)
+
+This measure is effective against Slow DoS request body attacks.
+
+== SecRequestBodyAccess ==
+'''Description''': Configures whether request bodies will be buffered and processed by ModSecurity.
+
+'''Syntax:''' SecRequestBodyAccess On|Off 
+
+'''Example Usage''': SecRequestBodyAccess On
+
+'''Scope:''' Any 
+
+'''Version:''' 2.0.0
+
+This directive is required if you want to inspect the data transported request bodies (e.g., POST parameters). Request buffering is also required in order to make reliable blocking possible.  The possible values are:
+*On: buffer request bodies
+*Off: do not buffer request bodies
+
+== SecRequestBodyInMemoryLimit ==
+'''Description''': Configures the maximum request body size that ModSecurity will store in mem- ory.
+
+'''Syntax:''' SecRequestBodyInMemoryLimit LIMIT_IN_BYTES 
+
+'''Example Usage:''' SecRequestBodyInMemoryLimit 131072 
+
+'''Scope:''' Any 
+
+'''Version:''' 2.0.0
+
+'''Default:''' 131072 (128 KB) 
+
+When a multipart/form-data request is being processed, once the in-memory limit is reached, the request body will start to be streamed into a temporary file on disk.
+
+== SecRequestBodyLimit ==
+'''Description:''' Configures the maximum request body size ModSecurity will accept for buffering.
+
+'''Syntax:''' SecRequestBodyLimit LIMIT_IN_BYTES 
+
+'''Example Usage:''' SecRequestBodyLimit 134217728 
+
+'''Scope:''' Any 
+
+'''Version:''' 2.0.0
+
+'''Default:''' 134217728 (131072 KB) 
+
+Anything over the limit will be rejected with status code 413 (Request Entity Too Large). There is a hard limit of 1 GB.
+; Note : In ModSecurity 2.5.x and earlier, SecRequestBodyLimit works only when used in the main server configuration, or a VirtualHost container. In these versions, request body limit is enforced immediately after phase 1, but before phase 2 configuration (i.e. whatever is placed in a Location container) is resolved.  You can work around this limitation by using a phase 1 rule that changes the request body limit dynamically, using the ctl:requestBodyLimit action. ModSecurity 2.6.x (currently in the trunk only) and better do not have this limitation.
+
+== SecRequestBodyNoFilesLimit ==
+'''Description''': Configures the maximum request body size ModSecurity will accept for buffering, excluding the size of any files being transported in the request. This directive is useful to reduce susceptibility to DoS attacks when someone is sending request bodies of very large sizes. Web applications that require file uploads must configure SecRequestBodyLimit to a high value, but because large files are streamed to disk, file uploads will not increase memory consumption. However, it’s still possible for someone to take advantage of a large request body limit and send non-upload requests with large body sizes. This directive eliminates that loophole.
+
+'''Syntax:''' SecRequestBodyNoFilesLimit NUMBER_IN_BYTES 
+
+'''Example Usage:''' SecRequestBodyLimit 131072 
+
+'''Scope:''' Any 
+
+'''Version''': 2.5.0
+
+'''Default:''' 1048576 (1 MB)
+
+Generally speaking, the default value is not small enough. For most applications, you should be able to reduce it down to 128 KB or lower. Anything over the limit will be rejected with status code 413 (Request Entity Too Large). There is a hard limit of 1 GB.
+
+== SecRequestBodyLimitAction == 
+'''Description''': Controls what happens once a request body limit, configured with SecRequestBodyLimit, is encountered
+
+'''Syntax:''' SecRequestBodyLimitAction Reject|ProcessPartial 
+
+'''Example Usage:''' SecRequestBodyLimitAction ProcessPartial
+
+'''Scope:''' Any 
+
+'''Version''': 2.6.0
+
+By default, ModSecurity will reject a request body that is longer than specified.  This is problematic especially when ModSecurity is being run in DetectionOnly mode and the intent is to be totally passive and not take any disruptive actions against the transaction. With the ability to choose what happens once a limit is reached, site administrators can choose to inspect only the first part of the request, the part that can fit into the desired limit, and let the rest through.  This is not ideal from a possible evasion issue perspective, however it may be acceptable under certain circumstances.
+
+; Note : When the SecRuleEngine is set to DetectionOnly, SecRequestBodyLimitAction is automatically set to ProcessPartial in order to not cause any disruptions.  If you want to know if/when a request body size is over your limit, you can create a rule to check for the existence of the INBOUND_ERROR_DATA variable.
+
+== SecResponseBodyLimit ==
+'''Description:''' Configures the maximum response body size that will be accepted for buffering.
+
+'''Syntax:''' SecResponseBodyLimit LIMIT_IN_BYTES 
+
+'''Example Usage:''' SecResponseBodyLimit 524228 
+
+'''Scope:''' Any 
+
+'''Version:''' 2.0.0
+
+'''Default''': 524288 (512 KB)
+
+Anything over this limit will be rejected with status code 500 (Internal Server Error). This setting will not affect the responses with MIME types that are not selected for buffering. There is a hard limit of 1 GB.
+
+== SecResponseBodyLimitAction ==
+'''Description:''' Controls what happens once a response body limit, configured with SecResponseBodyLimit, is encountered. 
+
+'''Syntax:''' SecResponseBodyLimitAction Reject|ProcessPartial 
+
+'''Example Usage:''' SecResponseBodyLimitAction ProcessPartial 
+
+'''Scope:''' Any 
+
+'''Version:''' 2.5.0
+
+By default, ModSecurity will reject a response body that is longer than specified. Some web sites, however, will produce very long responses, making it difficult to come up with a reasonable limit. Such sites would have to raise the limit significantly to function properly, defying the purpose of having the limit in the first place (to control memory consumption). With the ability to choose what happens once a limit is reached, site administrators can choose to inspect only the first part of the response, the part that can fit into the desired limit, and let the rest through. Some could argue that allowing parts of responses to go uninspected is a weakness. This is true in theory, but applies only to cases in which the attacker controls the output (e.g., can make it arbitrary long). In such cases, however, it is not possible to prevent leakage anyway. The attacker could compress, obfuscate, or even encrypt data before it is sent back, and therefore bypass any monitoring device.
+
+== SecResponseBodyMimeType ==
+'''Description:''' Configures which MIME types are to be considered for response body buffering. 
+
+'''Syntax:''' SecResponseBodyMimeType MIMETYPE MIMETYPE ... 
+
+'''Example Usage''': SecResponseBodyMimeType text/plain text/html text/xml
+
+'''Scope:''' Any
+
+'''Version:''' 2.0.0 
+
+'''Default:''' text/plain text/html
+
+Multiple SecResponseBodyMimeType directives can be used to add MIME types. Use SecResponseBodyMimeTypesClear to clear previously configured MIME types and start over.
+
+==  SecResponseBodyMimeTypesClear ==
+'''Description:''' Clears the list of MIME types considered for response body buffering, allowing you to start populating the list from scratch.
+
+'''Syntax:''' SecResponseBodyMimeTypesClear 
+
+'''Example Usage:''' SecResponseBodyMimeTypesClear 
+
+'''Scope:''' Any 
+
+'''Version:''' 2.0.0
+
+== SecResponseBodyAccess ==
+'''Description:''' Configures whether response bodies are to be buffered. 
+
+'''Syntax:''' SecResponseBodyAccess On|Off 
+
+'''Example Usage:''' SecResponseBodyAccess On 
+
+'''Scope:''' Any
+
+'''Version:''' 2.0.0 
+
+'''Default:''' Off
+
+This directive is required if you plan to inspect HTML responses and implement response blocking.  Possible values are: 
+*On: buffer response bodies (but only if the response MIME type matches the list configured with SecResponseBodyMimeType). 
+*Off: do not buffer response bodies.
+
+== SecRule ==
+'''Description:''' Creates a rule that will analyze the selected variables using the selected operator. 
+
+'''Syntax:''' SecRule VARIABLES OPERATOR [ACTIONS] 
+
+'''Example Usage:''' SecRule ARGS "@rx attack" "phase:1,log,deny,id:1" 
+
+'''Scope:''' Any
+
+'''Version:''' 2.0.0
+
+Every rule must provide one or more variables along with the operator that should be used to inspect them. If no actions are provided, the default list will be used. (There is always a default list, even if one was not explicitly set with SecDefaultAction.) If there are actions specified in a rule, they will be merged with the default list to form the final actions that will be used. (The actions in the rule will overwrite those in the default list.) Refer to SecDefaultAction for more information.
+
+== SecRuleInheritance ==
+'''Description:''' Configures whether the current context will inherit the rules from the parent context.
+
+'''Syntax:''' SecRuleInheritance On|Off 
+
+'''Example Usage:''' SecRuleInheritance Off 
+
+'''Scope:''' Any 
+
+'''Version:''' 2.0.0 
+
+'''Default:''' On
+
+Sometimes when you create a more specific configuration context (for example using the  container), you may wish to use a different set of rules than those used in the parent context. By setting SecRuleInheritance to Off, you prevent the parent rules to be inherited, which allows you to start from scratch. In ModSecurity 2.5.x it is not possible to override phase 1 rules from a  configuration context. There are no limitations in that respect in the current development version (and there won’t be in the next major version).
+
+The possible values are: 
+*On: inherit rules from the parent context 
+*Off: do not inherit rules from the parent context
+; Note : Configuration contexts are an Apache concept. Directives , , , and  are all used to create configuration contexts. For more information, please go to the Apache documentation, under Configuration Sections [http://httpd.apache.org/docs/2.0/sections.html]. This directive does not affect how configuration options are inherited.
+
+== SecRuleEngine ==
+'''Description:''' Configures the rules engine. 
+
+'''Syntax:''' SecRuleEngine On|Off|DetectionOnly
+
+'''Example Usage:''' SecRuleEngine On 
+
+'''Scope''': Any 
+
+'''Version:''' 2.0.0 
+
+'''Default:''' Off
+
+The possible values are: 
+*'''On''': process rules
+*'''Off''': do not process rules 
+*'''DetectionOnly''': process rules but never executes any disruptive actions (block, deny, drop, allow, proxy and redirect)
+
+== SecRulePerfTime ==
+'''Description:''' Set a performance threshold for rules. Rules that spends too much time will be logged into audit log Part H in the format id=usec. 
+
+'''Syntax:''' SecRulePerfTime USECS 
+
+'''Example Usage:''' SecRulePerfTime 1000 
+
+'''Scope:''' Any
+
+'''Version:''' 2.7 
+
+== SecRuleRemoveById ==
+'''Description:''' Removes the matching rules from the current configuration context. 
+
+'''Syntax:''' SecRuleRemoveById ID ID RANGE ... 
+
+'''Example Usage:''' SecRuleRemoveByID 1 2 "9000-9010" 
+
+'''Scope:''' Any
+
+'''Version:''' 2.0.0 
+
+This directive supports multiple parameters, each of which can be a rule ID or a range. Parameters that contain spaces must be delimited using double quotes.
+
+; Note : '''This directive must be specified after the rule in which it is disabling'''.  This should be used within local custom rule files that are processed after third party rule sets.  Example file - modsecurity_crs_60_customrules.conf.
+
+== SecRuleRemoveByMsg ==
+'''Description:''' Removes the matching rules from the current configuration context. 
+
+'''Syntax:''' SecRuleRemoveByMsg REGEX 
+
+'''Example Usage:''' SecRuleRemoveByMsg "FAIL" 
+
+'''Scope:''' Any
+
+'''Version:''' 2.0.0
+
+Normally, you would use SecRuleRemoveById to remove rules, but that requires the rules to have IDs defined. If they don’t, then you can remove them with SecRuleRemoveByMsg, which matches a regular expression against rule messages.
+
+; Note : This directive must be specified after the rule in which it is disabling. This should be used within local custom rule files that are processed after third party rule sets. Example file - modsecurity_crs_60_customrules.conf.
+
+== SecRuleRemoveByTag ==
+'''Description:''' Removes the matching rules from the current configuration context. 
+
+'''Syntax:''' SecRuleRemoveByTab REGEX 
+
+'''Example Usage:''' SecRuleRemoveByTag "WEB_ATTACK/XSS" 
+
+'''Scope:''' Any
+
+'''Version:''' 2.6
+
+Normally, you would use SecRuleRemoveById to remove rules, but that requires the rules to have IDs defined. If they don’t, then you can remove them with SecRuleRemoveByTag, which matches a regular expression against rule tag data.  This is useful if you want to disable entire groups of rules based on tag data.  Example tags used in the OWASP ModSecurity CRS include:
+*AUTOMATION/MALICIOUS
+*AUTOMATION/MISC
+*AUTOMATION/SECURITY_SCANNER
+*LEAKAGE/SOURCE_CODE_ASP_JSP
+*LEAKAGE/SOURCE_CODE_CF
+*LEAKAGE/SOURCE_CODE_PHP
+*WEB_ATTACK/CF_INJECTION
+*WEB_ATTACK/COMMAND_INJECTION
+*WEB_ATTACK/FILE_INJECTION
+*WEB_ATTACK/HTTP_RESPONSE_SPLITTING
+*WEB_ATTACK/LDAP_INJECTION
+*WEB_ATTACK/PHP_INJECTION
+*WEB_ATTACK/REQUEST_SMUGGLING
+*WEB_ATTACK/SESSION_FIXATION
+*WEB_ATTACK/SQL_INJECTION
+*WEB_ATTACK/SSI_INJECTION
+*WEB_ATTACK/XSS
+
+; Note : This directive must be specified after the rule in which it is disabling. This should be used within local custom rule files that are processed after third party rule sets. Example file - modsecurity_crs_60_customrules.conf.
+
+== SecRuleScript ==
+Description: This directive creates a special rule that executes a Lua script to decide whether to match or not. The main difference from SecRule is that there are no targets nor operators. The script can fetch any variable from the ModSecurity context and use any (Lua) operator to test them. The second optional parameter is the list of actions whose meaning is identical to that of SecRule.
+
+'''Syntax:''' SecRuleScript /path/to/script.lua [ACTIONS]
+
+'''Example Usage:''' SecRuleScript "/path/to/file.lua" "block"
+
+'''Scope:''' Any
+
+'''Version:''' 2.5.0
+
+; Note : All Lua scripts are compiled at configuration time and cached in memory. To reload scripts you must reload the entire ModSecurity configuration by restarting Apache.
+
+Example script:
 
 -- Your script must define the main entry
 -- point, as below.
@@ -1736,1353 +1243,1352 @@ function main()
     -- Log something at level 1. Normally you shouldn't be
     -- logging anything, especially not at level 1, but this is
     -- just to show you can. Useful for debugging.
-    m.log(1, "Hello world!");
+    m.log(1, "Hello world!");
 
     -- Retrieve one variable.
-    local var1 = m.getvar("REMOTE_ADDR");
+    local var1 = m.getvar("REMOTE_ADDR");
 
     -- Retrieve one variable, applying one transformation function.
     -- The second parameter is a string.
-    local var2 = m.getvar("ARGS", "lowercase");
+    local var2 = m.getvar("ARGS", "lowercase");
 
     -- Retrieve one variable, applying several transformation functions.
     -- The second parameter is now a list. You should note that m.getvar()
     -- requires the use of comma to separate collection names from
     -- variable names. This is because only one variable is returned.
-    local var3 = m.getvar("ARGS.p", { "lowercase", "compressWhitespace" } );
+    local var3 = m.getvar("ARGS.p", { "lowercase", "compressWhitespace" } );
 
     -- If you want this rule to match return a string
     -- containing the error message. The message must contain the name
     -- of the variable where the problem is located.
-    -- return "Variable ARGS:p looks suspicious!"
+    -- return "Variable ARGS:p looks suspicious!"
 
     -- Otherwise, simply return nil.
     return nil;
 end
 

-
In this first example we were only retrieving one variable at the time. In this case the name of the variable is known to you. In many cases, however, you will want to examine variables whose names you won't know in advance, for example script parameters.
-
Example showing use of m.getvars() to retrieve many variables at once:
-

+In this first example we were only retrieving one variable at the time. In this case the name of the variable is known to you. In many cases, however, you will want to examine variables whose names you won't know in advance, for example script parameters.
+
+Example showing use of m.getvars() to retrieve many variables at once:
 
 function main()
     -- Retrieve script parameters.
-    local d = m.getvars("ARGS", { "lowercase", "htmlEntityDecode" } );
+    local d = m.getvars("ARGS", { "lowercase", "htmlEntityDecode" } );
 
     -- Loop through the paramters.
     for i = 1, #d do
         -- Examine parameter value.
-        if (string.find(d[i].value, "<script")) then
+        if (string.find(d[i].value, "
-
 Note 
 Go to http://www.lua.org/ to find more about the Lua programming language. The reference manual too is available online, at http://www.lua.org/manual/5.1/.
-

-
 Note 
 Lua support is marked as experimental as the way the progamming interface may continue to evolve while we are working for the best implementation style. Any user input into the programming interface is appreciated.
-

-
[edit]  SecRuleUpdateActionById 

+; Note : Go to http://www.lua.org/ to find more about the Lua programming language. The reference manual too is available online, at http://www.lua.org/manual/5.1/.
 
-
Description: Updates the action list of the specified rule.
-
Syntax: SecRuleUpdateActionById RULEID[:offset] ACTIONLIST
-
Example Usage: SecRuleUpdateActionById 12345 "deny,status:403"
-
Scope: Any
-
Version: 2.6.0
+; Note : Lua support is marked as experimental as the way the progamming interface may continue to evolve while we are working for the best implementation style. Any user input into the programming interface is appreciated.
 
-
This directive will overwrite the action list of the specified rule with the actions provided in the second parameter. It has two limitations: it cannot be used to change the ID or phase of a rule. Only the actions that can appear only once are overwritten. The actions that are allowed to appear multiple times in a list, will be appended to the end of the list.
-

+== SecRuleUpdateActionById ==
+'''Description:''' Updates the action list of the specified rule.
+
+'''Syntax:''' SecRuleUpdateActionById RULEID[:offset] ACTIONLIST
+
+'''Example Usage:''' SecRuleUpdateActionById 12345 "deny,status:403"
+
+'''Scope:''' Any
+
+'''Version:''' 2.6.0
+
+This directive will overwrite the action list of the specified rule with the actions provided in the second parameter. It has two limitations: it cannot be used to change the ID or phase of a rule. Only the actions that can appear only once are overwritten. The actions that are allowed to appear multiple times in a list, will be appended to the end of the list.
 
-SecRule ARGS attack "phase:2,id:12345,t:lowercase,log,pass,msg:'Message text'"
-SecRuleUpdateActionById 12345 "t:none,t:compressWhitespace,deny,status:403,msg:'New message text'"
+SecRule ARGS attack "phase:2,id:12345,t:lowercase,log,pass,msg:'Message text'"
+SecRuleUpdateActionById 12345 "t:none,t:compressWhitespace,deny,status:403,msg:'New message text'"
 

-
The effective resulting rule in the previous example will be as follows:
-

+The effective resulting rule in the previous example will be as follows:
 
-SecRule ARGS attack "phase:2,id:12345,t:lowercase,t:none,t:compressWhitespace,deny,status:403,msg:'New Message text'"
+SecRule ARGS attack "phase:2,id:12345,t:lowercase,t:none,t:compressWhitespace,deny,status:403,msg:'New Message text'"
 

+The addition of t:none will neutralize any previous transformation functions specified (t:lowercase, in the example).
 
-
The addition of t:none will neutralize any previous transformation functions specified (t:lowercase, in the example).
-

-
 Note 
 If the target rule is a chained rule, you must currently specify chain in the SecRuleUpdateActionById action list as well.  This will be fixed in a future version.
-

-
[edit]  SecRuleUpdateTargetById 

-
Description: Updates the target (variable) list of the specified rule.
+; Note : If the target rule is a chained rule, you must currently specify chain in the SecRuleUpdateActionById action list as well.  This will be fixed in a future version.
 
-
Syntax: SecRuleUpdateTargetById RULEID TARGET1[,TARGET2,TARGET3] REPLACED_TARGET
-
Example Usage: SecRuleUpdateTargetById 12345 "!ARGS:foo"
-
Scope: Any
-
Version: 2.6
-
This directive will append (or replace) variables to the current target list of the specified rule with the targets provided in the second parameter. Starting with 2.7.0 this feature supports id range.
-
Explicitly Appending Targets
+== SecRuleUpdateTargetById ==
+'''Description:''' Updates the target (variable) list of the specified rule.
 
-
This is useful for implementing exceptions where you want to externally update a target list to exclude inspection of specific variable(s).
-

+'''Syntax:''' SecRuleUpdateTargetById RULEID TARGET1[,TARGET2,TARGET3] REPLACED_TARGET
+
+'''Example Usage:''' SecRuleUpdateTargetById 12345 "!ARGS:foo"
+
+'''Scope:''' Any
+
+'''Version:''' 2.6
+
+This directive will append (or replace) variables to the current target list of the specified rule with the targets provided in the second parameter. Starting with 2.7.0 this feature supports id range.
+
+'''Explicitly Appending Targets'''
+
+This is useful for implementing exceptions where you want to externally update a target list to exclude inspection of specific variable(s).
 
-SecRule REQUEST_FILENAME|ARGS_NAMES|ARGS|XML:/* "[\;\|\`]\W*?\bmail\b" \
-     "phase:2,rev:'2.1.1',capture,t:none,t:htmlEntityDecode,t:compressWhitespace,t:lowercase,ctl:auditLogParts=+E,block,msg:'System Command Injection',id:'958895',tag:'WEB_ATTACK/COMMAND_INJECTION',tag:'WASCTC/WASC-31',tag:'OWASP_TOP_10/A1',tag:'PCI/6.5.2',logdata:'%{TX.0}',severity:'2',setvar:'tx.msg=%{rule.msg}',setvar:tx.anomaly_score=+%{tx.critical_anomaly_score},setvar:tx.command_injection_score=+%{tx.critical_anomaly_score},setvar:tx.%{rule.id}-WEB_ATTACK/COMMAND_INJECTION-%{matched_var_name}=%
-{tx.0}"
+SecRule REQUEST_FILENAME|ARGS_NAMES|ARGS|XML:/* "[\;\|\`]\W*?\bmail\b" \
+     "phase:2,rev:'2.1.1',capture,t:none,t:htmlEntityDecode,t:compressWhitespace,t:lowercase,ctl:auditLogParts=+E,block,msg:'System Command Injection',id:'958895',tag:'WEB_ATTACK/COMMAND_INJECTION',tag:'WASCTC/WASC-31',tag:'OWASP_TOP_10/A1',tag:'PCI/6.5.2',logdata:'%{TX.0}',severity:'2',setvar:'tx.msg=%{rule.msg}',setvar:tx.anomaly_score=+%{tx.critical_anomaly_score},setvar:tx.command_injection_score=+%{tx.critical_anomaly_score},setvar:tx.%{rule.id}-WEB_ATTACK/COMMAND_INJECTION-%{matched_var_name}=%
+{tx.0}"
 
-SecRuleUpdateTargetById 958895 !ARGS:email
+SecRuleUpdateTargetById 958895 !ARGS:email
 

-
The effective resulting rule in the previous example will append the target to the end of the variable list as follows:
-

+The effective resulting rule in the previous example will append the target to the end of the variable list as follows:
 
-
-SecRule REQUEST_FILENAME|ARGS_NAMES|ARGS|XML:/*|!ARGS:email "[\;\|\`]\W*?\bmail\b" \
-     "phase:2,rev:'2.1.1',capture,t:none,t:htmlEntityDecode,t:compressWhitespace,t:lowercase,ctl:auditLogParts=+E,block,msg:'System Command Injection',id:'958895',tag:'WEB_ATTACK/COMMAND_INJECTION',tag:'WASCTC/WASC-31',tag:'OWASP_TOP_10/A1',tag:'PCI/6.5.2',logdata:'%{TX.0}',severity:'2',setvar:'tx.msg=%{rule.msg}',setvar:tx.anomaly_score=+%{tx.critical_anomaly_score},setvar:tx.command_injection_score=+%{tx.critical_anomaly_score},setvar:tx.%{rule.id}-WEB_ATTACK/COMMAND_INJECTION-%{matched_var_name}=%
-{tx.0}""
+SecRule REQUEST_FILENAME|ARGS_NAMES|ARGS|XML:/*|!ARGS:email "[\;\|\`]\W*?\bmail\b" \
+     "phase:2,rev:'2.1.1',capture,t:none,t:htmlEntityDecode,t:compressWhitespace,t:lowercase,ctl:auditLogParts=+E,block,msg:'System Command Injection',id:'958895',tag:'WEB_ATTACK/COMMAND_INJECTION',tag:'WASCTC/WASC-31',tag:'OWASP_TOP_10/A1',tag:'PCI/6.5.2',logdata:'%{TX.0}',severity:'2',setvar:'tx.msg=%{rule.msg}',setvar:tx.anomaly_score=+%{tx.critical_anomaly_score},setvar:tx.command_injection_score=+%{tx.critical_anomaly_score},setvar:tx.%{rule.id}-WEB_ATTACK/COMMAND_INJECTION-%{matched_var_name}=%
+{tx.0}""
 

-
Explicitly Replacing Targets
-
You can also entirely replace the target list to something more appropriate for your environment.  For example, lets say you want to inspect REQUEST_URI instead of REQUEST_FILENAME, you could do this:
-

+'''Explicitly Replacing Targets'''
+
+You can also entirely replace the target list to something more appropriate for your environment.  For example, lets say you want to inspect REQUEST_URI instead of REQUEST_FILENAME, you could do this:
 
-SecRule REQUEST_FILENAME|ARGS_NAMES|ARGS|XML:/* "[\;\|\`]\W*?\bmail\b" \
-     "phase:2,rev:'2.1.1',capture,t:none,t:htmlEntityDecode,t:compressWhitespace,t:lowercase,ctl:auditLogParts=+E,block,msg:'System Command Injection',id:'958895',tag:'WEB_ATTACK/COMMAND_INJECTION',tag:'WASCTC/WASC-31',tag:'OWASP_TOP_10/A1',tag:'PCI/6.5.2',logdata:'%{TX.0}',severity:'2',setvar:'tx.msg=%{rule.msg}',setvar:tx.anomaly_score=+%{tx.critical_anomaly_score},setvar:tx.command_injection_score=+%{tx.critical_anomaly_score},setvar:tx.%{rule.id}-WEB_ATTACK/COMMAND_INJECTION-%{matched_var_name}=%
-{tx.0}"
+SecRule REQUEST_FILENAME|ARGS_NAMES|ARGS|XML:/* "[\;\|\`]\W*?\bmail\b" \
+     "phase:2,rev:'2.1.1',capture,t:none,t:htmlEntityDecode,t:compressWhitespace,t:lowercase,ctl:auditLogParts=+E,block,msg:'System Command Injection',id:'958895',tag:'WEB_ATTACK/COMMAND_INJECTION',tag:'WASCTC/WASC-31',tag:'OWASP_TOP_10/A1',tag:'PCI/6.5.2',logdata:'%{TX.0}',severity:'2',setvar:'tx.msg=%{rule.msg}',setvar:tx.anomaly_score=+%{tx.critical_anomaly_score},setvar:tx.command_injection_score=+%{tx.critical_anomaly_score},setvar:tx.%{rule.id}-WEB_ATTACK/COMMAND_INJECTION-%{matched_var_name}=%
+{tx.0}"
 
 SecRuleUpdateTargetById 958895 REQUEST_URI REQUEST_FILENAME
 

-
The effective resulting rule in the previous example will append the target to the end of the variable list as follows:
-

+The effective resulting rule in the previous example will append the target to the end of the variable list as follows:
 
-SecRule REQUEST_URI|ARGS_NAMES|ARGS|XML:/* "[\;\|\`]\W*?\bmail\b" \
-     "phase:2,rev:'2.1.1',capture,t:none,t:htmlEntityDecode,t:compressWhitespace,t:lowercase,ctl:auditLogParts=+E,block,msg:'System Command Injection',id:'958895',tag:'WEB_ATTACK/COMMAND_INJECTION',tag:'WASCTC/WASC-31',tag:'OWASP_TOP_10/A1',tag:'PCI/6.5.2',logdata:'%{TX.0}',severity:'2',setvar:'tx.msg=%{rule.msg}',setvar:tx.anomaly_score=+%{tx.critical_anomaly_score},setvar:tx.command_injection_score=+%{tx.critical_anomaly_score},setvar:tx.%{rule.id}-WEB_ATTACK/COMMAND_INJECTION-%{matched_var_name}=%
-{tx.0}""
+SecRule REQUEST_URI|ARGS_NAMES|ARGS|XML:/* "[\;\|\`]\W*?\bmail\b" \
+     "phase:2,rev:'2.1.1',capture,t:none,t:htmlEntityDecode,t:compressWhitespace,t:lowercase,ctl:auditLogParts=+E,block,msg:'System Command Injection',id:'958895',tag:'WEB_ATTACK/COMMAND_INJECTION',tag:'WASCTC/WASC-31',tag:'OWASP_TOP_10/A1',tag:'PCI/6.5.2',logdata:'%{TX.0}',severity:'2',setvar:'tx.msg=%{rule.msg}',setvar:tx.anomaly_score=+%{tx.critical_anomaly_score},setvar:tx.command_injection_score=+%{tx.critical_anomaly_score},setvar:tx.%{rule.id}-WEB_ATTACK/COMMAND_INJECTION-%{matched_var_name}=%
+{tx.0}""
 

-
Conditionally Appending Targets
-
You could also do the same by using the ctl action.  This is useful if you want to only update the targets for a particular URL
-

+'''Conditionally Appending Targets'''
 
+You could also do the same by using the ctl action.  This is useful if you want to only update the targets for a particular URL
 
-SecRule REQUEST_FILENAME "@streq /path/to/file.php" "phase:1,id:2,t:none,nolog,pass,ctl:ruleUpdateTargetById=958895;!ARGS:email"
+SecRule REQUEST_FILENAME "@streq /path/to/file.php" "phase:1,id:2,t:none,nolog,pass,ctl:ruleUpdateTargetById=958895;!ARGS:email"
 

-
Conditionally Replacing Targets
-
You could also replace targets using the ctl action.  For example, lets say you want to only inspect ARGS for a particular URL:
-

-
-SecRule REQUEST_FILENAME "@streq /path/to/file.php" "phase:1,id:3,t:none,nolog,pass,ctl:ruleUpdateTargetById=958895;REQUEST_URI;REQUEST_FILENAME"
 
+'''Conditionally Replacing Targets'''
+
+You could also replace targets using the ctl action.  For example, lets say you want to only inspect ARGS for a particular URL:
+
+SecRule REQUEST_FILENAME "@streq /path/to/file.php" "phase:1,id:3,t:none,nolog,pass,ctl:ruleUpdateTargetById=958895;REQUEST_URI;REQUEST_FILENAME"
 

-
 Note 
 This ctl is deprecated and will be removed from the code, since we cannot use it per-transaction. Please use the new ruleRemoveTargetById ctl option if you want to remove a target or target list per-transaction.
-

-
[edit]  SecRuleUpdateTargetByMsg 

-
Description: Updates the target (variable) list of the specified rule by rule message.
-
Syntax: SecRuleUpdateTargetByMsg TEXT TARGET1[,TARGET2,TARGET3] REPLACED_TARGET
 
-
Example Usage: SecRuleUpdateTargetByMsg "Cross-site Scripting (XSS) Attack" "!ARGS:foo"
-
Scope: Any
-
Version: 2.7
-
This directive will append (or replace) variables to the current target list of the specified rule with the targets provided in the second parameter.
-
Explicitly Appending Targets
-
This is useful for implementing exceptions where you want to externally update a target list to exclude inspection of specific variable(s).
-

+; Note : This ctl is deprecated and will be removed from the code, since we cannot use it per-transaction. Please use the new ruleRemoveTargetById ctl option if you want to remove a target or target list per-transaction.
+
+== SecRuleUpdateTargetByMsg ==
+'''Description:''' Updates the target (variable) list of the specified rule by rule message.
+
+'''Syntax:''' SecRuleUpdateTargetByMsg TEXT TARGET1[,TARGET2,TARGET3] REPLACED_TARGET
+
+'''Example Usage:''' SecRuleUpdateTargetByMsg "Cross-site Scripting (XSS) Attack" "!ARGS:foo"
+
+'''Scope:''' Any
+
+'''Version:''' 2.7
+
+This directive will append (or replace) variables to the current target list of the specified rule with the targets provided in the second parameter.
+
+'''Explicitly Appending Targets'''
+
+This is useful for implementing exceptions where you want to externally update a target list to exclude inspection of specific variable(s).
 
-SecRule REQUEST_FILENAME|ARGS_NAMES|ARGS|XML:/* "[\;\|\`]\W*?\bmail\b" \
-     "phase:2,rev:'2.1.1',capture,t:none,t:htmlEntityDecode,t:compressWhitespace,t:lowercase,ctl:auditLogParts=+E,block,msg:'System Command Injection',id:'958895',tag:'WEB_ATTACK/COMMAND_INJECTION',tag:'WASCTC/WASC-31',tag:'OWASP_TOP_10/A1',tag:'PCI/6.5.2',logdata:'%{TX.0}',severity:'2',setvar:'tx.msg=%{rule.msg}',setvar:tx.anomaly_score=+%{tx.critical_anomaly_score},setvar:tx.command_injection_score=+%{tx.critical_anomaly_score},setvar:tx.%{rule.id}-WEB_ATTACK/COMMAND_INJECTION-%{matched_var_name}=%
-{tx.0}"
+SecRule REQUEST_FILENAME|ARGS_NAMES|ARGS|XML:/* "[\;\|\`]\W*?\bmail\b" \
+     "phase:2,rev:'2.1.1',capture,t:none,t:htmlEntityDecode,t:compressWhitespace,t:lowercase,ctl:auditLogParts=+E,block,msg:'System Command Injection',id:'958895',tag:'WEB_ATTACK/COMMAND_INJECTION',tag:'WASCTC/WASC-31',tag:'OWASP_TOP_10/A1',tag:'PCI/6.5.2',logdata:'%{TX.0}',severity:'2',setvar:'tx.msg=%{rule.msg}',setvar:tx.anomaly_score=+%{tx.critical_anomaly_score},setvar:tx.command_injection_score=+%{tx.critical_anomaly_score},setvar:tx.%{rule.id}-WEB_ATTACK/COMMAND_INJECTION-%{matched_var_name}=%
+{tx.0}"
 
-SecRuleUpdateTargetByMsg "System Command Injection" !ARGS:email
+SecRuleUpdateTargetByMsg "System Command Injection" !ARGS:email
 

-
The effective resulting rule in the previous example will append the target to the end of the variable list as follows:
-

+The effective resulting rule in the previous example will append the target to the end of the variable list as follows:
 
-SecRule REQUEST_FILENAME|ARGS_NAMES|ARGS|XML:/*|!ARGS:email "[\;\|\`]\W*?\bmail\b" \
-     "phase:2,rev:'2.1.1',capture,t:none,t:htmlEntityDecode,t:compressWhitespace,t:lowercase,ctl:auditLogParts=+E,block,msg:'System Command Injection',id:'958895',tag:'WEB_ATTACK/COMMAND_INJECTION',tag:'WASCTC/WASC-31',tag:'OWASP_TOP_10/A1',tag:'PCI/6.5.2',logdata:'%{TX.0}',severity:'2',setvar:'tx.msg=%{rule.msg}',setvar:tx.anomaly_score=+%{tx.critical_anomaly_score},setvar:tx.command_injection_score=+%{tx.critical_anomaly_score},setvar:tx.%{rule.id}-WEB_ATTACK/COMMAND_INJECTION-%{matched_var_name}=%
-{tx.0}""
+SecRule REQUEST_FILENAME|ARGS_NAMES|ARGS|XML:/*|!ARGS:email "[\;\|\`]\W*?\bmail\b" \
+     "phase:2,rev:'2.1.1',capture,t:none,t:htmlEntityDecode,t:compressWhitespace,t:lowercase,ctl:auditLogParts=+E,block,msg:'System Command Injection',id:'958895',tag:'WEB_ATTACK/COMMAND_INJECTION',tag:'WASCTC/WASC-31',tag:'OWASP_TOP_10/A1',tag:'PCI/6.5.2',logdata:'%{TX.0}',severity:'2',setvar:'tx.msg=%{rule.msg}',setvar:tx.anomaly_score=+%{tx.critical_anomaly_score},setvar:tx.command_injection_score=+%{tx.critical_anomaly_score},setvar:tx.%{rule.id}-WEB_ATTACK/COMMAND_INJECTION-%{matched_var_name}=%
+{tx.0}""
 

-
Explicitly Replacing Targets
+'''Explicitly Replacing Targets'''
 
-
You can also entirely replace the target list to something more appropriate for your environment.  For example, lets say you want to inspect REQUEST_URI instead of REQUEST_FILENAME, you could do this:
-

+You can also entirely replace the target list to something more appropriate for your environment.  For example, lets say you want to inspect REQUEST_URI instead of REQUEST_FILENAME, you could do this:
 
-SecRule REQUEST_FILENAME|ARGS_NAMES|ARGS|XML:/* "[\;\|\`]\W*?\bmail\b" \
-     "phase:2,rev:'2.1.1',capture,t:none,t:htmlEntityDecode,t:compressWhitespace,t:lowercase,ctl:auditLogParts=+E,block,msg:'System Command Injection',id:'958895',tag:'WEB_ATTACK/COMMAND_INJECTION',tag:'WASCTC/WASC-31',tag:'OWASP_TOP_10/A1',tag:'PCI/6.5.2',logdata:'%{TX.0}',severity:'2',setvar:'tx.msg=%{rule.msg}',setvar:tx.anomaly_score=+%{tx.critical_anomaly_score},setvar:tx.command_injection_score=+%{tx.critical_anomaly_score},setvar:tx.%{rule.id}-WEB_ATTACK/COMMAND_INJECTION-%{matched_var_name}=%
-{tx.0}"
+SecRule REQUEST_FILENAME|ARGS_NAMES|ARGS|XML:/* "[\;\|\`]\W*?\bmail\b" \
+     "phase:2,rev:'2.1.1',capture,t:none,t:htmlEntityDecode,t:compressWhitespace,t:lowercase,ctl:auditLogParts=+E,block,msg:'System Command Injection',id:'958895',tag:'WEB_ATTACK/COMMAND_INJECTION',tag:'WASCTC/WASC-31',tag:'OWASP_TOP_10/A1',tag:'PCI/6.5.2',logdata:'%{TX.0}',severity:'2',setvar:'tx.msg=%{rule.msg}',setvar:tx.anomaly_score=+%{tx.critical_anomaly_score},setvar:tx.command_injection_score=+%{tx.critical_anomaly_score},setvar:tx.%{rule.id}-WEB_ATTACK/COMMAND_INJECTION-%{matched_var_name}=%
+{tx.0}"
 
-SecRuleUpdateTargetByMsg "System Command Injection" REQUEST_URI REQUEST_FILENAME
+SecRuleUpdateTargetByMsg "System Command Injection" REQUEST_URI REQUEST_FILENAME
 

-
The effective resulting rule in the previous example will append the target to the end of the variable list as follows:
-

-
+The effective resulting rule in the previous example will append the target to the end of the variable list as follows:
 
-SecRule REQUEST_URI|ARGS_NAMES|ARGS|XML:/* "[\;\|\`]\W*?\bmail\b" \
-     "phase:2,rev:'2.1.1',capture,t:none,t:htmlEntityDecode,t:compressWhitespace,t:lowercase,ctl:auditLogParts=+E,block,msg:'System Command Injection',id:'958895',tag:'WEB_ATTACK/COMMAND_INJECTION',tag:'WASCTC/WASC-31',tag:'OWASP_TOP_10/A1',tag:'PCI/6.5.2',logdata:'%{TX.0}',severity:'2',setvar:'tx.msg=%{rule.msg}',setvar:tx.anomaly_score=+%{tx.critical_anomaly_score},setvar:tx.command_injection_score=+%{tx.critical_anomaly_score},setvar:tx.%{rule.id}-WEB_ATTACK/COMMAND_INJECTION-%{matched_var_name}=%
-{tx.0}""
+SecRule REQUEST_URI|ARGS_NAMES|ARGS|XML:/* "[\;\|\`]\W*?\bmail\b" \
+     "phase:2,rev:'2.1.1',capture,t:none,t:htmlEntityDecode,t:compressWhitespace,t:lowercase,ctl:auditLogParts=+E,block,msg:'System Command Injection',id:'958895',tag:'WEB_ATTACK/COMMAND_INJECTION',tag:'WASCTC/WASC-31',tag:'OWASP_TOP_10/A1',tag:'PCI/6.5.2',logdata:'%{TX.0}',severity:'2',setvar:'tx.msg=%{rule.msg}',setvar:tx.anomaly_score=+%{tx.critical_anomaly_score},setvar:tx.command_injection_score=+%{tx.critical_anomaly_score},setvar:tx.%{rule.id}-WEB_ATTACK/COMMAND_INJECTION-%{matched_var_name}=%
+{tx.0}""
 

-
[edit]  SecRuleUpdateTargetByTag 

-
Description: Updates the target (variable) list of the specified rule by rule tag.
 
-
Syntax: SecRuleUpdateTargetByTag TEXT TARGET1[,TARGET2,TARGET3] REPLACED_TARGET
-
Example Usage: SecRuleUpdateTargetByTag "WEB_ATTACK/XSS" "!ARGS:foo"
-
Scope: Any
-
Version: 2.7
-
This directive will append (or replace) variables to the current target list of the specified rule with the targets provided in the second parameter.
-
Explicitly Appending Targets
+== SecRuleUpdateTargetByTag ==
+'''Description:''' Updates the target (variable) list of the specified rule by rule tag.
 
-
This is useful for implementing exceptions where you want to externally update a target list to exclude inspection of specific variable(s).
-

+'''Syntax:''' SecRuleUpdateTargetByTag TEXT TARGET1[,TARGET2,TARGET3] REPLACED_TARGET
+
+'''Example Usage:''' SecRuleUpdateTargetByTag "WEB_ATTACK/XSS" "!ARGS:foo"
+
+'''Scope:''' Any
+
+'''Version:''' 2.7
+
+This directive will append (or replace) variables to the current target list of the specified rule with the targets provided in the second parameter.
+
+'''Explicitly Appending Targets'''
+
+This is useful for implementing exceptions where you want to externally update a target list to exclude inspection of specific variable(s).
 
-SecRule REQUEST_FILENAME|ARGS_NAMES|ARGS|XML:/* "[\;\|\`]\W*?\bmail\b" \
-     "phase:2,rev:'2.1.1',capture,t:none,t:htmlEntityDecode,t:compressWhitespace,t:lowercase,ctl:auditLogParts=+E,block,msg:'System Command Injection',id:'958895',tag:'WEB_ATTACK/COMMAND_INJECTION',tag:'WASCTC/WASC-31',tag:'OWASP_TOP_10/A1',tag:'PCI/6.5.2',logdata:'%{TX.0}',severity:'2',setvar:'tx.msg=%{rule.msg}',setvar:tx.anomaly_score=+%{tx.critical_anomaly_score},setvar:tx.command_injection_score=+%{tx.critical_anomaly_score},setvar:tx.%{rule.id}-WEB_ATTACK/COMMAND_INJECTION-%{matched_var_name}=%
-{tx.0}"
+SecRule REQUEST_FILENAME|ARGS_NAMES|ARGS|XML:/* "[\;\|\`]\W*?\bmail\b" \
+     "phase:2,rev:'2.1.1',capture,t:none,t:htmlEntityDecode,t:compressWhitespace,t:lowercase,ctl:auditLogParts=+E,block,msg:'System Command Injection',id:'958895',tag:'WEB_ATTACK/COMMAND_INJECTION',tag:'WASCTC/WASC-31',tag:'OWASP_TOP_10/A1',tag:'PCI/6.5.2',logdata:'%{TX.0}',severity:'2',setvar:'tx.msg=%{rule.msg}',setvar:tx.anomaly_score=+%{tx.critical_anomaly_score},setvar:tx.command_injection_score=+%{tx.critical_anomaly_score},setvar:tx.%{rule.id}-WEB_ATTACK/COMMAND_INJECTION-%{matched_var_name}=%
+{tx.0}"
 
-SecRuleUpdateTargetByTag "WASCTC/WASC-31" !ARGS:email
+SecRuleUpdateTargetByTag "WASCTC/WASC-31" !ARGS:email
 

-
The effective resulting rule in the previous example will append the target to the end of the variable list as follows:
-

+The effective resulting rule in the previous example will append the target to the end of the variable list as follows:
 
-
-SecRule REQUEST_FILENAME|ARGS_NAMES|ARGS|XML:/*|!ARGS:email "[\;\|\`]\W*?\bmail\b" \
-     "phase:2,rev:'2.1.1',capture,t:none,t:htmlEntityDecode,t:compressWhitespace,t:lowercase,ctl:auditLogParts=+E,block,msg:'System Command Injection',id:'958895',tag:'WEB_ATTACK/COMMAND_INJECTION',tag:'WASCTC/WASC-31',tag:'OWASP_TOP_10/A1',tag:'PCI/6.5.2',logdata:'%{TX.0}',severity:'2',setvar:'tx.msg=%{rule.msg}',setvar:tx.anomaly_score=+%{tx.critical_anomaly_score},setvar:tx.command_injection_score=+%{tx.critical_anomaly_score},setvar:tx.%{rule.id}-WEB_ATTACK/COMMAND_INJECTION-%{matched_var_name}=%
-{tx.0}""
+SecRule REQUEST_FILENAME|ARGS_NAMES|ARGS|XML:/*|!ARGS:email "[\;\|\`]\W*?\bmail\b" \
+     "phase:2,rev:'2.1.1',capture,t:none,t:htmlEntityDecode,t:compressWhitespace,t:lowercase,ctl:auditLogParts=+E,block,msg:'System Command Injection',id:'958895',tag:'WEB_ATTACK/COMMAND_INJECTION',tag:'WASCTC/WASC-31',tag:'OWASP_TOP_10/A1',tag:'PCI/6.5.2',logdata:'%{TX.0}',severity:'2',setvar:'tx.msg=%{rule.msg}',setvar:tx.anomaly_score=+%{tx.critical_anomaly_score},setvar:tx.command_injection_score=+%{tx.critical_anomaly_score},setvar:tx.%{rule.id}-WEB_ATTACK/COMMAND_INJECTION-%{matched_var_name}=%
+{tx.0}""
 

-
Explicitly Replacing Targets
-
You can also entirely replace the target list to something more appropriate for your environment.  For example, lets say you want to inspect REQUEST_URI instead of REQUEST_FILENAME, you could do this:
-

-
-SecRule REQUEST_FILENAME|ARGS_NAMES|ARGS|XML:/* "[\;\|\`]\W*?\bmail\b" \
-     "phase:2,rev:'2.1.1',capture,t:none,t:htmlEntityDecode,t:compressWhitespace,t:lowercase,ctl:auditLogParts=+E,block,msg:'System Command Injection',id:'958895',tag:'WEB_ATTACK/COMMAND_INJECTION',tag:'WASCTC/WASC-31',tag:'OWASP_TOP_10/A1',tag:'PCI/6.5.2',logdata:'%{TX.0}',severity:'2',setvar:'tx.msg=%{rule.msg}',setvar:tx.anomaly_score=+%{tx.critical_anomaly_score},setvar:tx.command_injection_score=+%{tx.critical_anomaly_score},setvar:tx.%{rule.id}-WEB_ATTACK/COMMAND_INJECTION-%{matched_var_name}=%
-{tx.0}"
+'''Explicitly Replacing Targets'''
 
-SecRuleUpdateTargetByTag "WASCTC/WASC-31" REQUEST_URI REQUEST_FILENAME
+You can also entirely replace the target list to something more appropriate for your environment.  For example, lets say you want to inspect REQUEST_URI instead of REQUEST_FILENAME, you could do this:
+
+SecRule REQUEST_FILENAME|ARGS_NAMES|ARGS|XML:/* "[\;\|\`]\W*?\bmail\b" \
+     "phase:2,rev:'2.1.1',capture,t:none,t:htmlEntityDecode,t:compressWhitespace,t:lowercase,ctl:auditLogParts=+E,block,msg:'System Command Injection',id:'958895',tag:'WEB_ATTACK/COMMAND_INJECTION',tag:'WASCTC/WASC-31',tag:'OWASP_TOP_10/A1',tag:'PCI/6.5.2',logdata:'%{TX.0}',severity:'2',setvar:'tx.msg=%{rule.msg}',setvar:tx.anomaly_score=+%{tx.critical_anomaly_score},setvar:tx.command_injection_score=+%{tx.critical_anomaly_score},setvar:tx.%{rule.id}-WEB_ATTACK/COMMAND_INJECTION-%{matched_var_name}=%
+{tx.0}"
+
+SecRuleUpdateTargetByTag "WASCTC/WASC-31" REQUEST_URI REQUEST_FILENAME
 

-
The effective resulting rule in the previous example will append the target to the end of the variable list as follows:
-

+The effective resulting rule in the previous example will append the target to the end of the variable list as follows:
 
-SecRule REQUEST_URI|ARGS_NAMES|ARGS|XML:/* "[\;\|\`]\W*?\bmail\b" \
-     "phase:2,rev:'2.1.1',capture,t:none,t:htmlEntityDecode,t:compressWhitespace,t:lowercase,ctl:auditLogParts=+E,block,msg:'System Command Injection',id:'958895',tag:'WEB_ATTACK/COMMAND_INJECTION',tag:'WASCTC/WASC-31',tag:'OWASP_TOP_10/A1',tag:'PCI/6.5.2',logdata:'%{TX.0}',severity:'2',setvar:'tx.msg=%{rule.msg}',setvar:tx.anomaly_score=+%{tx.critical_anomaly_score},setvar:tx.command_injection_score=+%{tx.critical_anomaly_score},setvar:tx.%{rule.id}-WEB_ATTACK/COMMAND_INJECTION-%{matched_var_name}=%
-{tx.0}""
+SecRule REQUEST_URI|ARGS_NAMES|ARGS|XML:/* "[\;\|\`]\W*?\bmail\b" \
+     "phase:2,rev:'2.1.1',capture,t:none,t:htmlEntityDecode,t:compressWhitespace,t:lowercase,ctl:auditLogParts=+E,block,msg:'System Command Injection',id:'958895',tag:'WEB_ATTACK/COMMAND_INJECTION',tag:'WASCTC/WASC-31',tag:'OWASP_TOP_10/A1',tag:'PCI/6.5.2',logdata:'%{TX.0}',severity:'2',setvar:'tx.msg=%{rule.msg}',setvar:tx.anomaly_score=+%{tx.critical_anomaly_score},setvar:tx.command_injection_score=+%{tx.critical_anomaly_score},setvar:tx.%{rule.id}-WEB_ATTACK/COMMAND_INJECTION-%{matched_var_name}=%
+{tx.0}""
 

-
[edit]  SecServerSignature 

 
-
Description: Instructs ModSecurity to change the data presented in the "Server:" response header token.
-
Syntax: SecServerSignature "WEB SERVER SOFTWARE"
-
Example Usage: SecServerSignature "Microsoft-IIS/6.0"
-
Scope: Main
-
Version: 2.0.0
+== SecServerSignature ==
+'''Description:''' Instructs ModSecurity to change the data presented in the "Server:" response header token.
 
-
In order for this directive to work, you must set the Apache ServerTokens directive to Full. ModSecurity will overwrite the server signature data held in this memory space with the data set in this directive. If ServerTokens is not set to Full, then the memory space is most likely not large enough to hold the new data we are looking to insert.
-

-
[edit]  SecStreamInBodyInspection 

-
Description: Configures the ability to use stream inspection for inbound request data in a re-allocable buffer. For security reasons we are still buffering the stream. 
-
Syntax: SecStreamInBodyInspection On|Off
-
Example Usage: SecStreamInBodyInspection On
+'''Syntax:''' SecServerSignature "WEB SERVER SOFTWARE"
 
-
Scope: Any
-
Version: 2.6.0
-
Default: Off
-
This feature enables the creation of the STREAM_INPUT_BODY variable and is useful for data modification or to match data in raw data for any content-types.
-

-
 Note 
 This directive provides full access to REQUEST_BODY payload data.  It does not include REQUEST_URI or REQUEST_HEADER data. Also it provides data to all kind of content types, different than REQUEST_BODY.
-

-
[edit]  SecStreamOutBodyInspection 

+'''Example Usage:''' SecServerSignature "Microsoft-IIS/6.0"
 
-
Description: Configures the ability to use stream inspection for outbound request data in a re-allocable buffer.  For security reasons we are still buffering the stream.
-
Syntax: SecStreamOutBodyInspection On|Off
-
Example Usage: SecStreamOutBodyInspection On
-
Scope: Any
-
Version: 2.6.0
+'''Scope:''' Main
 
-
Default: Off
-
This feature enables the creation of the STREAM_OUTPUT_BODY variable and is useful when you need to do data modification into response body.
-

-
 Note 
 This directive provides access to RESPONSE_BODY payload data. It does not include RESPONSE_HEADER data.
-

-
[edit]  SecTmpDir 

+'''Version:''' 2.0.0
 
-
Description: Configures the directory where temporary files will be created.
-
Syntax: SecTmpDir /path/to/dir
-
Example Usage: SecTmpDir /tmp
-
Scope: Any
-
Version: 2.0.0
+In order for this directive to work, you must set the Apache ServerTokens directive to Full. ModSecurity will overwrite the server signature data held in this memory space with the data set in this directive. If ServerTokens is not set to Full, then the memory space is most likely not large enough to hold the new data we are looking to insert.
 
-
The location specified needs to be writable by the Apache user process. This is the directory location where ModSecurity will swap data to disk if it runs out of memory (more data than what was specified in the SecRequestBodyInMemoryLimit directive) during inspection.
-

-
[edit]  SecUnicodeMapFile 

-
Description: Defines the path to the file that will be used by the urlDecodeUni transformation function to map Unicode code points during normalization.
-
Syntax: SecUnicodeMapFile /path/to/unicode.mapping
-
Example Usage: SecUnicodeMapFile /usr/local/apache/conf/crs/unicode.mapping
+== SecStreamInBodyInspection ==
+'''Description:''' Configures the ability to use stream inspection for inbound request data in a re-allocable buffer. For security reasons we are still buffering the stream. 
 
-
Scope: Any
-
Version: 2.6.1
-

-
[edit]  SecUnicodeCodePage 

-
Description: Defines which Unicode code point will be used by the urlDecodeUni transformation function during normalization.
+'''Syntax:''' SecStreamInBodyInspection On|Off
 
-
Syntax: SecUnicodeCodePage XXXXX
-
Example Usage: SecUnicodeCodePage 20127
-
Scope: Any
-
Version: 2.6.1
-

-
[edit]  SecUploadDir 

+'''Example Usage:''' SecStreamInBodyInspection On
 
-
Description: Configures the directory where intercepted files will be stored.
-
Syntax: SecUploadDir /path/to/dir
-
Example Usage: SecUploadDir /tmp
-
Scope: Any
-
Version: 2.0.0
+'''Scope:''' Any
 
-
This directory must be on the same filesystem as the temporary directory defined with SecTmpDir. This directive is used with SecUploadKeepFiles.
-

-
[edit]  SecUploadFileLimit 

-
Description: Configures the maximum number of file uploads processed in a multipart POST.
-
Syntax: SecUploadFileLimit number
-
Example Usage: SecUploadFileLimit 10
+'''Version:''' 2.6.0
 
-
Scope: Any
-
Version: 2.5.12
-
The default is set to 100 files, but you are encouraged to reduce this value. Any file over the limit will not be extracted and the MULTIPART_FILE_LIMIT_EXCEEDED and MULTIPART_STRICT_ERROR flags will be set. To prevent bypassing any file checks, you must check for one of these flags.
-

-
 Note 
 If the limit is exceeded, the part name and file name will still be recorded in FILES_NAME and FILES, the file size will be recorded in FILES_SIZES, but there will be no record in FILES_TMPNAMES as a temporary file was not created.
-

-
[edit]  SecUploadFileMode 

+'''Default:''' Off
 
-
Description: Configures the mode (permissions) of any uploaded files using an octal mode (as used in chmod).
-
Syntax: SecUploadFileMode octal_mode|"default"
-
Example Usage: SecUploadFileMode 0640
-
Scope: Any
-
Version: 2.1.6
+This feature enables the creation of the STREAM_INPUT_BODY variable and is useful for data modification or to match data in raw data for any content-types.
 
-
This feature is not available on operating systems not supporting octal file modes. The default mode (0600) only grants read/write access to the account writing the file. If access from another account is needed (using clamd is a good example), then this directive may be required. However, use this directive with caution to avoid exposing potentially sensitive data to unauthorized users. Using the value "default" will revert back to the default setting.
-

-
 Note 
 The process umask may still limit the mode if it is being more restrictive than the mode set using this directive.
-

-
[edit]  SecUploadKeepFiles 

-
Description: Configures whether or not the intercepted files will be kept after transaction is processed.
+; Note : This directive provides full access to REQUEST_BODY payload data.  It does not include REQUEST_URI or REQUEST_HEADER data. Also it provides data to all kind of content types, different than REQUEST_BODY.
 
-
Syntax: SecUploadKeepFiles On|Off|RelevantOnly
-
Example Usage: SecUploadKeepFiles On
-
Scope: Any
-
Version: 2.0.0
-
This directive requires the storage directory to be defined (using SecUploadDir).
-
Possible values are:
-

+== SecStreamOutBodyInspection ==
+'''Description:''' Configures the ability to use stream inspection for outbound request data in a re-allocable buffer.  For security reasons we are still buffering the stream.
 
-
  • On - Keep uploaded files.
-
  • Off - Do not keep uploaded files.
-
  • RelevantOnly - This will keep only those files that belong to requests that are deemed relevant.
-

-
[edit]  SecWebAppId 

+'''Syntax:''' SecStreamOutBodyInspection On|Off
 
-
Description: Creates an application namespace, allowing for separate persistent session and user storage.
-
Syntax: SecWebAppId "NAME" 
-
Example Usage: SecWebAppId "WebApp1" 
-
Scope: Any 
-
Version: 2.0.0 
+'''Example Usage:''' SecStreamOutBodyInspection On
 
-
Default: default
-
Application namespaces are used to avoid collisions between session IDs and user IDs when multiple applications are deployed on the same server. If it isn’t used, a collision between session IDs might occur.
-

+'''Scope:''' Any
+
+'''Version:''' 2.6.0
+
+'''Default:''' Off
+
+This feature enables the creation of the STREAM_OUTPUT_BODY variable and is useful when you need to do data modification into response body.
+
+; Note : This directive provides access to RESPONSE_BODY payload data. It does not include RESPONSE_HEADER data.
+
+== SecTmpDir ==
+'''Description:''' Configures the directory where temporary files will be created.
+
+'''Syntax:''' SecTmpDir /path/to/dir
+
+'''Example Usage:''' SecTmpDir /tmp
+
+'''Scope:''' Any
+
+'''Version:''' 2.0.0
+
+The location specified needs to be writable by the Apache user process. This is the directory location where ModSecurity will swap data to disk if it runs out of memory (more data than what was specified in the SecRequestBodyInMemoryLimit directive) during inspection.
+
+== SecUnicodeMapFile ==
+'''Description:''' Defines the path to the file that will be used by the urlDecodeUni transformation function to map Unicode code points during normalization.
+
+'''Syntax:''' SecUnicodeMapFile /path/to/unicode.mapping
+
+'''Example Usage:''' SecUnicodeMapFile /usr/local/apache/conf/crs/unicode.mapping
+
+'''Scope:''' Any
+
+'''Version:''' 2.6.1
+
+== SecUnicodeCodePage ==
+'''Description:''' Defines which Unicode code point will be used by the urlDecodeUni transformation function during normalization.
+
+'''Syntax:''' SecUnicodeCodePage XXXXX
+
+'''Example Usage:''' SecUnicodeCodePage 20127
+
+'''Scope:''' Any
+
+'''Version:''' 2.6.1
+
+== SecUploadDir ==
+'''Description:''' Configures the directory where intercepted files will be stored.
+
+'''Syntax:''' SecUploadDir /path/to/dir
+
+'''Example Usage:''' SecUploadDir /tmp
+
+'''Scope:''' Any
+
+'''Version:''' 2.0.0
+
+This directory must be on the same filesystem as the temporary directory defined with SecTmpDir. This directive is used with SecUploadKeepFiles.
+
+== SecUploadFileLimit ==
+'''Description:''' Configures the maximum number of file uploads processed in a multipart POST.
+
+'''Syntax:''' SecUploadFileLimit number
+
+'''Example Usage:''' SecUploadFileLimit 10
+
+'''Scope:''' Any
+
+'''Version:''' 2.5.12
+
+The default is set to 100 files, but you are encouraged to reduce this value. Any file over the limit will not be extracted and the MULTIPART_FILE_LIMIT_EXCEEDED and MULTIPART_STRICT_ERROR flags will be set. To prevent bypassing any file checks, you must check for one of these flags.
+
+; Note : If the limit is exceeded, the part name and file name will still be recorded in FILES_NAME and FILES, the file size will be recorded in FILES_SIZES, but there will be no record in FILES_TMPNAMES as a temporary file was not created.
+
+== SecUploadFileMode ==
+'''Description:''' Configures the mode (permissions) of any uploaded files using an octal mode (as used in chmod).
+
+'''Syntax:''' SecUploadFileMode octal_mode|"default"
+
+'''Example Usage:''' SecUploadFileMode 0640
+
+'''Scope:''' Any
+
+'''Version:''' 2.1.6
+
+This feature is not available on operating systems not supporting octal file modes. The default mode (0600) only grants read/write access to the account writing the file. If access from another account is needed (using clamd is a good example), then this directive may be required. However, use this directive with caution to avoid exposing potentially sensitive data to unauthorized users. Using the value "default" will revert back to the default setting.
+
+; Note : The process umask may still limit the mode if it is being more restrictive than the mode set using this directive.
+
+== SecUploadKeepFiles ==
+'''Description:''' Configures whether or not the intercepted files will be kept after transaction is processed.
+
+'''Syntax:''' SecUploadKeepFiles On|Off|RelevantOnly
+
+'''Example Usage:''' SecUploadKeepFiles On
+
+'''Scope:''' Any
+
+'''Version:''' 2.0.0
+
+This directive requires the storage directory to be defined (using SecUploadDir).
+
+Possible values are:
+
+*'''On''' - Keep uploaded files.
+*'''Off''' - Do not keep uploaded files.
+*'''RelevantOnly''' - This will keep only those files that belong to requests that are deemed relevant.
+
+== SecWebAppId ==
+'''Description:''' Creates an application namespace, allowing for separate persistent session and user storage.
+
+'''Syntax:''' SecWebAppId "NAME" 
+
+'''Example Usage:''' SecWebAppId "WebApp1" 
+
+'''Scope:''' Any 
+
+'''Version:''' 2.0.0 
+
+'''Default:''' default
+
+Application namespaces are used to avoid collisions between session IDs and user IDs when multiple applications are deployed on the same server. If it isn’t used, a collision between session IDs might occur.
 
-<VirtualHost *:80> 
+ 
 ServerName app1.example.com 
-SecWebAppId "App1" ...
-</VirtualHost>
-
-<VirtualHost *:80> 
+SecWebAppId "App1" ...
+
 
+ 
 ServerName app2.example.com 
-SecWebAppId "App2" ...
-</VirtualHost>
+SecWebAppId "App2" ...
+
 

-
In the two examples configurations shown, SecWebAppId is being used in conjunction with the Apache VirtualHost directives. Applications namespace information is also recorded in the audit logs (using the WebApp-Info header of the H part).
-
This directive is used to set collections timeout. For example:
-

+In the two examples configurations shown, SecWebAppId is being used in conjunction with the Apache VirtualHost directives. Applications namespace information is also recorded in the audit logs (using the WebApp-Info header of the H part).
+
+This directive is used to set collections timeout. For example:
 
SecCollectionTimeout 500

-
[edit]  SecCollectionTimeout 

+== SecCollectionTimeout ==
+'''Description:''' Specifies the collections timeout. Default is 3600 seconds.
 
-
Description: Specifies the collections timeout. Default is 3600 seconds.
-
Syntax: SecCollectionTimeout seconds
-
Default: 3600 
-
Scope: Any
-
Version: 2.6.3
-

+'''Syntax:''' SecCollectionTimeout seconds
 
-
[edit]  Processing Phases 

-
ModSecurity 2.x allows rules to be placed in one of the following five phases of the Apache request cycle:
-

-
  • Request headers (REQUEST_HEADERS)
-
  • Request body (REQUEST_BODY)
-
  • Response headers (RESPONSE_HEADERS)
-
  • Response body (RESPONSE_BODY)
-
  • Logging (LOGGING)
-

-
Below is a diagram of the standard Apache Request Cycle. In the diagram, the 5 ModSecurity processing phases are shown.
-

+'''Default:''' 3600 
 
-
In order to select the phase a rule executes during, use the phase action either directly in the rule or in using the SecDefaultAction directive:
-

+'''Scope:''' Any
+
+'''Version:''' 2.6.3
+
+= Processing Phases =
+ModSecurity 2.x allows rules to be placed in one of the following five phases of the Apache request cycle:
+*Request headers (REQUEST_HEADERS)
+*Request body (REQUEST_BODY)
+*Response headers (RESPONSE_HEADERS)
+*Response body (RESPONSE_BODY)
+*Logging (LOGGING)
+
+Below is a diagram of the standard Apache Request Cycle. In the diagram, the 5 ModSecurity processing phases are shown.
+
+[[File:Apache_request_cycle-modsecurity.jpg|600px]]
+
+In order to select the phase a rule executes during, use the phase action either directly in the rule or in using the SecDefaultAction directive:
 
-SecDefaultAction "log,pass,phase:2,id:4"
-SecRule REQUEST_HEADERS:Host "!^$" "deny,phase:1,id:5"
+SecDefaultAction "log,pass,phase:2,id:4"
+SecRule REQUEST_HEADERS:Host "!^$" "deny,phase:1,id:5"
 

-
 Note 
 The data available in each phase is cumulative.  This means that as you move onto later phases, you have access to more and more data from the transaction.
-
 Note 
 Keep in mind that rules are executed according to phases, so even if two rules are adjacent in a configuration file, but are set to execute in different phases, they would not happen one after the other. The order of rules in the configuration file is important only within the rules of each phase. This is especially important when using the skip and skipAfter actions.
+; Note : The data available in each phase is cumulative.  This means that as you move onto later phases, you have access to more and more data from the transaction.
+; Note : Keep in mind that rules are executed according to phases, so even if two rules are adjacent in a configuration file, but are set to execute in different phases, they would not happen one after the other. The order of rules in the configuration file is important only within the rules of each phase. This is especially important when using the skip and skipAfter actions.
 
-

-
 Note 
 The LOGGING phase is special. It is executed at the end of each transaction no matter what happened in the previous phases. This means it will be processed even if the request was intercepted or the allow action was used to pass the transaction through.
-

-
[edit]  Phase Request Headers 

-
Rules in this phase are processed immediately after Apache completes reading the request headers (post-read-request phase). At this point the request body has not been read yet, meaning not all request arguments are available. Rules should be placed in this phase if you need to have them run early (before Apache does something with the request), to do something before the request body has been read, determine whether or not the request body should be buffered, or decide how you want the request body to be processed (e.g. whether to parse it as XML or not).
-

-
 Note 
 Rules in this phase can not leverage Apache scope directives (Directory, Location, LocationMatch, etc...) as the post-read-request hook does not have this information yet. The exception here is the VirtualHost directive. If you want to use ModSecurity rules inside Apache locations, then they should run in Phase 2. Refer to the Apache Request Cycle/ModSecurity Processing Phases diagram.
+; Note : The LOGGING phase is special. It is executed at the end of each transaction no matter what happened in the previous phases. This means it will be processed even if the request was intercepted or the allow action was used to pass the transaction through.
+== Phase Request Headers ==
+Rules in this phase are processed immediately after Apache completes reading the request headers (post-read-request phase). At this point the request body has not been read yet, meaning not all request arguments are available. Rules should be placed in this phase if you need to have them run early (before Apache does something with the request), to do something before the request body has been read, determine whether or not the request body should be buffered, or decide how you want the request body to be processed (e.g. whether to parse it as XML or not).
 
-

-
[edit]  Phase Request Body 

-
This is the general-purpose input analysis phase. Most of the application-oriented rules should go here. In this phase you are guaranteed to have received the request arguments (provided the request body has been read). ModSecurity supports three encoding types for the request body phase:
-

-
  • application/x-www-form-urlencoded - used to transfer form data
-
  • multipart/form-data - used for file transfers
-
  • text/xml - used for passing XML data
+; Note : Rules in this phase can not leverage Apache scope directives (Directory, Location, LocationMatch, etc...) as the post-read-request hook does not have this information yet. The exception here is the VirtualHost directive. If you want to use ModSecurity rules inside Apache locations, then they should run in Phase 2. Refer to the Apache Request Cycle/ModSecurity Processing Phases diagram.
 
-

-
Other encodings are not used by most web applications.
-

-
 Note 
 In order to access the Request Body phase data, you must have SecRequestBodyAccess set to On.
-

-
[edit]  Phase Response Headers 

-
This phase takes place just before response headers are sent back to the client. Run here if you want to observe the response before that happens, and if you want to use the response headers to determine if you want to buffer the response body. Note that some response status codes (such as 404) are handled earlier in the request cycle by Apache and my not be able to be triggered as expected. Additionally, there are some response headers that are added by Apache at a later hook (such as Date, Server and Connection) that we would not be able to trigger on or sanitize. This should work appropriately in a proxy setup or within phase:5 (logging).
-

+== Phase Request Body ==
+This is the general-purpose input analysis phase. Most of the application-oriented rules should go here. In this phase you are guaranteed to have received the request arguments (provided the request body has been read). ModSecurity supports three encoding types for the request body phase:
+*'''application/x-www-form-urlencoded''' - used to transfer form data
+*'''multipart/form-data''' - used for file transfers
+*'''text/xml''' - used for passing XML data
 
-
[edit]  Phase Response Body 

-
This is the general-purpose output analysis phase. At this point you can run rules against the response body (provided it was buffered, of course). This is the phase where you would want to inspect the outbound HTML for information disclosure, error messages or failed authentication text.
-

-
 Note 
 In order to access the Response Body phase data, you must have SecResponseBodyAccess set to On
-

-
[edit]  Phase Logging 

+Other encodings are not used by most web applications.
 
-
This phase is run just before logging takes place. The rules placed into this phase can only affect how the logging is performed. This phase can be used to inspect the error messages logged by Apache. You cannot deny/block connections in this phase as it is too late. This phase also allows for inspection of other response headers that weren't available during phase:3 or phase:4. Note that you must be careful not to inherit a disruptive action into a rule in this phase as this is a configuration error in ModSecurity 2.5.0 and later versions
-

-
[edit]  Variables 

-
The following variables are supported in ModSecurity 2.x:
-

-
[edit]  ARGS 

+; Note : In order to access the Request Body phase data, you must have SecRequestBodyAccess set to On.
 
-
ARGS is a collection and can be used on its own (means all arguments including the POST Payload), with a static parameter (matches arguments with that name), or with a regular expression (matches all arguments with name that matches the regular expression). To look at only the query string or body arguments, see the ARGS_GET and ARGS_POST collections.
-
Some variables are actually collections, which are expanded into more variables at runtime. The following example will examine all request arguments:
-
SecRule ARGS dirty "id:7"
-
Sometimes, however, you will want to look only at parts of a collection. This can be achieved with the help of the selection operator(colon). The following example will only look at the arguments named p (do note that, in general, requests can contain multiple arguments with the same name):
-
SecRule ARGS:p dirty "id:8"
-
It is also possible to specify exclusions. The following will examine all request arguments for the word dirty, except the ones named z (again, there can be zero or more arguments named z):
-
SecRule ARGS|!ARGS:z dirty "id:9"
-
There is a special operator that allows you to count how many variables there are in a collection. The following rule will trigger if there is more than zero arguments in the request (ignore the second parameter for the time being):
-
SecRule &ARGS !^0$ "id:10"
-
And sometimes you need to look at an array of parameters, each with a slightly different name. In this case you can specify a regular expression in the selection operator itself. The following rule will look into all arguments whose names begin with id_:
+== Phase Response Headers ==
+This phase takes place just before response headers are sent back to the client. Run here if you want to observe the response before that happens, and if you want to use the response headers to determine if you want to buffer the response body. Note that some response status codes (such as 404) are handled earlier in the request cycle by Apache and my not be able to be triggered as expected. Additionally, there are some response headers that are added by Apache at a later hook (such as Date, Server and Connection) that we would not be able to trigger on or sanitize. This should work appropriately in a proxy setup or within phase:5 (logging).
 
-
SecRule ARGS:/^id_/ dirty "id:11"
-

-
 Note 
 Using ARGS:p will not result in any invocations against the operator if argument p does not exist.
-

-
In ModSecurity 1.X, the ARGS variable stood for QUERY_STRING + POST_PAYLOAD, whereas now it expands to individual variables.
-

-
[edit]  ARGS_COMBINED_SIZE 

+== Phase Response Body ==
+This is the general-purpose output analysis phase. At this point you can run rules against the response body (provided it was buffered, of course). This is the phase where you would want to inspect the outbound HTML for information disclosure, error messages or failed authentication text.
 
-
Contains the combined size of all request parameters. Files are excluded from the calculation. This variable can be useful, for example, to create a rule to ensure that the total size of the argument data is below a certain threshold. The following rule detects a request whose para- meters are more than 2500 bytes long:
-
SecRule ARGS_COMBINED_SIZE "@gt 2500" "id:12"
-

-
[edit]  ARGS_GET 

-
ARGS_GET is similar to ARGS, but contains only query string parameters.
-

-
[edit]  ARGS_GET_NAMES 

+; Note : In order to access the Response Body phase data, you must have SecResponseBodyAccess set to On
 
-
ARGS_GET_NAMES is similar to ARGS_NAMES, but contains only the names of query string parameters.
-

-
[edit]  ARGS_NAMES 

-
Contains all request parameter names. You can search for specific parameter names that you want to inspect. In a positive policy scenario, you can also whitelist (using an inverted rule with the exclamation mark) only the authorized argument names.
+== Phase Logging ==
+This phase is run just before logging takes place. The rules placed into this phase can only affect how the logging is performed. This phase can be used to inspect the error messages logged by Apache. You cannot deny/block connections in this phase as it is too late. This phase also allows for inspection of other response headers that weren't available during phase:3 or phase:4. Note that you must be careful not to inherit a disruptive action into a rule in this phase as this is a configuration error in ModSecurity 2.5.0 and later versions
+
+= Variables =
+The following variables are supported in ModSecurity 2.x:
+
+== ARGS == 
+ARGS is a collection and can be used on its own (means all arguments including the POST Payload), with a static parameter (matches arguments with that name), or with a regular expression (matches all arguments with name that matches the regular expression). To look at only the query string or body arguments, see the ARGS_GET and ARGS_POST collections.
+
+Some variables are actually collections, which are expanded into more variables at runtime. The following example will examine all request arguments:
+
+SecRule ARGS dirty "id:7"
+
+Sometimes, however, you will want to look only at parts of a collection. This can be achieved with the help of the selection operator(colon). The following example will only look at the arguments named p (do note that, in general, requests can contain multiple arguments with the same name):
+
+SecRule ARGS:p dirty "id:8"
+
+It is also possible to specify exclusions. The following will examine all request arguments for the word dirty, except the ones named z (again, there can be zero or more arguments named z):
+
+SecRule ARGS|!ARGS:z dirty "id:9"
+
+There is a special operator that allows you to count how many variables there are in a collection. The following rule will trigger if there is more than zero arguments in the request (ignore the second parameter for the time being):
+
+SecRule &ARGS !^0$ "id:10"
+
+And sometimes you need to look at an array of parameters, each with a slightly different name. In this case you can specify a regular expression in the selection operator itself. The following rule will look into all arguments whose names begin with id_:
+
+SecRule ARGS:/^id_/ dirty "id:11"
+
+; Note : Using ARGS:p will not result in any invocations against the operator if argument p does not exist.
+
+In ModSecurity 1.X, the ARGS variable stood for QUERY_STRING + POST_PAYLOAD, whereas now it expands to individual variables.
+
+== ARGS_COMBINED_SIZE ==
+Contains the combined size of all request parameters. Files are excluded from the calculation. This variable can be useful, for example, to create a rule to ensure that the total size of the argument data is below a certain threshold. The following rule detects a request whose para- meters are more than 2500 bytes long:
+
+SecRule ARGS_COMBINED_SIZE "@gt 2500" "id:12"
+
+== ARGS_GET == 
+ARGS_GET is similar to ARGS, but contains only query string parameters.
+
+== ARGS_GET_NAMES == 
+ARGS_GET_NAMES is similar to ARGS_NAMES, but contains only the names of query string parameters.
+
+== ARGS_NAMES == 
+Contains all request parameter names. You can search for specific parameter names that you want to inspect. In a positive policy scenario, you can also whitelist (using an inverted rule with the exclamation mark) only the authorized argument names.
 This example rule allows only two argument names: p and a: 
-
SecRule ARGS_NAMES "!^(p|a)$" "id:13"
-

-
[edit]  ARGS_POST 

 
-
ARGS_POST is similar to ARGS, but only contains arguments from the POST body.
-

-
[edit]  ARGS_POST_NAMES 

-
ARGS_POST_NAMES is similar to ARGS_NAMES, but contains only the names of request body parameters.
-

-
[edit]  AUTH_TYPE 

+SecRule ARGS_NAMES "!^(p|a)$" "id:13"
 
-
This variable holds the authentication method used to validate a user, if any of the methods built into HTTP are used. In a reverse-proxy deployment, this information will not be available if the authentication is handled in the backend web server.
-
SecRule AUTH_TYPE "Basic" "id:14"
-

-
[edit]  DURATION 

-
Contains the number of milliseconds elapsed since the beginning of the current transaction. Available starting with 2.6.0.
-

-
 Note 
 Starting with ModSecurity 2.7.0 the time is microseconds.
+== ARGS_POST == 
+ARGS_POST is similar to ARGS, but only contains arguments from the POST body.
 
-

-
[edit]  ENV 

-
Collection that provides access to environment variables set by ModSecurity. Requires a single parameter to specify the name of the desired variable.
-

+== ARGS_POST_NAMES == 
+ARGS_POST_NAMES is similar to ARGS_NAMES, but contains only the names of request body parameters.
+
+== AUTH_TYPE == 
+This variable holds the authentication method used to validate a user, if any of the methods built into HTTP are used. In a reverse-proxy deployment, this information will not be available if the authentication is handled in the backend web server.
+
+SecRule AUTH_TYPE "Basic" "id:14"
+
+== DURATION ==
+Contains the number of milliseconds elapsed since the beginning of the current transaction. Available starting with 2.6.0.
+
+; Note : Starting with ModSecurity 2.7.0 the time is microseconds.
+
+== ENV == 
+Collection that provides access to environment variables set by ModSecurity. Requires a single parameter to specify the name of the desired variable.
 
 # Set environment variable 
-SecRule REQUEST_FILENAME "printenv" \
-"phase:2,id:15,pass,setenv:tag=suspicious" 
-
+SecRule REQUEST_FILENAME "printenv" \
+"phase:2,id:15,pass,setenv:tag=suspicious" 
 
 # Inspect environment variable
-SecRule ENV:tag "suspicious" "id:16"
+SecRule ENV:tag "suspicious" "id:16"
 

-
 Note 
 Use setenv to set environment variables to be accessed by Apache.
-

-
[edit]  FILES 

 
-
Contains a collection of original file names (as they were called on the remote user’s filesys- tem). Available only on inspected multipart/form-data requests.
-
SecRule FILES "@rx \.conf$" "id:17"
-

-
 Note 
 Only available if files were extracted from the request body.
-

-
[edit]  FILES_COMBINED_SIZE 

-
Contains the total size of the files transported in request body. Available only on inspected multipart/form-data requests.
+; Note : Use setenv to set environment variables to be accessed by Apache.
 
-
SecRule FILES_COMBINED_SIZE "@gt 100000" "id:18"
-

-
[edit]  FILES_NAMES 

-
Contains a list of form fields that were used for file upload. Available only on inspected multipart/form-data requests.
-
SecRule FILES_NAMES "^upfile$" "id:19"
-

-
[edit]  FILES_SIZES 

+== FILES == 
+Contains a collection of original file names (as they were called on the remote user’s filesys- tem). Available only on inspected multipart/form-data requests.
 
-
Contains a list of individual file sizes. Useful for implementing a size limitation on individual uploaded files. Available only on inspected multipart/form-data requests.
-
SecRule FILES_SIZES "@gt 100" "id:20"
-

-
[edit]  FILES_TMPNAMES 

-
Contains a list of temporary files’ names on the disk. Useful when used together with @inspectFile. Available only on inspected multipart/form-data requests.
-
SecRule FILES_TMPNAMES "@inspectFile /path/to/inspect_script.pl" "id:21"
-

-
[edit]  GEO 

+SecRule FILES "@rx \.conf$" "id:17"
 
-
GEO is a collection populated by the results of the last @geoLookup operator. The collection can be used to match geographical fields looked from an IP address or hostname.
-
Available since ModSecurity 2.5.0.
-
Fields:
-

-
  • COUNTRY_CODE: Two character country code. EX: US, GB, etc.
-
  • COUNTRY_CODE3: Up to three character country code.
-
  • COUNTRY_NAME: The full country name.
-
  • COUNTRY_CONTINENT: The two character continent that the country is located. EX: EU
-
  • REGION: The two character region. For US, this is state. For Canada, providence, etc.
-
  • CITY: The city name if supported by the database.
-
  • POSTAL_CODE: The postal code if supported by the database.
-
  • LATITUDE: The latitude if supported by the database.
-
  • LONGITUDE: The longitude if supported by the database.
-
  • DMA_CODE: The metropolitan area code if supported by the database. (US only)
-
  • AREA_CODE: The phone system area code. (US only)
-

-
Example:
+; Note : Only available if files were extracted from the request body.
 
-

+== FILES_COMBINED_SIZE ==
+Contains the total size of the files transported in request body. Available only on inspected multipart/form-data requests.
+
+SecRule FILES_COMBINED_SIZE "@gt 100000" "id:18"
+
+== FILES_NAMES ==
+Contains a list of form fields that were used for file upload. Available only on inspected multipart/form-data requests.
+
+SecRule FILES_NAMES "^upfile$" "id:19"
+
+== FILES_SIZES == 
+Contains a list of individual file sizes. Useful for implementing a size limitation on individual uploaded files. Available only on inspected multipart/form-data requests.
+
+SecRule FILES_SIZES "@gt 100" "id:20"
+
+== FILES_TMPNAMES == 
+Contains a list of temporary files’ names on the disk. Useful when used together with @inspectFile. Available only on inspected multipart/form-data requests.
+
+SecRule FILES_TMPNAMES "@inspectFile /path/to/inspect_script.pl" "id:21"
+
+== GEO == 
+GEO is a collection populated by the results of the last @geoLookup operator. The collection can be used to match geographical fields looked from an IP address or hostname.
+
+Available since ModSecurity 2.5.0.
+
+Fields:
+*COUNTRY_CODE: Two character country code. EX: US, GB, etc.
+*COUNTRY_CODE3: Up to three character country code.
+*COUNTRY_NAME: The full country name.
+*COUNTRY_CONTINENT: The two character continent that the country is located. EX: EU
+*REGION: The two character region. For US, this is state. For Canada, providence, etc.
+*CITY: The city name if supported by the database.
+*POSTAL_CODE: The postal code if supported by the database.
+*LATITUDE: The latitude if supported by the database.
+*LONGITUDE: The longitude if supported by the database.
+*DMA_CODE: The metropolitan area code if supported by the database. (US only)
+*AREA_CODE: The phone system area code. (US only)
+
+Example:
 
 SecGeoLookupDb /usr/local/geo/data/GeoLiteCity.dat
 ...
-SecRule REMOTE_ADDR "@geoLookup" "chain,id:22,drop,msg:'Non-GB IP address'"
-SecRule GEO:COUNTRY_CODE "!@streq GB"
+SecRule REMOTE_ADDR "@geoLookup" "chain,id:22,drop,msg:'Non-GB IP address'"
+SecRule GEO:COUNTRY_CODE "!@streq GB"
 

-
[edit]  HIGHEST_SEVERITY 

+== HIGHEST_SEVERITY == 
+This variable holds the highest severity of any rules that have matched so far. Severities are numeric values and thus can be used with comparison operators such as @lt, and so on. A value of 255 indicates that no severity has been set.
 
-
This variable holds the highest severity of any rules that have matched so far. Severities are numeric values and thus can be used with comparison operators such as @lt, and so on. A value of 255 indicates that no severity has been set.
-
SecRule HIGHEST_SEVERITY "@le 2" "phase:2,id:23,deny,status:500,msg:'severity %{HIGHEST_SEVERITY}'"
-

-
 Note 
 Higher severities have a lower numeric value.
-

-
[edit]  INBOUND_DATA_ERROR 

+SecRule HIGHEST_SEVERITY "@le 2" "phase:2,id:23,deny,status:500,msg:'severity %{HIGHEST_SEVERITY}'"
+; Note : Higher severities have a lower numeric value.
 
-
This variable will be set to 1 when the request body size is above the setting configured by SecRequestBodyLimit directive.  Your policies should always contain a rule to check this variable.  Depending on the rate of false positives and your default policy you should decide whether to block or just warn when the rule is triggered.
-
The best way to use this variable is as in the example below:
-
SecRule INBOUND_DATA_ERROR "@eq 1" "phase:1,id:24,t:none,log,pass,msg:'Request Body Larger than SecRequestBodyLimit Setting'"
-

-
[edit]  MATCHED_VAR 

-
This variable holds the value of the most-recently matched variable. It is similar to the TX:0, but it is automatically supported by all operators and there is no need to specify the capture action.
-

+== INBOUND_DATA_ERROR ==
+This variable will be set to 1 when the request body size is above the setting configured by SecRequestBodyLimit directive.  Your policies should always contain a rule to check this variable.  Depending on the rate of false positives and your default policy you should decide whether to block or just warn when the rule is triggered.
+
+The best way to use this variable is as in the example below:
+
+SecRule INBOUND_DATA_ERROR "@eq 1" "phase:1,id:24,t:none,log,pass,msg:'Request Body Larger than SecRequestBodyLimit Setting'"
+
+== MATCHED_VAR == 
+This variable holds the value of the most-recently matched variable. It is similar to the TX:0, but it is automatically supported by all operators and there is no need to specify the capture action.
 
 SecRule ARGS pattern chain,deny,id:25
-  SecRule MATCHED_VAR "further scrutiny"
-
+  SecRule MATCHED_VAR "further scrutiny"
 

-
 Note 
 Be aware that this variable holds data for the last operator match.  This means that if there are more than one matches, only the last one will be populated.  Use MATCHED_VARS variable if you want all matches.
-

-
[edit]  MATCHED_VARS 

-
Similar to MATCHED_VAR except that it is a collection of all matches for the current operator check.
+; Note : Be aware that this variable holds data for the '''''last''''' operator match.  This means that if there are more than one matches, only the last one will be populated.  Use MATCHED_VARS variable if you want all matches.
 
-

+== MATCHED_VARS ==
+Similar to MATCHED_VAR except that it is a collection of '''''all matches''''' for the current operator check.
 
-SecRule ARGS pattern "chain,deny,id:26"
-  SecRule MATCHED_VARS "@eq ARGS:param"
+SecRule ARGS pattern "chain,deny,id:26"
+  SecRule MATCHED_VARS "@eq ARGS:param"
 

-
[edit]  MATCHED_VAR_NAME 

 
-
This variable holds the full name of the variable that was matched against.
-

+== MATCHED_VAR_NAME == 
+This variable holds the full name of the variable that was matched against.
 
-SecRule ARGS pattern "chain,deny,id:27"
-  SecRule MATCHED_VAR_NAME "@eq ARGS:param"
+SecRule ARGS pattern "chain,deny,id:27"
+  SecRule MATCHED_VAR_NAME "@eq ARGS:param"
 

-
 Note 
 Be aware that this variable holds data for the last operator match.  This means that if there are more than one matches, only the last one will be populated.  Use MATCHED_VARS_NAMES variable if you want all matches.
 
-

-
[edit]  MATCHED_VARS_NAMES 

-
Similar to MATCHED_VAR_NAME except that it is a collection of all matches for the current operator check.
-

+; Note : Be aware that this variable holds data for the '''''last''''' operator match.  This means that if there are more than one matches, only the last one will be populated.  Use MATCHED_VARS_NAMES variable if you want all matches.
+
+== MATCHED_VARS_NAMES ==
+Similar to MATCHED_VAR_NAME except that it is a collection of '''''all matches''''' for the current operator check.
 
-SecRule ARGS pattern "chain,deny,id:28"
-
-  SecRule MATCHED_VARS_NAMES "@eq ARGS:param"
+SecRule ARGS pattern "chain,deny,id:28"
+  SecRule MATCHED_VARS_NAMES "@eq ARGS:param"
 

-
[edit]  MODSEC_BUILD 

-
This variable holds the ModSecurity build number. This variable is intended to be used to check the build number prior to using a feature that is available only in a certain build. Example:
-

-
-SecRule MODSEC_BUILD "!@ge 02050102" "skipAfter:12345,id:29"
 
-SecRule ARGS "@pm some key words" "id:12345,deny,status:500"
+== MODSEC_BUILD == 
+This variable holds the ModSecurity build number. This variable is intended to be used to check the build number prior to using a feature that is available only in a certain build. Example:
+
+SecRule MODSEC_BUILD "!@ge 02050102" "skipAfter:12345,id:29"
+SecRule ARGS "@pm some key words" "id:12345,deny,status:500"
 

-
[edit]  MULTIPART_CRLF_LF_LINES 

-
This flag variable will be set to 1 whenever a multi-part request uses mixed line terminators. The multipart/form-data RFC requires CRLF sequence to be used to terminate lines. Since some client implementations use only LF to terminate lines you might want to allow them to proceed under certain circumstances (if you want to do this you will need to stop using MULTIPART_STRICT_ERROR and check each multi-part flag variable individually, avoiding MULTIPART_LF_LINE). However, mixing CRLF and LF line terminators is dangerous as it can allow for evasion. Therefore, in such cases, you will have to add a check for MULTIPART_CRLF_LF_LINES.
-

-
[edit]  MULTIPART_STRICT_ERROR 

 
-
MULTIPART_STRICT_ERROR will be set to 1 when any of the following variables is also set to 1: REQBODY_PROCESSOR_ERROR, MULTIPART_BOUNDARY_QUOTED, MULTIPART_BOUNDARY_WHITESPACE, MULTIPART_DATA_BEFORE, MULTIPART_DATA_AFTER, MULTIPART_HEADER_FOLDING, MULTIPART_LF_LINE, MULTIPART_MISSING_SEMICOLON MULTIPART_INVALID_QUOTING MULTIPART_INVALID_HEADER_FOLDING MULTIPART_FILE_LIMIT_EXCEEDED. Each of these variables covers one unusual (although sometimes legal) aspect of the request body in multipart/form-data format. Your policies should always contain a rule to check either this variable (easier) or one or more individual variables (if you know exactly what you want to accomplish). Depending on the rate of false positives and your default policy you should decide whether to block or just warn when the rule is triggered.
-
The best way to use this variable is as in the example below:
-

+== MULTIPART_CRLF_LF_LINES == 
+This flag variable will be set to 1 whenever a multi-part request uses mixed line terminators. The multipart/form-data RFC requires CRLF sequence to be used to terminate lines. Since some client implementations use only LF to terminate lines you might want to allow them to proceed under certain circumstances (if you want to do this you will need to stop using MULTIPART_STRICT_ERROR and check each multi-part flag variable individually, avoiding MULTIPART_LF_LINE). However, mixing CRLF and LF line terminators is dangerous as it can allow for evasion. Therefore, in such cases, you will have to add a check for MULTIPART_CRLF_LF_LINES.
+
+== MULTIPART_STRICT_ERROR == 
+MULTIPART_STRICT_ERROR will be set to 1 when any of the following variables is also set to 1: REQBODY_PROCESSOR_ERROR, MULTIPART_BOUNDARY_QUOTED, MULTIPART_BOUNDARY_WHITESPACE, MULTIPART_DATA_BEFORE, MULTIPART_DATA_AFTER, MULTIPART_HEADER_FOLDING, MULTIPART_LF_LINE, MULTIPART_MISSING_SEMICOLON MULTIPART_INVALID_QUOTING MULTIPART_INVALID_HEADER_FOLDING MULTIPART_FILE_LIMIT_EXCEEDED. Each of these variables covers one unusual (although sometimes legal) aspect of the request body in multipart/form-data format. Your policies should always contain a rule to check either this variable (easier) or one or more individual variables (if you know exactly what you want to accomplish). Depending on the rate of false positives and your default policy you should decide whether to block or just warn when the rule is triggered.
+
+The best way to use this variable is as in the example below:
 
-SecRule MULTIPART_STRICT_ERROR "!@eq 0" \
-"phase:2,id:30,t:none,log,deny,msg:'Multipart request body \
+SecRule MULTIPART_STRICT_ERROR "!@eq 0" \
+"phase:2,id:30,t:none,log,deny,msg:'Multipart request body \
 failed strict validation: \
-PE %{REQBODY_PROCESSOR_ERROR}, \
-BQ %{MULTIPART_BOUNDARY_QUOTED}, \
-BW %{MULTIPART_BOUNDARY_WHITESPACE}, \
-DB %{MULTIPART_DATA_BEFORE}, \
-DA %{MULTIPART_DATA_AFTER}, \
-HF %{MULTIPART_HEADER_FOLDING}, \
-LF %{MULTIPART_LF_LINE}, \
-SM %{MULTIPART_MISSING_SEMICOLON}, \
-IQ %{MULTIPART_INVALID_QUOTING}, \
-IQ %{MULTIPART_INVALID_HEADER_FOLDING}, \
-FE %{MULTIPART_FILE_LIMIT_EXCEEDED}'"
-
+PE %{REQBODY_PROCESSOR_ERROR}, \
+BQ %{MULTIPART_BOUNDARY_QUOTED}, \
+BW %{MULTIPART_BOUNDARY_WHITESPACE}, \
+DB %{MULTIPART_DATA_BEFORE}, \
+DA %{MULTIPART_DATA_AFTER}, \
+HF %{MULTIPART_HEADER_FOLDING}, \
+LF %{MULTIPART_LF_LINE}, \
+SM %{MULTIPART_MISSING_SEMICOLON}, \
+IQ %{MULTIPART_INVALID_QUOTING}, \
+IQ %{MULTIPART_INVALID_HEADER_FOLDING}, \
+FE %{MULTIPART_FILE_LIMIT_EXCEEDED}'"
 

-
The multipart/form-data parser was upgraded in ModSecurity v2.1.3 to actively look for signs of evasion. Many variables (as listed above) were added to expose various facts discovered during the parsing process. The MULTIPART_STRICT_ERROR variable is handy to check on all abnormalities at once. The individual variables allow detection to be fine-tuned according to your circumstances in order to reduce the number of false positives.
-

-
[edit]  MULTIPART_UNMATCHED_BOUNDARY 

-
Set to 1 when, during the parsing phase of a multipart/request-body, ModSecurity encounters what feels like a boundary but it is not. Such an event may occur when evasion of ModSecurity is attempted.
-
The best way to use this variable is as in the example below:
-

+The multipart/form-data parser was upgraded in ModSecurity v2.1.3 to actively look for signs of evasion. Many variables (as listed above) were added to expose various facts discovered during the parsing process. The MULTIPART_STRICT_ERROR variable is handy to check on all abnormalities at once. The individual variables allow detection to be fine-tuned according to your circumstances in order to reduce the number of false positives.
+
+== MULTIPART_UNMATCHED_BOUNDARY == 
+Set to 1 when, during the parsing phase of a multipart/request-body, ModSecurity encounters what feels like a boundary but it is not. Such an event may occur when evasion of ModSecurity is attempted.
+
+The best way to use this variable is as in the example below:
 
-SecRule MULTIPART_UNMATCHED_BOUNDARY "!@eq 0" \
-
-"phase:2,id:31,t:none,log,deny,msg:'Multipart parser detected a possible unmatched boundary.'"
+SecRule MULTIPART_UNMATCHED_BOUNDARY "!@eq 0" \
+"phase:2,id:31,t:none,log,deny,msg:'Multipart parser detected a possible unmatched boundary.'"
 

-
Change the rule from blocking to logging-only if many false positives are encountered.
-

-
[edit]  OUTBOUND_DATA_ERROR 

-
This variable will be set to 1 when the response body size is above the setting configured by SecResponseBodyLimit directive.  Your policies should always contain a rule to check this variable.  Depending on the rate of false positives and your default policy you should decide whether to block or just warn when the rule is triggered.
-
The best way to use this variable is as in the example below:
-
SecRule OUTBOUND_DATA_ERROR "@eq 1" "phase:1,id:32,t:none,log,pass,msg:'Response Body Larger than SecResponseBodyLimit Setting'"
-

+Change the rule from blocking to logging-only if many false positives are encountered.
 
-
[edit]  PATH_INFO 

-
Contains the extra request URI information, also known as path info. (For example, in the URI /index.php/123, /123 is the path info.) Available only in embedded deployments.
-
SecRule PATH_INFO "^/(bin|etc|sbin|opt|usr)" "id:33"
-

-
[edit]  PERF_COMBINED 

+== OUTBOUND_DATA_ERROR ==
+This variable will be set to 1 when the response body size is above the setting configured by SecResponseBodyLimit directive.  Your policies should always contain a rule to check this variable.  Depending on the rate of false positives and your default policy you should decide whether to block or just warn when the rule is triggered.
 
-
Contains the time, in microseconds, spent in ModSecurity during the current transaction. The value in this variable is arrived to by adding all the performance variables except PERF_SREAD (the time spent reading from persistent storage is already included in the phase measurements). Available starting with 2.6.
-

-
[edit]  PERF_GC 

-
Contains the time, in microseconds, spent performing garbage collection. Available starting with 2.6.
-

-
[edit]  PERF_LOGGING 

+The best way to use this variable is as in the example below:
 
-
Contains the time, in microseconds, spent in audit logging. This value is known only after the handling of a transaction is finalized, which means that it can only be logged using mod_log_config and the %{VARNAME}M syntax. Available starting with 2.6.
-

-
[edit]  PERF_PHASE1 

-
Contains the time, in microseconds, spent processing phase 1. Available starting with 2.6.
-

-
[edit]  PERF_PHASE2 

+SecRule OUTBOUND_DATA_ERROR "@eq 1" "phase:1,id:32,t:none,log,pass,msg:'Response Body Larger than SecResponseBodyLimit Setting'"
 
-
Contains the time, in microseconds, spent processing phase 2. Available starting with 2.6.
-

-
[edit]  PERF_PHASE3 

-
Contains the time, in microseconds, spent processing phase 3. Available starting with 2.6.
-

-
[edit]  PERF_PHASE4 

+== PATH_INFO == 
+Contains the extra request URI information, also known as path info. (For example, in the URI /index.php/123, /123 is the path info.) Available only in embedded deployments.
 
-
Contains the time, in microseconds, spent processing phase 4. Available starting with 2.6.
-

-
[edit]  PERF_PHASE5 

-
Contains the time, in microseconds, spent processing phase 5. Available starting with 2.6.
-

-
[edit]  PERF_RULES 

+SecRule PATH_INFO "^/(bin|etc|sbin|opt|usr)" "id:33"
 
-
Contains the time of rules, in microseconds. Available starting with 2.7.
-
SecRule PERF_RULES "@gt 1000" "id:12345,phase:5"
-

-
[edit]  PERF_SREAD 

-
Contains the time, in microseconds, spent reading from persistent storage. Available starting with 2.6.
-

-
[edit]  PERF_SWRITE 

+== PERF_COMBINED ==
+Contains the time, in microseconds, spent in ModSecurity during the current transaction. The value in this variable is arrived to by adding all the performance variables except PERF_SREAD (the time spent reading from persistent storage is already included in the phase measurements). Available starting with 2.6.
 
-
Contains the time, in microseconds, spent writing to persistent storage. Available starting with 2.6.
-

-
[edit]  QUERY_STRING 

-
Contains the query string part of a request URI. The value in QUERY_STRING is always provided raw, without URL decoding taking place.
-
SecRule QUERY_STRING "attack" "id:34"
-

-
[edit]  REMOTE_ADDR 

+== PERF_GC ==
+Contains the time, in microseconds, spent performing garbage collection. Available starting with 2.6.
 
-
This variable holds the IP address of the remote client.
-
SecRule REMOTE_ADDR "@ipMatch 192.168.1.101" "id:35"
-

-
[edit]  REMOTE_HOST 

-
If the Apache directive HostnameLookups is set to On, then this variable will hold the remote hostname resolved through DNS. If the directive is set to Off, this variable it will hold the remote IP address (same as REMOTE_ADDR). Possible uses for this variable would be to deny known bad client hosts or network blocks, or conversely, to allow in authorized hosts.
-
SecRule REMOTE_HOST "\.evil\.network\org$" "id:36"
-

-
[edit]  REMOTE_PORT 

+== PERF_LOGGING ==
+Contains the time, in microseconds, spent in audit logging. This value is known only after the handling of a transaction is finalized, which means that it can only be logged using mod_log_config and the %{VARNAME}M syntax. Available starting with 2.6.
 
-
This variable holds information on the source port that the client used when initiating the connection to our web server.
-
In the following example, we are evaluating to see whether the REMOTE_PORT is less than 1024, which would indicate that the user is a privileged user:
-
SecRule REMOTE_PORT "@lt 1024" "id:37"
-

-
[edit]  REMOTE_USER 

-
This variable holds the username of the authenticated user. If there are no password access controls in place (Basic or Digest authentication), then this variable will be empty.
-
SecRule REMOTE_USER "^admin$" "id:38"
-

-
 Note 
 In a reverse-proxy deployment, this information will not be available if the authentication is
+== PERF_PHASE1 ==
+Contains the time, in microseconds, spent processing phase 1. Available starting with 2.6.
 
-

-
handled in the backend web server.
-

-
[edit]  REQBODY_ERROR 

-
Contains the status of the request body processor used for request body parsing. The values can be 0 (no error) or 1 (error). This variable will be set by request body processors (typically the multipart/request-data parser or the XML parser) when they fail to do their work.
-
SecRule REQBODY_ERROR "@eq 1" deny,phase:2,id:39 
-

-
 Note 
 Your policies must have a rule to check for request body processor errors at the very beginning of phase 2. Failure to do so will leave the door open for impedance mismatch attacks. It is possible, for example, that a payload that cannot be parsed by ModSecurity can be successfully parsed by more tolerant parser operating in the application. If your policy dictates blocking, then you should reject the request if error is detected. When operating in detection-only mode, your rule should alert with high severity when request body processing fails.
+== PERF_PHASE2 ==
+Contains the time, in microseconds, spent processing phase 2. Available starting with 2.6.
 
-

-
[edit]  REQBODY_ERROR_MSG 

-
If there’s been an error during request body parsing, the variable will contain the following error message:
-
SecRule REQBODY_ERROR_MSG "failed to parse" "id:40"
-

-
[edit]  REQBODY_PROCESSOR 

+== PERF_PHASE3 ==
+Contains the time, in microseconds, spent processing phase 3. Available starting with 2.6.
+
+== PERF_PHASE4 ==
+Contains the time, in microseconds, spent processing phase 4. Available starting with 2.6.
+
+== PERF_PHASE5 ==
+Contains the time, in microseconds, spent processing phase 5. Available starting with 2.6.
+
+== PERF_RULES ==
+Contains the time of rules, in microseconds. Available starting with 2.7.
+
+SecRule PERF_RULES "@gt 1000" "id:12345,phase:5"
+
+== PERF_SREAD ==
+Contains the time, in microseconds, spent reading from persistent storage. Available starting with 2.6.
+
+== PERF_SWRITE ==
+Contains the time, in microseconds, spent writing to persistent storage. Available starting with 2.6.
+
+== QUERY_STRING == 
+Contains the query string part of a request URI. The value in QUERY_STRING is always provided raw, without URL decoding taking place.
+
+SecRule QUERY_STRING "attack" "id:34"
+
+== REMOTE_ADDR == 
+This variable holds the IP address of the remote client.
+
+SecRule REMOTE_ADDR "@ipMatch 192.168.1.101" "id:35"
+
+== REMOTE_HOST == 
+If the Apache directive HostnameLookups is set to On, then this variable will hold the remote hostname resolved through DNS. If the directive is set to Off, this variable it will hold the remote IP address (same as REMOTE_ADDR). Possible uses for this variable would be to deny known bad client hosts or network blocks, or conversely, to allow in authorized hosts.
+
+SecRule REMOTE_HOST "\.evil\.network\org$" "id:36"
+
+== REMOTE_PORT ==
+This variable holds information on the source port that the client used when initiating the connection to our web server.
+
+In the following example, we are evaluating to see whether the REMOTE_PORT is less than 1024, which would indicate that the user is a privileged user:
+
+SecRule REMOTE_PORT "@lt 1024" "id:37"
+
+== REMOTE_USER ==
+This variable holds the username of the authenticated user. If there are no password access controls in place (Basic or Digest authentication), then this variable will be empty.
+
+SecRule REMOTE_USER "^admin$" "id:38"
+
+; Note : In a reverse-proxy deployment, this information will not be available if the authentication is
+handled in the backend web server.
+
+== REQBODY_ERROR ==
+Contains the status of the request body processor used for request body parsing. The values can be 0 (no error) or 1 (error). This variable will be set by request body processors (typically the multipart/request-data parser or the XML parser) when they fail to do their work.
+
+SecRule REQBODY_ERROR "@eq 1" deny,phase:2,id:39 
+
+; Note : Your policies must have a rule to check for request body processor errors at the very beginning of phase 2. Failure to do so will leave the door open for impedance mismatch attacks. It is possible, for example, that a payload that cannot be parsed by ModSecurity can be successfully parsed by more tolerant parser operating in the application. If your policy dictates blocking, then you should reject the request if error is detected. When operating in detection-only mode, your rule should alert with high severity when request body processing fails.
+
+== REQBODY_ERROR_MSG ==
+If there’s been an error during request body parsing, the variable will contain the following error message:
+
+SecRule REQBODY_ERROR_MSG "failed to parse" "id:40"
+
+== REQBODY_PROCESSOR ==
+Contains the name of the currently used request body processor. The possible values are URLENCODED, MULTIPART, and XML.
 
-
Contains the name of the currently used request body processor. The possible values are URLENCODED, MULTIPART, and XML.
-

 
-SecRule REQBODY_PROCESSOR "^XML$ chain,id:41 
-  SecRule XML "@validateDTD /opt/apache-frontend/conf/xml.dtd"
+SecRule REQBODY_PROCESSOR "^XML$ chain,id:41 
+  SecRule XML "@validateDTD /opt/apache-frontend/conf/xml.dtd"
 

-
[edit]  REQUEST_BASENAME 

-
This variable holds just the filename part of REQUEST_FILENAME (e.g., index.php). 
-
SecRule REQUEST_BASENAME "^login\.php$" phase:2,id:42,t:none,t:lowercase
 
-

-
 Note 
 Please note that anti-evasion transformations are not applied to this variable by default. REQUEST_BASENAME will recognise both / and \ as path separators. You should understand that the value of this variable depends on what was provided in request, and that it does not have to correspond to the resource (on disk) that will be used by the web server.
-

-
[edit]  REQUEST_BODY 

-
Holds the raw request body. This variable is available only if the URLENCODED request body processor was used, which will occur by default when the application/x-www-form-urlencoded content type is detected, or if the use of the URLENCODED request body parser was forced. 
-
SecRule REQUEST_BODY "^username=\w{25,}\&password=\w{25,}\&Submit\=login$" "id:43"
+== REQUEST_BASENAME ==
+This variable holds just the filename part of REQUEST_FILENAME (e.g., index.php). 
 
-
As of 2.5.7, it is possible to force the presence of the REQUEST_BODY variable, but only when there is no request body processor defined using the ctl:forceRequestBodyVariable option in the REQUEST_HEADERS phase.
-

-
[edit]  REQUEST_BODY_LENGTH 

-
Contains the number of bytes read from a request body. Available starting with v2.6
-

-
[edit]  REQUEST_COOKIES 

+SecRule REQUEST_BASENAME "^login\.php$" phase:2,id:42,t:none,t:lowercase
 
-
This variable is a collection of all of request cookies (values only).  Example: the following example is using the Ampersand special operator to count how many variables are in the collection. In this rule, it would trigger if the request does not include any Cookie headers.
-
SecRule &REQUEST_COOKIES "@eq 0" "id:44"
-

-
[edit]  REQUEST_COOKIES_NAMES 

-
This variable is a collection of the names of all request cookies. For example, the following rule will trigger if the JSESSIONID cookie is not present:
-
SecRule &REQUEST_COOKIES_NAMES:JSESSIONID "@eq 0" "id:45"
-

+; Note : Please note that anti-evasion transformations are not applied to this variable by default. REQUEST_BASENAME will recognise both / and \ as path separators. You should understand that the value of this variable depends on what was provided in request, and that it does not have to correspond to the resource (on disk) that will be used by the web server.
 
-
[edit]  REQUEST_FILENAME 

-
This variable holds the relative request URL without the query string part (e.g., /index.php). 
-
SecRule REQUEST_FILENAME "^/cgi-bin/login\.php$" phase:2,id:46,t:none,t:normalizePath
-

-
 Note 
 Please note that anti-evasion transformations are not used on REQUEST_FILENAME, which means that you will have to specify them in the rules that use this variable.
-

-
[edit]  REQUEST_HEADERS 

+== REQUEST_BODY ==
+Holds the raw request body. This variable is available only if the URLENCODED request body processor was used, which will occur by default when the application/x-www-form-urlencoded content type is detected, or if the use of the URLENCODED request body parser was forced. 
 
-
This variable can be used as either a collection of all of the request headers or can be used to inspect selected headers (by using the REQUEST_HEADERS:Header-Name syntax).
-
SecRule REQUEST_HEADERS:Host "^[\d\.]+$" "deny,id:47,log,status:400,msg:'Host header is a numeric IP address'"
-

-
[edit]  REQUEST_HEADERS_NAMES 

-
This variable is a collection of the names of all of the request headers.
-
SecRule REQUEST_HEADERS_NAMES "^x-forwarded-for" "log,deny,id:48,status:403,t:lowercase,msg:'Proxy Server Used'"
-

-
[edit]  REQUEST_LINE 

+SecRule REQUEST_BODY "^username=\w{25,}\&password=\w{25,}\&Submit\=login$" "id:43"
+
+As of 2.5.7, it is possible to force the presence of the REQUEST_BODY variable, but only when there is no request body processor defined using the ctl:forceRequestBodyVariable option in the REQUEST_HEADERS phase.
+
+== REQUEST_BODY_LENGTH ==
+Contains the number of bytes read from a request body. Available starting with v2.6
+
+== REQUEST_COOKIES ==
+This variable is a collection of all of request cookies (values only).  Example: the following example is using the Ampersand special operator to count how many variables are in the collection. In this rule, it would trigger if the request does not include any Cookie headers.
+
+SecRule &REQUEST_COOKIES "@eq 0" "id:44"
+
+== REQUEST_COOKIES_NAMES ==
+This variable is a collection of the names of all request cookies. For example, the following rule will trigger if the JSESSIONID cookie is not present:
+
+SecRule &REQUEST_COOKIES_NAMES:JSESSIONID "@eq 0" "id:45"
+
+== REQUEST_FILENAME ==
+This variable holds the relative request URL without the query string part (e.g., /index.php). 
+
+SecRule REQUEST_FILENAME "^/cgi-bin/login\.php$" phase:2,id:46,t:none,t:normalizePath
+
+; Note : Please note that anti-evasion transformations are not used on REQUEST_FILENAME, which means that you will have to specify them in the rules that use this variable.
+
+== REQUEST_HEADERS ==
+This variable can be used as either a collection of all of the request headers or can be used to inspect selected headers (by using the REQUEST_HEADERS:Header-Name syntax).
+
+SecRule REQUEST_HEADERS:Host "^[\d\.]+$" "deny,id:47,log,status:400,msg:'Host header is a numeric IP address'"
+
+== REQUEST_HEADERS_NAMES ==
+This variable is a collection of the names of all of the request headers.
+
+SecRule REQUEST_HEADERS_NAMES "^x-forwarded-for" "log,deny,id:48,status:403,t:lowercase,msg:'Proxy Server Used'"
+
+== REQUEST_LINE ==
+This variable holds the complete request line sent to the server (including the request method and HTTP version information).
 
-
This variable holds the complete request line sent to the server (including the request method and HTTP version information).
-

 
 # Allow only POST, GET and HEAD request methods, as well as only
 # the valid protocol versions 
-SecRule REQUEST_LINE "!(^((?:(?:POS|GE)T|HEAD))|HTTP/(0\.9|1\.0|1\.1)$)" "phase:1,id:49,log,block,t:none"
+SecRule REQUEST_LINE "!(^((?:(?:POS|GE)T|HEAD))|HTTP/(0\.9|1\.0|1\.1)$)" "phase:1,id:49,log,block,t:none"
 

-
[edit]  REQUEST_METHOD 

-
This variable holds the request method used in the transaction.
 
-
SecRule REQUEST_METHOD "^(?:CONNECT|TRACE)$" "id:50,t:none"
-

-
[edit]  REQUEST_PROTOCOL 

-
This variable holds the request protocol version information.
-
SecRule REQUEST_PROTOCOL "!^HTTP/(0\.9|1\.0|1\.1)$" "id:51"
-

-
[edit]  REQUEST_URI 

+== REQUEST_METHOD ==
+This variable holds the request method used in the transaction.
 
-
This variable holds the full request URL including the query string data (e.g., /index.php? p=X). However, it will never contain a domain name, even if it was provided on the request line.
-
SecRule REQUEST_URI "attack" "phase:1,id:52,t:none,t:urlDecode,t:lowercase,t:normalizePath"
-

-
 Note 
 Please note that anti-evasion transformations are not used on REQUEST_URI, which means that you will have to specify them in the rules that use this variable.
-

-
[edit]  REQUEST_URI_RAW 

-
Same as REQUEST_URI but will contain the domain name if it was provided on the request line (e.g., http://www.example.com/index.php?p=X).
+SecRule REQUEST_METHOD "^(?:CONNECT|TRACE)$" "id:50,t:none"
 
-
SecRule REQUEST_URI_RAW "http:/" "phase:1,id:53,t:none,t:urlDecode,t:lowercase,t:normalizePath"
-

-
 Note 
 Please note that anti-evasion transformations are not used on REQUEST_URI_RAW, which means that you will have to specify them in the rules that use this variable.
-

-
[edit]  RESPONSE_BODY 

-
This variable holds the data for the response body, but only when response body buffering is enabled.
-
SecRule RESPONSE_BODY "ODBC Error Code" "phase:4,id:54,t:none"
+== REQUEST_PROTOCOL ==
+This variable holds the request protocol version information.
 
-

-
[edit]  RESPONSE_CONTENT_LENGTH 

-
Response body length in bytes. Can be available starting with phase 3, but it does not have to be (as the length of response body is not always known in advance). If the size is not known, this variable will contain a zero. If RESPONSE_CONTENT_LENGTH contains a zero in phase 5 that means the actual size of the response body was 0. The value of this variable can change between phases if the body is modified. For example, in embedded mode, mod_deflate can compress the response body between phases 4 and 5.
-

-
[edit]  RESPONSE_CONTENT_TYPE 

+SecRule REQUEST_PROTOCOL "!^HTTP/(0\.9|1\.0|1\.1)$" "id:51"
 
-
Response content type. Available only starting with phase 3. The value available in this variable is taken directly from the internal structures of Apache, which means that it may contain the information that is not yet available in response headers. In embedded deployments, you should always refer to this variable, rather than to RESPONSE_HEADERS:Content-Type.
-

-
[edit]  RESPONSE_HEADERS 

-
This variable refers to response headers, in the same way as REQUEST_HEADERS does to request headers.
-
SecRule RESPONSE_HEADERS:X-Cache "MISS" "id:55"
-
This variable may not have access to some headers when running in embedded mode. Headers such as Server, Date, Connection, and Content-Type could be added just prior to sending the data to the client. This data should be available in phase 5 or when deployed in proxy mode.
-

-
[edit]  RESPONSE_HEADERS_NAMES 

+== REQUEST_URI ==
+This variable holds the full request URL including the query string data (e.g., /index.php? p=X). However, it will never contain a domain name, even if it was provided on the request line.
 
-
This variable is a collection of the response header names.
-
SecRule RESPONSE_HEADERS_NAMES "Set-Cookie" "phase:3,id:56,t:none"
-
The same limitations apply as the ones discussed in RESPONSE_HEADERS.
-

-
[edit]  RESPONSE_PROTOCOL 

-
This variable holds the HTTP response protocol information.
-
SecRule RESPONSE_PROTOCOL "^HTTP\/0\.9" "phase:3,id:57,t:none"
-

-
[edit]  RESPONSE_STATUS 

+SecRule REQUEST_URI "attack" "phase:1,id:52,t:none,t:urlDecode,t:lowercase,t:normalizePath"
 
-
This variable holds the HTTP response status code:
-
SecRule RESPONSE_STATUS "^[45]" "phase:3,id:58,t:none"
-
This variable may not work as expected in embedded mode, as Apache sometimes handles certain requests differently, and without invoking ModSecurity (all other modules).
-

-
[edit]  RULE 

-
This is a special collection that provides access to the id, rev, severity, logdata, and msg fields of the rule that triggered the action. It can be used to refer to only the same rule in which it resides.
-
SecRule &REQUEST_HEADERS:Host "@eq 0" "log,deny,id:59,setvar:tx.varname=%{RULE.id}"
-

+; Note : Please note that anti-evasion transformations are not used on REQUEST_URI, which means that you will have to specify them in the rules that use this variable.
 
-
[edit]  SCRIPT_BASENAME 

-
This variable holds just the local filename part of SCRIPT_FILENAME.
-
SecRule SCRIPT_BASENAME "^login\.php$" "id:60"
-

-
 Note 
  Not available in proxy mode.
-

-
[edit]  SCRIPT_FILENAME 

+== REQUEST_URI_RAW ==
+Same as REQUEST_URI but will contain the domain name if it was provided on the request line (e.g., http://www.example.com/index.php?p=X).
 
-
This variable holds the full internal path to the script that will be used to serve the request. 
-
SecRule SCRIPT_FILENAME "^/usr/local/apache/cgi-bin/login\.php$" "id:61"
-

-
 Note 
 Not available in proxy mode.
-

-
[edit]  SCRIPT_GID 

-
This variable holds the numerical identifier of the group owner of the script. 
+SecRule REQUEST_URI_RAW "http:/" "phase:1,id:53,t:none,t:urlDecode,t:lowercase,t:normalizePath"
 
-
SecRule SCRIPT_GID "!^46$" "id:62"
-

-
 Note 
 Not available in proxy mode.
-

-
[edit]  SCRIPT_GROUPNAME 

-
This variable holds the name of the group owner of the script. 
-
SecRule SCRIPT_GROUPNAME "!^apache$" "id:63"
+; Note : Please note that anti-evasion transformations are not used on REQUEST_URI_RAW, which means that you will have to specify them in the rules that use this variable.
+
+== RESPONSE_BODY ==
+This variable holds the data for the response body, but only when response body buffering is enabled.
+
+SecRule RESPONSE_BODY "ODBC Error Code" "phase:4,id:54,t:none"
+
+== RESPONSE_CONTENT_LENGTH ==
+Response body length in bytes. Can be available starting with phase 3, but it does not have to be (as the length of response body is not always known in advance). If the size is not known, this variable will contain a zero. If RESPONSE_CONTENT_LENGTH contains a zero in phase 5 that means the actual size of the response body was 0. The value of this variable can change between phases if the body is modified. For example, in embedded mode, mod_deflate can compress the response body between phases 4 and 5.
+
+== RESPONSE_CONTENT_TYPE ==
+Response content type. Available only starting with phase 3. The value available in this variable is taken directly from the internal structures of Apache, which means that it may contain the information that is not yet available in response headers. In embedded deployments, you should always refer to this variable, rather than to RESPONSE_HEADERS:Content-Type.
+
+== RESPONSE_HEADERS ==
+This variable refers to response headers, in the same way as REQUEST_HEADERS does to request headers.
+
+SecRule RESPONSE_HEADERS:X-Cache "MISS" "id:55"
+
+This variable may not have access to some headers when running in embedded mode. Headers such as Server, Date, Connection, and Content-Type could be added just prior to sending the data to the client. This data should be available in phase 5 or when deployed in proxy mode.
+
+== RESPONSE_HEADERS_NAMES ==
+This variable is a collection of the response header names.
+
+SecRule RESPONSE_HEADERS_NAMES "Set-Cookie" "phase:3,id:56,t:none"
+
+The same limitations apply as the ones discussed in RESPONSE_HEADERS.
+
+== RESPONSE_PROTOCOL ==
+This variable holds the HTTP response protocol information.
+
+SecRule RESPONSE_PROTOCOL "^HTTP\/0\.9" "phase:3,id:57,t:none"
+
+== RESPONSE_STATUS ==
+This variable holds the HTTP response status code:
+
+SecRule RESPONSE_STATUS "^[45]" "phase:3,id:58,t:none"
+
+This variable may not work as expected in embedded mode, as Apache sometimes handles certain requests differently, and without invoking ModSecurity (all other modules).
+
+== RULE ==
+This is a special collection that provides access to the id, rev, severity, logdata, and msg fields of the rule that triggered the action. It can be used to refer to only the same rule in which it resides.
+
+SecRule &REQUEST_HEADERS:Host "@eq 0" "log,deny,id:59,setvar:tx.varname=%{RULE.id}"
+
+== SCRIPT_BASENAME ==
+This variable holds just the local filename part of SCRIPT_FILENAME.
+
+SecRule SCRIPT_BASENAME "^login\.php$" "id:60"
+
+; Note :  Not available in proxy mode.
+
+== SCRIPT_FILENAME ==
+This variable holds the full internal path to the script that will be used to serve the request. 
+
+SecRule SCRIPT_FILENAME "^/usr/local/apache/cgi-bin/login\.php$" "id:61"
+
+; Note : Not available in proxy mode.
+
+== SCRIPT_GID ==
+This variable holds the numerical identifier of the group owner of the script. 
+
+SecRule SCRIPT_GID "!^46$" "id:62"
+
+; Note : Not available in proxy mode.
+
+== SCRIPT_GROUPNAME ==
+This variable holds the name of the group owner of the script. 
+
+SecRule SCRIPT_GROUPNAME "!^apache$" "id:63"
+
+; Note : Not available in proxy mode.
+
+== SCRIPT_MODE ==
+This variable holds the script’s permissions mode data (e.g., 644).  
 
-

-
 Note 
 Not available in proxy mode.
-

-
[edit]  SCRIPT_MODE 

-
This variable holds the script’s permissions mode data (e.g., 644).  
-

 
 # Do not allow scripts that can be written to
-SecRule SCRIPT_MODE "^(2|3|6|7)$" "id:64"
-
+SecRule SCRIPT_MODE "^(2|3|6|7)$" "id:64"
 

-
 Note 
 Not available in proxy mode.
-

-
[edit]  SCRIPT_UID 

-
This variable holds the numerical identifier of the owner of the script. 
-

+
+; Note : Not available in proxy mode.
+
+== SCRIPT_UID ==
+This variable holds the numerical identifier of the owner of the script. 
+
 
 # Do not run any scripts that are owned 
 # by Apache (Apache's user id is 46) 
-SecRule SCRIPT_UID "!^46$" "id:65"
-
+SecRule SCRIPT_UID "!^46$" "id:65"
 

-
 Note 
 Not available in proxy mode.
-

-
[edit]  SCRIPT_USERNAME 

-
This variable holds the username of the owner of the script. 
-

+
+; Note : Not available in proxy mode.
+
+== SCRIPT_USERNAME ==
+This variable holds the username of the owner of the script. 
+
 
 # Do not run any scripts owned by Apache SecRule 
-SCRIPT_USERNAME "^apache$" "id:66"
-
+SCRIPT_USERNAME "^apache$" "id:66"
 

-
 Note 
 Not available in proxy mode.
-

-
[edit]  SERVER_ADDR 

-
This variable contains the IP address of the server.
-
SecRule SERVER_ADDR "@ipMatch 192.168.1.100" "id:67"
-

 
-
[edit]  SERVER_NAME 

-
This variable contains the transaction’s hostname or IP address, taken from the request itself (which means that, in principle, it should not be trusted).
-
SecRule SERVER_NAME "hostname\.com$" "id:68"
-

-
[edit]  SERVER_PORT 

+; Note : Not available in proxy mode.
+
+== SERVER_ADDR ==
+This variable contains the IP address of the server.
+
+SecRule SERVER_ADDR "@ipMatch 192.168.1.100" "id:67"
+
+== SERVER_NAME ==
+This variable contains the transaction’s hostname or IP address, taken from the request itself (which means that, in principle, it should not be trusted).
+
+SecRule SERVER_NAME "hostname\.com$" "id:68"
+
+== SERVER_PORT ==
+This variable contains the local port that the web server (or reverse proxy) is listening on.
+
+SecRule SERVER_PORT "^80$" "id:69"
+
+== SESSION ==
+This variable is a collection that contains session information. It becomes available only after setsid is executed.
+
+The following example shows how to initialize SESSION using setsid, how to use setvar to increase the SESSION.score values, how to set the SESSION.blocked variable, and finally, how to deny the connection based on the SESSION:blocked value:
 
-
This variable contains the local port that the web server (or reverse proxy) is listening on.
-
SecRule SERVER_PORT "^80$" "id:69"
-

-
[edit]  SESSION 

-
This variable is a collection that contains session information. It becomes available only after setsid is executed.
-
The following example shows how to initialize SESSION using setsid, how to use setvar to increase the SESSION.score values, how to set the SESSION.blocked variable, and finally, how to deny the connection based on the SESSION:blocked value:
-

 
 # Initialize session storage 
-SecRule REQUEST_COOKIES:PHPSESSID !^$ "phase:2,id:70,nolog,pass,setsid:%{REQUEST_COOKIES.PHPSESSID}"
+SecRule REQUEST_COOKIES:PHPSESSID !^$ "phase:2,id:70,nolog,pass,setsid:%{REQUEST_COOKIES.PHPSESSID}"
 
 # Increment session score on attack 
-SecRule REQUEST_URI "^/cgi-bin/finger$" "phase:2,id:71,t:none,t:lowercase,t:normalizePath,pass,setvar:SESSION.score=+10" 
+SecRule REQUEST_URI "^/cgi-bin/finger$" "phase:2,id:71,t:none,t:lowercase,t:normalizePath,pass,setvar:SESSION.score=+10" 
 
 # Detect too many attacks in a session
-SecRule SESSION:score "@gt 50" "phase:2,id:72,pass,setvar:SESSION.blocked=1"
+SecRule SESSION:score "@gt 50" "phase:2,id:72,pass,setvar:SESSION.blocked=1"
 
 # Enforce session block 
-SecRule SESSION:blocked "@eq 1" "phase:2,id:73,deny,status:403"
-
+SecRule SESSION:blocked "@eq 1" "phase:2,id:73,deny,status:403"
 

-
[edit]  SESSIONID 

-
This variable contains the value set with setsid. See SESSION (above) for a complete example.
-

-
[edit]  STREAM_INPUT_BODY 

 
-
This variable give access to the raw request body content.  This variable is best used for two use-cases:
-

-
  1. For fast pattern matching - using @pm/@pmf to prequalify large text strings against any kind of content-type data.  This is more performant vs. using REQUEST_BODY/ARGS_POST/ARGS_POST_NAMES as it happens before ModSecurity parsing in phase:2 variable population.
-
  2. For data substitution - using @rsub against this variable allows you to manipulate live request body data.  Example - to remove offending payloads or to substitute benign data.
-

-
 Note 
 You must enable the SecStreamInBodyInspection directive
-

-
[edit]  STREAM_OUTPUT_BODY 

+== SESSIONID ==
+This variable contains the value set with setsid. See SESSION (above) for a complete example.
 
-
This variable give access to the raw response body content.  This variable is best used for case:
-

-
  1. For data substitution - using @rsub against this variable allows you to manipulate live request body data.  Example - to remove offending payloads or to substitute benign data.
-

-
 Note 
 You must enable the SecStreamOutBodyInspection directive
-

-
[edit]  TIME 

-
This variable holds a formatted string representing the time (hour:minute:second).
+== STREAM_INPUT_BODY ==
+This variable give access to the raw request body content.  This variable is best used for two use-cases:
+#For fast pattern matching - using @pm/@pmf to prequalify large text strings against any kind of content-type data.  This is more performant vs. using REQUEST_BODY/ARGS_POST/ARGS_POST_NAMES as it happens before ModSecurity parsing in phase:2 variable population.
+#For data substitution - using @rsub against this variable allows you to manipulate live request body data.  Example - to remove offending payloads or to substitute benign data.
+; Note : You must enable the SecStreamInBodyInspection directive
 
-
SecRule TIME "^(([1](8|9))|([2](0|1|2|3))):\d{2}:\d{2}$" "id:74"
-

-
[edit]  TIME_DAY 

-
This variable holds the current date (1–31). The following rule triggers on a transaction that’s happening anytime between the 10th and 20th in a month:
-
SecRule TIME_DAY "^(([1](0|1|2|3|4|5|6|7|8|9))|20)$" "id:75"
-

-
[edit]  TIME_EPOCH 

+== STREAM_OUTPUT_BODY ==
+This variable give access to the raw response body content.  This variable is best used for case:
 
-
This variable holds the time in seconds since 1970.
-

-
[edit]  TIME_HOUR 

-
This variable holds the current hour value (0–23). The following rule triggers when a request is made “off hours”:
-
SecRule TIME_HOUR "^(0|1|2|3|4|5|6|[1](8|9)|[2](0|1|2|3))$" "id:76"
-

-
[edit]  TIME_MIN 

+#For data substitution - using @rsub against this variable allows you to manipulate live request body data.  Example - to remove offending payloads or to substitute benign data.
+; Note : You must enable the SecStreamOutBodyInspection directive
 
-
This variable holds the current minute value (0–59). The following rule triggers during the last half hour of every hour:
-
SecRule TIME_MIN "^(3|4|5)" "id:77"
-

-
[edit]  TIME_MON 

-
This variable holds the current month value (0–11). The following rule matches if the month is either November (value 10) or December (value 11):
-
SecRule TIME_MON "^1" "id:78"
-

-
[edit]  TIME_SEC 

+== TIME ==
+This variable holds a formatted string representing the time (hour:minute:second).
 
-
This variable holds the current second value (0–59).
-
SecRule TIME_SEC "@gt 30" "id:79"
-

-
[edit]  TIME_WDAY 

-
This variable holds the current weekday value (0–6). The following rule triggers only on Satur- day and Sunday:
-
SecRule TIME_WDAY "^(0|6)$" "id:80"
-

-
[edit]  TIME_YEAR 

+SecRule TIME "^(([1](8|9))|([2](0|1|2|3))):\d{2}:\d{2}$" "id:74"
+
+== TIME_DAY ==
+This variable holds the current date (1–31). The following rule triggers on a transaction that’s happening anytime between the 10th and 20th in a month:
+
+SecRule TIME_DAY "^(([1](0|1|2|3|4|5|6|7|8|9))|20)$" "id:75"
+
+== TIME_EPOCH ==
+This variable holds the time in seconds since 1970.
+
+== TIME_HOUR ==
+This variable holds the current hour value (0–23). The following rule triggers when a request is made “off hours”:
+
+SecRule TIME_HOUR "^(0|1|2|3|4|5|6|[1](8|9)|[2](0|1|2|3))$" "id:76"
+
+== TIME_MIN ==
+This variable holds the current minute value (0–59). The following rule triggers during the last half hour of every hour:
+
+SecRule TIME_MIN "^(3|4|5)" "id:77"
+
+== TIME_MON ==
+This variable holds the current month value (0–11). The following rule matches if the month is either November (value 10) or December (value 11):
+
+SecRule TIME_MON "^1" "id:78"
+
+== TIME_SEC ==
+This variable holds the current second value (0–59).
+
+SecRule TIME_SEC "@gt 30" "id:79"
+
+== TIME_WDAY ==
+This variable holds the current weekday value (0–6). The following rule triggers only on Satur- day and Sunday:
+
+SecRule TIME_WDAY "^(0|6)$" "id:80"
+
+== TIME_YEAR ==
+This variable holds the current four-digit year value.
+
+SecRule TIME_YEAR "^2006$" "id:81"
+
+== TX ==
+This is the transient transaction collection, which is used to store pieces of data, create a transaction anomaly score, and so on. The variables placed into this collection are available only until the transaction is complete.
 
-
This variable holds the current four-digit year value.
-
SecRule TIME_YEAR "^2006$" "id:81"
-

-
[edit]  TX 

-
This is the transient transaction collection, which is used to store pieces of data, create a transaction anomaly score, and so on. The variables placed into this collection are available only until the transaction is complete.
-

 
 # Increment transaction attack score on attack 
-SecRule ARGS attack "phase:2,id:82,nolog,pass,setvar:TX.score=+5"
+SecRule ARGS attack "phase:2,id:82,nolog,pass,setvar:TX.score=+5"
 
 # Block the transactions whose scores are too high 
-SecRule TX:SCORE "@gt 20" "phase:2,id:83,log,deny"
+SecRule TX:SCORE "@gt 20" "phase:2,id:83,log,deny"
 

-
Some variable names in the TX collection are reserved and cannot be used: 
-

-
  • TX:0: the matching value when using the @rx or @pm operator with the capture action
-
  • TX:1-TX:9: the captured subexpression value when using the @rx operator with capturing parens and the capture action
-
  • TX:MSC_.*: ModSecurity processing flags 
-
  • MSC_PCRE_LIMITS_EXCEEDED: Set to nonzero if PCRE match limits are exceeded. See SecPcreMatchLimit and SecPcreMatchLimitRecursion for more information.
-

-
[edit]  UNIQUE_ID 

 
-
This variable holds the data created by mod_unique_id [7].  This module provides a magic token for each request which is guaranteed to be unique across "all" requests under very specific conditions. The unique identifier is even unique across multiple machines in a properly configured cluster of machines. The environment variable UNIQUE_ID is set to the identifier for each request.  The UNIQUE_ID environment variable is constructed by encoding the 112-bit (32-bit IP address, 32 bit pid, 32 bit time stamp, 16 bit counter) quadruple using the alphabet [A-Za-z0-9@-] in a manner similar to MIME base64 encoding, producing 19 characters.
-

-
[edit]  URLENCODED_ERROR 

-
This variable is created when an invalid URL encoding is encountered during the parsing of a query string (on every request) or during the parsing of an application/x-www-form-urlencoded request body (only on the requests that use the URLENCODED request body processor).
-

-
[edit]  USERID 

+Some variable names in the TX collection are reserved and cannot be used: 
+*TX:0: the matching value when using the @rx or @pm operator with the capture action
+*TX:1-TX:9: the captured subexpression value when using the @rx operator with capturing parens and the capture action
+*TX:MSC_.*: ModSecurity processing flags 
+*MSC_PCRE_LIMITS_EXCEEDED: Set to nonzero if PCRE match limits are exceeded. See SecPcreMatchLimit and SecPcreMatchLimitRecursion for more information.
+
+== UNIQUE_ID ==
+This variable holds the data created by mod_unique_id [http://httpd.apache.org/docs/2.2/mod/mod_unique_id.html].  This module provides a magic token for each request which is guaranteed to be unique across "all" requests under very specific conditions. The unique identifier is even unique across multiple machines in a properly configured cluster of machines. The environment variable UNIQUE_ID is set to the identifier for each request.  The UNIQUE_ID environment variable is constructed by encoding the 112-bit (32-bit IP address, 32 bit pid, 32 bit time stamp, 16 bit counter) quadruple using the alphabet [A-Za-z0-9@-] in a manner similar to MIME base64 encoding, producing 19 characters.
+
+== URLENCODED_ERROR == 
+This variable is created when an invalid URL encoding is encountered during the parsing of a query string (on every request) or during the parsing of an application/x-www-form-urlencoded request body (only on the requests that use the URLENCODED request body processor).
+
+== USERID ==
+This variable contains the value set with setuid. 
 
-
This variable contains the value set with setuid. 
-

 
 # Initialize user tracking
-SecAction "nolog,id:84,pass,setuid:%{REMOTE_USER}" 
+SecAction "nolog,id:84,pass,setuid:%{REMOTE_USER}" 
 
 # Is the current user the administrator?
-SecRule USERID "admin" "id:85"
+SecRule USERID "admin" "id:85"
 

-
[edit]  USERAGENT_IP 

 
-
This variable is created when running modsecurity with apache2.4 and will contains the client ip address set by mod_remoteip in proxied connections.
-

-
[edit]  WEBAPPID 

-
This variable contains the current application name, which is set in configuration using SecWebAppId.
-

-
[edit]  WEBSERVER_ERROR_LOG 

+== USERAGENT_IP == 
+This variable is created when running modsecurity with apache2.4 and will contains the client ip address set by mod_remoteip in proxied connections.
+
+== WEBAPPID ==
+This variable contains the current application name, which is set in configuration using SecWebAppId.
+
+== WEBSERVER_ERROR_LOG ==
+Contains zero or more error messages produced by the web server. This variable is best accessed from phase 5 (logging).
+
+SecRule WEBSERVER_ERROR_LOG "File does not exist" "phase:5,id:86,t:none,nolog,pass,setvar:TX.score=+5"
+
+== XML ==
+Special collection used to interact with the XML parser. It can be used standalone as a target for the validateDTD and validateSchema operator. Otherwise, it must contain a valid XPath expression, which will then be evaluated against a previously parsed XML DOM tree.
 
-
Contains zero or more error messages produced by the web server. This variable is best accessed from phase 5 (logging).
-
SecRule WEBSERVER_ERROR_LOG "File does not exist" "phase:5,id:86,t:none,nolog,pass,setvar:TX.score=+5"
-

-
[edit]  XML 

-
Special collection used to interact with the XML parser. It can be used standalone as a target for the validateDTD and validateSchema operator. Otherwise, it must contain a valid XPath expression, which will then be evaluated against a previously parsed XML DOM tree.
-

 
 SecDefaultAction log,deny,status:403,phase:2,id:90
-SecRule REQUEST_HEADERS:Content-Type ^text/xml$ "phase:1,id:87,t:lowercase,nolog,pass,ctl:requestBodyProcessor=XML"
+SecRule REQUEST_HEADERS:Content-Type ^text/xml$ "phase:1,id:87,t:lowercase,nolog,pass,ctl:requestBodyProcessor=XML"
+SecRule REQBODY_PROCESSOR "!^XML$" skipAfter:12345,id:88
 
-SecRule REQBODY_PROCESSOR "!^XML$" skipAfter:12345,id:88
-
-SecRule XML:/employees/employee/name/text() Fred "id:89"
-SecRule XML:/xq:employees/employee/name/text() Fred "id:12345,xmlns:xq=http://www.example.com/employees"
+SecRule XML:/employees/employee/name/text() Fred "id:89"
+SecRule XML:/xq:employees/employee/name/text() Fred "id:12345,xmlns:xq=http://www.example.com/employees"
 

-
The first XPath expression does not use namespaces. It would match against payload such as this one:
-

+
+The first XPath expression does not use namespaces. It would match against payload such as this one:
 
-<employees>
-    <employee>
-
-        <name>Fred Jones</name>
-        <address location="home">
-            <street>900 Aurora Ave.</street>
-            <city>Seattle</city>
-
-            <state>WA</state>
-            <zip>98115</zip>
-        </address>
-        <address location="work">
-
-            <street>2011 152nd Avenue NE</street>
-            <city>Redmond</city>
-            <state>WA</state>
-            <zip>98052</zip>
-
-        </address>
-        <phone location="work">(425)555-5665</phone>
-        <phone location="home">(206)555-5555</phone>
-        <phone location="mobile">(206)555-4321</phone>
-
-    </employee>
-</employees>
+
+    
+        Fred Jones
+        

+            900 Aurora Ave.
+            Seattle
+            WA
+            98115
+        

+        

+            2011 152nd Avenue NE
+            Redmond
+            WA
+            98052
+        

+        (425)555-5665
+        (206)555-5555
+        (206)555-4321
+    
+
 

-
The second XPath expression does use namespaces. It would match the following payload:
-

+
+The second XPath expression does use namespaces. It would match the following payload:
 
-<xq:employees xmlns:xq="http://www.example.com/employees">
-    <employee>
-        <name>Fred Jones</name>
-
-        <address location="home">
-            <street>900 Aurora Ave.</street>
-            <city>Seattle</city>
-            <state>WA</state>
-
-            <zip>98115</zip>
-        </address>
-        <address location="work">
-            <street>2011 152nd Avenue NE</street>
-
-            <city>Redmond</city>
-            <state>WA</state>
-            <zip>98052</zip>
-        </address>
-
-        <phone location="work">(425)555-5665</phone>
-        <phone location="home">(206)555-5555</phone>
-        <phone location="mobile">(206)555-4321</phone>
-
-    </employee>
-</xq:employees>
+
+    
+        Fred Jones
+        

+            900 Aurora Ave.
+            Seattle
+            WA
+            98115
+        

+        

+            2011 152nd Avenue NE
+            Redmond
+            WA
+            98052
+        

+        (425)555-5665
+        (206)555-5555
+        (206)555-4321
+    
+
 

-
Note the different namespace used in the second example.
-

-
[edit]  Transformation functions 

-
Transformation functions are used to alter input data before it is used in matching (i.e., operator execution). The input data is never modified, actually—whenever you request a transformation function to be used, ModSecurity will create a copy of the data, transform it, and then run the operator against the result.
-

 
-
 Note 
 There are no default transformation functions, as there were in the first generation of ModSecurity (1.x).
-

-
In the following example, the request parameter values are converted to lowercase before matching:
-
SecRule ARGS "xp_cmdshell" "t:lowercase,id:91"
-
Multiple transformation actions can be used in the same rule, forming a transformation pipeline. The transformations will be performed in the order in which they appear in the rule.
-
In most cases, the order in which transformations are performed is very important. In the following example, a series of transformation functions is performed to counter evasion. Performing the transformations in any other order would allow a skillful attacker to evade detection:
-
SecRule ARGS "(asfunction|javascript|vbscript|data|mocha|livescript):" "id:92,t:none,t:htmlEntityDecode,t:lowercase,t:removeNulls,t:removeWhitespace"
-

-
 Warning 
 It is currently possible to use SecDefaultAction to specify a default list of transformation functions, which will be applied to all rules that follow the SecDefaultAction directive. However, this practice is not recommended, because it means that mistakes are very easy to make. It is recommended that you always specify the transformation functions that are needed by a particular rule, starting the list with t:none (which clears the possibly inherited transformation functions).
+Note the different namespace used in the second example.
 
-

-
The remainder of this section documents the transformation functions currently available in ModSecurity.
-

-
[edit]  base64Decode 

-
Decodes a Base64-encoded string.
-

+= Transformation functions =
+Transformation functions are used to alter input data before it is used in matching (i.e., operator execution). The input data is never modified, actually—whenever you request a transformation function to be used, ModSecurity will create a copy of the data, transform it, and then run the operator against the result.
+
+; Note : There are no default transformation functions, as there were in the first generation of ModSecurity (1.x).
+
+In the following example, the request parameter values are converted to lowercase before matching:
+
+SecRule ARGS "xp_cmdshell" "t:lowercase,id:91"
+
+Multiple transformation actions can be used in the same rule, forming a transformation pipeline. The transformations will be performed in the order in which they appear in the rule.
+
+In most cases, the order in which transformations are performed is very important. In the following example, a series of transformation functions is performed to counter evasion. Performing the transformations in any other order would allow a skillful attacker to evade detection:
+
+SecRule ARGS "(asfunction|javascript|vbscript|data|mocha|livescript):" "id:92,t:none,t:htmlEntityDecode,t:lowercase,t:removeNulls,t:removeWhitespace"
+
+; Warning : It is currently possible to use SecDefaultAction to specify a default list of transformation functions, which will be applied to all rules that follow the SecDefaultAction directive. However, this practice is not recommended, because it means that mistakes are very easy to make. It is recommended that you always specify the transformation functions that are needed by a particular rule, starting the list with t:none (which clears the possibly inherited transformation functions).
+
+The remainder of this section documents the transformation functions currently available in ModSecurity.
+
+== base64Decode ==
+Decodes a Base64-encoded string.
 
-SecRule REQUEST_HEADERS:Authorization "^Basic ([a-zA-Z0-9]+=*)$" "phase:1,id:93,capture,chain,logdata:%{TX.1}"
-
+SecRule REQUEST_HEADERS:Authorization "^Basic ([a-zA-Z0-9]+=*)$" "phase:1,id:93,capture,chain,logdata:%{TX.1}"
   SecRule TX:1 ^(\w+): t:base64Decode,capture,chain
     SecRule TX:1 ^(admin|root|backup)$ 
 

-
[edit]  sqlHexDecode 

-
Decode sql hex data. Example (0x414243) will be decoded to (ABC). Available as of 2.6.3
-

-
[edit]  base64DecodeExt 

 
-
Decodes a Base64-encoded string. Unlike base64Decode, this version uses a forgiving implementation, which ignores invalid characters. Available as of 2.5.13.
-
See blog post on Base64Decoding evasion issues on PHP sites - http://blog.spiderlabs.com/2010/04/impedance-mismatch-and-base64.html
-

-
[edit]  base64Encode 

-
Encodes input string using Base64 encoding.
-

-
[edit]  cmdLine 

+== sqlHexDecode ==
+Decode sql hex data. Example (0x414243) will be decoded to (ABC). Available as of 2.6.3
 
-
 Note 
 This is a community contribution developed by Marc Stern [8]
-

-
In Windows and Unix, commands may be escaped by different means, such as:
-

-
  • c^ommand /c ...
-
  • "command" /c ...
-
  • command,/c ...
-
  • backslash in the middle of a Unix command
-

-
The cmdLine transformation function avoids this problem by manipulating the variable contend in the following ways:
-

-
  • deleting all backslashes [\]
+== base64DecodeExt ==
+Decodes a Base64-encoded string. Unlike base64Decode, this version uses a forgiving implementation, which ignores invalid characters. Available as of 2.5.13.
 
-
  • deleting all double quotes ["]
-
  • deleting all sigle quotes [']
-
  • deleting all carets [^]
-
  • deleting spaces before a slash [/]
-
  • deleting spaces before an open parentesis [(]
-
  • replacing all commas [,] and semicolon [;] into a space
-
  • replacing all multiple spaces (including tab, newline, etc.) into one space
-
  • transform all characters to lowercase
-

-
Example Usage:
-

+See blog post on Base64Decoding evasion issues on PHP sites - http://blog.spiderlabs.com/2010/04/impedance-mismatch-and-base64.html
+
+== base64Encode ==
+Encodes input string using Base64 encoding.
+
+== cmdLine ==
+; Note : This is a community contribution developed by Marc Stern [http://www.linkedin.com/in/marcstern]
+In Windows and Unix, commands may be escaped by different means, such as:
+*c^ommand /c ...
+*"command" /c ...
+*command,/c ...
+*backslash in the middle of a Unix command
+The cmdLine transformation function avoids this problem by manipulating the variable contend in the following ways:
+*deleting all backslashes [\]
+*deleting all double quotes ["]
+*deleting all sigle quotes [']
+*deleting all carets [^]
+*deleting spaces before a slash [/]
+*deleting spaces before an open parentesis [(]
+*replacing all commas [,] and semicolon [;] into a space
+*replacing all multiple spaces (including tab, newline, etc.) into one space
+*transform all characters to lowercase
+
+'''Example Usage:'''
 
-SecRule ARGS "(?:command(?:.com)?|cmd(?:.exe)?)(?:/.*)?/[ck]" "phase:2,id:94,t:none, t:cmdLine"
-
+SecRule ARGS "(?:command(?:.com)?|cmd(?:.exe)?)(?:/.*)?/[ck]" "phase:2,id:94,t:none, t:cmdLine"
 

-
[edit]  compressWhitespace 

-
Converts any of the whitespace characters (0x20, \f, \t, \n, \r, \v, 0xa0) to spaces (ASCII 0x20), compressing multiple consecutive space characters into one.
-

-
[edit]  cssDecode 

 
-
Decodes characters encoded using the CSS 2.x escape rules syndata.html#characters. This function uses only up to two bytes in the decoding process, meaning that it is useful to uncover ASCII characters encoded using CSS encoding (that wouldn’t normally be encoded), or to counter evasion, which is a combination of a backslash and non-hexadecimal characters (e.g., ja\vascript is equivalent to javascript).
-

-
[edit]  escapeSeqDecode 

-
Decodes ANSI C escape sequences: \a, \b, \f, \n, \r, \t, \v, \\, \?, \', \", \xHH (hexadecimal), \0OOO (octal). Invalid encodings are left in the output.
-

-
[edit]  hexDecode 

+== compressWhitespace ==
+Converts any of the whitespace characters (0x20, \f, \t, \n, \r, \v, 0xa0) to spaces (ASCII 0x20), compressing multiple consecutive space characters into one.
 
-
Decodes a string that has been encoded using the same algorithm as the one used in hexEncode (see following entry).
-

-
[edit]  hexEncode 

-
Encodes string (possibly containing binary characters) by replacing each input byte with two hexadecimal characters. For example, xyz is encoded as 78797a.
-

-
[edit]  htmlEntityDecode 

+== cssDecode == 
+Decodes characters encoded using the CSS 2.x escape rules [http://www.w3.org/TR/CSS2/ syndata.html#characters]. This function uses only up to two bytes in the decoding process, meaning that it is useful to uncover ASCII characters encoded using CSS encoding (that wouldn’t normally be encoded), or to counter evasion, which is a combination of a backslash and non-hexadecimal characters (e.g., ja\vascript is equivalent to javascript).
 
-
Decodes the characters encoded as HTML entities. The following variants are supported: 
-

-
  • &#xHH and &#xHH; (where H is any hexadecimal number)
-
  • &#DDD and &#DDD; (where D is any decimal number) 
-
  • &quotand" 
-
  • &nbspand  
-
  • &ltand<
-
  • &gtand>
-

-
This function always converts one HTML entity into one byte, possibly resulting in a loss of information (if the entity refers to a character that cannot be represented with the single byte). It is thus useful to uncover bytes that would otherwise not need to be encoded, but it cannot do anything meaningful with the characters from the range above 0xff.
-

+== escapeSeqDecode == 
+Decodes ANSI C escape sequences: \a, \b, \f, \n, \r, \t, \v, \\, \?, \', \", \xHH (hexadecimal), \0OOO (octal). Invalid encodings are left in the output.
 
-
[edit]  jsDecode 

-
Decodes JavaScript escape sequences. If a \uHHHH code is in the range of FF01-FF5E (the full width ASCII codes), then the higher byte is used to detect and adjust the lower byte. Otherwise, only the lower byte will be used and the higher byte zeroed (leading to possible loss of information).
-

-
[edit]  length 

-
Looks up the length of the input string in bytes, placing it (as string) in output. For example, if it gets ABCDE on input, this transformation function will return 5 on output.
+== hexDecode == 
+Decodes a string that has been encoded using the same algorithm as the one used in hexEncode (see following entry).
 
-

-
[edit]  lowercase 

-
Converts all characters to lowercase using the current C locale.
-

-
[edit]  md5 

+== hexEncode == 
+Encodes string (possibly containing binary characters) by replacing each input byte with two hexadecimal characters. For example, xyz is encoded as 78797a.
 
-
Calculates an MD5 hash from the data in input. The computed hash is in a raw binary form and may need encoded into text to be printed (or logged). Hash functions are commonly used in combination with hexEncode (for example: t:md5,t:hexEncode).
-

-
[edit]  none 

-
Not an actual transformation function, but an instruction to ModSecurity to remove all transformation functions associated with the current rule.
-

-
[edit]  normalisePath 

+== htmlEntityDecode == 
+Decodes the characters encoded as HTML entities. The following variants are supported: 
+*&#xHH and &#xHH; (where H is any hexadecimal number)
+*&#DDD and &#DDD; (where D is any decimal number) 
+*"and" 
+* and  
+*<and<
+*>and>
 
-
Removes multiple slashes, directory self-references, and directory back-references (except when at the beginning of the input) from input string.
-

-
[edit]  normalisePathWin 

-
Same as normalisePath, but first converts backslash characters to forward slashes.
-

-
[edit]  parityEven7bit 

+This function always converts one HTML entity into one byte, possibly resulting in a loss of information (if the entity refers to a character that cannot be represented with the single byte). It is thus useful to uncover bytes that would otherwise not need to be encoded, but it cannot do anything meaningful with the characters from the range above 0xff.
 
-
Calculates even parity of 7-bit data replacing the 8th bit of each target byte with the calculated parity bit.
-

-
[edit]  parityOdd7bit 

-
Calculates odd parity of 7-bit data replacing the 8th bit of each target byte with the calculated parity bit.
-

-
[edit]  parityZero7bit 

+== jsDecode == 
+Decodes JavaScript escape sequences. If a \uHHHH code is in the range of FF01-FF5E (the full width ASCII codes), then the higher byte is used to detect and adjust the lower byte. Otherwise, only the lower byte will be used and the higher byte zeroed (leading to possible loss of information).
 
-
Calculates zero parity of 7-bit data replacing the 8th bit of each target byte with a zero-parity bit, which allows inspection of even/odd parity 7-bit data as ASCII7 data.
-

-
[edit]  removeNulls 

-
Removes all NUL bytes from input.
-

-
[edit]  removeWhitespace 

+== length == 
+Looks up the length of the input string in bytes, placing it (as string) in output. For example, if it gets ABCDE on input, this transformation function will return 5 on output.
 
-
Removes all whitespace characters from input.
-

-
[edit]  replaceComments 

-
Replaces each occurrence of a C-style comment (/* ... */) with a single space (multiple consecutive occurrences of which will not be compressed). Unterminated comments will also be replaced with a space (ASCII 0x20). However, a standalone termination of a comment (*/) will not be acted upon.
-

-
[edit]  removeCommentsChar 

+== lowercase == 
+Converts all characters to lowercase using the current C locale.
 
-
Removes common comments chars (/*, */, --, #).
-

-
[edit]  removeComments 

-
Removes each occurrence of comment (/* ... */, --, #). Multiple consecutive occurrences of which will not be compressed.
-

-
[edit]  replaceNulls 

+== md5 ==
+Calculates an MD5 hash from the data in input. The computed hash is in a raw binary form and may need encoded into text to be printed (or logged). Hash functions are commonly used in combination with hexEncode (for example: t:md5,t:hexEncode).
+ 
+== none == 
+Not an actual transformation function, but an instruction to ModSecurity to remove all transformation functions associated with the current rule.
 
-
Replaces NUL bytes in input with space characters (ASCII 0x20).
-

-
[edit]  urlDecode 

-
Decodes a URL-encoded input string. Invalid encodings (i.e., the ones that use non-hexadecimal characters, or the ones that are at the end of string and have one or two bytes missing) are not converted, but no error is raised. To detect invalid encodings, use the @validateUrlEncoding operator on the input data first. The transformation function should not be used against variables that have already been URL-decoded (such as request parameters) unless it is your intention to perform URL decoding twice!
-

-
[edit]  urlDecodeUni 

+== normalisePath == 
+Removes multiple slashes, directory self-references, and directory back-references (except when at the beginning of the input) from input string.
 
-
Like urlDecode, but with support for the Microsoft-specific %u encoding. If the code is in the range of FF01-FF5E (the full-width ASCII codes), then the higher byte is used to detect and adjust the lower byte. Otherwise, only the lower byte will be used and the higher byte zeroed.
-

-
[edit]  urlEncode 

-
Encodes input string using URL encoding.
-

-
[edit]  utf8toUnicode 

+== normalisePathWin == 
+Same as normalisePath, but first converts backslash characters to forward slashes.
 
-
Converts all UTF-8 characters sequences to Unicode. This help input normalization specially for non-english languages minimizing false-positives and false-negatives. (available with 2.7.0)
-

-
[edit]  sha1 

-
Calculates a SHA1 hash from the input string. The computed hash is in a raw binary form and may need encoded into text to be printed (or logged). Hash functions are commonly used in combination with hexEncode (for example, t:sha1,t:hexEncode).
-

-
[edit]  trimLeft 

+== parityEven7bit == 
+Calculates even parity of 7-bit data replacing the 8th bit of each target byte with the calculated parity bit.
 
-
Removes whitespace from the left side of the input string.
-

-
[edit]  trimRight 

-
Removes whitespace from the right side of the input string.
-

-
[edit]  trim 

+== parityOdd7bit == 
+Calculates odd parity of 7-bit data replacing the 8th bit of each target byte with the calculated parity bit.
 
-
Removes whitespace from both the left and right sides of the input string.
-

-
[edit]  Actions 

-
Each action belongs to one of five groups:
-

-
  • Disruptive actions - Cause ModSecurity to do something. In many cases something means block transaction, but not in all. For example, the allow action is classified as a disruptive action, but it does the opposite of blocking. There can only be one disruptive action per rule (if there are multiple disruptive actions present, or inherited, only the last one will take effect), or rule chain (in a chain, a disruptive action can only appear in the first rule).
-

-
 Note 
 Disruptive actions will NOT be executed if the SecRuleEngine is set to DetectionOnly.  If you are creating exception/whitelisting rules that use the allow action, you should also add the ctl:ruleEngine=On action to execute the action.
+== parityZero7bit == 
+Calculates zero parity of 7-bit data replacing the 8th bit of each target byte with a zero-parity bit, which allows inspection of even/odd parity 7-bit data as ASCII7 data.
 
-

-
  •  Non-disruptive actions - Do something, but that something does not and cannot affect the rule processing flow. Setting a variable, or changing its value is an example of a non-disruptive action. Non-disruptive action can appear in any rule, including each rule belonging to a chain.
-
  •  Flow actions - These actions affect the rule flow (for example skip or skipAfter).
-
  •  Meta-data actions - Meta-data actions are used to provide more information about rules. Examples include id, rev, severity and msg.
-
  •  Data actions - Not really actions, these are mere containers that hold data used by other actions. For example, the status action holds the status that will be used for blocking (if it takes place).
+== removeNulls == 
+Removes all NUL bytes from input.
 
-

-
[edit]  accuracy 

-
Description: Specifies the relative accuracy level of the rule related to false positives/negatives.  The value is a string based on a numeric scale (1-9 where 9 is very strong and 1 has many false positives).
-
Action Group: Meta-data
-
Version: 2.7
+== removeWhitespace == 
+Removes all whitespace characters from input.
 
-
Example:
-

+== replaceComments == 
+Replaces each occurrence of a C-style comment (/* ... */) with a single space (multiple consecutive occurrences of which will not be compressed). Unterminated comments will also be replaced with a space (ASCII 0x20). However, a standalone termination of a comment (*/) will not be acted upon.
+
+== removeCommentsChar == 
+Removes common comments chars (/*, */, --, #).
+
+== removeComments == 
+Removes each occurrence of comment (/* ... */, --, #). Multiple consecutive occurrences of which will not be compressed.
+
+== replaceNulls == 
+Replaces NUL bytes in input with space characters (ASCII 0x20).
+
+== urlDecode == 
+Decodes a URL-encoded input string. Invalid encodings (i.e., the ones that use non-hexadecimal characters, or the ones that are at the end of string and have one or two bytes missing) are not converted, but no error is raised. To detect invalid encodings, use the @validateUrlEncoding operator on the input data first. The transformation function should not be used against variables that have already been URL-decoded (such as request parameters) unless it is your intention to perform URL decoding twice!
+
+== urlDecodeUni == 
+Like urlDecode, but with support for the Microsoft-specific %u encoding. If the code is in the range of FF01-FF5E (the full-width ASCII codes), then the higher byte is used to detect and adjust the lower byte. Otherwise, only the lower byte will be used and the higher byte zeroed.
+
+== urlEncode == 
+Encodes input string using URL encoding.
+
+== utf8toUnicode == 
+Converts all UTF-8 characters sequences to Unicode. This help input normalization specially for non-english languages minimizing false-positives and false-negatives. (available with 2.7.0)
+
+== sha1 == 
+Calculates a SHA1 hash from the input string. The computed hash is in a raw binary form and may need encoded into text to be printed (or logged). Hash functions are commonly used in combination with hexEncode (for example, t:sha1,t:hexEncode).
+
+== trimLeft == 
+Removes whitespace from the left side of the input string.
+
+== trimRight == 
+Removes whitespace from the right side of the input string.
+
+== trim ==
+Removes whitespace from both the left and right sides of the input string.
+
+= Actions =
+Each action belongs to one of five groups:
+*'''Disruptive actions''' - Cause ModSecurity to do something. In many cases something means block transaction, but not in all. For example, the allow action is classified as a disruptive action, but it does the opposite of blocking. There can only be one disruptive action per rule (if there are multiple disruptive actions present, or inherited, only the last one will take effect), or rule chain (in a chain, a disruptive action can only appear in the first rule).
+; Note : '''Disruptive actions will NOT be executed if the SecRuleEngine is set to DetectionOnly'''.  If you are creating exception/whitelisting rules that use the allow action, you should also add the ctl:ruleEngine=On action to execute the action.
+* '''Non-disruptive action'''s - Do something, but that something does not and cannot affect the rule processing flow. Setting a variable, or changing its value is an example of a non-disruptive action. Non-disruptive action can appear in any rule, including each rule belonging to a chain.
+* '''Flow actions''' - These actions affect the rule flow (for example skip or skipAfter).
+* '''Meta-data actions''' - Meta-data actions are used to provide more information about rules. Examples include id, rev, severity and msg.
+* '''Data actions''' - Not really actions, these are mere containers that hold data used by other actions. For example, the status action holds the status that will be used for blocking (if it takes place).
+
+== accuracy ==
+'''Description:''' Specifies the relative accuracy level of the rule related to false positives/negatives.  The value is a string based on a numeric scale (1-9 where 9 is very strong and 1 has many false positives).
+
+'''Action Group:''' Meta-data
+
+'''Version:''' 2.7
+
+'''Example:'''
 
-SecRule REQUEST_FILENAME|ARGS_NAMES|ARGS|XML:/* "\bgetparentfolder\b" \
-	"phase:2,ver:'CRS/2.2.4,accuracy:'9',maturity:'9',capture,t:none,t:htmlEntityDecode,t:compressWhiteSpace,t:lowercase,ctl:auditLogParts=+E,block,msg:'Cross-site Scripting (XSS) Attack',id:'958016',tag:'WEB_ATTACK/XSS',tag:'WASCTC/WASC-8',tag:'WASCTC/WASC-22',tag:'OWASP_TOP_10/A2',tag:'OWASP_AppSensor/IE1',tag:'PCI/6.5.1',logdata:'% \
-{TX.0}',severity:'2',setvar:'tx.msg=%{rule.msg}',setvar:tx.xss_score=+%{tx.critical_anomaly_score},setvar:tx.anomaly_score=+%{tx.critical_anomaly_score},setvar:tx.%{rule.id}-WEB_ATTACK/XSS-%{matched_var_name}=%{tx.0}"
+SecRule REQUEST_FILENAME|ARGS_NAMES|ARGS|XML:/* "\bgetparentfolder\b" \
+	"phase:2,ver:'CRS/2.2.4,accuracy:'9',maturity:'9',capture,t:none,t:htmlEntityDecode,t:compressWhiteSpace,t:lowercase,ctl:auditLogParts=+E,block,msg:'Cross-site Scripting (XSS) Attack',id:'958016',tag:'WEB_ATTACK/XSS',tag:'WASCTC/WASC-8',tag:'WASCTC/WASC-22',tag:'OWASP_TOP_10/A2',tag:'OWASP_AppSensor/IE1',tag:'PCI/6.5.1',logdata:'% \
+{TX.0}',severity:'2',setvar:'tx.msg=%{rule.msg}',setvar:tx.xss_score=+%{tx.critical_anomaly_score},setvar:tx.anomaly_score=+%{tx.critical_anomaly_score},setvar:tx.%{rule.id}-WEB_ATTACK/XSS-%{matched_var_name}=%{tx.0}"
 

-
[edit]  allow 

 
-
Description: Stops rule processing on a successful match and allows the transaction to proceed.
-
Action Group: Disruptive
-
Example:
-

+== allow == 
+'''Description:''' Stops rule processing on a successful match and allows the transaction to proceed.
+
+'''Action Group:''' Disruptive
+
+Example:
 
 # Allow unrestricted access from 192.168.1.100 
-SecRule REMOTE_ADDR "^192\.168\.1\.100$" phase:1,id:95,nolog,allow
+SecRule REMOTE_ADDR "^192\.168\.1\.100$" phase:1,id:95,nolog,allow
 

-


-Prior to ModSecurity 2.5 the allow action would only affect the current phase. An allow in phase 1 would skip processing the remaining rules in phase 1 but the rules from phase 2 would execute. Starting with v2.5.0 allow was enhanced to allow for fine-grained control of what is done. The following rules now apply:
-

 
-
  1. If used one its own, like in the example above, allow will affect the entire transaction, stopping processing of the current phase but also skipping over all other phases apart from the logging phase. (The logging phase is special; it is designed to always execute.)
-
  2. If used with parameter "phase", allow will cause the engine to stop processing the current phase. Other phases will continue as normal.
-
  3. If used with parameter "request", allow will cause the engine to stop processing the current phase. The next phase to be processed will be phase RESPONSE_HEADERS.
-

-
Examples:
-

+
+Prior to ModSecurity 2.5 the allow action would only affect the current phase. An allow in phase 1 would skip processing the remaining rules in phase 1 but the rules from phase 2 would execute. Starting with v2.5.0 allow was enhanced to allow for fine-grained control of what is done. The following rules now apply:
+#If used one its own, like in the example above, allow will affect the entire transaction, stopping processing of the current phase but also skipping over all other phases apart from the logging phase. (The logging phase is special; it is designed to always execute.)
+#If used with parameter "phase", allow will cause the engine to stop processing the current phase. Other phases will continue as normal.
+#If used with parameter "request", allow will cause the engine to stop processing the current phase. The next phase to be processed will be phase RESPONSE_HEADERS.
+
+Examples:
 
 # Do not process request but process response.
 SecAction phase:1,allow:request,id:96
@@ -3090,40 +2596,46 @@ SecAction phase:1,allow:request,id:96
 # Do not process transaction (request and response).
 SecAction phase:1,allow,id:97
 

-
If you want to allow a response through, put a rule in phase RESPONSE_HEADERS and simply use allow on its own:
-

+
+If you want to allow a response through, put a rule in phase RESPONSE_HEADERS and simply use allow on its own:
 
 # Allow response through.
 SecAction phase:3,allow,id:98
 

-
[edit]  append 

 
-
Description: Appends text given as parameter to the end of response body. Content injection must be en- abled (using the SecContentInjection directive). No content type checks are made, which means that before using any of the content injection actions, you must check whether the content type of the response is adequate for injection.
-
Action Group: Non-disruptive
-
Processing Phases: 3 and 4.
-
Example:
-

-
SecRule RESPONSE_CONTENT_TYPE "^text/html" "nolog,id:99,pass,append:'<hr>Footer'"

+== append ==
+'''Description''': Appends text given as parameter to the end of response body. Content injection must be en- abled (using the SecContentInjection directive). No content type checks are made, which means that before using any of the content injection actions, you must check whether the content type of the response is adequate for injection.
 
-
 Warning 
 Although macro expansion is allowed in the additional content, you are strongly cau- tioned against inserting user-defined data fields into output. Doing so would create a cross-site scripting vulnerability.
-

-
[edit]  auditlog 

-
Description: Marks the transaction for logging in the audit log.
-
Action Group: Non-disruptive
+'''Action Group:''' Non-disruptive
 
-
Example:
-
SecRule REMOTE_ADDR "^192\.168\.1\.100$" auditlog,phase:1,id:100,allow
-

-
 Note 
 The auditlog action is now explicit if log is already specified.
-

-
[edit]  block 

-
Description: Performs the disruptive action defined by the previous SecDefaultAction.
+'''Processing Phases:''' 3 and 4.
 
-
Action Group: Disruptive
-
This action is essentially a placeholder that is intended to be used by rule writers to request a blocking action, but without specifying how the blocking is to be done. The idea is that such decisions are best left to rule users, as well as to allow users, to override blocking if they so desire. 
+Example:
+
+
SecRule RESPONSE_CONTENT_TYPE "^text/html" "nolog,id:99,pass,append:'
Footer'"

+
+; Warning : Although macro expansion is allowed in the additional content, you are strongly cau- tioned against inserting user-defined data fields into output. Doing so would create a cross-site scripting vulnerability.
+
+== auditlog ==
+'''Description:''' Marks the transaction for logging in the audit log.
+
+'''Action Group''': Non-disruptive
+
+Example:
+
+SecRule REMOTE_ADDR "^192\.168\.1\.100$" auditlog,phase:1,id:100,allow
+
+; Note : The auditlog action is now explicit if log is already specified.
+
+== block ==
+'''Description:''' Performs the disruptive action defined by the previous SecDefaultAction.
+
+'''Action Group:''' Disruptive
+
+This action is essentially a placeholder that is intended to be used by rule writers to request a blocking action, but without specifying how the blocking is to be done. The idea is that such decisions are best left to rule users, as well as to allow users, to override blocking if they so desire. 
 In future versions of ModSecurity, more control and functionality will be added to define "how" to block.
-
Examples:
-

+
+Examples:
 
 # Specify how blocking is to be done 
 SecDefaultAction phase:2,deny,id:101,status:403,log,auditlog
@@ -3134,15 +2646,13 @@ SecRule ARGS attack1 phase:2,block,id:102
 # Detect attacks where we want only to warn 
 SecRule ARGS attack2 phase:2,pass,id:103
 

-
It is possible to use the SecRuleUpdateActionById directive to override how a rule handles blocking. This is useful in three cases:
-

-
  1. If a rule has blocking hard-coded, and you want it to use the policy you determine 
-
  2. If a rule was written to block, but you want it to only warn 
-
  3. If a rule was written to only warn, but you want it to block
-

-
The following example demonstrates the first case, in which the hard-coded block is removed in favor of the user-controllable block:
-

 
+It is possible to use the SecRuleUpdateActionById directive to override how a rule handles blocking. This is useful in three cases:
+#If a rule has blocking hard-coded, and you want it to use the policy you determine 
+#If a rule was written to block, but you want it to only warn 
+#If a rule was written to only warn, but you want it to block
+
+The following example demonstrates the first case, in which the hard-coded block is removed in favor of the user-controllable block:
 
 # Specify how blocking is to be done 
 SecDefaultAction phase:2,deny,status:403,log,auditlog,id:104
@@ -3153,756 +2663,775 @@ SecRule ARGS attack1 phase:2,id:1,deny
 # Change how rule ID 1 blocks 
 SecRuleUpdateActionById 1 block
 

-
[edit]  capture 

-
Description: When used together with the regular expression operator (@rx), the capture action will create copies of the regular expression captures and place them into the transaction variable collection.
-
Action Group: Non-disruptive
-
Example:
 
-

+== capture ==
+'''Description:''' When used together with the regular expression operator (@rx), the capture action will create copies of the regular expression captures and place them into the transaction variable collection.
+
+'''Action Group:''' Non-disruptive
+
+Example:
 
-SecRule REQUEST_BODY "^username=(\w{25,})" phase:2,capture,t:none,chain,id:105
-  SecRule TX:1 "(?:(?:a(dmin|nonymous)))"
+SecRule REQUEST_BODY "^username=(\w{25,})" phase:2,capture,t:none,chain,id:105
+  SecRule TX:1 "(?:(?:a(dmin|nonymous)))"
 

-
Up to 10 captures will be copied on a successful pattern match, each with a name consisting of a digit from 0 to 9. The TX.0 variable always contains the entire area that the regular expression matched. All the other variables contain the captured values, in the order in which the capturing parentheses appear in the regular expression.
-

-
[edit]  chain 

 
-
Description: Chains the current rule with the rule that immediately follows it, creating a rule chain. Chained rules allow for more complex processing logic.
-
Action Group: Flow
-
Example:
-

+Up to 10 captures will be copied on a successful pattern match, each with a name consisting of a digit from 0 to 9. The TX.0 variable always contains the entire area that the regular expression matched. All the other variables contain the captured values, in the order in which the capturing parentheses appear in the regular expression.
+
+== chain ==
+'''Description:''' Chains the current rule with the rule that immediately follows it, creating a rule chain. Chained rules allow for more complex processing logic.
+
+'''Action Group:''' Flow
+
+Example:
 
 # Refuse to accept POST requests that do not contain Content-Length header. 
 # (Do note that this rule should be preceded by a rule 
 # that verifies only valid request methods are used.) 
-SecRule REQUEST_METHOD "^POST$" phase:1,chain,t:none,id:105
-  SecRule &REQUEST_HEADERS:Content-Length "@eq 0" t:none
-
+SecRule REQUEST_METHOD "^POST$" phase:1,chain,t:none,id:105
+  SecRule &REQUEST_HEADERS:Content-Length "@eq 0" t:none
 

-
 Note 
 Rule chains allow you to simulate logical AND. The disruptive actions specified in the first portion of the chained rule will be triggered only if all of the variable checks return positive hits. If any one aspect of a chained rule comes back negative, then the entire rule chain will fail to match. Also note that disruptive actions, execution phases, metadata actions (id, rev, msg, tag, severity, logdata), skip, and skipAfter actions can be specified only by the chain starter rule.
-

-
The following directives can be used in rule chains: 
-

-
  • SecAction
-
  • SecRule
-
  • SecRuleScript 
-

-
Special rules control the usage of actions in chained rules:
-

-
  • Any actions that affect the rule flow (i.e., the disruptive actions, skip and skipAfter) can be used only in the chain starter. They will be executed only if the entire chain matches.
-
  • Non-disruptive rules can be used in any rule; they will be executed if the rule that contains them matches and not only when the entire chain matches.
-
  • The metadata actions (e.g., id, rev, msg) can be used only in the chain starter.
 
-

-
[edit]  ctl 

-
Description: Changes ModSecurity configuration on transient, per-transaction basis. Any changes made using this action will affect only the transaction in which the action is executed. The default configuration, as well as the other transactions running in parallel, will be unaffected.
-
Action Group: Non-disruptive
-
Example:
-

+; Note : Rule chains allow you to simulate logical AND. The disruptive actions specified in the first portion of the chained rule will be triggered only if all of the variable checks return positive hits. If any one aspect of a chained rule comes back negative, then the entire rule chain will fail to match. Also note that disruptive actions, execution phases, metadata actions (id, rev, msg, tag, severity, logdata), skip, and skipAfter actions can be specified only by the chain starter rule.
+
+The following directives can be used in rule chains: 
+*SecAction
+*SecRule
+*SecRuleScript 
+Special rules control the usage of actions in chained rules:
+*Any actions that affect the rule flow (i.e., the disruptive actions, skip and skipAfter) can be used only in the chain starter. They will be executed only if the entire chain matches.
+*Non-disruptive rules can be used in any rule; they will be executed if the rule that contains them matches and not only when the entire chain matches.
+*The metadata actions (e.g., id, rev, msg) can be used only in the chain starter.
+
+== ctl ==
+'''Description''': Changes ModSecurity configuration on transient, per-transaction basis. Any changes made using this action will affect only the transaction in which the action is executed. The default configuration, as well as the other transactions running in parallel, will be unaffected.
+
+'''Action Group:''' Non-disruptive
+
+'''Example:'''
 
-
-# Parse requests with Content-Type "text/xml" as XML 
-SecRule REQUEST_CONTENT_TYPE ^text/xml "nolog,pass,id:106,ctl:requestBodyProcessor=XML"
+# Parse requests with Content-Type "text/xml" as XML 
+SecRule REQUEST_CONTENT_TYPE ^text/xml "nolog,pass,id:106,ctl:requestBodyProcessor=XML"
 

-
The following configuration options are supported: 
-

-
  1. auditEngine 
-
  2. auditLogParts 
-
  3. debugLogLevel
-
  4. forceRequestBodyVariable 
 
-
  5. requestBodyAccess
-
  6. requestBodyLimit 
-
  7. requestBodyProcessor 
-
  8. responseBodyAccess 
-
  9. responseBodyLimit
-
  10. ruleEngine
-
  11. ruleRemoveById - since this action us triggered at run time, it should be specified before the rule in which it is disabling.
+The following configuration options are supported: 
+#'''auditEngine''' 
+#'''auditLogParts''' 
+#'''debugLogLevel'''
+#'''forceRequestBodyVariable''' 
+#'''requestBodyAccess'''
+#'''requestBodyLimit''' 
+#'''requestBodyProcessor''' 
+#'''responseBodyAccess''' 
+#'''responseBodyLimit'''
+#'''ruleEngine'''
+#'''ruleRemoveById''' - since this action us triggered at run time, it should be specified '''before''' the rule in which it is disabling.
+#'''ruleUpdateTargetById''' - This is deprecated and will be removed from the code. Use ruleRemoveTargetById for per-request exceptions.
+#'''ruleRemoveTargetById''' - since this action is used to just remove targets, users don't need to use the char ! before the target list. 
+#'''ruleRemoveByMsg'''
+#'''encryptionEngine'''
+#'''encryptionEnforcement'''
 
-
  12. ruleUpdateTargetById - This is deprecated and will be removed from the code. Use ruleRemoveTargetById for per-request exceptions.
-
  13. ruleRemoveTargetById - since this action is used to just remove targets, users don't need to use the char ! before the target list. 
-
  14. ruleRemoveByMsg
-
  15. encryptionEngine
-
  16. encryptionEnforcement
-

-
With the exception of the requestBodyProcessor and forceRequestBodyVariable settings, each configuration option corresponds to one configuration directive and the usage is identical.
-
The requestBodyProcessor option allows you to configure the request body processor. By default, ModSecurity will use the URLENCODED and MULTIPART processors to process an application/x-www-form-urlencoded and a multipart/form-data body, respectively. A third processor, XML, is also supported, but it is never used implicitly. Instead, you must tell ModSecurity to use it by placing a few rules in the REQUEST_HEADERS processing phase. After the request body is processed as XML, you will be able to use the XML-related features to inspect it.
-
Request body processors will not interrupt a transaction if an error occurs during parsing. Instead, they will set the variables REQBODY_PROCESSOR_ERROR and REQBODY_PROCESSOR_ERROR_MSG. These variables should be inspected in the REQUEST_BODY phase and an appropriate action taken.
+With the exception of the requestBodyProcessor and forceRequestBodyVariable settings, each configuration option corresponds to one configuration directive and the usage is identical.
+
+The requestBodyProcessor option allows you to configure the request body processor. By default, ModSecurity will use the URLENCODED and MULTIPART processors to process an application/x-www-form-urlencoded and a multipart/form-data body, respectively. A third processor, XML, is also supported, but it is never used implicitly. Instead, you must tell ModSecurity to use it by placing a few rules in the REQUEST_HEADERS processing phase. After the request body is processed as XML, you will be able to use the XML-related features to inspect it.
+
+Request body processors will not interrupt a transaction if an error occurs during parsing. Instead, they will set the variables REQBODY_PROCESSOR_ERROR and REQBODY_PROCESSOR_ERROR_MSG. These variables should be inspected in the REQUEST_BODY phase and an appropriate action taken.
 The forceRequestBodyVariable option allows you to configure the REQUEST_BODY variable to be set when there is no request body processor configured. This allows for inspection of request bodies of unknown types.
 
-

-
[edit]  deny 

-
Description: Stops rule processing and intercepts transaction.
-
Action Group: Disruptive
-
Example:
+== deny ==
+'''Description:''' Stops rule processing and intercepts transaction.
+
+'''Action Group:''' Disruptive
+
+Example:
 SecRule REQUEST_HEADERS:User-Agent "nikto" "log,deny,id:107,msg:'Nikto Scanners Identified'"
 
-

-
[edit]  deprecatevar 

-
Description: Decrements numerical value over time, which makes sense only applied to the variables stored in persistent storage.
-
Action Group: Non-Disruptive
-
Example: The following example will decrement the counter by 60 every 300 seconds.
-

+== deprecatevar ==
+'''Description''': Decrements numerical value over time, which makes sense only applied to the variables stored in persistent storage.
+
+'''Action Group:''' Non-Disruptive
+
+Example: The following example will decrement the counter by 60 every 300 seconds.
 
 SecAction phase:5,id:108,nolog,pass,deprecatevar:SESSION.score=60/300
-
 

-
Counter values are always positive, meaning that the value will never go below zero. Unlike expirevar, the deprecate action must be executed on every request.
-

-
[edit]  drop 

-
Description: Initiates an immediate close of the TCP connection by sending a FIN packet.
-
Action Group: Disruptive
-
Example: The following example initiates an IP collection for tracking Basic Authentication attempts. If the client goes over the threshold of more than 25 attempts in 2 minutes, it will DROP subsequent connections.
 
-

+Counter values are always positive, meaning that the value will never go below zero. Unlike expirevar, the deprecate action must be executed on every request.
+
+== drop ==
+'''Description:''' Initiates an immediate close of the TCP connection by sending a FIN packet.
+
+'''Action Group:''' Disruptive
+
+'''Example:''' The following example initiates an IP collection for tracking Basic Authentication attempts. If the client goes over the threshold of more than 25 attempts in 2 minutes, it will DROP subsequent connections.
 
 SecAction phase:1,id:109,initcol:ip=%{REMOTE_ADDR},nolog
-SecRule ARGS:login "!^$" "nolog,phase:1,id:110,setvar:ip.auth_attempt=+1,deprecatevar:ip.auth_attempt=20/120"
-SecRule IP:AUTH_ATTEMPT "@gt 25" "log,drop,phase:1,id:111,msg:'Possible Brute Force Attack'"
+SecRule ARGS:login "!^$" "nolog,phase:1,id:110,setvar:ip.auth_attempt=+1,deprecatevar:ip.auth_attempt=20/120"
+SecRule IP:AUTH_ATTEMPT "@gt 25" "log,drop,phase:1,id:111,msg:'Possible Brute Force Attack'"
 

-
 Note 
 This action is currently not available on Windows based builds. 
 
-

-
This action is extremely useful when responding to both Brute Force and Denial of Service attacks in that, in both cases, you want to minimize both the network bandwidth and the data returned to the client. This action causes error message to appear in the log "(9)Bad file descriptor: core_output_filter: writing data to the network"
-

-
[edit]  exec 

-
Description: Executes an external script/binary supplied as parameter. As of v2.5.0, if the parameter supplied to exec is a Lua script (detected by the .lua extension) the script will be processed internally. This means you will get direct access to the internal request context from the script. Please read the SecRuleScript documentation for more details on how to write Lua scripts.
-
Action Group: Non-disruptive
-
Example:
+; Note : This action is currently not available on Windows based builds. 
+This action is extremely useful when responding to both Brute Force and Denial of Service attacks in that, in both cases, you want to minimize both the network bandwidth and the data returned to the client. This action causes error message to appear in the log "(9)Bad file descriptor: core_output_filter: writing data to the network"
 
-

+== exec ==
+'''Description:''' Executes an external script/binary supplied as parameter. As of v2.5.0, if the parameter supplied to exec is a Lua script (detected by the .lua extension) the script will be processed internally. This means you will get direct access to the internal request context from the script. Please read the SecRuleScript documentation for more details on how to write Lua scripts.
+
+'''Action Group:''' Non-disruptive
+
+'''Example:'''
 
 # Run external program on rule match 
-SecRule REQUEST_URI "^/cgi-bin/script\.pl" "phase:2,id:112,t:none,t:lowercase,t:normalizePath,block,\ exec:/usr/local/apache/bin/test.sh"
+SecRule REQUEST_URI "^/cgi-bin/script\.pl" "phase:2,id:112,t:none,t:lowercase,t:normalizePath,block,\ exec:/usr/local/apache/bin/test.sh"
 
 # Run Lua script on rule match 
-SecRule ARGS:p attack "phase:2,id:113,block,exec:/usr/local/apache/conf/exec.lua"
+SecRule ARGS:p attack "phase:2,id:113,block,exec:/usr/local/apache/conf/exec.lua"
 

-
The exec action is executed independently from any disruptive actions specified. External scripts will always be called with no parameters. Some transaction information will be placed in environment variables. All the usual CGI environment variables will be there. You should be aware that forking a threaded process results in all threads being replicated in the new process. Forking can therefore incur larger overhead in a multithreaded deployment. The script you execute must write something (anything) to stdout; if it doesn’t, ModSecurity will assume that the script failed, and will record the failure.
-

-
[edit]  expirevar 

+The exec action is executed independently from any disruptive actions specified. External scripts will always be called with no parameters. Some transaction information will be placed in environment variables. All the usual CGI environment variables will be there. You should be aware that forking a threaded process results in all threads being replicated in the new process. Forking can therefore incur larger overhead in a multithreaded deployment. The script you execute must write something (anything) to stdout; if it doesn’t, ModSecurity will assume that the script failed, and will record the failure.
 
-
Description: Configures a collection variable to expire after the given time period (in seconds).
-
Action Group: Non-disruptive
-
Example:
-

+== expirevar ==
+'''Description:''' Configures a collection variable to expire after the given time period (in seconds).
+
+'''Action Group:''' Non-disruptive
+
+'''Example:'''
 
-SecRule REQUEST_COOKIES:JSESSIONID "!^$" "nolog,phase:1,id:114,pass,setsid:%{REQUEST_COOKIES:JSESSIONID}"
-SecRule REQUEST_URI "^/cgi-bin/script\.pl" "phase:2,id:115,t:none,t:lowercase,t:normalisePath,log,allow,setvar:session.suspicious=1,expirevar:session.suspicious=3600,phase:1"
-
+SecRule REQUEST_COOKIES:JSESSIONID "!^$" "nolog,phase:1,id:114,pass,setsid:%{REQUEST_COOKIES:JSESSIONID}"
+SecRule REQUEST_URI "^/cgi-bin/script\.pl" "phase:2,id:115,t:none,t:lowercase,t:normalisePath,log,allow,setvar:session.suspicious=1,expirevar:session.suspicious=3600,phase:1"
 

-
You should use the expirevar actions at the same time that you use setvar actions in order to keep the indented expiration time. If they are used on their own (perhaps in a SecAction directive), the expire time will be reset.
-

-
[edit]  id 

-
Description: Assigns a unique ID to the rule or chain in which it appears. Starting with ModSecurity 2.7 this action is mandatory and must be numeric.
-
Action Group: Meta-data
-
Example:
 
-

+You should use the expirevar actions at the same time that you use setvar actions in order to keep the indented expiration time. If they are used on their own (perhaps in a SecAction directive), the expire time will be reset.
+
+== id ==
+'''Description''': Assigns a unique ID to the rule or chain in which it appears. Starting with ModSecurity 2.7 this action is mandatory and must be numeric.
+
+'''Action Group:''' Meta-data
+
+'''Example:'''
 
-SecRule &REQUEST_HEADERS:Host "@eq 0" "log,id:60008,severity:2,msg:'Request Missing a Host Header'"
+SecRule &REQUEST_HEADERS:Host "@eq 0" "log,id:60008,severity:2,msg:'Request Missing a Host Header'"
 

-
 Note 
 The id action is required for all SecRule/SecAction directives as of v2.7.0
-

-
These are the reserved ranges:
-

-
  • 1–99,999: reserved for local (internal) use. Use as you see fit, but do not use this range for rules that are distributed to others
 
-
  • 100,000–199,999: reserved for internal use of the engine, to assign to rules that do not have explicit IDs
-
  • 200,000–299,999: reserved for rules published at modsecurity.org
-
  • 300,000–399,999: reserved for rules published at gotroot.com
-
  • 400,000–419,999: unused (available for reservation)
-
  • 420,000–429,999: reserved for ScallyWhack [9]
-
  • 430,000–439,999: reserved for rules published by Flameeyes [10] 
-
  • 440.000-599,999: unused (available for reservation)
-
  • 600,000-699,999: reserved for use by Akamai [11]
-
  • 700,000–799,999: reserved for Ivan Ristic
-
  • 900,000–999,999: reserved for the OWASP ModSecurity Core Rule Set [12] project
+; Note : The id action is required for all SecRule/SecAction directives as of v2.7.0
 
-
  • 1,000,000-1,999,999: unused (available for reservation)
-
  • 2,000,000-2,999,999: reserved for rules from Trustwave's SpiderLabs Research team
-
  • 3,000,000 and above: unused (available for reservation)
-

-
[edit]  initcol 

-
Description: Initializes a named persistent collection, either by loading data from storage or by creating a new collection in memory.
-
Action Group: Non-disruptive
+These are the reserved ranges:
 
-
Example: The following example initiates IP address tracking, which is best done in phase 1:
-

+*1–99,999: reserved for local (internal) use. Use as you see fit, but do not use this range for rules that are distributed to others
+*100,000–199,999: reserved for internal use of the engine, to assign to rules that do not have explicit IDs
+*200,000–299,999: reserved for rules published at modsecurity.org
+*300,000–399,999: reserved for rules published at gotroot.com
+*400,000–419,999: unused (available for reservation)
+*420,000–429,999: reserved for ScallyWhack [http://projects.otaku42.de/wiki/Scally-Whack]
+*430,000–439,999: reserved for rules published by Flameeyes [http://www.flameeyes.eu/projects/modsec] 
+*440.000-599,999: unused (available for reservation)
+*600,000-699,999: reserved for use by Akamai [http://www.akamai.com/html/solutions/waf.html]
+*700,000–799,999: reserved for Ivan Ristic
+*900,000–999,999: reserved for the OWASP ModSecurity Core Rule Set [http://www.owasp.org/index.php/Category:OWASP_ModSecurity_Core_Rule_Set_Project] project
+*1,000,000-1,999,999: unused (available for reservation)
+*2,000,000-2,999,999: reserved for rules from Trustwave's SpiderLabs Research team
+*3,000,000 and above: unused (available for reservation)
+
+== initcol ==
+'''Description:''' Initializes a named persistent collection, either by loading data from storage or by creating a new collection in memory.
+
+'''Action Group:''' Non-disruptive
+
+'''Example:''' The following example initiates IP address tracking, which is best done in phase 1:
 
 SecAction phase:1,id:116,nolog,pass,initcol:ip=%{REMOTE_ADDR}
 

-
Collections are loaded into memory on-demand, when the initcol action is executed. A collection will be persisted only if a change was made to it in the course of transaction processing.
-
See the "Persistant Storage" section for further details.
-

-
[edit]  log 

 
-
Description: Indicates that a successful match of the rule needs to be logged.
-
Action Group: Non-disruptive
-
Example:
-

+Collections are loaded into memory on-demand, when the initcol action is executed. A collection will be persisted only if a change was made to it in the course of transaction processing.
+
+See the "Persistant Storage" section for further details.
+
+== log ==
+'''Description:''' Indicates that a successful match of the rule needs to be logged.
+
+'''Action Group:''' Non-disruptive
+
+'''Example:'''
 
 SecAction phase:1,id:117,pass,initcol:ip=%{REMOTE_ADDR},log
 

-
This action will log matches to the Apache error log file and the ModSecurity audit log.
-

-
[edit]  logdata 

 
-
Description: Logs a data fragment as part of the alert message.
-
Action Group: Non-disruptive
-
Example:
-

+This action will log matches to the Apache error log file and the ModSecurity audit log.
+
+== logdata ==
+'''Description:''' Logs a data fragment as part of the alert message.
+
+'''Action Group:''' Non-disruptive
+
+'''Example:'''
 
-SecRule ARGS:p "@rx <script>" "phase:2,id:118,log,pass,logdata:%{MATCHED_VAR}"
+SecRule ARGS:p "@rx 
-	
-
-	
-	
-
-
-
- -
- - - - -

© 2012 Geeknet, Inc.   Terms of Use - Privacy Policy - -- Cookies/Opt Out -

- - - -