This module provides security enhancements against (HTTP) Flood & Brute Force Attacks for Wordpress.

iosec

This module provides security enhancements against (HTTP) Flood & Brute Force Attacks for WordPress. 
Massive scanning tools (like vulnerability scanners), HTTP Flood tools can be blocked or detected by this module. 
This module can be integrated with htaccess, any firewall, iptables or etc. via “banlist” file.
To see a quick test page follow this link: http://www.iosec.org/test.php for proof of concept.
Watch the proof of concept video: http://youtu.be/LzLY_SKLq9w
Note: Change the default configuration values before activating the plugin.
<h3>CONFIGURATION DESCRIPTIONS</h3>
BENEFITS
<ul>
<li>You can block proxies (via header information)</li>
<li>You can detect flooding IP addresses.</li>
<li>You can slow down or restrict access for automated tools (HTTP DoS tools & Flood tools, Brute force tools, Vulnerability scanners, etc.)</li>
<li>You can save your server resources (database, cpu, ram, etc.) under an attack.</li>
<li>You can restrict access permanently or temporarily for listed IP addresses in “banlist” file.</li>
<li>You can notify yourself via email alerts when attacks begin.</li>
</ul>
CONS
<ul>
<li>You have to tweak configuration file and even script’s itself to avoid false positives.</li>
<li>You have to restrict access for world writeable files and apply least privilige permissions to file properties.</li>
</ul>
Functions of files:
/wp-content/iosec_admin/
<ul>
<li>banlist (Detected IP addresses listed here. You can use this file with iptables, htaccess with bash scripts.)</li>
<li>banlisttemp (Just a system file. IP and Time correlations listed in it.)</li>
<li>ips (Just a system file. Every request is listed in it.) </li>
<li>whitelist (Excluded IP List seperated by new lines.)</li>
<li>excluded (Excluded File List seperated by new lines. E.g. for http://YOUR_SITE/wordpress/index.php file add this line to excluded file: /wordpress/index.php)</li>
</ul>
You should configure plugin by editing iosec.php file.
<ol>
<li>
Connection Interval: This is second based interval for accepting another connection. 
If you choose value 1 (1 second), another request in 1 second will be suspended by module. You can enter values like 0.1, 0.001, etc.
</li>
<li>
Max. Connection Count: This is the interval based maximum connection limit count for accepting another connection. 
If you choose value 10 and your connection interval is 1 second. This means only 10 connections permitted in 1 second.
</li>
<li>
Suspended Process Timeout: When a connection interval rule finds a connection is not prohibited, this timeout value will be activated. 
For example, if connection interval is 1 and this value is 30 then, second connection in 1 second will be suspended for 30 seconds.
</li>
<li>
Page Redirection: You redirect your detected users to another page after timeout page disappears.
</li>
<li>
Send Me Mail: Module can send you a mail when an IP address detected.
</li>
<li>
Block Proxies: You can identify and block proxies via http header.
</li>
<li>
Show Debug Info: Time and IP information will be displayed on suspension page when this option is activated.
</li>
<li>
Use Incremental Blocking: This option will increase time of suspension if attack is still happening. 
For example, if C.I. is 1 and a second connection happens in 1 second this will be suspended for 30 seconds (above ex.). 
If one connection in 10 seconds happens, this will increase suspension time when this option is activated.
</li>
<li>
Implicit Deny Timeout: If you want to block every request as default for a timeout period (seconds), set this value to greater than “0”. This is an emergency option for DDoS attacks etc.
</li>
<li>
Cached Requests: Monitoring data window size for last requests (for “ips” file size) (default is “150”).
</li>
<li>
Implicit Deny for banlist Timeout: If you want to block every recorded IP that is listed in the banlist as default and let the human users to view page for a timeout period (seconds), set this value to greater than “0” (default is “0”).
</li>
</ol>
CHANGES v.1.8.1 – v.1.8.2
<ul>
<li>Improved Implicit Deny for Banned IP Addresses (Deny without detection)</li>
<li>Minor Performance Tweaks</li>
</ul>
CHANGES v.1.5 – v.1.8
<ul>
<li>Added Implicit Deny for the Banned IP Addresses</li>
<li>Added Request Cache Size Option</li>
<li>Added Excluded Files Support</li>
<li>Added/Improved Implicit Deny Mode (with detection)</li>
</ul>
CHANGES v.1.3 – v.1.4
<ul>
<li>Added Connection Limit Support</li>
</ul>
CHANGES v.1.2
<ul>
<li>Added Whitelist Support</li>
</ul>
CHANGES v.1.1
<ul>
<li>Added Reverse Proxy Support</li>
<li>Added reCAPTCHA Support </li>
<li>Now Blocks Brute Force More Efficiently</li>
<li>Minor Security Fixes</li>
</ul>
Gökhan Muharremoğlu 
Information Security Specialist
You can reach me @ 
Twitter: https://twitter.com/iosec_org 
gokhanmuh@users.sourceforge.net 
gokhan.muharremoglu@iosec.org 
https://sourceforge.net/projects/iosec/ 
http://www.iosec.org 
http://www.linkedin.com/in/gokhanmuharremoglu

Alternatives to IOSEC HTTP Anti Flood/DoS Security Gateway Module

Top alternatives