<?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"
	>
<channel>
	<title>Comments on: VMware Addressing Virtual Security Concerns</title>
	<atom:link href="http://blog.scottlowe.org/2007/08/18/vmware-addressing-virtual-security-concerns/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.scottlowe.org/2007/08/18/vmware-addressing-virtual-security-concerns/</link>
	<description>The weblog of an IT pro specializing in virtualization, storage, and servers</description>
	<pubDate>Mon, 01 Dec 2008 19:54:53 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6</generator>
		<item>
		<title>By: slowe</title>
		<link>http://blog.scottlowe.org/2007/08/18/vmware-addressing-virtual-security-concerns/#comment-34244</link>
		<dc:creator>slowe</dc:creator>
		<pubDate>Tue, 20 Nov 2007 22:50:17 +0000</pubDate>
		<guid isPermaLink="false">http://blog.scottlowe.org/2007/08/18/vmware-addressing-virtual-security-concerns/#comment-34244</guid>
		<description>Paul,

Send me an e-mail...perhaps we can work together to take a closer look at Astaro and see how well it works.  Thanks!</description>
		<content:encoded><![CDATA[<p>Paul,</p>
<p>Send me an e-mail&#8230;perhaps we can work together to take a closer look at Astaro and see how well it works.  Thanks!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Paul</title>
		<link>http://blog.scottlowe.org/2007/08/18/vmware-addressing-virtual-security-concerns/#comment-34239</link>
		<dc:creator>Paul</dc:creator>
		<pubDate>Tue, 20 Nov 2007 20:48:26 +0000</pubDate>
		<guid isPermaLink="false">http://blog.scottlowe.org/2007/08/18/vmware-addressing-virtual-security-concerns/#comment-34239</guid>
		<description>"There is one area, however, where I do agree with some of the complaints, and that is visibility into the virtualized networking environment.  Without that, there is no way to detect (and/or mitigate) guest-to-guest attacks on the same host.  I believe that VMwareâ€™s rumored move to allow Cisco switches on ESX Server is one step to help mitigate this weakness.  After all, if weâ€™ve got native IOS running on a switch on ESX, that means (presumably) that we can mirror track to another virtual switch port for use by an IDS/IPS, most likely running in another VM."

Again, Astaro Offers virtual appliances that are 802.1q capable and could be used to segment and secure the virtual network. With transparent bridging, inline snort, granular iptables, transparent proxies and IPSEC capabilities, all in a high performance hardened linux distro, all bases should be well covered. I've been chomping at the bit to setup a VM stack or two and segment with this virtual firewall to do some benchmarking. Now... if I could just get a hold of a ESX farm to benchmark my theory...

Paul</description>
		<content:encoded><![CDATA[<p>&#8220;There is one area, however, where I do agree with some of the complaints, and that is visibility into the virtualized networking environment.  Without that, there is no way to detect (and/or mitigate) guest-to-guest attacks on the same host.  I believe that VMwareâ€™s rumored move to allow Cisco switches on ESX Server is one step to help mitigate this weakness.  After all, if weâ€™ve got native IOS running on a switch on ESX, that means (presumably) that we can mirror track to another virtual switch port for use by an IDS/IPS, most likely running in another VM.&#8221;</p>
<p>Again, Astaro Offers virtual appliances that are 802.1q capable and could be used to segment and secure the virtual network. With transparent bridging, inline snort, granular iptables, transparent proxies and IPSEC capabilities, all in a high performance hardened linux distro, all bases should be well covered. I&#8217;ve been chomping at the bit to setup a VM stack or two and segment with this virtual firewall to do some benchmarking. Now&#8230; if I could just get a hold of a ESX farm to benchmark my theory&#8230;</p>
<p>Paul</p>
]]></content:encoded>
	</item>
</channel>
</rss>
