The best file integrity monitoring and HIDS tools for Linux in 2026

Updated November 15, 2026By HostCrust10 tools compared12 min read

Wazuh is the best overall: free, open-source HIDS with file integrity monitoring, log analysis and a central dashboard for a whole fleet. AIDE is the best simple file integrity checker for one or a few servers, and it's in every major distribution. auditd is the best way to see who changed a file, and it's already running on RHEL-family servers.

Falco (runtime security) and CrowdSec (behavior detection from logs) catch different things and work best alongside an FIM tool, not instead of one.

Our top picks

Compare at a glance

ToolBest forPricingOpen sourceDeploymentTested by us
Wazuhfleets that want free HIDS, FIM and a dashboard in oneFree to self-host (open source); Wazuh Cloud starts at $571 per month for up to 100 agentsYesSelf-hosted or SaaS (Wazuh Cloud)Docs only
AIDEsimple file integrity checks on one or a few serversFreeYesSelf-hosted command-line toolYes
Linux Audit (auditd)knowing who changed a file, and with whatFreeYesBuilt into Linux (kernel audit plus the auditd daemon)Yes
OSSECa lightweight, classic HIDSFree (OSSEC, and OSSEC+ with registration); Atomicorp's commercial Atomic OSSEC from about $5 per agent per monthYesSelf-hostedDocs only
osqueryasking your servers questions in SQLFreeYesSelf-hosted agentYes
Falcoreal-time behavior detection on hosts and KubernetesFreeYesSelf-hostedDocs only
CrowdSecdetecting attacks in logs (behavior-based)Security Engine and Community plan free; Console Premium pay-as-you-grow; Platinum Blocklists from $1,900 per monthYesSelf-hosted engine, optional SaaS consoleYes
Tripwire Enterprisecompliance-driven FIM (PCI, NIST, CIS)No public price (contact sales)NoSelf-hosted (agent and agentless)Docs only
Samhaina tamper-resistant monitor with central baselinesFreeYesSelf-hosted (single host or client/server)Docs only
Open Source Tripwireexisting installs onlyFree to use under its open-source license (GPL-2.0-or-later); Tripwire Enterprise is a separate commercial productYesSelf-hosted command-line toolDocs only

The full ranking

Wazuh

Best for: fleets that want free HIDS, FIM and a dashboard in one

Wazuh is the strongest free HIDS for Linux fleets. One agent per server does file integrity monitoring, log analysis, rootkit checks and configuration assessment, and a central server correlates alerts and shows them in a dashboard. It's open source (agent and server GPL-2.0, indexer and dashboard Apache-2.0), agents cover Linux, Windows, macOS, Solaris, AIX and HP-UX, and Wazuh Cloud starts at $571 per month for up to 100 agents if you'd rather not run the server. Running it yourself isn't light: the all-in-one install asks for 4 vCPU and 8 GiB of RAM for up to 25 agents. For one or two servers, AIDE plus auditd is simpler.

Pricing
Free to self-host (open source); Wazuh Cloud starts at $571 per month for up to 100 agents (checked November 15, 2026, source)
License
Open source: manager and agent GPL-2.0 (the newer analysis engine AGPL-3.0, some shared libraries dual GPL-2.0 or AGPL-3.0); indexer and dashboard Apache-2.0
Deployment
Self-hosted or SaaS (Wazuh Cloud)
Runs on
Agents for Linux, Windows, macOS, Solaris, AIX and HP-UX; server on 64-bit Linux

Pros

  • FIM, log analysis, rootkit checks and configuration assessment in one agent
  • Open source, central dashboard included (agent and server GPL-2.0, indexer and dashboard Apache-2.0)
  • Wide agent support, including Solaris, AIX and HP-UX
  • Hosted option with public pricing

Cons

  • Server needs 4 vCPU and 8 GiB of RAM even for small fleets
  • Several components to run and upgrade
  • Alert volume needs tuning for your environment

Not tested by us yet: based on the vendor's documentation.

AIDE

Best for: simple file integrity checks on one or a few servers

AIDE is the simplest serious file integrity monitor: it builds a database of hashes and attributes, then reports what was added, removed or changed. It's GPL-2.0, packaged by Debian, Ubuntu and the RHEL family, and still maintained (0.19.5 shipped in October 2026). On our Debian 12 server, the default config took about 4.5 minutes to build a 12.8 MB baseline and about 5 minutes per check, and it caught our test file and every user-account change. It tells you what changed, not who changed it, and on a busy server its rules need tuning or the reports turn into noise.

