PAGES
← all tools
◆ Runtime Security

Tracee

v0.24.0 (2025-11-14) open-source

Tracee is an open-source runtime security and forensics 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. to trace system events and detect suspicious behavior in Linux environments.

Summary

Tracee is an open-source runtime security and forensics tool, free to use, that attaches eBPF programs to a running Linux kernel to catch behavior other tools only see after the fact. It runs as a service on the host or inside a container, managed through traceectl, a dedicated CLI bundled for interacting with it, and exposes metrics and event counts over a gRPCgRPCAn open-source remote procedure call framework from Google that uses HTTP/2 and Protocol Buffers to let services call each other's functions across a network, giving tools low-latency, strongly typed inter-process communication. API. Detection logic ships as Go-based signatures, with events like stack_pivot and suspicious_syscall_source aimed at catching exploitation techniques such as shellcode injection or memory tampering, which 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 incident responders working in containerized Linux environments. Its documentation frames it as a runtime security and observability layer built on eBPF rather than a policy-scanning tool. First committed in 2019, it has 113 contributors and remains under active development, with 737 commits in the past year.

Tracee is an open-source runtime security and forensics tool that uses eBPF to trace system events and detect suspicious behavior in Linux environments.

How Tracee helps

Which processes on this host are exploiting memory in ways a file-based scanner would never catch?

watches syscalls in real time for stack pivoting and calls originating from suspicious, non-standard memory regions, flagging the process and call path the moment it happens

Who changed permissions on sensitive files, and from which process?

tracks every chmod-family operation across all processes through a single unified event, naming the process and target path

Did someone tamper with resource limits or the system clock to cover their tracks or escape containment?

raises a dedicated event whenever a process alters resource limits or modifies system time through the kernel hook, showing which process made the change

What actually happened on this host during an incident, beyond what the application logs captured?

correlates process lineage, file operations, and network activity from kernel-level events, plus full packet capture with process and container context for the traffic itself

Which of my detection signatures are actually still running after an upgrade?

reports metadata about the running instance and per-event counts over its API, so a signature that stopped firing shows up as a drop in counts rather than silence

Is a container escaping its expected file or mount namespace?

reports file-open activity enriched with namespace and mount context, so an open that crosses into an unexpected namespace is visible in the event data

all 16 features, with the evidence for each →

Languages

Not documented

Features

16 capabilities · 3 backed by code, an API document or a real run

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

  • Tracee covers 1 of the 11 endpoint investigation and controls capabilities we track.

What Tracee offers you

  • Command-line interface4
  • gRPC API support2
  • Outbound webhooks (the product notifies you)2
  • Offline mode1
  • Plugin API support1
  • Plugin system1
  • Scripting language support1
  • User-defined detection rules1
All capabilities 16 capabilities
Runtime event tracing shipped suggested Traces security-relevant events across the host, with filtering by event type or container scope. 78 releases · 15 other sources · first seen May 2020

Suggested capability: Process telemetry. This is our guess, not confirmed.

release 78 total

  • Adds heartbeat event type v0.24.0 (2025-11-14) · Nov 2025 · source · release history
  • Adds open_file_ns and open_file_mount events for filesystem tracking v0.24.0 (2025-11-14) · Nov 2025 · source · release history
  • Reintroduces the --containers flag to filter output by container context v0.24.0 (2025-11-14) · Nov 2025 · source · release history
  • Adds open_file_ns and open_file_mount events for tracking file-open activity with namespace and mount context. v0.24.0 · Nov 2025 · source · release history
  • Adds security_sb_umount eBPF event detection v0.24.0 (2025-11-14) · Nov 2025 · source · release history
  • Separates data field decoding types in the API payload v0.24.0 (2025-11-14) · Nov 2025 · source · release history

example 15 total

  • Track all chmod-family permission change operations across processes using the new unified chmod_common event. docker run --privileged --pid=host -v /etc/os-release:/etc/os-release -v /sys/kernel/security:/sys/kernel/security aquasec/tracee:0.23.0 --events chmod_common v0.23.0 · Feb 2025 · source
  • Detect syscalls issued from suspicious (non-standard) memory regions to catch shellcode or injection activity. docker run --privileged --pid=host -v /etc/os-release:/etc/os-release -v /sys/kernel/security:/sys/kernel/security aquasec/tracee:0.23.0 --events suspicious_syscall_source v0.23.0 · Feb 2025 · source
  • Detect stack pivoting exploitation attempts in real time by enabling the new stack_pivot event. docker run --privileged --pid=host -v /etc/os-release:/etc/os-release -v /sys/kernel/security:/sys/kernel/security aquasec/tracee:0.23.0 --events stack_pivot v0.23.0 · Feb 2025 · source
  • Filter syscalls by specific argument values using the new args filter. tracee --args-filter 'syscall=openat,fd,>0' v0.10.0 · Dec 2022 · source
  • Filter events by the name of the executable binary. tracee --binary-filter 'bash' v0.10.0 · Dec 2022 · source
  • Quickly check which system calls or events are supported before writing a filter rule. tracee --list-events v0.6.3 · Oct 2021 · source
