PAGES
← all tools
◆ Detection Engineering

Kunai

v0.6.0 open-source

Kunai is a Linux security monitoring and threat-hunting tool that uses eBPFeBPFA Linux technology for running verified programs inside the kernel without changing its source. Tools use it to observe processes, enforce rules and process network traffic. kernel-level probes to capture, enrich, and correlate system events.

Summary

Kunai is an open-source detection-engineering tool that monitors Linux systems for security events using eBPF probes, capturing kernel-level activity and correlating it into chronologically ordered, enriched events in userland. It ships as a self-contained Rust binary you install and run directly on a host, including inside containers, since it understands Linux namespaces and can trace container activity alongside the underlying system. This makes it a fit for detection engineers and threat hunters running Linux fleets rather than desktop endpoints. Its own README describes it as the Linux counterpart to Sysmon, with detection rules supporting YARA-X matching, filtering, and testing from the CLI. First committed in 2023, it has had 153 commits and 10 releases in the past year, suggesting active, ongoing development.

Kunai is a Linux security monitoring and threat-hunting tool that uses eBPF kernel-level probes to capture, enrich, and correlate system events.

How Kunai helps

What is happening on this host right now, in the order it actually occurred?

streams kernel-level events captured by eBPF probes into a single chronologically ordered feed, with reordering and enrichment done in userland before anything reaches the analyst

Did the activity I'm seeing come from inside a container or from the underlying host?

understands Linux namespaces so container process activity is traced and attributed alongside host-level events rather than blurred together

Which processes on this box are spawning suspicious children, and with what command line?

execve events carry parent command-line context, letting an analyst trace the full lineage of a suspicious execution back to what launched it

Is this network activity from my host the same connection another tool logged elsewhere?

tags network events with a Community-ID value so the same flow can be matched across Kunai and other monitoring tools

Am I losing visibility during a burst of activity?

emits an event when the kernel drops events before they reach userland, and rate-limits filesystem events per task and globally so floods don't silently swallow data

Would this detection rule actually fire on the events I've already collected?

runs saved detection rules against a stored log of events and reports matches, so rule logic can be checked before it is trusted live

all 25 features, with the evidence for each →

Languages

Not documented

Features

25 capabilities across 3 capability groups

Built from Kunai'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 →

  • Kunai covers 3 of the 11 logs and telemetry capabilities we track.

What Kunai offers you

  • Command-line interface5
  • Offline mode1
Log enrichment 2 features Logs and telemetry since 2024
event-enrichment shipped Adds contextual metadata to events, including external tool identification and parent command lineage, for richer analysis. 2 releases · 1 other source · first seen Apr 2024

Shared capability: Log enrichment

release

  • Adds parent_command_line field to execve and execve_script events for richer process execution context. v0.6.0 · Jun 2025 · source · release history
  • Adds info.event.source field to Kunai logs for external tool identification v0.2.0 · Apr 2024 · source · release history

docs

  • Version: 0.6.0 Every kunai event gets a set of common fields shared between all the events. These fields give various information which might be used for advanced purposes such as event identification, grouping or correlation. For the general event layout, every event will have a data section and an info section. seen Oct 2026 · source
user-context-enrichment shipped Resolves user and group names in events to provide human-readable context for audit and security analysis. 1 release · first seen Jan 2025

Shared capability: Log enrichment

release

  • Adds user and group name resolution so events include human-readable user/group context for richer audit and security analysis. v0.5.0 · Jan 2025 · source · release history
Log replay 2 features Logs and telemetry since 2024
offline-log-replay shipped Reprocesses previously captured eBPF event data stored in logs for offline analysis, benchmarking, or full event output. 2 releases · 1 other source · first seen May 2024

Shared capability: Log replay

Also counts toward: Command-line interface, Offline mode

release

  • Adds print all option to the replay command, enabling output of all events during log replay. v0.5.4 · Feb 2025 · source · release history
  • Adds the replay subcommand to reprocess previously captured eBPF event data v0.2.1 · May 2024 · source · release history

example

  • Replay stored event logs for offline analysis without running the eBPF collector again. kunai replay --input /var/lib/kunai/events.bin v0.2.1 · May 2024 · source
performance-benchmarking shipped Measures event processing throughput and capacity via a dedicated benchmarking feature in the replay command. 1 release · 1 other source · first seen Nov 2024

Shared capability: Log replay

Also counts toward: Command-line interface

release

  • Adds benchmarking capability to the replay command to measure event processing throughput. v0.4.0 · Nov 2024 · source · release history

example

  • Benchmark how fast Kunai can process a saved event log — useful for capacity planning or tuning rule sets. kunai replay --benchmark events.jsonl v0.4.0 · Nov 2024 · source
Security event correlation 1 feature Logs and telemetry since 2024
network-correlation shipped Integrates the Community-ID standard to facilitate correlation of network events across different security tools. 1 release · first seen Nov 2024

Shared capability: Security event correlation

