<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.technet.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Security Risks of Virtualization</title><link>http://blogs.technet.com/rhalbheer/archive/2008/05/21/security-risks-of-virtualization.aspx</link><description>One fact strikes me pretty often: Companies have the problem that they have legacy software running on legacy operating systems (e.g. NT4) running on legacy hardware. This is a severe problem as you all know. Now, these companies look into virtualization</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>re: Security Risks of Virtualization</title><link>http://blogs.technet.com/rhalbheer/archive/2008/05/21/security-risks-of-virtualization.aspx#3062519</link><pubDate>Thu, 29 May 2008 11:36:29 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3062519</guid><dc:creator>Hall Mil</dc:creator><description>&lt;p&gt;As far as the risks considered here is concerned, the LivePCs available by MokaFive can work to much extent and help in solving many of these issues. You may check the technology at their website:&lt;/p&gt;
&lt;p&gt;&lt;a rel="nofollow" target="_new" href="http://www.mokafive.com/"&gt;http://www.mokafive.com/&lt;/a&gt;&lt;/p&gt;
</description></item><item><title>re: Security Risks of Virtualization</title><link>http://blogs.technet.com/rhalbheer/archive/2008/05/21/security-risks-of-virtualization.aspx#3062534</link><pubDate>Thu, 29 May 2008 11:55:38 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3062534</guid><dc:creator>rhalbh</dc:creator><description>&lt;p&gt;Help me understanding this: This technology to me seems similar to VMVare or VirtualPC. At the end of the day, if the virtualization software has vulnerability, this might impact the guest as well&lt;/p&gt;
&lt;p&gt;Roger&lt;/p&gt;
</description></item></channel></rss>