Signature management engine shipped Provides an API and CLI interface for loading, unloading, listing, and versioning detection signatures, including support for Rego policies. 18 releases · 2 other sources · first seen Feb 2021

Also counts toward: Command-line interface, User-defined detection rules, Scripting language support

release 18 total

  • Adds GetProtoHTTPRequestByName and GetProtoHTTPResponseByName signature helper functions for HTTP protocol inspection. v0.23.0 · Feb 2025 · source · release history
  • Introduces ArgVal signature helper function for building detection rules that inspect syscall arguments v0.21.0 · Jun 2024 · source · release history
  • signatures helpers are exposed as a Go module for external tooling integration. v0.20.0 · Feb 2024 · source · release history
  • signature name is exposed in the Event definition, allowing direct correlation of findings to signature rules. v0.20.0 · Feb 2024 · source · release history
  • Threat objects with name and properties are now embedded in events for richer threat context. v0.20.0 · Feb 2024 · source · release history
  • Adds support for multiple values to the --signatures-dir flag to load signature directories from multiple paths v0.18.0 · Oct 2023 · source · release history

example

  • Pass multiple signature directories to --signatures-dir to load rules from different paths. tracee --signatures-dir ./sig1 --signatures-dir ./sig2 v0.16.0 · Jul 2023 · source
  • Load custom rule files directly from a K8s entrypoint script without rebuilding the image. ./entrypoint.sh --custom-rules /path/to/rules/ v0.10.0 · Dec 2022 · source
CLI management interface (traceectl) verified suggested Provides a command-line interface for interacting with and controlling tracee, including server-mode operation. 12 releases · 5 other sources · first seen Nov 2020

Suggested capability: Process telemetry. This is our guess, not confirmed.

Also counts toward: Command-line interface

release 12 total

  • Adds traceectl, a new dedicated CLI tool bundled with Tracee for interacting with the Tracee service. v0.24.0 · Nov 2025 · source · release history
  • Introduces traceectl CLI tool alongside the main Tracee service v0.24.0 (2025-11-14) · Nov 2025 · source · release history
  • Adds baseline eBPF capability management, automatically computing required kernel capabilities. v0.22.0 · Aug 2024 · source · release history
  • Adds atomic level control for loggers via the --log-level flag with precise granularity v0.18.0 · Oct 2023 · source · release history
  • Enables k8s enrichment by default in the Helm chart. v0.15.0 · Jun 2023 · source · release history
  • Adds ARM64 architecture support via aarch64-0.13.0 Docker images and CI runners v0.13.0 · Apr 2023 · source · release history

command line

example

  • Pull the new aarch64 image for running Tracee on ARM-based hosts. docker pull docker.io/aquasec/tracee:aarch64-0.16.0 v0.16.0 · Jul 2023 · source
  • Start Tracee without dropping any capabilities at all, overriding the default behavior for environments where privilege loss causes errors. tracee --caps cancel-drop v0.8.2 · Sep 2022 · source
  • Run Tracee while keeping all original capabilities if one of the expected drops fails, useful for debugging permission issues on non-standard systems. tracee --caps allow-failed-drop v0.8.2 · Sep 2022 · source
Event streaming output formatting shipped Allows users to customize the format of streamed events using Go templates and supports epoch timestamping for precise temporal analysis. 10 releases · first seen Aug 2020

Also counts toward: Outbound webhooks (the product notifies you)

release 10 total

  • Makes epoch timestamps standard (feat(time)!: epoch timestamps as standard) replacing previous time format v0.23.0 (2025-02-19) · Feb 2025 · source · release history
  • Introduces epoch timestamps as the standard time format for all events. v0.23.0 · Feb 2025 · source · release history
  • Timestamps are now emitted in epoch format by default; any pipeline or parser expecting the previous time format will break on upgrade. v0.22.6 · Feb 2025 · source · release history
  • Epoch timestamps are now the standard for all events; integrations that relied on the previous timestamp format will receive differently formatted time values. v0.23.0 · Feb 2025 · source · release history
  • Adopts epoch timestamps as the standard time representation across all Tracee events. v0.22.6 · Feb 2025 · source · release history
  • Adds container image field to the table printer output v0.10.0 · Dec 2022 · source · release history
Advanced signature evaluation shipped Optimizes signature performance through partial evaluation, multiple runtime targets (OPA/WASM), and event origin filtering. 7 releases · 2 other sources · first seen Oct 2021

