Session

Clearing the Runtime Confusion: Which Agent Runtime Is the GOAT?

You've probably heard that containers aren't the most secure boundary for an agent. You keep hearing about microVMs and gVisor, but microVMs cost the most and containers are the Kubernetes default. What do microVMs actually stop that containers don't?

In this session we run Claude Code in agent-sandbox on each runtime and replay the public coding-agent escapes of 2026/2027:

Config-file hooks (Cymulate)
Symlinks (Wiz GhostApproval)
A Docker socket and allowlisted git (Pillar Security)
DNS tunneling (AWS AgentCore)
Plus new ones that have arisen since Q4 of 2026

Patched kernel and runtime CVEs that go through the boundary instead of around it run alongside. A live scoreboard shows which runtime stopped, detected or missed each attack, first alone, then with Kyverno, Cilium FQDN egress and Falco added.

For platform and security engineers choosing a substrate for coding agents. Attendees leave with the harness, SandboxTemplates and raw results to rerun on their own clusters.

Michael Rishi Forrester

Forward deployed engineer training and enterprise AI adoption

Atlanta, Georgia, United States

Actions

Please note that Sessionize is not responsible for the accuracy or validity of the data provided by speakers. If you suspect this profile to be fake or spam, please let us know.

Jump to top