release

  • Integrates the Community-ID standard for easier correlation of network events across tools. v0.3.0 · Nov 2024 · source · release history
Other / not yet classified 20 features Features we have not matched to a capability yet. A suggested match is marked.
rule-validation-tools shipped Provides CLI commands to test filters, validate rules, and inspect filter logic against events. 3 releases · 1 other source · first seen Jan 2025

Also counts toward: Command-line interface

release

  • New test command to test filters against events. v0.6.0 · Jun 2025 · source · release history
  • Includes filter information in scan results to aid understanding and debugging of filtering rules. v0.6.0 · Jun 2025 · source · release history
  • Adds rule testing capability to validate and test detection rules directly from the CLI. v0.5.3 · Jan 2025 · source · release history

docs

  • Built For Security Monitoring Feed your SIEM with high quality Linux events. Threat Hunting Explore what really happens on your Linux hosts. Incident Response Reconstruct process trees and attacker activity. Detection Engineering Write and test rules against real events. docs update · Oct 2026 · source
advanced-rule-filtering shipped Provides complex boolean logic and exclusion operators within detection rules to precisely control which events are processed. 2 releases · 1 other source · first seen Jul 2024

release

  • Supports prefixing event-IDs with - (minus) in event selection to exclude specific event types from processing. v0.2.6 · Jul 2024 · source · release history
  • Adds none of them, none of $VAR_PREFIX, any of them, any of $VAR_PREFIX, all of them, all of $VAR_PREFIX, N of them, and N of $VAR_PREFIX condition expressions to rule definitions. v0.2.6 · Jul 2024 · source · release history

docs

  • Version: 0.6.0 Using Kunai to monitor every single event happening on a system is nice as it gives a very deep insight of what is going on. However, this approach generates loads of events. docs update · Oct 2026 · source
ioc-scanning shipped Scans for Indicators of Compromise (IoC) within captured events to identify known malicious artifacts or behaviors. 1 release · 2 other sources · first seen Apr 2024

release

  • Adds IoC (Indicators of Compromise) scanning capability via commit implementing fix #22 v0.2.0 · Apr 2024 · source · release history

docs

  • Version: 0.6.0 Event Layout and Info Section Every kunai event gets a set of common fields shared between all the events. These fields give various information which might be used for advanced purposes such as event identification, grouping or correlation. docs update · Oct 2026 · source
  • Version: 0.6.0 IoC (Indicator of Compromise) scanning results from the same motivation behind detection rules . It addresses the need to log only events matching specific IoCs . Even though one can match IoC with detection rules it is not very convenient to manage for lots of IoCs and even less to automate. docs update · Oct 2026 · source
system-logging shipped Provides structured logging of agent internal states, including startup information and log levels. 2 releases · first seen Jan 2025

release

  • New log event (refactored from error event) distinguishes informational, warning, and error messages from the agent. v0.5.0 · Jan 2025 · source · release history
  • New start event surfaces detailed agent startup information and system metadata at launch time. v0.5.0 · Jan 2025 · source · release history
file-event-detection shipped Detects and logs specific file activity events, including creation and write-close operations. 2 releases · first seen Nov 2024

release

  • New file_create event detects and logs file creation activity on the host. v0.4.0 · Nov 2024 · source · release history
  • Adds a new security event triggered when a file is written then closed (write_close), enabling finer-grained file-activity monitoring. v0.3.0 · Nov 2024 · source · release history
log-access shipped Provides CLI commands to view live or stored logs directly without manual file system navigation. 1 release · 1 other source · first seen Nov 2024

Also counts toward: Command-line interface

release

  • Revamps the CLI for a smoother user experience, including a new logs command for fast log access and an install command to simplify installation. v0.3.0 · Nov 2024 · source · release history

example

  • View live or stored Kunai logs directly from the CLI without manually locating log files. kunai logs v0.3.0 · Nov 2024 · source
log-management shipped suggested Manages log storage and retention through automatic rotation, compression, and configurable file size limits. 2 releases · first seen Jul 2024

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

release

  • Adds automatic log rotation to keep log files clean and manageable. v0.3.0 · Nov 2024 · source · release history
  • Adds log rotation support with configurable maximum file size and compression to manage long-running output logs. v0.2.5 · Jul 2024 · source · release history
kernel-probe-detection shipped Detects usage of specific kernel probe functions such as finit_module and prctl to identify potential rootkit or hooking activity. 2 releases · first seen Apr 2024

release

configuration-validation shipped Validates configuration file syntax and correctness before deployment to prevent runtime errors. 1 release · first seen Jun 2025

Also counts toward: Command-line interface

release

  • New validate command to check configuration files for correctness before deployment. v0.6.0 · Jun 2025 · source · release history
io-monitoring shipped Supports tracking of io_uring submission queue entries for modern I/O monitoring. 1 release · first seen Jun 2025

release

  • Adds io_uring_sqe event support for tracking I/O ring submission queue entries. v0.6.0 · Jun 2025 · source · release history
