Sandbox (computer security)

In computer security, a sandbox is a security mechanism for separating running programs. It is often used to execute untested or untrusted programs or code, possibly from unverified or untrusted third parties, suppliers, users or websites, without risking harm to the host machine or operating system.^[1] A sandbox typically provides a tightly controlled set of resources for guest programs to run in, such as scratch space on disk and memory. Network access, the ability to inspect the host system or read from input devices are usually disallowed or heavily restricted.

In the sense of providing a highly controlled environment, sandboxes may be seen as a specific example of virtualization. Sandboxing is frequently used to test unverified programs that may contain a virus or other malicious code, without allowing the software to harm the host device.^[2]

Implementations

A sandbox is implemented by executing the software in a restricted operating system environment, thus controlling the resources (for example, file descriptors, memory, file system space, etc.) that a process may use.^[3]

Examples of sandbox implementations include the following:

• A jail: network-access restrictions, and a restricted filesystem namespace. Jails are most commonly used in virtual hosting.^[4]
• Rule-based execution gives users full control over what processes are started, spawned (by other applications), or allowed to inject code into other applications and have access to the net, by having the system assign access levels for users or programs according to a set of determined rules.^[5] It also can control file/registry security (what programs can read and write to the file system/registry). In such an environment, viruses and trojans have fewer opportunities of infecting a computer. The SELinux and Apparmor security frameworks are two such implementations for Linux.
• Virtual machines emulate a complete host computer, on which a conventional operating system may boot and run as on actual hardware. The guest operating system runs sandboxed in the sense that it does not function natively on the host and can only access host resources through the emulator.
• Sandboxing on native hosts: Security researchers rely heavily on sandboxing technologies to analyse malware behaviour. By creating an environment that mimics or replicates the targeted desktops, researchers can evaluate how malware infects and compromises a target host. Numerous malware analysis services are based on the sandboxing technology.^[6]
• Capability systems can be thought of as a fine-grained sandboxing mechanism, in which programs are given opaque tokens when spawned and have the ability to do specific things based on what tokens they hold. Capability-based implementations can work at various levels, from kernel to user-space. An example of capability-based user-level sandboxing involves HTML rendering in a Web browser.
• Secure Computing Mode (seccomp) is a sandbox built in the Linux kernel. When activated, seccomp only allows the write(), read(), exit(), and sigreturn() system calls.
• HTML5 has a "sandbox" attribute for use with iframes.^[7]
• Java virtual machines include a sandbox to restrict the actions of untrusted code, such as a Java applet.
• The .NET Common Language Runtime provides Code Access Security to enforce restrictions on untrusted code.

Some of the use cases for sandboxes include the following:

• Online judge systems to test programs in programming contests.
• New-generation pastebins allowing users to execute pasted code snippets on the pastebin's server.

See also

• Sandboxie

References

External links

• Security In-Depth for Linux Software: Preventing and Mitigating Security Bugs
• Sandbox – The Chromium Projects
• FreeBSD capsicum(4) man page – a lightweight OS capability and sandbox framework
• OpenBSD pledge(2) man page – a way to restrict system operations