Skip to content
Vol. 1 · Ed. 2026
CyberGlossary
Entry № 549

Host-Based IDS (HIDS)

Reviewed byCybersecurity entrepreneur & security researcher

What is Host-Based IDS (HIDS)?

Host-Based IDS (HIDS)An intrusion-detection agent installed on a server or endpoint that monitors local files, processes, logs, and system calls for malicious activity.


A Host-Based Intrusion Detection System (HIDS) runs as an agent inside the operating system and watches local artefacts — file integrity, registry changes, process creation, system calls, authentication events, and logs — to detect intrusions that may never cross a network sensor. It draws telemetry from the OS's own audit plumbing: the Linux Audit framework (auditd) or newer eBPF probes on Linux, Sysmon and the Windows Event Log on Windows, and increasingly kernel-level hooks shared with EDR. Classic agents include OSSEC, its fork Wazuh, Tripwire, AIDE, and Samhain; modern EDR/XDR products are HIDS extended with behavioural analytics and response.

Two detection modes dominate. File Integrity Monitoring (FIM) baselines cryptographic hashes of critical files and alerts on change — the mechanism behind OSSEC's checksum alerts, and a control explicitly required by PCI DSS Requirement 11.5 and reflected in CIS Controls. Log and rule analysis correlates events (for example a new entry in /etc/cron.d, a sudo to root, or a service binary rewritten) against signatures or anomaly baselines. HIDS sees what a NIDS cannot: actions on the host itself, activity inside TLS, and post-compromise persistence such as a cron or systemd implant. Its weaknesses are real: per-host agent management, CPU cost on busy servers, and — because the sensor lives on the asset it protects — exposure to tampering once an attacker gains root, which is why forwarding logs off-host to a tamper-evident store (SIEM) is essential. Defenders pair HIDS with NIDS for layered visibility.

flowchart TD
  subgraph Host
    K[OS audit sources:<br/>auditd / eBPF / Sysmon / Event Log] --> AG[HIDS agent]
    FS[Critical files & registry] -->|hash baseline| AG
    AG --> FIM[File Integrity Monitoring]
    AG --> LA[Log & system-call analysis]
  end
  FIM --> E{Deviation from baseline<br/>or rule match?}
  LA --> E
  E -- yes --> AL[Alert + forward off-host]
  E -- no --> C[Continue monitoring]
  AL --> SIEM[(Tamper-evident SIEM store)]

● Examples

  1. 01

    Wazuh agent alerting on a suspicious cron job created in /etc/cron.d.

  2. 02

    OSSEC detecting that a critical binary in /usr/bin has changed checksum.

● Frequently asked questions

What is Host-Based IDS (HIDS)?

An intrusion-detection agent installed on a server or endpoint that monitors local files, processes, logs, and system calls for malicious activity. It belongs to the Network Security category of cybersecurity.

What does Host-Based IDS (HIDS) mean?

An intrusion-detection agent installed on a server or endpoint that monitors local files, processes, logs, and system calls for malicious activity.

How do you defend against Host-Based IDS (HIDS)?

Defences for Host-Based IDS (HIDS) typically combine technical controls and operational practices, as detailed in the full definition above.

What are other names for Host-Based IDS (HIDS)?

Common alternative names include: HIDS, Host IDS.

● Related terms