Skip to main content
Definition Website Computer and Technology

Sandbox

Subject: Computer and Technology noun /ˈsænd.bɑːks/ 1 definition

  1. Definition (noun)

    Entry #154 · Updated

    A Sandbox is a tightly controlled, isolated execution environment that separates running programs, untrusted code, or experimental changes from the underlying host system. By enforcing strict privilege boundaries—restricting file system access, network communication, system calls, and hardware interaction—it ensures that software faults, exploits, or malicious payloads remain contained within disposable boundaries rather than compromising production data or host infrastructure. Commonly deployed across web browsers, operating systems, virtualization layers, and testing pipelines, a sandbox applies the principle of least privilege so code receives only the minimal capabilities required for its intended task.

    Common Types

    • Application and Browser Sandboxes: Confine untrusted web scripts, plugins, or mobile apps inside restricted runtime processes—such as Chromium's multi-process renderer or a WebAssembly runtime—blocking direct access to local files, OS APIs, and cross-origin data.

    • OS-Level Sandboxes: Isolate processes directly on a shared host kernel using operating system primitives like Linux namespaces, cgroups, seccomp-bpf system-call filtering, or macOS App Sandbox entitlements to restrict filesystem paths, network sockets, and privileges.

    • Hardware-Virtualized Sandboxes: Execute untrusted binaries or suspected malware inside dedicated virtual machines or microVMs (such as Firecracker or QEMU) backed by CPU virtualization extensions, establishing a strong hypervisor boundary separate from the host kernel.

    • Development and Testing Sandboxes: Provide replica staging environments—mirroring production APIs, payment gateways, or database schemas with synthetic data—where engineers can safely validate integrations and reproduce bugs without affecting live users or billing systems.

    Example

    When a security analyst opens a suspicious PDF attachment inside a Firecracker microVM sandbox, the guest operating system allows the document's embedded exploit to execute and attempt outbound connections while logging its system activity. Because the sandbox confines the guest memory, virtual disk, and simulated network interface behind a hardware hypervisor boundary, the malware cannot reach the host workstation and is completely discarded once the microVM terminates.