release 7 total

  • Adds a heartbeat event to signal that Tracee is alive and processing. v0.24.0 · Nov 2025 · source · release history
  • Enables signatures consuming other signatures in the analyze engine v0.23.0 (2025-02-19) · Feb 2025 · source · release history
  • Enables signatures to consume other signature findings in the analyze pipeline (chained detection logic). v0.23.0 · Feb 2025 · source · release history
  • Adds DataSource type support for signatures in tracee events. v0.15.0 · Jun 2023 · source · release history
  • Adds not-equal operator parsing to policy definitions. v0.15.0 · Jun 2023 · source · release history
  • Adds --partial-eval flag to tracee-rules to enable partial evaluation of signatures v0.6.2 · Oct 2021 · source · release history

example

  • Select the WASM target for Rego signature evaluation instead of the default OPA runtime. tracee-ebpf --rego-target wasm v0.6.2 · Oct 2021 · source
  • Enable partial evaluation to optimize tracee-rules by pre-computing static parts of Rego policies. tracee-rules --partial-eval v0.6.2 · Oct 2021 · source
Metrics and debug access shipped Exposes runtime metrics and debug data via HTTP for external monitoring and troubleshooting. 6 releases · 2 other sources · first seen Sep 2021

Also counts toward: gRPC API support

release

  • Adds EventCounts field to GetMetricsResponse in the gRPC API. v0.23.0 · Feb 2025 · source · release history
  • Adds a metric tracking perf event writes to monitor data flow through the performance events subsystem v0.22.5 · Dec 2024 · source · release history
  • Adds tracee_info event that emits metadata about the running Tracee instance. v0.22.0 · Aug 2024 · source · release history
  • Enables diagnostic checks via a new gRPC endpoint accessible through the diagnostic RPC service v0.18.0 · Oct 2023 · source · release history
  • Adds a new /healthz HTTP endpoint to both tracee-ebpf and tracee-rules services v0.8.3 · Sep 2022 · source · release history
  • Adds Prometheus support for exporting trace events as metrics v0.7.0 · Mar 2022 · source · release history

example

  • Verify the health status of the tracee-ebpf service via HTTP. curl http://localhost:3301/healthz v0.8.3 · Sep 2022 · source
  • Access metrics and debug data from the rules engine via HTTP. curl http://localhost:6060/debug/pprof/profile v0.6.1 · Sep 2021 · source
Network activity capture shipped Captures network-related events for security analysis and visibility into host communications. 7 releases · first seen Aug 2021

release 7 total

  • Adds full-payload packet capture event containing complete packet contents for all captured packets. v0.22.0 · Aug 2024 · source · release history
  • Adds packet capture context, enriching captured packets with process/container metadata. v0.22.0 · Aug 2024 · source · release history
  • net_flow_tcp_begin is a new event that captures the beginning of TCP connections for flow analysis. v0.20.0 · Feb 2024 · source · release history
  • Adds new network protocol event types for DNS, TCP, and UDP in the engine v0.10.0 · Dec 2022 · source · release history
  • Captures ICMP network traffic through net_packet eBPF events v0.8.0 · Jul 2022 · source · release history
  • Adds net_packet event for capturing network packet data v0.7.0 · Mar 2022 · source · release history
Event streaming verified suggested Streams live events from tracee to the CLI for real-time observation. 5 releases · 1 other source · first seen Jul 2020

Suggested capability: Process telemetry. This is our guess, not confirmed.

Also counts toward: Command-line interface, gRPC API support

release

  • packet metadata type introduces structured packet metadata into the event stream, replacing ad-hoc fields. v0.20.0 · Feb 2024 · source · release history
  • Adds an initial gRPC service (tracee-rpc) to support streaming events and remote diagnostics v0.18.0 · Oct 2023 · source · release history
  • Adds fluent_forward output option for syslog-compatible forwarding v0.12.0 · Mar 2023 · source · release history
  • Adds webhook printer for sending findings to HTTP webhooks v0.12.0 · Mar 2023 · source · release history
  • Adds --gob flag to enable gob output format v0.0.2 · Jul 2020 · source · release history

command line

File capture and inspection shipped Captures file read operations in userspace and allows filtering by ELF type. 3 releases · 1 other source · first seen Aug 2020

release

  • Enables filtering file capture by ELF type using the --filter-elf-type flag v0.18.0 · Oct 2023 · source · release history
  • Adds read capture capability for tracing file reads in userspace. v0.15.0 · Jun 2023 · source · release history
  • Enables saving writes to /dev/null by PID for targeted capture v0.0.3 · Aug 2020 · source · release history

example

  • Capture file read operations using the new read capture feature. tracee --capture read v0.15.0 · Jun 2023 · source
Container ID identification via UTS namespace shipped Identifies container IDs by utilizing the UTS namespace node name during tracing. 4 releases · first seen May 2020

Shared capability: Process telemetry

