<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Hypervisor vs. Operating System Security Title Match?</title>
	<atom:link href="http://spiresecurity.com/?feed=rss2&#038;p=269" rel="self" type="application/rss+xml" />
	<link>http://spiresecurity.com/?p=269</link>
	<description>Risk and Cybersecurity Analysis</description>
	<lastBuildDate>Wed, 21 Aug 2013 23:28:51 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.5.1</generator>
	<item>
		<title>By: Anonymous</title>
		<link>http://spiresecurity.com/?p=269&#038;cpage=1#comment-368</link>
		<dc:creator>Anonymous</dc:creator>
		<pubDate>Fri, 28 Sep 2007 03:39:58 +0000</pubDate>
		<guid isPermaLink="false">http://spiresecurity.com/blog/?p=269#comment-368</guid>
		<description><![CDATA[@Greg -

I guess by theoretical you mean that they haven&#039;t been found in the wild yet, right? There has been some interesting proof-of-concept and bugfinding work done by Tom Shelton (attack against VMWare&#039;s NAT); Tavis Ormandy (paper on remote code exploits for most virtualization software); and Tom Liston at IntelGuardians (details here slightly less clear).

In any case, I am not sure what point you are making. It seems like you are doing exactly what I am cautioning against - comparing hypervisor security to OS security. My point is that you get your latter situation in either physical or virtual machine. If that is the case, then the hypervisor attack surface, however slight it may be, adds to the attack surface of the VM.

Pete
]]></description>
		<content:encoded><![CDATA[<p>@Greg -</p>
<p>I guess by theoretical you mean that they haven&#8217;t been found in the wild yet, right? There has been some interesting proof-of-concept and bugfinding work done by Tom Shelton (attack against VMWare&#8217;s NAT); Tavis Ormandy (paper on remote code exploits for most virtualization software); and Tom Liston at IntelGuardians (details here slightly less clear).</p>
<p>In any case, I am not sure what point you are making. It seems like you are doing exactly what I am cautioning against &#8211; comparing hypervisor security to OS security. My point is that you get your latter situation in either physical or virtual machine. If that is the case, then the hypervisor attack surface, however slight it may be, adds to the attack surface of the VM.</p>
<p>Pete</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Greg Ness</title>
		<link>http://spiresecurity.com/?p=269&#038;cpage=1#comment-367</link>
		<dc:creator>Greg Ness</dc:creator>
		<pubDate>Thu, 27 Sep 2007 21:27:15 +0000</pubDate>
		<guid isPermaLink="false">http://spiresecurity.com/blog/?p=269#comment-367</guid>
		<description><![CDATA[Pete:

I think most would agree that hypervisor attacks are theoretical at this point, as compared to the VM OS/App vulnerabilities which exist, have established attacks and which are now in &quot;fluid-like&quot; states creating an attack surface that can mutate faster than most security appliances can keep up.

Greg N
]]></description>
		<content:encoded><![CDATA[<p>Pete:</p>
<p>I think most would agree that hypervisor attacks are theoretical at this point, as compared to the VM OS/App vulnerabilities which exist, have established attacks and which are now in &#8220;fluid-like&#8221; states creating an attack surface that can mutate faster than most security appliances can keep up.</p>
<p>Greg N</p>
]]></content:encoded>
	</item>
</channel>
</rss>
