Reading room / Boundaries
A boundary around a program
A sandbox gives a program a restricted or isolated environment. Its purpose is to limit how activity inside that environment can affect the surrounding system.
General educational information
Boundaries take different forms
Some sandboxes restrict particular capabilities. Others use a separate virtualized environment. The details determine which files, devices and system resources a program can reach. A temporary desktop is one example of isolation, rather than a definition of every sandbox.
A hypothetical example
Imagine opening a sample document inside a disposable environment. Changes to its private files might disappear when the environment closes. If a writable folder from the host is shared into it, changes to that shared folder may remain. The location of the file matters.
Look at the connections
Network access, clipboard sharing and mapped folders are important parts of the boundary. Microsoft’s Windows Sandbox documentation describes these as configurable features. Isolation does not automatically mean that a program has no network connection or no route to shared information.
Containment is a layer
A sandbox is useful only in relation to its configuration and the behavior being considered. It does not prove that a file is harmless. A practical reading question is: what can cross this boundary, in which direction, and with what permissions? That question keeps attention on the actual separation rather than the reassuring name. Different implementations can give very different answers even when both are described as sandboxes.
Further reading: Microsoft: Windows Sandbox configuration.