OSSEC HIDS
4.4.0 open-sourceThe section your link pointed to isn't on OSSEC HIDS's page any more, so we've brought you to the top.
OSSEC is an Open Source Host-based Intrusion Detection System that performs log analysis, file integrity checking, policy monitoring, rootkit detection, real-time alerting and active response.
### Approved internal networks
### private LAN
url https://example.com/page#anchor ### keep the # in the value
<localfile>
<log_format>modsec-audit</log_format>
<location>/var/log/modsec_audit.log</location>
</localfile>
agent_control -M enable -u 042
<syslog_output>
<server>siem.example.com</server>
<port>6514</port>
<protocol>tcp</protocol>
<tls>yes</tls>
<tls_verify>yes</tls_verify>
<tls_ca>/var/ossec/etc/ca-bundle.crt</tls_ca>
<format>json</format>
</syslog_output>
<localfile>
<log_format>modsec-audit</log_format>
<location>/var/log/modsec_audit.log</location>
</localfile>
agent_control -M enable -u 042
# ... perform maintenance ...
agent_control -M end -u 042
<syslog_output>
<server>siem.example.com</server>
<port>6514</port>
<protocol>tcp</protocol>
<tls>yes</tls>
<tls_verify>yes</tls_verify>
<tls_ca>/var/ossec/etc/ca.pem</tls_ca>
<format>json</format>
</syslog_output>
<localfile>
<log_format>modsec-audit</log_format>
<location>/var/log/modsec_audit.log</location>
</localfile>
<client>
<crypto_method>blowfish</crypto_method>
</client>
<syscheck>
<directories check_sha256sum="no">/etc</directories>
</syscheck>
<localfile><location>journal</location></localfile>
<rule id='1000' level='5'>
<match_pcre2>failed password</match_pcre2>
</rule>
<ossec_config>
<analysisd>
<decoder_order_size>50</decoder_order_size>
</analysisd>
</ossec_config>
export PCRE2_SYSTEM=yes
make USE_PRECOMPIDED_SHOWMSG=no
ossec-authd -f
manage_agents -f /path/to/clients.txt
<ossec_config>
<rootcheck>
<disabled>yes</disabled>
<check_pids>no</check_pids>
<check_ports>yes</check_ports>
</rootcheck>
</ossec_config>
<ossec_config>
<syslog_output>
<format>json</format>
</syslog_output>
</ossec_config>
Summary
OSSEC HIDS is an open-source host-based intrusion detection platform, free to use, that combines file integrity monitoring, log analysis, and rootkit detection into one system. It runs as a manager-and-agent deployment: a server daemon receives events from agents installed on Linux, Windows, and AIX hosts, encrypting communication with AES by default and hashing monitored files with SHA-256SHA-256A cryptographic hash function that turns data into a fixed 256-bit fingerprint. It is used to check integrity; hashing does not encrypt the original data.. This suits SOCSOCA security operations center, the team or function that monitors threats, investigates alerts and coordinates incident response. Its work can be internal, outsourced or shared. analysts and system administrators who need host-level visibility rather than network-based detection, and its own README describes it as mixing HIDS, log monitoring, and SIEMSIEMSecurity information and event management, collecting logs from many systems and correlating events to find suspicious activity. Analysts use it to investigate alerts and incidents. functions into one solution rather than pointing to a specific competitor. First committed in 2005, it remains active, with 193 contributors and a release cut 19 days ago.
OSSEC is an Open Source Host-based Intrusion Detection System that performs log analysis, file integrity checking, policy monitoring, rootkit detection, real-time alerting and active response.
How OSSEC HIDS helps
Has a file that shouldn't change been modified since the last check?
hashes monitored files and directories with SHA-256 by default and alerts when a checksum no longer matches the baseline, though directories can be opted out of SHA-256 in favor of older hash formats
Is someone brute-forcing or otherwise attacking a host right now?
parses incoming logs against its decoder and rule set and raises an alert when a pattern like repeated failed logins matches a signature
Is a rootkit hiding on one of these machines?
runs signature-based rootkit checks against the host and reports matches, with signatures updated for specific rootkit families over time
Which of my hosts are actually talking to the manager, and were any agents tampered with mid-registration?
encrypts agent-to-server traffic with AES by default and logs duplicate-IP or state-backup conditions when an agent is removed or force-deleted
Can I make planned maintenance on a server not flood me with integrity alerts?
lets an administrator put a specific agent's file integrity monitoring into a maintenance state so changes during that window are absorbed into the baseline instead of triggering alerts, then resumes scanning and alerting once ended
Where do my alerts end up, and can that channel be trusted on an untrusted network?
forwards alerts by email or to a syslog collector, and supports carrying that syslog traffic over TLS-secured TCP with certificate verification instead of plain UDP
Languages
Command line
No command matches.
| option | found in | since | description |
|---|
Values are placeholders taken from each option’s declared default. Nothing is executed here — the output shown is a recording of a run that already happened.
Score card
-
Shipping velocity releases a month, last 12 months
-
Documentation quality release-notes rubric, 0–100
-
Breaking-change discipline how rarely a release breaks users, and notice given
-
Maintenance risk quiet time against its own cadence, maintainers
-
Innovation & surface new capabilities, API and MCP surface
- Community health
-
Contributor trend distinct committers, this year against last
-
Maintainer concentration bus factor now against a year ago
-
Issue backlog trend issues closed per issue opened, 12 months
-
Responsiveness median time to a maintainer’s first reply
Nine scores for OSSEC HIDS, each built from the releases, notes and API history this site tracks — and, on Researcher and Business, where it stands among every measured tool in its category and how that has moved.
Score cards are part of every paid plan.
See plans → Already subscribed? Sign in →Trajectory
Blank means never measured; nothing here is a filled-in zero.
Peer standings are included with Researcher and Business. See how this tool ranks against its competitors, using data we don't publish anywhere else.
See plans →Each score is 0–100 on a published rubric, derived from data this site already shows. A dimension we cannot measure says so — it is never scored 0 and never enters a rank.
How this is scored
- Shipping velocity — releases a month over the last 12 months, on a log scale where 16 a month scores 100. Needs 3 releases in the window.
- Documentation quality — the release-notes rubric published on the analytics page, unchanged.
- Breaking-change discipline — the share of releases carrying a breaking change (none scores 100, half or more scores 0). Only projects that label breaking changes are measured: a clean record cannot be told from an unlabelled one.
- Maintenance risk — quiet time measured against the tool's own release cadence (quiet longer than 90 days and three typical gaps scores 0), plus the number of active maintainers and whether contributors are growing, where known. Higher is lower risk.
- Innovation & surface — new capabilities in the feature ledger this year, API and MCP operations added, and the share of commits that are features: the mean of whichever we hold.
- Community health (open-source tools only) — each is a direction, not a size: contributors this year against last, the bus factor now against a year ago, and issues closed per issue opened, where steady scores 50, doubled 100 and halved 0; plus the median time to a maintainer's first reply (an hour scores about 100, a month or more 0). A commercial card has no repository and carries none of the four.
- Documented delivery (commercial tools) — when a vendor's documented new capabilities have slowed against its own baseline, that counts against the overall standing as heavily as two low dimensions. Steady delivery, or too little history to judge, leaves the standing alone; it is never a sixth score.
- Open-source tools are scored on repository signals; commercial tools on their published changelog. Ranks compare tools within one category and one profile and need at least five measured peers; the overall standing needs three ranked dimensions. Best-in-breed or consolidator is a shape, not a quality, and is never scored.
Release-note detail over time
See how much detail OSSEC HIDS puts in its release notes, quarter by quarter, and compare it with tracked tools in the same category. This history uses up to ten retained, reviewed notes per tool; sparse or blank older quarters may reflect that limit.
Checking release-note history…
Coverage
Missing something? Tell us
What OSSEC HIDS connects to, runs on and detects, read from its release notes and docs. So far: 1 new detection.
1 change, tracked since Oct 5, 2026.
-
Oct 52026
new GeoIP IDS rules: multi-country authentication and impossible-travel
GeoIP IDS rules (multi-country auth, impossible-travel) plus ASN/country enrichment; SSH invalid-user dstuser extraction; feed if_matched_group when sid_prev_matched is also set
Nothing first seen in this window. That doesn't mean OSSEC HIDS shipped nothing, only that we found no record of it.
How we count
Read from 1 of 24 release notes and docs updates we hold for OSSEC HIDS. "First seen" is the earliest note that names something; "last" is the latest. Our history may start partway through OSSEC HIDS's life, so an old integration can show a recent first-seen date.
Each change counts once: "added 40 checks" is one line, so the numbers measure how often coverage moves, not how big the catalogue is or how well it detects.
Releases
24 entries
No entries match these filters.
- October 20261
- September 20262
- August 20264
- May 20261
- February 20261
- January 20251
- January 20221
- February 20201
- November 20191
- October 20191
- April 20191
- February 20191
- October 20181
- July 20181
- December 20171
- August 20171
- June 20171
- February 20171
- February 20142
Project health
Issue, contributor and maintainer activity in ossec/ossec-hids, 2023-10 – 2026-09, as of 2026-09-25. Twelve-month figures first; the trend lines run the whole window.
- Contributors 3 +2 vs prior 12 months
- Maintainers 1 +0 joined · −0 left, last 12 months
- Bus factor 1 committers behind half the commits
- Community-filed 100% of issues opened, last 12 months
- Median time to close 7.1 years first maintainer reply 7 days
- Open backlog 117 of 1,040 issues ever filed
- Issues opened / month 0 · 0 communitymaintainers
- Open backlog 117
- Contributors / month 1
- Commits / month 2
- Stars 5,060
- other 100%
Counts from the project's public repository and git history; no individuals are identified. Maintainers are the committers covering 80% of the last year's commits. how we measure this
Libraries its release ships
What its latest release locks, checked against known advisories.None of its release's images build from a lockfile we can read.
Add the badge to your README
Maintain this project? The badge links readers straight to this page, so they can follow every release here.