Applications running in different security domains
|Developer||Invisible Things Lab|
|Source model||Open source (except for Windows Support Tools)|
|Initial release||September 3, 2012|
|Latest release||2.0 / September 26, 2014|
|Update method||Yum (PackageKit)|
|Package manager||RPM Package Manager|
|Kernel type||Hybrid (Xen and Linux)|
|Default user interface||KDE|
|License||Free software licenses
On February 16, 2014, Qubes was selected as a finalist of Access Innovation Prize 2014 for Endpoint Security Solution.
Qubes Release 2 can also run Windows AppVMs in seamless mode, integrated onto the common Qubes trusted desktop, just like Linux AppVMs. The seamless GUI integration has been introduced in Qubes R2 Beta 3.
Qubes implements a Security by Isolation approach. The assumption is that there can be no perfect, bug-free desktop environment. Such an environment counts millions of lines of code, billions of software/hardware interactions. One critical bug in any of these interactions may be enough for malicious software to take control over a machine.
In order to secure a desktop, a Qubes user should take care of isolating various environments, so that if one of the components get compromised, the malicious software would get access to only the data inside that environment.
In Qubes, the isolation is provided in two dimensions: hardware controllers are isolated into functional domains (GUI, network and storage domains), whereas the user's digital life is decided in domains with different levels of trust. For instance: work domain (most trusted), shopping domain, random domain (less trusted). Each of those domains is run in a separate virtual machine.
Qubes is not a multi-user system.
System architecture overview
Xen hypervisor and administrative domain (Dom0)
The hypervisor provides isolation between different virtual machines. The administrative domain, also referred to as Dom0, has direct access to hardware. Dom0 hosts the GUI domain and controls the graphics device, as well as input devices, such as keyboard and mouse. The GUI domain runs the X server which displays the user desktop, and the window manager that allows to start and stop the applications and manipulate their windows.
Integration of the different virtual machines is provided by the Application Viewer, which provides an illusion for the user that applications execute natively on the desktop, while in fact they are hosted (and isolated) in different virtual machines. Qubes integrates all these virtual machines onto one common desktop environment.
Because Dom0 is security-sensitive, it is isolated from the network. It tends to have as little interface and communication with other domains as possible in order to minimize the possibility of an attack originating from an infected virtual machine.
The network domain
The network mechanism is the most exposed to security attacks. This is why it is isolated in a separate, unprivileged virtual machine, called the Network Domain.
The storage domain
Disk space is saved thanks to the fact that various virtual machines (VM) share the same root file system in a read-only mode. Separate disk storage is only used for userʼs directory and per-VM settings. This allows to centralize software installation and updates. Of course, some software can be installed only on a specific VM.
Cryptography is used to protect the filesystems, so that the storage domain cannot read confidential data owned by other domains.
Application Virtual Machines (AppVM)
AppVMs are the virtual machines used for hosting user applications, such as a web browser, an e-mail client or a text editor. For security purpose, these applications can be grouped in different domains, such as “personal”, “work”, “shopping”, “bank”, etc. The security domains are implemented as separate, Virtual Machines (VMs), thus being isolated from each other as if they were executing on different machines.
Some documents or application can be run in disposable VMs through an action available in the file manager. The mechanism follows the idea of sandboxes: after viewing the document or application, then the whole Disposable VM will be destroyed.
Each security domain is labelled by a color, and each window is marked by the color of the domain it belongs to. So it is always clearly visible to which domain a given window belongs.
- "Qubes OS License".
- "Introducing Qubes 1.0!". September 3, 2012.
- "Announcing Qubes OS Release 2!". September 26, 2014.
- "Qubes OS bakes in virty system-level security". The Register. September 5, 2012.
- "The three approaches to computer security". Joanna Rutkowska. September 2, 2008.
- "Qubes OS: An Operating System Designed For Security". tom's hardware. August 30, 2011.
- "Partitioning my digital life into security domains". Joanna Rutkowska. March 13, 2011.
- "(Un)Trusting your GUI Subsystem". Joanna Rutkowska. September 9, 2010.
- "The Linux Security Circus: On GUI isolation". Joanna Rutkowska. April 23, 2011.
- "Playing with Qubes Networking for Fun and Profit". Joanna Rutkowska. September 28, 2011.
- "Qubes To Implement Disposable Virtual Machines". OSnews. June 3, 2010.