Individual skill

implementing-ebpf-security-monitoring

Implements eBPF-based security monitoring using Cilium Tetragon for real-time process execution tracking, network connection observability, file access auditing, and runtime enforcement. Covers TracingPolicy CRD authoring with kprobe/tracepoint hooks, in-kernel filtering via matchArgs/matchBinaries selectors, JSON event export, and integration with SIEM pipelines. Use when building kernel-level runtime security observability for Linux hosts or Kubernetes clusters.

internal/tools/skills/data/security-operations/implementing-ebpf-security-monitoring/SKILL.md

Read pinned source

Source commit d42f381ad34843e71a42658e5c57290c713e85af

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Network or broad shell
Last checked
Nov 9, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
1,329
Repository last updated
Nov 9, 2026
License
Apache-2.0

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Implementing eBPF Security Monitoring

## When to Use

- When deploying kernel-level runtime security monitoring on Linux hosts or Kubernetes clusters
- When you need sub-millisecond visibility into process execution, network connections, and file access
- When traditional userspace monitoring tools introduce unacceptable performance overhead
- When building detection pipelines that require in-kernel filtering before events reach userspace
- When enforcing runtime security policies (kill process, send signal) at the kernel level

## Common Misconfigurations & Verification

- **No BTF = silent no-load:** Tetragon needs kernel BTF (`/sys/kernel/btf/vmlinux`) or a matching external BTF for kprobe arg typing. On older/stripped kernels (no `CONFIG_DEBUG_INFO_BTF`) probes fail to attach and you get zero kprobe events while `process_exec` still flows — masking the gap. Verify `ls /sys/kernel/btf/vmlinux` and check `kubectl logs -n kube-system -l app.kubernetes.io/name=tetragon` for attach errors.
- **Ring-buffer/event drops under load:** high event volume overflows the perf/ring buffer and Tetragon drops events — a coverage hole that looks like "nothing happened." Watch `tetragon_*_events_total` and missed/`map_errors` metrics, scope policies with in-kernel `matchArgs`/`matchBinaries` selectors (filter in-kernel, not in userspace), and avoid an unfiltered `tcp_connect` Post on a busy host.
Back to top