Skip to content
AS
12 / Security Engineering2026

Kubernetes Escape & eBPF Range

A vulnerable-versus-hardened Kubernetes range for container escape, sidecar injection, metadata theft, and kernel-level enforcement.

KuberneteseBPFTetragonLinux kernel
Case file
Role
Solo build — research, engineering, documentation, release
Status
Planned · frontier build
Year
2026
Position
12 of 13
Case 12 / k8s-ebpf-escape-labArchitecture · Evidence · Signal

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.

  1. 01

    Model service-account pivoting, privileged pod escape, and cloud IAM movement.

  2. 02

    Pair each chain with Cilium/Tetragon runtime enforcement.

  3. 03

    Measure the syscall-level control response.

03 — Architecture

The shape of the system.

01Workload

Microservices with deliberately weak isolation and identity boundaries.

02Chain

Application compromise through token pivot, escape, and IAM movement.

03Control

eBPF policy enforcement and telemetry at the kernel boundary.

04 — Evidence

Receipts, not adjectives.

eBPFruntime layer
K8starget platform
IAMcloud pivot

05 — Hiring signal

“Demonstrates cloud-native security from workload identity down to syscalls.”

Ships working systemsDocuments the methodExplains the trade-offsKeeps evidence attached

06 — What's next

Still being built.

Deploy the vulnerable range and validate the first escape chain.