Learning outcomes
- Explain the operating model behind Tool Sandboxing and Egress Control.
- Evaluate trade-offs and failure modes for Tool Sandboxing and Egress Control.
- Apply Tool Sandboxing and Egress Control to a production decision.
Mental model
A sandbox limits what compromised or mistaken execution can reach; egress policy limits where observed data can leave.
Learning outcomes
- Explain the mechanism and ownership boundaries behind Tool Sandboxing and Egress Control.
- Compare the main design alternatives and their operational trade-offs.
- Diagnose common failures and select evidence for a production decision.
Theory
Combine least-privilege identities, disposable environments, read-only inputs, allowlisted outputs, network destinations, resource quotas, syscall controls, and teardown verification. Treat sandbox escape and credential access as separate risks.
Trade-offs
Stronger isolation reduces blast radius but limits tool compatibility and adds startup cost. Network allowlists block exfiltration but require explicit dependency management.
Failure modes and misconceptions
Calling a container a sandbox; mounting host credentials; allowing unrestricted DNS or HTTPS; writable shared volumes; no CPU or memory limits; and trusting cleanup alone.
Decision scenario
A code agent must run an unknown repository's tests. Design the filesystem, secret, network, process, and artifact boundaries.
Why does blocking inbound traffic not prevent a sandboxed tool from exfiltrating data?
Primary sources
owasp-llmnist-zero-trust
Evidence assessment
Theory and decision mastery
Decision scenario
A production team must adopt Tool Sandboxing and Egress Control while meeting quality, latency, security, and operating constraints.
Which decision process is most defensible?
Relationships
Tool Sandboxing and Egress Control builds on Security and Privacy for LLM Systems.
Tool Sandboxing and Egress Control informs governed production decisions and review evidence.
Primary sources
- OWASP Top 10 for LLM Applications — OWASP, verified 2026-07-16
- Zero Trust Architecture — NIST, verified 2026-07-21