PAGES
← all tools
◆ Detection Engineering

Laurel

v0.8.0 open-source

Transform Linux Audit logs for 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. usage

Summary

Laurel is an open-source post-processing plugin for Linux's auditd, released under the GPLv3, that converts raw audit events into enriched, structured JSON suitable for modern log pipelines. It runs on the host as an auditd plugin rather than a separate service, adding context such as parent-process lineage, 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. hashes of executed binaries, and prefix-matched environment variables, then writing that out over a UNIX domain socket to local log consumers or a SIEM. This suits detection engineers and 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. teams who need Linux audit data usable enough to build reliable rules on, rather than raw syscall lines. Its README frames it as a rethink of existing auditd post-processors, built for better performance and usability rather than as a wrapper around one. With 17 contributors, 65 commits and 11 releases in the past year, and a release 35 days ago, it is under active development.

Transform Linux Audit logs for SIEM usage

How Laurel helps

Which process really launched this one, beyond the immediate parent?

attaches parent-process lineage to each event, naming the command, executable path and event ID of the ancestor so a detection rule can walk the chain without a separate lookup

Is this executed binary the one I expect, or has it been swapped?

computes a SHA-256 hash of the binary at execution time and includes it in the event, so the recorded hash can be checked against a known-good value

Can I capture specific environment variables without logging every credential that passes through a process?

matches environment variables by configured prefix, so only the named variables are pulled into the log rather than the full environment

Are my audit logs reaching my SIEM without a fragile file-tail step?

writes enriched events directly to a UNIX domain socket that local log consumers or a SIEM can read from, avoiding disk-based log shipping

all 11 features, with the evidence for each →

Languages

Not documented

Features

11 capabilities across 4 capability groups

Built from Laurel's releases, docs, README and our own runs. “Seen” marks the month we first spotted a release the vendor didn't date. Group names and tags are our labels.

Compare with peers →

  • Laurel covers 4 of the 11 logs and telemetry capabilities we track.

What Laurel offers you

  • JSON data export1
Log collection 1 feature Logs and telemetry since 2021
Event stream handling shipped Ingests continuous input streams that lack explicit end-of-event markers. 2 releases · first seen Dec 2021

Shared capability: Log collection

release

  • Configurable filtering behavior: keep first event for new processes v0.6.2 · May 2024 · source · release history
  • Adds support for input streams without EOE (End Of Event) messages v0.2.0 · Dec 2021 · source · release history
Log parsing and normalization 1 feature Logs and telemetry since 2021
Audit log translation shipped Translates kernel audit operations, such as IO_URING events, into readable fields for compatibility with auditd. 2 releases · 1 other source · first seen Dec 2021

Shared capability: Log parsing and normalization

Also counts toward: JSON data export

release

  • Translates IO_URING audit operations into readable fields, supporting auditd 3.1+ kernels v0.6.5 · Jan 2025 · source · release history
  • Adds translation of numeric/binary values equivalent to auditd log_format=ENRICHED v0.2.0 · Dec 2021 · source · release history

docs

  • Auditd event post-processing plugin that converts raw Linux audit logs into enriched, structured JSON for security monitoring.
Log enrichment 1 feature Logs and telemetry since 2025
Systemd integration shipped Enriches process records with systemd service information, including service name and unit state. 1 release · first seen Jan 2025

Shared capability: Log enrichment

release

  • Enriches process records with _systemd_ service information (e.g., service name, unit state) when processes run as part of systemd services v0.6.5 · Jan 2025 · source · release history
Log routing 1 feature Logs and telemetry since 2024
Log output destinations shipped Sends logging output to a UNIX domain socket for integration with local log consumers. 4 releases · 1 other source · first seen Feb 2024

Shared capability: Log routing

release

  • Adds logging output to a UNIX domain socket for integration with local log consumers. v0.8.0 · Jul 2026 · source · release history
  • Enables Logging to UNIX domain socket as a transport option for log output v0.8.0 · Jul 2026 · source · release history
  • Adds support to log events to an external program or script instead of stdout/stderr v0.6.4 · Dec 2024 · source · release history
  • Adds syslog_marker config key to customize the log source identifier written to Syslog v0.6.0 · Feb 2024 · source · release history

example

  • Pipe Laurel events directly into a custom processing script for real-time alerting. laurel --logger /usr/local/bin/custom_alert_handler.sh v0.6.4 · Dec 2024 · source
Other / not yet classified 7 features Features we have not matched to a capability yet. A suggested match is marked.
Environment variable capture shipped suggested Captures environment variables at process execution time, with support for selective capture by prefix matching. 5 releases · first seen Jan 2024

Suggested capability: Log enrichment. This is our guess, not confirmed.

