# Secrets, egress and blast radius

Keep credentials away from agents, limit where they can connect, and contain mistakes.

## Pages

- [Give your agent its own computer, not SSH to production](https://sanbox.cloud/kb/security/agent-own-computer-not-ssh-to-production.md): Don't give a coding agent a shell on production. Give it a Computer with staging-only credentials, deny-by-default egress and a snapshot, and review its diff before you deploy.
- [How do I give an AI agent API keys without exposing them?](https://sanbox.cloud/kb/security/api-keys-your-agent-cannot-see.md): Keep the key off the agent's machine. A Secret Proxy stores it and adds it to matching HTTPS requests on the way out, so the agent can call the API but never read the key.
- [How do I restrict which domains an AI agent can reach?](https://sanbox.cloud/kb/security/restrict-which-domains-an-agent-can-reach.md): Use a deny-by-default egress allowlist. On Sanbox, a template's network policy lists the hosts and ports its Computers may reach; a blocked request names the host.
- [How do I use --dangerously-skip-permissions in a disposable computer?](https://sanbox.cloud/kb/security/snapshot-before-skip-permissions.md): Run it in a disposable Computer: snapshot the stopped Computer, run Claude Code with --dangerously-skip-permissions, review the diff, and start fresh from the snapshot if needed.