Pricing
Free (checked November 15, 2026, source)
License
Open source (GPL-2.0)
Deployment
Self-hosted command-line tool
Runs on
Linux and other POSIX systems; packaged by Debian and RHEL-family distributions (AlmaLinux AppStream)

Pros

  • In every major distribution's repositories
  • Clear added, removed and changed report
  • No daemon; runs from a timer
  • Actively maintained

Cons

  • Doesn't say who made a change
  • Full scans take minutes and real CPU
  • Needs tuning on servers that change often; Debian's package pulled in a mail server

Tested by us: Debian 12 (web-01), AIDE 0.18.3, default Debian config, 14 Nov 2026: aideinit took 263 seconds and wrote a 12.8 MB database; aide --check took 313 seconds over 45,551 entries and reported our new test file, plus changes to /etc/passwd, /etc/shadow and /etc/group from a test user we had added and removed. Removed afterwards.

Linux Audit (auditd)

Best for: knowing who changed a file, and with what

auditd answers the question AIDE can't: who changed the file, and with which program. It's the kernel's audit system, installed and running on our AlmaLinux server, so a watch rule costs nothing to add. One temporary rule recorded our write and our chmod with the login user, the executable and the system call, and it even logged the rule being added and removed. It has no baseline and no dashboard, and the logs are verbose. Over a non-interactive SSH session, ausearch found nothing until we pointed it at the log file. Use it alongside AIDE or Wazuh, not instead of them.

Pricing
Free (checked November 15, 2026, source)
License
Open source (GPL-2.0; the libraries are LGPL-2.1)
Deployment
Built into Linux (kernel audit plus the auditd daemon)
Runs on
Linux; installed and running by default on RHEL-family systems

Pros

  • Already running on RHEL-family servers
  • Records user, program and system call for each change
  • Logs its own rule changes
  • No extra software

Cons

  • No baseline: can't say a file differs from last week
  • Verbose logs; needs shipping and filtering
  • ausearch reads stdin in scripts unless you pass --input-logs or --input

Tested by us: AlmaLinux 9.8 (web-01), audit 3.1.5, 14 Nov 2026: a temporary -w watch with -p wa on a test file in /etc recorded the write (openat by bash) and the chmod (fchmodat), each with auid=root, plus CONFIG_CHANGE events for the rule. The rule and file were removed; auditctl -l showed no rules, as before.

OSSEC

Best for: a lightweight, classic HIDS

OSSEC is the original open-source HIDS that Wazuh forked from, and it's still maintained: Atomicorp manages the project, and version 4.4.1 came out on 18 October 2026. It does log analysis, file integrity checks, rootkit detection and active response with a small agent, and it supports agents on Linux, Windows, BSD, Solaris, AIX, macOS and HP-UX. OSSEC+ adds more rules, threat intelligence and machine learning for free with registration, and Atomicorp's commercial version starts at about $5 per agent per month. Pick it when you want the lighter, classic design.

Pricing
Free (OSSEC, and OSSEC+ with registration); Atomicorp's commercial Atomic OSSEC from about $5 per agent per month (checked November 15, 2026, source)
License
Open source (GPL-2.0)
Deployment
Self-hosted
Runs on
Agents for Linux, Windows, BSD, Solaris, AIX, macOS and HP-UX

Pros

  • Lightweight agent and manager
  • Still maintained (4.4.1, October 2026)
  • Broad agent OS support
  • Free OSSEC+ rules with registration

Cons

  • Fewer built-in extras such as vulnerability detection
  • Extra rules need registration

Not tested by us yet: based on the vendor's documentation.

osquery

Best for: asking your servers questions in SQL

osquery turns a server into a database you can query with SQL: processes, listening ports, users, packages, file hashes and, with events enabled in the daemon, file changes. It's licensed Apache-2.0 or GPL-2.0 and runs on Linux, macOS and Windows. On our AlmaLinux 9.8 server, the 29.7 MB RPM installed cleanly, and osqueryi answered questions such as which ports are listening and which users have a login shell. It isn't a ready-made HIDS: you write or import the queries, and you need a fleet manager to schedule them and collect results centrally.

Pricing
Free (checked November 15, 2026, source)
License
Open source (Apache-2.0 or GPL-2.0)
Deployment
Self-hosted agent
Runs on
Linux, macOS and Windows

