{"id":170815,"date":"2011-09-19T06:30:54","date_gmt":"2011-09-19T06:30:54","guid":{"rendered":"https:\/\/www.microsoft.com\/en-us\/research\/project\/drawbridge\/"},"modified":"2019-08-19T15:13:19","modified_gmt":"2019-08-19T22:13:19","slug":"drawbridge","status":"publish","type":"msr-project","link":"https:\/\/www.microsoft.com\/en-us\/research\/project\/drawbridge\/","title":{"rendered":"Drawbridge"},"content":{"rendered":"

Drawbridge is a research prototype of a new form of virtualization for application sandboxing. Drawbridge combines two core technologies: First, a picoprocess, which is a process-based isolation container with a minimal kernel API surface. Second, a library OS, which is a version of Windows enlightened to run efficiently within a picoprocess.<\/p>\n

\"Library

A Windows Library OS in context<\/p><\/div>\n

<\/span><\/span>Hardware-based Virtual Machines (VMs) have fundamentally changed computing in data centers and enabled the cloud. VMs offer three compelling qualities:<\/p>\n

    \n
  1. Secure Isolation<\/b>: isolating applications so that an ill-behaved application can’t compromise other applications or its host.<\/li>\n
  2. Persistent Compatibility<\/b>: allowing host and application to evolve separately. Changes in the host don’t break applications.<\/li>\n
  3. Execution Continuity<\/b>: allowing applications to be freed of ties to a specific host computer. A running application isn’t tied to the computer on which it was started, but can be moved from computer to computer across space and time within a single run.<\/li>\n<\/ol>\n

    Despite these advantages, VMs have large resource overheads in terms of disk footprint, memory, CPU, and administrative costs.<\/p>\n

    Drawbridge combines two ideas from the literature, the picoprocess<\/em> and the library OS<\/em>, to provide a new form of computing, which retains the benefits of secure isolation, persistent compatibility, and execution continuity, but with drastically lower resource overheads.<\/p>\n

    While still an experiment, Drawbridge runs many existing Windows applications without modifications ranging from desktop applications like\u00a0Microsoft Office 2010 and Internet Explorer to server applications like IIS.<\/p>\n

    The Picoprocess<\/h2>\n
    \"Picoprocess\"

    The Picopress isolation container<\/p><\/div>\n

    The Drawbridge picoprocess is a lightweight, secure isolation container. It is built from an OS process address space, but with all traditional OS services removed. The application binary interface (ABI) between code running in the picoprocess and the OS follows the design patterns of hardware VMs; it consists of a closed set of 45 downcalls with fixed semantics that provide a stateless interface. All ABI calls are serviced by the security monitor, which plays a role similar to the hypervisor or VM monitor in traditional hardware VM designs.<\/p>\n

    While the Drawbridge picoprocess interface follows the design patterns of hardware VM interfaces, it uses a high level of abstraction. The Drawbridge picoprocess interface surfaces threads, private virtual memory, and I\/O streams instead of low-level hardware abstractions like CPUs, MMUs, and device registers. These higher-level abstractions allow for much more efficient implementations of OS code hosted within the picoprocess. These higher-level abstractions also allow for much more efficient resource utilization.<\/p>\n

    The Library OS<\/h2>\n

    A better sandbox container is a necessary, but not sufficient condition for greater scalability of virtualized applications. The key second ingredient is the library OS. A library OS is an operating system refactored to run as a set of libraries within the context of an application.<\/p>\n

    While Drawbridge can run many possible library OSes, a key contribution of Drawbridge is a version of Windows that has been enlightened to run within a single Drawbridge picoprocess. The Drawbridge Windows library OS consists of a user-mode NT kernel–informally referred to as NTUM–which runs within the picoprocess. NTUM provides the same NT API as the traditional NT kernel that runs on bare hardware and in hardware VMs, but is much smaller as it uses the higher-level abstractions exposed by the Drawbridge ABI. In addition to NTUM, Drawbridge includes a version of the Win32 subsystem that runs as a user-mode library within the picoprocess.<\/p>\n

    Upon the base services of NTUM and the user-mode Win32 subsystem, Drawbridge can run many of the DLLs and services from the hardware-based versions of Windows. As a result, the Drawbridge prototype can run large classes of Windows desktop and server applications with no modifications to the applications.<\/p>\n

    Presentations<\/h2>\n