By Vero SecurityBuilt and funded by Vero Security, the AI Security Engineering platform.Read the charter

Sandboxing and egress control

A sandbox limits what an agent can touch even after it has been tricked: which directories it can write and which hosts it can reach. Filesystem isolation stops tampering with credentials and config, while network allow lists stop quiet exfiltration. Pair OS-level sandboxes or dev containers with an egress proxy so approvals become the exception instead of the norm.

Read in this order

  1. ArticleMaking Claude Code safer with sandboxing (Anthropic)Start here: why filesystem and network isolation work together.
  2. Open sourcesandbox-runtime (Anthropic, open source)Hands on: run a harmless process under file and network limits, then compare what gets denied.
  3. ArticlePrompt injection to RCE in AI agents (Trail of Bits)Real attacks that a sandbox would have contained.

Save your progress

We email you a sign-in link. No password.

By signing in you agree to the terms. The privacy policy explains how we use your details.

Join the AI security engineering community

Free. Roadmap updates, chapters near you, and first word when credentials open.

We’ll email you community updates. Unsubscribe anytime. By sending this you agree to the terms. The privacy policy explains how we use your details.