Pros

  • SQL over processes, ports, users, packages and files
  • Cross-platform; very active project
  • Great for audits and investigations

Cons

  • No detection rules out of the box
  • File events need daemon configuration
  • Central use needs a separate fleet manager

Tested by us: AlmaLinux 9.8 (web-01), osquery 5.24.1 official RPM (SHA-256 matched the GitHub release), 14 Nov 2026: osqueryi queries for os_version, listening ports joined to processes (only sshd on 22), users with login shells, a SHA-256 of sshd_config, a count of SUID binaries (30) and package versions. A quick interactive file_events test reported events disabled, so we didn't test FIM. Removed afterwards.

Falco

Best for: real-time behavior detection on hosts and Kubernetes

Falco is runtime security, not file integrity monitoring. It watches Linux kernel events with eBPF and alerts when activity matches its rules, and plugins add other event sources. It's Apache-2.0 and a CNCF graduated project, and it runs on plain hosts as well as containers and Kubernetes, where it's most at home. It complements an FIM tool rather than replacing one: Falco tells you something suspicious is happening right now; AIDE or Wazuh tells you what changed on disk. Expect to spend time tuning rules to your workloads before the alerts are useful.

Pricing
Free (checked November 15, 2026, source)
License
Open source (Apache-2.0)
Deployment
Self-hosted
Runs on
Linux hosts, containers and Kubernetes (eBPF)

Pros

  • Real-time detection from kernel events (eBPF)
  • CNCF graduated, Apache-2.0
  • Hosts, containers and Kubernetes
  • Extensible with plugins

Cons

  • Not a file integrity baseline
  • Rules need tuning per workload
  • Keeps no record of file state for later comparison

Not tested by us yet: based on the vendor's documentation.

CrowdSec

Best for: detecting attacks in logs (behavior-based)

CrowdSec is behavior-based detection from logs, not a file integrity monitor. Its engine parses logs, matches scenarios such as SSH brute force, and can block attackers once you add a bouncer. On our AlmaLinux server, the 1.8.2 package auto-detected the sshd, system and audit logs on install and started parsing them. The engine is MIT-licensed and free; CrowdSec sells premium blocklists and console features. It's on this list because it catches attacks that file checks miss, but it won't tell you a binary was modified. Pair it with AIDE or Wazuh.

Pricing
Security Engine and Community plan free; Console Premium pay-as-you-grow; Platinum Blocklists from $1,900 per month (checked November 15, 2026, source)
License
Security Engine open source (MIT); Console and premium blocklists are proprietary
Deployment
Self-hosted engine, optional SaaS console
Runs on
Linux, with official package repositories for RHEL-family and Debian-family systems

Pros

  • Behavior scenarios out of the box (sshd, Linux, auditd)
  • Auto-detects log sources on install
  • MIT-licensed engine

Cons

  • Not a file integrity monitor
  • Blocking needs a separate bouncer
  • Large install (330 MB on our VM)

Tested by us: AlmaLinux 9.8 (web-01), CrowdSec 1.8.2 engine from its official repository, no bouncer, 14 Nov 2026: collections sshd, linux and auditd enabled automatically, and cscli metrics showed it reading /var/log/secure, /var/log/messages and the audit log. Removed afterwards.

Tripwire Enterprise

Best for: compliance-driven FIM (PCI, NIST, CIS)

Tripwire Enterprise is the commercial heavyweight. Fortra pairs file integrity monitoring with security configuration management, assessing systems against more than 4,000 combinations of platforms, policies and standards such as PCI, NIST and CIS, according to Fortra's datasheet, with reports aimed at auditors. That compliance content is the reason to buy it. It works with agents or agentlessly across Windows, Linux and Unix, and has no public price. For a Linux fleet that doesn't face a PCI or similar audit, Wazuh's free configuration assessment covers much of the same ground.

Pricing
No public price (contact sales) (checked November 15, 2026, source)
License
Proprietary
Deployment
Self-hosted (agent and agentless)
Runs on
Windows, Linux and Unix servers, network devices and cloud assets

Pros

  • FIM plus security configuration management
  • Large compliance policy library (PCI, NIST, CIS)
  • Agent and agentless monitoring

Cons

  • No public price
  • Heavyweight for small fleets
  • Vendor pages blocked our automated checks, so we relied on its datasheet

Not tested by us yet: based on the vendor's documentation.

Samhain

Best for: a tamper-resistant monitor with central baselines

