The filter inheritance scheme in ModSecurity follows the rules outlined below. By default, all filters, together with their per-rule action lists, are inherited by child contexts. The default action list is also inherited by child contexts. Action lists, defined in the SecFilterSignatureAction directive (per-ruleset actions), are never inherited by child contexts. It is possible ...

Modsecurity supports writing filters in the ways outlined below. For further information refer to the documentation. Simple Input Filter Syntax: SecFilter KEYWORD [ACTIONS] SecFilter !KEYWORD [ACTIONS] Advanced Input Filter Syntax: SecFilterSelective LOCATION KEYWORD [ACTIONS] SecFilterSelective LOCATION !KEYWORD [ACTIONS] Advanced output Filter Syntax: SecFilterSelective OUTPUT KEYWORD [ACTIONS] SecFilterSelective OUTPUT !KEYWORD [ACTIONS]

It is possible to use Apache’s custom logging feature in order to log requests, which matched a ModSecurity filter, on a per-virtualhost basis. The key for this to work is the fact that ModSecurity defines the environment variable mod_security-relevant whenever a rule is matched. So, by adding the following statement in ...

ModSecurity installation consists of the following steps:   ModSecurity 2.x works with Apache 2.0.x or better. Make sure you have mod_unique_id installed. (Optional) Install the latest version of libxml2, if it isn't already installed on the server. Unpack the ModSecurity archive Edit Makefile to configure ...

need basically 2 things: The source for mod_security A basic set of rules, which will be packaged in the RPM Once you have these files, you'll just need to unpack the tarball: [gallegosja@gallegosja gallegosja]$ tar -xvzf mod_security-1.8.4.tar.gz go to the apache 2 module (you ...

When ModSecurity receives request or response information, it makes a copy of this data and places it into memory. It is on this data in memory that transformation functions are applied. The raw request/response data is never altered. Transformation functions are used to transform a variable before testing it in ...

ModSecurity installation consists of the following steps: ModSecurity 2.x works with Apache 2.0.x or better. ...

Ajax security is a major issue for next generation Web applications. The techniques discussed in this article can give a head start to security professionals to improve the security posture of Web applications. Web 2.0 applications try to integrate various sources, including untrusted information sources, at one place. This trait of Web 2.0 ...