Sandbox (computer security)

In computer security, a sandbox is a security mechanism for separating running programs, usually in an effort to mitigate system failures or software vulnerabilities from spreading. 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 storage and memory scratch space. Network access, the ability to inspect the host system or read from input devices are usually disallowed or heavily restricted.

This article is about the computer security mechanism. For the software testing environment, see Sandbox (software development).

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:

  • Linux application sandboxing, built on Seccomp, cgroups and Linux namespaces. Notably used by Systemd, Google Chrome, Firefox, firejail.
  • Google Sandboxed API[4]
  • A jail: network-access restrictions, and a restricted file system namespace. Jails are most commonly used in virtual hosting.[5]
  • 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.[6] 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 negatively 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 behavior. 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.[7]
  • Native Client is a sandbox for running compiled C and C++ code in the browser efficiently and securely, independent of the user’s operating system.[8]
  • 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 in strict mode, seccomp only allows the write(), read(), exit(), and sigreturn() system calls.
  • HTML5 has a "sandbox" attribute for use with iframes.[9]
  • 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.
  • Software Fault Isolation (SFI),[10] allows running untrusted native code by sandboxing all store, read and jump assembly instructions to isolated segments of memory.
  • Windows Vista and later editions include a "low" mode process running, known as "User Account Control" (UAC), which only allows writing in a specific directory and registry keys. Windows 10, from version 1903 (released May 2019), provides a feature known as "Windows Sandbox: an isolated, temporary, desktop environment where you can run untrusted software without the fear of lasting impact to your PC". [11]

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.
gollark: What about it?
gollark: It's *just* a general suggestion to not add excessive things to your explanation for no reason.
gollark: By default we (should) basically just treat a new proposition as false, while remembering that we don't actually *know* and that new evidence might become available.
gollark: It's a Martian camouflage field.
gollark: By default, it's "don't know but you should probably say it isn't".

See also

References
  1. Ian Goldberg; David Wagner; Randi Thomas & Eric Brewer (1996). "A Secure Environment for Untrusted Helper Applications (Confining the Wily Hacker)" (PDF). Proceedings of the Sixth USENIX UNIX Security Symposium. Retrieved 25 October 2011.
  2. Geier, Eric (2012-01-16). "How to Keep Your PC Safe With Sandboxing". TechHive. Retrieved 2014-07-03.
  3. "Sandboxing Applications" (PDF). 2001. Retrieved 7 May 2013.
  4. Sandboxed API
  5. "Auto-Sandboxing secure system". Retrieved 2015-01-30.
  6. "Computer System Security and Access Controls". 1991. Archived from the original on 28 May 2013. Retrieved 17 May 2013.
  7. "Native Client Sandbox – Untrusted x86 Native Code" (PDF). Retrieved 2015-01-03.
  8. Welcome to Native Client
  9. Internet Explorer Team Blog. "Defense in Depth: Locking Down Mash-Ups with HTML5 Sandbox". IEBlog.
  10. Wahbe, Robert (1993). "Efficient Software-Based Fault Isolation" (PDF).
  11. "Windows Sandbox". 2018-12-18. Retrieved 2010-01-07.
This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.