Kubernetes Escape & eBPF Range
A vulnerable-versus-hardened Kubernetes range for container escape, sidecar injection, metadata theft, and kernel-level enforcement.
- Role
- Solo build — research, engineering, documentation, release
- Status
- Planned · frontier build
- Year
- 2026
- Position
- 12 of 13
01 — Context
The problem worth solving.
Container security controls should be tested against a complete exploit chain, from application compromise to cloud identity.
02 — Approach
How it was built.
- 01
Model service-account pivoting, privileged pod escape, and cloud IAM movement.
- 02
Pair each chain with Cilium/Tetragon runtime enforcement.
- 03
Measure the syscall-level control response.
03 — Architecture
The shape of the system.
Microservices with deliberately weak isolation and identity boundaries.
Application compromise through token pivot, escape, and IAM movement.
eBPF policy enforcement and telemetry at the kernel boundary.
04 — Evidence
Receipts, not adjectives.
05 — Hiring signal
“Demonstrates cloud-native security from workload identity down to syscalls.”
06 — What's next
Still being built.
Deploy the vulnerable range and validate the first escape chain.