Mod_security install

Apache - Proxy. Apache - Docker. Apache - PHP Docker. Apache - Monitoring via Zabbix. Apache - Monitoring log file via Zabbix. Apache - Modsecurity installation. Equipment list. The following section presents the list of equipment used to create this tutorial.

As an Amazon Associate, I earn from qualifying purchases. Apache - Related Tutorial:. On this page, we offer quick access to a list of tutorials related to Apache. List of Tutorials. Apache - Perl CGI. Apache - Golang CGI. Tutorial Apache - ModSecurity installation. Copy to Clipboard. Download the latest version of the Apache connector for ModSecurity.

You have finished the ModSecurity installation on the Apache server. In order to complete this tutorial, you will need LAMP installed on your server. This can be changed by editing the modsecurity. Another directive to modify is SecResponseBodyAccess. This configures whether response bodies are buffered i. This is only neccessary if data leakage detection and protection is required.

Therefore, leaving it On will use up droplet resources and also increase the logfile size. Two directives configure these:. If anything larger is sent by a client the server will respond with a Request Entity Too Large error. Since droplets use SSDs, this is not much of an issue; however, this can be set a decent value if you have RAM to spare. Before going ahead with configuring rules, we will create a PHP script which is vulnerable to SQL injection and try it out. Please note that this is just a basic PHP login script with no session handling.

Be sure to change the MySQL password in the script below so that it will connect to the database:. This script will display a login form. We need credentials in the database. Create a MySQL database and a table, then insert usernames and passwords. We can confirm that the script works right. The next job is to try our hand with SQL injection to bypass the login page. It is useful to know which ruleset is appropriate for your server depends heavily on the specific types of sites you will be hosting, and more importantly, the specific types of Apache requests that will be needed in order for the site applications to work.

If one of the types of requests being blocked by the ModSecurity ruleset installed is needed in order for one of the sites to work, then parts of that site will not work while that ruleset is installed. You can, of course, write your own rulesets or purchase custom licensed rulesets. A quick Google search can provide relevant listings. The tools for configuring ModSecurity do not do anything unless the module has been installed in Apache.

If ModSecurity is not yet installed, this can be done via EasyApache. Make sure that ModSecurity has been selected before beginning the build process. Once the build process has completed, the next step is to add a ruleset. If there is a different published ruleset you prefer to use instead, check with the developer of the ruleset if they make their ruleset available as a Vendor that can be added via WHM. If the ruleset is available in this format, it is the strongly preferred method of installing the ruleset.