release

  • Supports prefix matching for environment variables, enabling selective capture of env vars by prefix. v0.8.0 · Jul 2026 · source · release history
  • Adds Prefix matching for environment variables to allow filtering or grouping based on variable name prefixes v0.8.0 · Jul 2026 · source · release history
  • Adds --key-prefix configuration option to prepend a custom string instead of using capitalized key names for enriched/translated data v0.6.5 · Jan 2025 · source · release history
  • Removes the deprecated PARENT_INFO sub-structure from the output JSON v0.6.0 · Feb 2024 · source · release history
  • Improvements in enrichment of data from short-lived processes v0.5.6 · Jan 2024 · source · release history
Executed binary integrity checking shipped Calculates SHA-256 hashes of executed binaries to support integrity verification of process execution. 4 releases · 1 other source · first seen Sep 2021

release

  • Supports calculating SHA-256 hashes for executables in event records v0.8.0 · Jul 2026 · source · release history
  • Supports calculating SHA-256 hashes for executed binaries, enabling integrity checking of process execution. v0.8.0 · Jul 2026 · source · release history
  • Adds Apply labels for executables to processes found in /proc support, improving visibility into ephemeral processes. v0.7.0 · Mar 2025 · source · release history
  • Adds --dry-run CLI flag to validate configuration files without executing the tool v0.1.3 · Sep 2021 · source · release history

example

  • Validate your configuration changes before running the agent to catch syntax errors early laurel --dry-run v0.1.3 · Sep 2021 · source
Process lineage tracking shipped Tracks process ancestry across single-exec and fork/exec scenarios using a unified spawned-by field. 2 releases · 1 other source · first seen Dec 2024

release

  • New SYSCALL.SPAWNED_BY field unifies process-lineage tracking across both single-exec and fork/exec scenarios. v0.8.0 · Jul 2026 · source · release history
  • Adds the ability to add or remove process labels based on the execve() command-line arguments v0.6.4 · Dec 2024 · source · release history

example

  • Dynamically tag processes based on their arguments for specific audit rules. laurel --label-add 'cmd:arg' 'bash -i' --label-remove 'cmd:arg' 'ssh host' v0.6.4 · Dec 2024 · source
Container image distribution shipped Provides a dedicated container image for running the tool, including support for immutable container distributions. 2 releases · first seen May 2023

release

  • Adds setup instructions for running Laurel in a container on immutable container distros like CoreOS v0.5.2 · May 2023 · source · release history
  • Provides a dedicated container image for the service v0.5.2 · May 2023 · source · release history
Build identification shipped Allows configuring a custom build identifier to distinguish between deployment artifacts. 1 release · first seen Mar 2025

release

  • New Configurable build identifier setting allows distinguishing between deployment artifacts. v0.7.0 · Mar 2025 · source · release history
State persistence shipped Saves processing offsets across restarts to eliminate cold-start penalties. 1 release · first seen Mar 2025

release

  • Save state across restarts eliminates cold-start penalties by persisting the processing offset. v0.7.0 · Mar 2025 · source · release history
Library distribution shipped Distributes the cyber tooling via a dedicated library crate for programmatic integration. 1 release · first seen Dec 2021

release

Lines in monospace are the tool's own words: help text parsed from its source, or an endpoint from its API document. Under release, a line is our summary of a dated release. Under docs, it is quoted from the tool's own documentation or website. Each links back to the source it came from.

Screenshots

From the release notes, newest first. Click one to see it full size.

v0.8.0 Jul 15, 2026

Score card

  1. Shipping velocity releases a month, last 12 months
  2. Documentation quality release-notes rubric, 0–100
  3. Breaking-change discipline how rarely a release breaks users, and notice given
  4. Maintenance risk quiet time against its own cadence, maintainers
  5. Innovation & surface new capabilities, API and MCP surface
  6. Community health
  7. Contributor trend distinct committers, this year against last
  8. Maintainer concentration bus factor now against a year ago
  9. Issue backlog trend issues closed per issue opened, 12 months
  10. Responsiveness median time to a maintainer’s first reply

Nine scores for Laurel, 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 →

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 Laurel 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…

Explore the full chart →

Releases

Show

10 entries

  1. July 20261
  2. March 20251
  3. January 20251
  4. December 20241
  5. May 20241
  6. February 20241
  7. January 20241
  8. May 20231
  9. December 20211
  10. September 20211
    Show

    10 entries

    Project health

    Issue, contributor and maintainer activity in threathunters-io/laurel, 2023-10 – 2026-09, as of 2026-09-25. Twelve-month figures first; the trend lines run the whole window.

    1. Contributors 3 −1 vs prior 12 months
    2. Maintainers 1 +0 joined · −0 left, last 12 months
    3. Bus factor 1 committers behind half the commits
    4. Community-filed 100% of issues opened, last 12 months
    5. Median time to close 51 days first maintainer reply 3 hours
    6. Open backlog 7 of 89 issues ever filed
    1. Issues opened / month 0 · 0 communitymaintainers
    2. Open backlog 7
    3. Contributors / month 1
    4. Commits / month 3
    5. Stars 862
    Issue themes, last 12 months
    • 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.

    Tracked by Cyber Toolchain Choose a badge style and copy the code →
    browse all tools → score card for your toolchain →