Fail2ban alternatives for Linux servers

SSHGuard, CrowdSec, Wazuh and Vigilhold compared with fail2ban: what each does, where each one stops, and when fail2ban is still enough.

Fail2ban reads log files, spots repeated failures such as bad SSH passwords, and adds a firewall rule to ban the address for a while. It is free, widely packaged and does that one job well. People look for alternatives for a few recurring reasons.

Why people look elsewhere

  • Each server bans on its own. An address banned on one server can keep attacking the others.
  • It fails silently. If a log path or format changes, fail2ban keeps running and simply matches nothing, which looks the same as a quiet week.
  • It only blocks. It doesn’t tell you about the login that succeeded, the process that started afterwards or the file that changed.
  • Regex filters and jail files take time to tune and to keep working across distributions.

The alternatives

SSHGuard

A small daemon written in C that watches logs for SSH and a few other services and blocks attackers through your firewall. It is lighter and simpler than fail2ban, with less to configure, but it has the same scope: one host, blocking only.

CrowdSec

An open-source engine that parses logs with community-maintained scenarios and hands decisions to “bouncers” that enforce them in the firewall, a web server or a CDN. Its main difference is the community blocklist: addresses reported by other users can be blocked before they reach you. The engine is free; a hosted console adds paid features. Vigilhold vs CrowdSec, in detail ↗

Wazuh active response

Wazuh is a full open-source security platform: log analysis, file integrity monitoring, vulnerability detection and more, with “active response” scripts that can block addresses. It does far more than fail2ban, and asks far more of you: a manager, an indexer and a dashboard to install, size and keep updated. Vigilhold vs Wazuh, in detail ↗

Vigilhold

Our hosted host agent for Linux servers. When a response playbook bans an address, the ban goes to every server in your account, and servers that were offline pick it up when they reconnect. It also watches logins, processes, connections and file changes, and warns you if a server with SSH open to the internet stops reporting login activity for three hours, which catches the silent-failure case above. Vigilhold vs fail2ban, in detail ↗

Side by side

fail2banSSHGuardCrowdSecWazuhVigilhold
Blocks attacking IPsYesYesYesYes, via active responseYes
Bans shared across your serversNoNoYesConfigurableYes
Detects what happens after a loginNoNoNoYesYes
Warns when log monitoring goes quietNoNoNot by defaultNot by defaultYes
You run the server sideNothing to runNothing to runOptionalYesNo, hosted
CostFreeFreeFree engine, paid consoleFree, or paid cloudFrom $39/month for 5 servers

Which one to pick

  • One or two personal servers and fail2ban works: keep it, and check fail2ban-client status now and then to confirm it is still counting failures.
  • You want fail2ban’s job with less to configure: SSHGuard.
  • You want blocklists informed by many other servers: CrowdSec.
  • You have the people to run a security platform and need broad coverage: Wazuh.
  • A small team running a fleet that wants bans shared everywhere and detection beyond blocking, without running a server for it: Vigilhold, with a 14-day trial and no card.

Setting up a new server? The checklist covers fail2ban settings that commonly break on recent distributions. How to secure a Linux VPS →