Sandbox (computer security)

From Wikipedia, the free encyclopedia
Jump to: navigation, search

In computer security, a sandbox is a security mechanism for separating running programs. It is often used to execute untested code, or untrusted programs from unverified third-parties, suppliers, untrusted users and untrusted websites.[1]

The 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 this sense, sandboxes are a specific example of virtualization.

Sandboxing technology is frequently used to test unverified programs which may contain a virus or other malignant code, without allowing the software to harm the host device.[2]

Examples[edit]

Examples of sandboxes include:

  • A jail: network-access restrictions, and a restricted filesystem namespace.[3] Jails are most commonly used in virtual hosting.
  • Rule-based Execution gives users full control over what processes are started, spawned (by other applications), or allowed to inject code into other apps and have access to the net- by having the system assign access levels for users or programs according to a set of determined rules.[4] It also can control file/registry security (what programs can read and write to the file system/registry). In such an environment losers, 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. Cuckoo Sandbox is an open source tool that automates malware analysis.[5][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.
  • Online judge systems to test programs in programming contests.
  • New-generation pastebins allowing users to execute pasted code snippets.
  • 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]

References[edit]

  1. ^ Ian Goldberg, David Wagner, Randi Thomas, and Eric Brewer (1996). "A Secure Environment for Untrusted Helper Applications (Confining the Wily Hacker)". Proceedings of the Sixth USENIX UNIX Security Symposium. Retrieved 25 October 2011. 
  2. ^ http://www.techhive.com/article/247416/how_to_keep_your_pc_safe_with_sandboxing.html
  3. ^ "Sandboxing Applications". 2001. Retrieved 7 May 2013. 
  4. ^ "Computer System Security and Access Controls". 1991. Retrieved 17 May 2013. 
  5. ^ "Cuckoo, what it is". Retrieved 2014-01-21. 
  6. ^ Jurriaan Bremer, Claudio Guarnieri, Mark Schloesser (August 1, 2013). [url=https://media.blackhat.com/us-13/US-13-Bremer-Mo-Malware-Mo-Problems-Cuckoo-Sandbox-WP.pdf "Mo' Malware, Mo' Problems - Cuckoo Sandbox to the Rescue"]. Black hat USA 2013. Pompeian room, Caesars Place, Las Vegas, NV. Retrieved 2014-01-21. 
  7. ^ http://blogs.msdn.com/b/ie/archive/2011/07/14/defense-in-depth-locking-down-mash-ups-with-html5-sandbox.aspx, IEBlog

External links[edit]