endorlabs.comarticleA vendor blog primer (Endor Labs) that walks through the main families of sandboxing technology - VMs (Firecracker), shared-kernel containers (namespaces, cgroups, seccomp, runc), userspace-kernel middle grounds (gVisor, Kata Containers), and language/runtime sandboxes (Java SecurityManager, V8 isolates, WebAssembly/WASI) - explaining what each actually isolates, its cost, and known escape CVEs (VENOM/CVE-2015-3456, runc's CVE-2019-5736, Spectre/Meltdown). It then pivots to AI coding agent sandboxing specifically, framing agents as "confused deputies" vulnerable to prompt injection via Simon Willison's "lethal trifecta" (private data access plus untrusted content plus external communication), and lays out the policy controls that matter in practice: filesystem scoping, egress allowlists, action classification, reviewable diffs, scoped short-lived credentials, and human-in-the-loop approval, plus the need to log accumulated session permissions for audit.
DockerFirecrackergVisor+7
CVE-2015-3456CVE-2019-5736Simon Willison+1
ai-infra, coding-agents· Published and added 2 Oct 2026