Host intrusion detection for Linux servers

A host-based intrusion detection system (HIDS) runs on the server itself and looks for signs that someone got in: changed system files, suspicious log lines, unexpected programs and connections. A network IDS watches traffic between machines; a HIDS sees what actually happened on one.

ToolWhat it doesHow you run it
AIDEFile and directory integrity checker: builds a database of file hashes and attributes, then reports what changedIn most distributions; you run checks on a schedule and read the report
OSSECLog-based intrusion detection, file integrity monitoring, malware detection, active response and compliance auditingFree and open source, maintained by Atomicorp; agents report to a server you run
WazuhA broad security platform that grew out of OSSEC: integrity monitoring, vulnerability detection, log analysis, complianceFree and open source; you run a server, an indexer and a dashboard, or buy Wazuh Cloud
FalcoRuntime security that parses Linux system calls and alerts when a rule matches, with container and Kubernetes contextGraduated CNCF project; you write or tune rules and forward its alerts
rkhunterScans for known rootkits and suspicious file changesLast release 1.4.6, in February 2018

What a HIDS should notice

What to check before you choose

Where Vigilhold fits

Vigilhold is a hosted host security agent for Linux servers and Docker hosts. One command installs the agent; it watches processes, network connections, file changes and logins, and the dashboard is hosted, so there is no server or indexer to run and nothing to tune before it works. It responds only within limits you set, asks first for anything beyond them, and records every action in an audit log, with bans, quarantines and lockdowns you can undo.

Checked in November 2026: AIDE, OSSEC, Wazuh agent docs, Falco docs, Rootkit Hunter.

Vigilhold vs fail2ban · Vigilhold vs CrowdSec · Vigilhold vs Wazuh · Start a 14-day free trial