Using ModSecurity is not easy. The complexity of your site, your use of PHP, MySQL and other scripting languages will make it more difficult to configure correctly. Basically, the more complex your site, the more time you will need to work out issues with rules. This tutorial will provide you with several important tips to get started with ModSecurity.

What's happening on your web server that you do not know about? ModSecurity provides you insight into the activity on your web server that Apache is not designed to tell you about. ModSecurity Handbook by Ivan Ristic is a great read to start getting information about activity and then managing the access to your web server.

This article shows how to install and configure ModSecurity (version 2) for use with Apache2 on a Debian Etch system. ModSecurity is an Apache module that provides intrusion detection and prevention for web applications. It aims at shielding web applications from known and unknown attacks, such as SQL injection attacks, cross-site scripting, path traversal attacks, etc.

One of the big reasons people disable ModSecurity is that they see in their logs continual blocks on Googlebot. Obviously, if Google’s bot cannot list your site you will be in trouble with trying to get people to your site.

You have built a rock solid firewall, tested it with nmap scanning for ports that were open, locked down SSH with port knocking, restricted outgoing ports with iptables, setup psad to block attacks, and tcp_wrappers to limit access so you are set right? Well, not exactly....

Webmaster Tools from Google can enhance your understanding of what is making your website work. ModSecurity, a valuable security resource, may block the verification page that is necessary for Webmaster Tools to function. This article will show you how to write a rule that will allow you to use both effectively.

A few months ago I wanted to keep track of changes on a webpage... and wrote a script to do so. Later I discovered there were navigator plugins that did exactly that... But the fun in writing your own script is far greater than an anonymous script someone did.

SQL injection attacks can allow hackers to execute arbitrary SQL commands on your database through your Web site. To avoid these attacks, every piece of data supplied by a user on a Web form, through HTTP Post or CGI parameters, or other means, must be validated to not contain information that is not expected.

Using the same ALSA upgrade script as for 1.0.20, but with some minor tweaks, you can upgrade to ALSA 1.0.21 by running a simple sh file.

For instructions on how to run the script and other MUST READ info, please check our ALSA 1.0.20 upgade script post.

Once you do that, you can download the ALSA 1.0.21 upgrade script....[...]