data-integrity-monitoring shipped suggested Reports events when kernel-to-userland data drops occur, providing visibility into lost telemetry. 1 release · first seen Jan 2025

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

release

  • New event_loss event reports when kernel-to-userland event drops occur, giving visibility into data loss under high load. v0.5.0 · Jan 2025 · source · release history
resource-management shipped Prevents resource exhaustion by implementing configurable per-CPU filesystem event rate limiting. 1 release · first seen Jan 2025

release

  • New per-CPU filesystem event rate limiting (configurable task-level and global limits) prevents event floods and improves resource management. v0.5.0 · Jan 2025 · source · release history
event-streaming-performance shipped Optimizes event delivery latency through unbuffered output modes for downstream consumers. 1 release · first seen Nov 2024

release

  • Adds unbuffered output mode for lower-latency event streaming to downstream consumers. v0.4.0 · Nov 2024 · source · release history
rule-authoring-support shipped Enhances rule creation with string template support and other features to simplify authoring complex rules. 1 release · first seen Nov 2024

release

  • Introduces string template support in detection rules for more flexible rule authoring. v0.4.0 · Nov 2024 · source · release history
detection-response-actions shipped Allows detection rules to define specific actions or responses when a rule matches, enabling active reaction to threats. 1 release · first seen Nov 2024

release

  • Enables detection rules to handle specific actions, offering greater response flexibility. v0.3.0 · Nov 2024 · source · release history
event-name-filtering shipped Allows filtering events directly within detection rules based on the event name. 1 release · first seen Nov 2024

release

  • Adds event filtering by name directly within detection rules. v0.3.0 · Nov 2024 · source · release history
hardened-mode shipped Enforces a secure operational mode using Linux Security Modules (LSM) to protect the monitoring agent itself. 1 release · first seen Nov 2024

release

  • Supports running and installing Kunai in hardened mode via LSM (Linux Security Modules) integration for enhanced protection. v0.3.0 · Nov 2024 · source · release history
malware-detection-integration shipped Integrates YARA-X engine to enable advanced pattern-based malware detection within custom rules. 1 release · first seen Nov 2024

release

  • Integrates YARA-X for advanced malware detection within detection rules. v0.3.0 · Nov 2024 · source · release history
ptrace-monitoring shipped Provides visibility into ptrace-based system interactions through dedicated security events. 1 release · first seen Nov 2024

release

  • Introduces a new ptrace security event for deeper visibility into ptrace-based system interactions. v0.3.0 · Nov 2024 · source · release history
signal-monitoring shipped Tracks kill-signal activity on processes to monitor process termination events. 1 release · first seen Nov 2024

release

  • Introduces a new kill security event for tracking kill-signal activity. v0.3.0 · Nov 2024 · source · release history

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.

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 Kunai, 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 Kunai 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 →

Coverage

Missing something? Tell us

What Kunai connects to, runs on and detects, read from its release notes and docs. So far: 2 new detections, 1 new supported platform.

Show

3 changes, tracked since Oct 9, 2026.

  • Oct 92026

    new Kunai YAML detection rules with MITRE ATT&CK tagging

    With execve, execve_script, T1036, mimic.kthread

    Detection rules are simple YAML files matching on any event field. This one catches binaries masquerading as kernel threads, a technique sometimes used by malware to hide itself.

    Source ↗

  • Oct 92026

    new IoC matching and YARA file scanning with triggered actions

    With IoCs

    Match indicators of compromise live, scan files with YARA and trigger actions such as killing a malicious process.

    Source ↗

  • Oct 92026

    new Container-aware Linux security monitoring via eBPF

    With Aya

    Container Aware: Monitor activity inside your containers and apply all your threat-hunting rules to them seamlessly. Built with the Aya library: low overhead, memory safe and running on a wide range of kernels.

    Source ↗

How we count

Read from 1 of 14 release notes and docs updates we hold for Kunai. "First seen" is the earliest note that names something; "last" is the latest. Our history may start partway through Kunai'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

Show
Coverage in all entries

14 entries

  1. October 20264
  2. June 20251
  3. February 20251
  4. January 20252
  5. November 20242
  6. July 20242
  7. May 20241
  8. April 20241
    Show
    Coverage in all entries

    14 entries

    Project health

    Issue, contributor and maintainer activity in kunai-project/kunai, 2023-12 – 2026-11, as of 2026-11-03. Twelve-month figures first; the trend lines run the whole window.

    1. Contributors 2 ±0 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 86% of issues opened, last 12 months
    5. Median time to close 10 days first maintainer reply 9.8 days
    6. Open backlog 14 of 91 issues ever filed
    1. Issues opened / month 1 · 0 communitymaintainers
    2. Open backlog 14
    3. Contributors / month 0
    4. Commits / month 0
    5. Stars 1,091
    Issue themes, last 12 months
    • features 21%
    • other 79%

    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 →