Building safely

Sandbox

A fenced-off area where a program runs with limited access, so if it misbehaves it cannot touch the rest of the system.

In plain words

It is the sandbox in a playground: the child can dig and make a mess, but the mess stays inside the box.

When it affects you

Anyone who runs code they did not write: plugins, AI agent tools, customer scripts. A sandbox is only as strong as the software that builds the fence, and flaws in it can let code escape.

What to do today

  1. Treat every module or plugin you did not write as untrusted, even inside a sandbox.
  2. Keep the runtime that provides the sandbox updated.
  3. Give the process that runs outside code no access to your keys or production data.

← All termsNo. 24 / 32

Related on this site

News

Last reviewed: 2026-10-27. Written for non-experts. Check an advisory or your vendor for the details of a specific flaw.

Get the free runbooks

One-page security checklists for founders who build with AI. You get a confirmation email first, then the runbooks.

Send me the runbooks