📦 What is Sandboxing?

Sandboxing is a security technique where code runs in an isolated, restricted environment — a "sandbox" — that limits what it can access and what damage it can do. Think of it like a real sandpit at a playground: children can play freely inside the sandpit, but the walls keep the sand contained. The mess stays in the pit, not all over the park.

In software, sandboxing means: even if the code is malicious, buggy, or compromised, it cannot escape its container to affect the rest of the system. It cannot read other files, access other programs, or damage the operating system.

📖 Everyday Examples of Sandboxing (You Use These Daily)

Example	How It Sandboxes	What It Prevents
Chrome browser tabs	Each tab runs as a separate, isolated process with its own memory space. One tab cannot read another tab's data.	A malicious website in one tab cannot steal your banking session cookie from another tab. If one tab crashes, others keep working.
iPhone / Android apps	Each app has its own isolated storage area. Apps must request explicit permission to access camera, contacts, location, etc.	A dodgy game app cannot secretly read your text messages, banking app data, or photos without your explicit permission.
Docker containers	Server applications run in lightweight containers with isolated filesystems, network, and processes.	If a hacker exploits a vulnerability in the web server container, they are trapped inside it. They cannot access the database container or the host machine.
Virtual machines (VMs)	An entire operating system runs inside another operating system. Complete isolation at the hardware level.	Security researchers run malware inside VMs to study it safely. The malware cannot escape the VM to infect the host computer.
JavaScript in browsers	JavaScript runs in a sandboxed environment. It cannot access your filesystem, run system commands, or interact with other websites.	A script on a website cannot delete your files, install software, or read data from other websites (Same-Origin Policy).