Open Source Security » selinux http://www.ratliff.net/blog A blog about open source and security and open source security Tue, 10 Aug 2010 00:22:41 +0000 en hourly 1 http://wordpress.org/?v=3.0.1 sVirt Stronger Security for Linux Virtualization http://www.ratliff.net/blog/2009/12/22/svirt-stronger-security-for-linux-virtualization/ http://www.ratliff.net/blog/2009/12/22/svirt-stronger-security-for-linux-virtualization/#comments Tue, 22 Dec 2009 22:24:23 +0000 Bryan Jacobson http://www.ratliff.net/blog/?p=275 By Bryan Jacobson, Linux Technology Center.

While Virtualization offers many benefits, there can also be increased security risks. For example, consider a system running two hundred virtual images. All two hundred images are at risk if a flaw in the hypervisor (or configuration) allows any virtual guest to “break out” into the host environment and affect other virtual guests.

sVirt is a project to improve the security of Linux virtualization. Svirt applies the Mandatory Access Control (MAC) features of SELinux to strengthen the isolation between virtual images. Svirt works with KVM/QEMU and other Linux virtualization systems where the virtual image runs as a Linux user space process.

sVirt is a community project, with founding authors from Red Hat: Daniel Berrange, James Morris, and Dan Walsh. sVirt is integrated with libvirt.

One of my favorite sVirt use cases is: “Strongly isolating desktop applications by running them in separately labeled VMs (e.g. online banking in one VM and World of Warcraft in another; opening untrusted office documents in an isolated VM for view/print only).” (From the 8/11/2008 sVirt project announcement at www.redhat.com/archives/libvir-list/2008-August/msg00255.html).

The project announcement also identifies an excellent design goal: “Initially, sVirt should “just work” as a means to isolate VMs, with minimal administrative interaction. e.g. an option is added to virt-manager which allows a VM to be designated as “isolated”, and from then on, it is automatically run in a separate security context, with policy etc. being generated and managed by libvirt.”.

You can find a 48 minute video of James Morris’s February 2009 presentation on sVirt at Linux.conf.au: video.google.com/videoplay?docid=5750618585157629496#

Slides from that presentation are at: namei.org/presentations/svirt-lca-2009.pdf

]]> http://www.ratliff.net/blog/2009/12/22/svirt-stronger-security-for-linux-virtualization/feed/ 2 Fedora users love SELinux http://www.ratliff.net/blog/2008/04/10/fedora-users-love-selinux/ http://www.ratliff.net/blog/2008/04/10/fedora-users-love-selinux/#comments Thu, 10 Apr 2008 17:19:15 +0000 Emily Ratliff http://www.ratliff.net/blog/index.php/2008/04/10/fedora-users-love-selinux/ Fedora Weekly News continues to be a(n unexpectedly) great source for security content. I’ve recently been cleaning up the backlog of my email and have discovered nuggets of valuable information such as

94% of Fedora 8 installs have SELinux enabled

in Fedora Weekly News Issue 121 (Feb. 18, 2008). Now if you read the article, the number I selected to highlight is the raw number that James got off-list. 47%, 50%, and 74% were also tossed out there. Dan Walsh said that the statistics are misleading but being improved and Yaakov Nemoy says that smolt only measures 10% of Fedora machines. So, they are still working out the details. Even so, what they have measured so far is a quite a bit different from the statistics that we see about enterprise customers. I expect it is probably because Fedora users are satisfied with a completely open source stack and do not install as many 3rd party ISV applications which are not as integrated and do not have application specific SELinux policy. Still, this is an incredibly encouraging statistic. Once the Fedora community has been collecting the statistics a little longer, collects whether SELinux is enforcing or not, and starts publicizing these statistics widely, they may be able to help drive ISV adoption (or at least tolerance) of SELinux which will encourage commercial customers to follow the Fedora wave of early adopters on short order.

P.S. Yes, the title is tongue in cheek with a nod to the guys who participated in the discussion.

http://fedoraproject.org/wiki/FWN/Issue121

]]> http://www.ratliff.net/blog/2008/04/10/fedora-users-love-selinux/feed/ 0 So, would you call it SESolaris? SEOpenSolaris? http://www.ratliff.net/blog/2008/03/05/so-would-you-call-it-sesolaris-seopensolaris/ http://www.ratliff.net/blog/2008/03/05/so-would-you-call-it-sesolaris-seopensolaris/#comments Wed, 05 Mar 2008 22:46:20 +0000 Emily Ratliff http://www.ratliff.net/blog/index.php/2008/03/05/so-would-you-call-it-sesolaris-seopensolaris/ In a major validation of the FLASK architecture, the OpenSolaris community has created a new project called Flexible Mandatory Access Control (fmac) to adapt the FLASK architecture to OpenSolaris. (The FLASK architecture that is the basis for SELinux.) Stephen Smalley will be one of the community leads. OSNews picked up the email thread today with some interesting comments.

James Morris notes related work in his blog posting from this morning and offers to help the community preserve interoperability with SELinux.

Personally, I would be delighted to see widespread adoption of the FLASK architecture lead to usability improvements and complexity reduction across the board.

[1] http://www.opensolaris.org/os/project/fmac/
[2] http://www.opensolaris.org/jive/thread.jspa?messageID=204568𱼘
[3] http://www.osnews.com/thread?303491
[4] http://james-morris.livejournal.com/2008/03/05/

]]> http://www.ratliff.net/blog/2008/03/05/so-would-you-call-it-sesolaris-seopensolaris/feed/ 0