Cyber Risks · Trail of Bits Blog

Pitfalls of relying on eBPF for security monitoring (and some solutions)

Summary: Trail of Bits reports that eBPF, now the de facto Linux standard for security monitoring and endpoint observability, was built as a networking and debugging tool and the kernel does not guarantee its probes will fire as expected. The post catalogs the resulting pitfalls: a 512-byte stack limit, a 4,096-instruction program cap, no concurrency primitives or reliable locking, event overload at attach points, and page faults that block access to paged-out memory.

Bottom line: Tools like Falco, Sysdig, Cilium and Pixie are being used for security monitoring on a platform whose probes can silently miss events, so any detection stack built on eBPF has to be designed to handle missing and corrupted data rather than assume the kernel always delivers.

Read the original at Trail of Bits Blog ↗