Knob
Network egress
You might say: outbound access, network allowlist, exit policy
The destinations and protocols a runner may reach outside its boundary. A policy can block all traffic, allow a short list, or route requests through a controlled proxy.
- What it does
- Reduces the paths a compromised task can use to fetch payloads or send data away.
- Ask
- Which exact hosts must this task reach, and what happens to every other destination?
- Typical
- Prefer deny-all or a narrow domain or CIDR allowlist. Add package registries and source hosts only when the task needs them.
- Trouble
- The task cannot fetch a required dependency, reaches an unexpected host, or uses a broad route to exfiltrate data.
What to look for
- An allowlist of hostnames in the runner or proxy settings
- A proxy or firewall decision in the run log
- A blocked outbound request with its host named
Connections
- See also: Prompt injection
- See also: Secrets
Sources
- Anthropic, Configure the sandboxed Bash tool, What the sandbox restricts
Network | No direct route out. Connections go through a proxy on your machine that checks each host against your allowed domains, which start empty.
- OpenAI, OpenAI-hosted sandboxes, Control network access
restricted | Allow only the hosts listed in `allowed_domains`.
- Daytona, Isolation, Network isolation
each sandbox can be locked down further with one of three mutually exclusive settings: block all traffic, allow specific CIDR ranges, or allow specific domains.
Use it on your project
teardown-apply: hold "Network egress" (network-egress) from the teardown at https://teardownatlas.com/software-factory/ against my project
Paste it into a coding agent that has the teardown skills.
An AI agent wrote this map with the teardown skill. It can contain errors: check the sources before you rely on a part. About and legal