Oleg Šelajev - You're absolutely right, it was your home directory! - AI Native DevCon June 2026

Published 2026-07-25 · Duration 33:15

Summary

The session addresses the security risks posed by autonomous AI agents running locally, noting that these agents can pose significant threats by accessing sensitive data and executing arbitrary code. To mitigate this risk, Docker introduces sandboxing using MicroVMs—a hardware-level isolation primitive superior to traditional containers. This approach allows developers to run powerful AI agents in a restricted environment with controlled access to the filesystem, network, and secrets, enabling high productivity without sacrificing security.

Download summary

Key takeaways

The Danger of Autonomous Agents 2:00
AI agents are highly autonomous and persistent; if given sufficient access (data, external communication, internet), they can execute malicious actions like stealing SSH keys or cloud credentials, leading to massive security incidents. The stakes are asymmetric: the attacker only needs to succeed once.
MicroVMs for Hard Isolation 6:00
Traditional containers share a kernel and are insufficient for high-stakes AI agent sandboxing due to potential container escaping exploits. Docker's solution uses MicroVMs, providing hardware-level isolation that significantly raises the security boundary.
The Role of Kits (YAML) 10:00
To improve developer experience in isolated environments, 'Kits' are introduced. These declarative YAML files define reusable configurations for a sandbox, specifying required commands, tools (e.g., programming language toolchains), file placements, and network rules.
Controlled Access Mechanisms 8:00
Sandboxes implement critical controls including networking proxies (to block specific domains/services) and secrets injection mechanisms, allowing agents to function without direct access to the host machine's private data.

Technical details

AI Agent Security Risks 120s
Agents can exploit vulnerabilities by installing malicious dependencies (e.g., via Python) or performing prompt injections, leading to unauthorized access of secrets and credentials.
Container vs. MicroVM Isolation 360s
Containers are ideal for immutable software but fail when an agent needs to actively change its environment (install tools). MicroVMs provide the necessary hardware-level isolation boundary that security teams require.
SBX Sandbox Workflow 720s
The `SBX run` command executes agents (e.g., Claude, Gemini) within a fully isolated MicroVM environment. This sandbox can run tests and build projects while enforcing network policies and limiting file system access.
Sandbox Configuration with Kits 600s
Kits are YAML-defined artifacts that manage the setup of a sandbox by defining commands (e.g., `install Tessel`), environment variables, network rules, and secure credential swaps.

Mentioned resources

SBX (CLI Tool)
The AI Native Dev Podcast (Podcast)
Docker Documentation (Documentation)

Channel & topics

Watch on YouTube · Back to latest

This independent, AI-assisted summary is provided for commentary and informational purposes. It may contain errors or omit important context. Please watch the original video for the creator's complete presentation. Video, thumbnail, and related copyrights belong to their respective owners.