Samhain is a capable, still-maintained HIDS (4.5.4, October 2025) that few people know about. It checks file integrity, monitors logs, detects rootkits, rogue SUID files and hidden processes, and has a client/server mode that keeps baselines and configs on a central server. PGP-signed databases and a stealth mode make the monitor itself harder for an intruder to tamper with. The trade-offs are a small community and an older web console (Beltane), and Debian 12 still ships 4.1.4, well behind upstream. Choose it when the integrity of the monitor matters more than a modern interface.

Pricing
Free (checked November 15, 2026, source)
License
Open source (GPL)
Deployment
Self-hosted (single host or client/server)
Runs on
Linux and other POSIX systems

Pros

  • Central baselines and configs (client/server)
  • Signed databases and a stealth mode
  • Rootkit, SUID and hidden-process checks

Cons

  • Small community
  • Dated web console
  • Distribution packages lag upstream

Not tested by us yet: based on the vendor's documentation.

Open Source Tripwire

Best for: existing installs only

Open Source Tripwire still shows up in every list, but it shouldn't be your choice for a new server. Its last release, 2.4.3.7, came out in March 2018, and the last commit to its GitHub repository was in March 2019. It still works and Debian 12 still packages it, so existing installs don't need to be ripped out in a hurry. But AIDE does the same job, is actively maintained and is easier to set up. Don't confuse it with Tripwire Enterprise, Fortra's separate commercial product, which is maintained.

Pricing
Free to use under its open-source license (GPL-2.0-or-later); Tripwire Enterprise is a separate commercial product (checked November 15, 2026, source)
License
Open source (GPL-2.0-or-later)
Deployment
Self-hosted command-line tool
Runs on
Linux and Unix; packaged by Debian

Pros

  • Well known and documented
  • Still packaged by Debian
  • GPL-2.0

Cons

  • No release since 2018
  • No commits since 2019
  • AIDE is a maintained drop-in choice

Not tested by us yet: based on the vendor's documentation.

How we picked

We ranked tools that detect intrusions on the Linux server itself, as opposed to network intrusion detection. The criteria were: does it detect changes to files reliably, can it tell you who made a change, can it alert centrally across many servers, is it maintained, what does it cost to run (in money and in RAM and CPU), and how much tuning does it need before alerts mean something. Prices, licenses and release dates come from each project's own site or repository, checked on 15 November 2026.

On 14 November 2026 we ran AIDE, auditd, osquery and CrowdSec on our two test servers (Debian 12 and AlmaLinux 9.8, each with 2 vCPU and about 2 GB of RAM) and removed them afterwards. Wazuh's all-in-one server asks for 8 GiB of RAM, more than those VMs have, so it's covered from its documentation, along with OSSEC, Falco, Samhain and both Tripwire editions. Falco and CrowdSec aren't file integrity monitors; they're here because people searching for HIDS often mean them, and each card says what they do instead.

What is file integrity monitoring?

