Features/SVirt Mandatory Access Control
sVirt integrates SELinux with the Fedora virtualization stack to allow Mandatory Access Control (MAC) security be applied to guest virtual machines. Amongst other things, this prevents a security bug in the hypervisor from allowing guests to attack the host or one another.
- Name: Dan Walsh
- Targeted release: Fedora 11
- Last updated: 2009-03-4
- Percentage of completion: 100%
The core support in libvirt 0.6.1, and SELinux policy & tools is now available in rawhide. Changes to virt-manager are not required, since libvirt automatically assigns unique security labels to all guests.
- Initial announcement and subsequent discussion (August 2008)
- See latest readme
- See sVirt TODO list
- Merge the patch into upstream libvirt, release and package in Fedora [DONE]
- Policy [DONE]
- sVirt available in libvirt 0.6.1 http://www.redhat.com/archives/libvir-list/2009-March/msg00144.html
Before virtualization, machines were physically separated. Any security exploit is reasonably well contained to the affected machine, with the obvious exception of network attacks.
With virtualization, a security flaw in the hypervisor may be exploited by a guest and allow the guest to attack the host, or even other guests running on that host. Hypervisors are complex pieces of code, so hypervisor vulnerabilities are far from a theoretical concern.
The sVirt framework allows guests and their resources to be uniquely labelled. Once labelled, rules can be applied which reject accesses between different guests.
Benefit to Fedora
The strong security policy enforcement provided by SELinux means that Fedora systems are well protected from malicious attempts to exploit security flaws.
sVirt brings that same benefit to Fedora's virtualization support. Integration of MAC will help increase the overall robustness and security assurance of Fedora host systems.
sVirt is a foray into an emerging field of security research. By adopting this work, Fedora will continue to lead the way in providing fully integrated security solutions and virtualization support.
The work primarily involves modifications to libvirt, SELinux policy and, libselinux.
Future work will be done on virt-manager and python-virtinst to allow static setting of the labels.
How To Test
Make sure the virtual machines are running with a categorized context.
If you had a virtual machine named F11
- If it is running as
system_u:system_r:qemu_t:s0or some other context then sVirt is not working.
ps -eZ | grep qemu.
- The image file for the qemu should be labeled similarly
ls -lZ /var/lib/libvirt/images/F11.img
Should show a context like the following.
- To make sure SELinux is blocking illegal access you can change the context on the image
chcon -l s0:c1 /var/lib/libvirt/images/F11.img
Now the running image will start to blow up with a permission denied and generate an avc indicating
system_u:system_r:svirt_t:s0:c344,c902 tried to write to system_u:object_r:svirt_image_t:s0:c1
I would like to see insertion of CDROM devices, USB Other forms of devices and make sure they are labeled correctly.
Make sure you can stop and start a service.
Check cloning and saving to a /var/lib/libvirt/images directory.
Theoretically the user should not experience anything. This should just happen automatically and the virtual machines should just work.
The user will be able to configure whether or not he wants isolated virtual machines.
svirt depends on updates to libvirt, selinux-policy, libselinux.
The goal is to get all the plumbing for svirt to work in F11, but the GUI for managing the environment might not be ready.
Dynamic labeling is now completed. In the future we want to allow static labeling where libvirt will just label the processes with a static label given to it from the virt-manager/virsh. This functionality could then be used by MLS environments that would like to run their virtual machines at a single level.
- Project home page
- initial requirements analysis
- LCA presentation (January 2009)
- Discussion on libvir-list about issues relating to locking down qemu.
Fedora 11 integrates SELinux's Mandatory Access Control with Virtualization. Virtual machines can now be much more effectively isolated from the host and one another, giving the increased assurance that security flaws cannot be exploited by malicious guests.