Fail2Ban
fail2ban is a real pet peeve of mine because anyone security conscious enough to deploy this will have likely already mitigated any actual security risks this could help with either by using a strong password or public key authentication.<p>That leaves noise in the logs - which sure, it's nice to reduce, but using an alternative port can help here.<p>I may sound like a spoilsport - but the fact that there have been a number of security vulnerabilities (<a href="https://www.cvedetails.com/vulnerability-list/vendor_id-5567/Fail2ban.html" rel="nofollow noreferrer">https://www.cvedetails.com/vulnerability-list/vendor_id-5567...</a>) in this project, make it worse than security theatre, it actually increases risk whilst not at all reducing it.