File integrity monitoring (FIM) records a trusted baseline of important files, such as their hashes, permissions, owners and sizes, and later reports any file that was added, removed or changed. On Linux that means system binaries in /usr/bin and /usr/sbin, configuration in /etc, and anything an attacker would modify to keep access, such as SSH keys, sudoers, cron jobs and systemd units. A change isn't proof of an attack: package updates, configuration management and admins change files all the time. FIM is useful when you can explain every change, either because it matches a known update or deployment, or because you tuned the rules to ignore paths that change by design. That's why baseline tools like AIDE pair well with auditd, which records who made each change, and why FIM is a staple of compliance programs (Fortra's Tripwire datasheet leads with PCI, NIST and CIS). A host intrusion detection system (HIDS) such as Wazuh or OSSEC wraps FIM together with log analysis and alerting.

HIDS, FIM, runtime security and behavior detection

These four terms get mixed up in search results. Here's what each tool on this page actually does:

TypeAnswersTools hereMisses
File integrity monitoringWhat changed on disk since the baseline?AIDE, Samhain, Open Source Tripwire, Tripwire EnterpriseWho did it; attacks that change nothing on disk
Audit loggingWho touched this file or ran this call, and how?auditdAnything you didn't write a rule for
Host intrusion detection (HIDS)FIM plus log analysis, rootkit checks and alertsWazuh, OSSEC, SamhainDepends on rules and tuning
Runtime securityIs a process behaving suspiciously right now?FalcoA durable record of file state
Behavior detection from logsIs someone attacking a service (for example SSH brute force)?CrowdSecChanges made after a successful login
Endpoint queriesWhat is true on this host right now?osqueryNeeds your queries and a fleet manager

What we saw on our test servers

AIDE on Debian 12 with Debian's default configuration, after we created one test file in /etc:

$ aideinit -y -f                      # 263 seconds, 12.8 MB database
$ aide --config=/etc/aide/aide.conf --check
AIDE found differences between database and filesystem!!
  Total number of entries:	45551
  Added entries:		11
  Removed entries:		42129
  Changed entries:		46
f+++++++++++++++++: /etc/hc-aide-test.conf
f =.... mci.... . : /etc/passwd
f =.... mci.... . : /etc/shadow

The new file and the account files (changed by a test user we had added and removed) are exactly what you'd want flagged. The 42,129 removed entries were another test's directory being deleted while AIDE ran: a reminder that on a server where things change, you must exclude busy paths or every report will be long. Two practical notes: Debian's aide package pulled in a mail server (exim4, listening on localhost:25) to send daily reports, so use --no-install-recommends if you don't want one, and it installs a daily timer.

auditd on AlmaLinux 9.8, with one temporary watch rule:

$ auditctl -w /etc/hc-fim-test.conf -p wa -k hc-fim-test
$ echo "a=1" > /etc/hc-fim-test.conf; chmod 600 /etc/hc-fim-test.conf
$ ausearch --input /var/log/audit/audit.log -k hc-fim-test -i | grep SYSCALL
... syscall=openat ... auid=root ... comm=bash exe=/usr/bin/bash ... key=hc-fim-test
... syscall=fchmodat ... auid=root ... comm=chmod exe=/usr/bin/chmod ... key=hc-fim-test
$ auditctl -W /etc/hc-fim-test.conf -p wa -k hc-fim-test   # remove the rule

Run without --input over a non-interactive SSH session, the same ausearch printed <no matches>, because it can read raw log data from standard input. Its manual says --input-logs is needed when you run it from a cron job; scripts need it too.

Wazuh alternatives

People look for Wazuh alternatives because the server is resource-hungry for small setups, because the default rules are noisy, or because they only need one part of what it does. If you need only file integrity checks, AIDE (with a daily timer and email) does that with no server at all. If you want the classic lightweight HIDS that Wazuh grew out of, OSSEC is still maintained by Atomicorp, with optional free extra rules through OSSEC+. If you want to know who did what, add auditd rules on sensitive paths, which costs nothing on RHEL-family servers. If you want SQL-style visibility across a fleet, osquery with a fleet manager is the flexible option. If your real worry is live attacks rather than changed files, Falco on Kubernetes or CrowdSec on internet-facing services fits better. And if you need compliance reporting against PCI, NIST or CIS with vendor support, Tripwire Enterprise is the commercial option. For a SIEM-style replacement, see our open-source SIEM ranking.

Open source or commercial?

Almost everything here is open source: Wazuh (agent and server GPL-2.0, indexer and dashboard Apache-2.0), OSSEC (GPL-2.0), AIDE (GPL-2.0), auditd (GPL-2.0), osquery (Apache-2.0 or GPL-2.0), Falco (Apache-2.0), Samhain (GPL) and the CrowdSec engine (MIT). The commercial options are Tripwire Enterprise, Wazuh Cloud, Atomicorp's commercial OSSEC and CrowdSec's paid blocklists. You pay for commercial FIM mainly to get compliance content, reports that auditors accept, and someone to call. For a small team running Linux, the open-source tools are complete; the real cost is the time to tune rules so that alerts stay rare and meaningful. Budget for that time either way: a commercial product with untuned rules is just as noisy. Also count the running cost of self-hosting. AIDE, auditd and osquery need no server; Wazuh needs one with 8 GiB of RAM or more, plus storage for its indexer, and someone to keep it patched and backed up.

Do you need a HIDS at all?

If you run a handful of servers with no compliance requirement, start small: patch promptly, keep SSH key-only, ship logs off the server, and run AIDE on /etc, /usr and your SSH and sudo configuration with a daily report. That catches the classic persistence tricks (a new SSH key, a modified binary, an unexpected cron job) for almost no effort. Move to Wazuh or OSSEC when you have enough servers that reading reports one by one stops working, or when an auditor asks for central alerting and retention. And remember that FIM tells you something happened; it doesn't stop it, so it's a complement to a firewall, patching and access control, not a replacement. The most valuable part is often the habit it forces: every change on a server should have an explanation.

How we checked this: On 14 Nov 2026 (UTC), on our two test VMs (both called web-01 here, 2 vCPU and about 2 GB of RAM each). Debian 12: AIDE 0.18.3 from Debian's packages with the default config, aideinit to build the baseline, then aide --check after adding a test file. AlmaLinux 9.8: auditd 3.1.5 with a temporary watch rule on a test file, read back with ausearch and then deleted; osquery 5.24.1 from the official RPM (SHA-256 checked against the GitHub release) with osqueryi queries; and the CrowdSec 1.8.2 engine from its official repository, without a bouncer. Everything we installed was removed afterwards. Wazuh, OSSEC, Falco, Samhain and both Tripwire editions are covered from their documentation; Wazuh's all-in-one server asks for 8 GiB of RAM, more than our test VMs have. Anything we didn't run ourselves comes from the official documentation listed under Sources.

Check which CVEs are really open on your server

HostCrust Patch Proof compares every installed package with your distribution's own security data. It counts fixes your distro backported and checks the kernel that is actually running, not just the one on disk. Read-only, no root, free.

Run the free check About Patch Proof

FAQ

What's the best open-source file integrity monitoring tool for Linux?

For one or a few servers, AIDE: it's GPL-2.0, packaged by Debian, Ubuntu and the RHEL family, and still maintained. For a fleet, Wazuh, which adds central alerting, log analysis and configuration checks. Add auditd rules on the files that matter most if you need to know who made each change.

Is Wazuh free?

Yes, to self-host: every Wazuh component is open source. The agent and server are GPL-2.0 (the server's newer analysis engine is AGPL-3.0), and the indexer and dashboard are Apache-2.0. You pay for the hardware (the all-in-one install asks for 4 vCPU and 8 GiB of RAM for up to 25 agents). Wazuh Cloud, the hosted version, starts at $571 per month for up to 100 agents.

What's the difference between Wazuh and OSSEC?

Wazuh started as a fork of OSSEC and has grown into a full security platform with its own indexer, dashboard, vulnerability detection and configuration assessment. OSSEC is still maintained by Atomicorp (4.4.1 shipped in October 2026) and stays closer to the original lightweight HIDS: log analysis, file integrity checks, rootkit detection and active response.

Does Falco do file integrity monitoring?

Not in the AIDE sense. Falco watches kernel events as they happen and alerts when activity matches its rules, which can include writes to sensitive files. It doesn't keep a baseline of hashes to compare against later. Use Falco for real-time behavior and an FIM tool for proof of what changed on disk.

Is Open Source Tripwire still maintained?

Not actively. Its last release, 2.4.3.7, came out in March 2018, and the last commit to its GitHub repository was in March 2019. Debian 12 still packages it. AIDE does the same job and is maintained. Tripwire Enterprise, sold by Fortra, is a separate commercial product that is maintained.

Is auditd enough for file integrity monitoring?

Not on its own. auditd records who touched a watched file and with which program, as it happens, but it keeps no baseline, so it can't tell you that a file differs from last week's known-good state. It's the perfect partner for AIDE or Wazuh, which can't tell you who made a change.

Sources

  1. Wazuh Cloud pricing
  2. Wazuh docs: quickstart (all-in-one requirements, supported systems)
  3. Wazuh docs: agent installation (Linux, Windows, macOS, Solaris, AIX, HP-UX)
  4. Wazuh LICENSE: GPL-2.0, with the engine under AGPL-3.0 and some shared libraries dual-licensed
  5. Wazuh indexer LICENSE (Apache-2.0)
  6. Wazuh dashboard LICENSE (Apache-2.0)
  7. Wazuh docs: use cases (FIM, vulnerability detection, configuration assessment)
  8. OSSEC project site (4.4.1, OSSEC+ and Atomicorp)
  9. OSSEC docs: supported systems
  10. AIDE project site (0.19.5, GPL-2.0)
  11. Linux Audit userspace (auditd) on GitHub
  12. ausearch(8) manual: --input-logs and reading from stdin
  13. osquery 5.24.1 release on GitHub (packages and checksums)
  14. Falco project site (CNCF graduated, eBPF)
  15. CrowdSec pricing
  16. CrowdSec docs: Linux installation (the engine alone does not block)
  17. Fortra Tripwire datasheet (FIM and security configuration management)
  18. Open Source Tripwire on GitHub
  19. Samhain project site
  20. Samhain downloads (4.5.4, October 2025)