Stop WordPress Brut Force Attacks Automatically Using ModSecurity ConfigServer

Absolutely! There are certainly some nice WP plugins that will probably do a better job than what we're doing here with modsec. This only protects from brute force attempts on wp-login.php, I'll be adjusting it to also include xmlrpc, but there are lots of other threats that plugins, like tinyShield, will also cover that this will not. I recommend using both if you're able to. But, if you have customers setting up WP sites on your server, at least they'll have some brute force protection whether they install a security plugin using these modsec ruels. I've used a couple Jetpack, Wordfence, and Securi, I'm going to check out tinyShield. Thanks for the recommendation @KH-Jonathan!
 
Since I finally added it to my new Dedi I already have...
68.183.180.46 # lfd: (mod_security) mod_security (id:5000135) triggered by 68.183.180.46 (SG/Singapore/-): 1 in the last 3600 secs - Tue Mar 24 14:57:57 2020
158.69.124.147 # lfd: (mod_security) mod_security (id:5000135) triggered by 158.69.124.147 (CA/Canada/ns521554.ip-158-69-124.net): 1 in the last 3600 secs - Tue Mar 24 15:32:14 2020
85.204.246.240 # lfd: (mod_security) mod_security (id:5000135) triggered by 85.204.246.240 (RO/Romania/-): 1 in the last 3600 secs - Tue Mar 24 15:43:25 2020

Doing it's job nicely! ;)
 
Top