It's a reasonable enough way of protecting hosted websites, especially if you're running more than one server. You can monitor multiple logs for abuse from different sources, and then update all servers to drop traffic from those sources. So, if someone runs a WordPress vulnerability scan on a hosted website, you can detect that and immediately refuse any mail/ssh/dns/www/ftp/other service from that IP.
It requires a little bit of kludging to do this though. :-( As packaged, it's not much more useful than a hacky shell script.
It requires a little bit of kludging to do this though. :-( As packaged, it's not much more useful than a hacky shell script.