<?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: Microsoft Exploitability Index</title>
	<atom:link href="http://spiresecurity.com/?feed=rss2&#038;p=148" rel="self" type="application/rss+xml" />
	<link>http://spiresecurity.com/?p=148</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: Josh</title>
		<link>http://spiresecurity.com/?p=148&#038;cpage=1#comment-165</link>
		<dc:creator>Josh</dc:creator>
		<pubDate>Fri, 08 Aug 2008 14:58:31 +0000</pubDate>
		<guid isPermaLink="false">http://spiresecurity.com/blog/?p=148#comment-165</guid>
		<description><![CDATA[Personally I think Microsoft should by default just list a criticality label for the whole vulnerability to avoid confusion and noise.  That said, Microsoft already has a full DREAD rating for the vulnerability internally, and they could display that in a div that is hidden by default but displayed when an advanced user clicks on a &quot;show details&quot; link or something similar.  That way advanced users could make patch decisions based off of the specific details if they chose, but less advanced users wouldn&#039;t be confused.
]]></description>
		<content:encoded><![CDATA[<p>Personally I think Microsoft should by default just list a criticality label for the whole vulnerability to avoid confusion and noise.  That said, Microsoft already has a full DREAD rating for the vulnerability internally, and they could display that in a div that is hidden by default but displayed when an advanced user clicks on a &#8220;show details&#8221; link or something similar.  That way advanced users could make patch decisions based off of the specific details if they chose, but less advanced users wouldn&#8217;t be confused.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
