How to protect WordPress with Fail2Ban
By using WP Cerber and Fail2Ban together you can reinforce protection at the most effective level. That allows you to protect a WordPress from brute-force and DoS attacks at OS level with iptables.
Read more about attacks: Brute-force, DoS, and DDoS attacks – what’s the difference?
Note: you have to have the root access to your Linux server to setup Fail2Ban.
With WP Cerber you have three options to use Fail2Ban
- Using HTTP 403 response headers if you want to monitor Apache access log
- Using syslog files to monitor failed login attempts
- Using specified custom log file to monitor failed login attempts
Let’s look at the details.
Monitor Apache access log for HTTP 403 responses
When an attempt to log in fails WP Cerber returns 403 response in the HTTP header. That response will be written in the Apache access log and those records may be monitored by Fail2Ban. That behavior of WP Cerber is enabled by default. The downside to this approach is that Fail2Ban has to parse the entire access.log in order to find those attempts.
Using syslog to monitor failed login attempts
By default, WP Cerber uses the LOG_AUTH facility for logging failed attempts to the syslog file. However, you can specify a facility with your own value. To setup new value you have to define CERBER_LOG_FACILITY constant with an integer value. To enable writing to the syslog or custom file (see below) you need to check Write failed login attempts to the file in the Activity section of settings.
Using custom log file to monitor failed login attempts
If you want to write all failed attempts to any custom log file you need to specify a file name with an absolute path using constant CERBER_FAIL_LOG. Don’t forget set write permission for Apache process on the folder or log file and check Write failed login attempts to the file. If the file does not exist, WP Cerber attempts to create it. If the CERBER_FAIL_LOG is defined, WP Cerber will not write messages to the default syslog.
Make sure that web server process (Apache) has permission to write to a specified file.
Let's make things clear with these intruder activities that happens every day with any website. How are they dangerous? What tools or plugin can mitigate them? What are chances that we can do that successfully?