release

  • Updates docker images to include embedded eBPF CO-RE obj with BTFHUB support v0.7.0 · Mar 2022 · source · release history
  • Introduces cgroup ID-based container filtering to resolve container IDs more reliably than previous methods v0.6.5 · Dec 2021 · source · release history
  • Adds event origin signature filtering capability (Feature/event origin signature filter). v0.6.0 · Aug 2021 · source · release history
  • Adds container tracing capability by using UTS namespace node name to identify container ID v0.0.1 · May 2020 · source · release history
Post-hoc event analysis shipped Allows users to evaluate policy configurations against captured trace data in an offline or batch mode. 2 releases · 1 other source · first seen Jul 2023

Also counts toward: Command-line interface, Offline mode

release

  • Adds the analyze subcommand to perform post-hoc analysis of captured events v0.18.0 · Oct 2023 · source · release history
  • Adds the new tracee analyze subcommand for policy analysis workflows v0.16.0 · Jul 2023 · source · release history

example

  • Run the new analysis subcommand to evaluate policy configurations against trace data. tracee analyze --policy my_policy.yaml v0.16.0 · Jul 2023 · source
Application profiling mode shipped Enables performance monitoring and debugging of applications via pprof endpoints and dedicated profiler workflows. 3 releases · first seen Jun 2021

release

  • Enables pprof profiling endpoints on tracee-rules for performance monitoring. v0.6.1 · Sep 2021 · source · release history
  • Adds the --output ignore flag to tracee-ebpf to discard all event output. v0.6.1 · Sep 2021 · source · release history
  • feat: Tracee Profiler Mode is now available for application profiling workflows. v0.5.3 · Jun 2021 · source · release history
Chained detection logic shipped Enables signatures to consume and evaluate findings from other signatures within the analysis pipeline for complex threat detection. 2 releases · first seen Feb 2025

release

  • Enables signatures consuming other signatures in the analyze engine v0.23.0 (2025-02-19) · Feb 2025 · source · release history
  • Enables signatures to consume other signature findings in the analyze pipeline (chained detection logic). v0.23.0 · Feb 2025 · source · release history
Custom data source integration shipped Allows users to define and load custom event ingestion pipelines via a pluggable interface, extending the built-in event model. 1 release · 1 other source · first seen Feb 2024

Also counts toward: Plugin API support, Plugin system

release

  • ctime is added to the containers data source, providing container creation timestamps for auditing. v0.20.0 · Feb 2024 · source · release history

example

  • Configure pluggable data sources in your Tracee policy to add custom event ingestion pipelines. # In tracee-policy.yaml: # datasources: # my_custom_ds: # type: writeable # endpoint: tcp://localhost:9090 v0.20.0 · Feb 2024 · source
Event triggering verified Allows users to manually trigger events within tracee. 1 other source · first seen Nov 2025

command line

Outbound notification webhooks shipped Supports configuring webhook endpoints to send events or alerts externally. 1 release · first seen Jun 2024

Also counts toward: Outbound webhooks (the product notifies you)

release

  • Adds webhook configuration support in Helm chart values for outbound notifications v0.21.0 · Jun 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 Tracee, 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 Tracee 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 →

Website history

trivy.dev, every change

Aqua Security's home page and 3 more pages as they looked each month from December 2021 to October 2026: 19 renders, 6 changes of tagline or palette. Step through them, play them, or put any two months side by side.

Website history is included with Researcher and Business.

See plans →

Releases

Show

39 entries

  1. November 20252
  2. February 20253
  3. December 20241
  4. August 20241
  5. June 20241
  6. February 20241
  7. October 20231
  8. July 20231
  9. June 20231
  10. May 20232
  11. April 20231
  12. March 20231
  13. December 20221
  14. October 20221
  15. September 20222
  16. August 20221
  17. July 20221
  18. March 20221
  19. December 20211
  20. November 20211
  21. October 20212
  22. September 20211
  23. August 20211
  24. June 20212
  25. April 20211
  26. February 20211
  27. January 20211
  28. December 20201
  29. November 20201
  30. August 20201
  31. July 20201
  32. May 20201
    Show

    39 entries

    Project health

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

    1. Contributors 16 −4 vs prior 12 months
    2. Maintainers 3 +2 joined · −3 left, last 12 months
    3. Bus factor 2 committers behind half the commits
    4. Community-filed 49% of issues opened, last 12 months
    5. Median time to close 719 days first maintainer reply 32 hours
    6. Open backlog 111 of 1,627 issues ever filed
    1. Issues opened / month 0 · 0 communitymaintainers
    2. Open backlog 111
    3. Contributors / month 1
    4. Commits / month 1
    5. Stars 4,620
    Issue themes, last 12 months
    • bugs 63%
    • features 17%
    • docs 3%
    • other 17%

    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 →