<?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: To Patch or Not To Patch</title>
	<atom:link href="http://spiresecurity.com/?feed=rss2&#038;p=481" rel="self" type="application/rss+xml" />
	<link>http://spiresecurity.com/?p=481</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: Pete</title>
		<link>http://spiresecurity.com/?p=481&#038;cpage=1#comment-758</link>
		<dc:creator>Pete</dc:creator>
		<pubDate>Mon, 09 Jan 2006 13:48:39 +0000</pubDate>
		<guid isPermaLink="false">http://spiresecurity.com/blog/?p=481#comment-758</guid>
		<description><![CDATA[@Stuart -

Good point on the client vs. server patching. I would expect that there is very little impact on servers from the WMF vulnerability.

Regarding political costs of NOT taking action, I think that is a great point. All the fanfare can force (re)action. Meanwhile, there is Sober and the Oracle worm to consider.
]]></description>
		<content:encoded><![CDATA[<p>@Stuart -</p>
<p>Good point on the client vs. server patching. I would expect that there is very little impact on servers from the WMF vulnerability.</p>
<p>Regarding political costs of NOT taking action, I think that is a great point. All the fanfare can force (re)action. Meanwhile, there is Sober and the Oracle worm to consider.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Stuart Berman</title>
		<link>http://spiresecurity.com/?p=481&#038;cpage=1#comment-757</link>
		<dc:creator>Stuart Berman</dc:creator>
		<pubDate>Mon, 09 Jan 2006 03:58:22 +0000</pubDate>
		<guid isPermaLink="false">http://spiresecurity.com/blog/?p=481#comment-757</guid>
		<description><![CDATA[I think you are partly correct.

In the case of WMF there seem to be plenty of anti-virus products that effectively block most known forms of exploits. There is also the issue of client versus server patching. Patching servers is far more serious and expensive than client patching (due to the impact of affecing critical servers). Roling out client patches is often fairly straightforward and even phased roll outs can be automated.

The bit that you don&#039;t seem to address is the political cost. When an exploit (and patch) such as WMF hits the mainstream press now you are obligated to consider the backlash if you don&#039;t appear to be doing something effective if the worst case does in fact hit. (Or even something unrelated but likely to be misconstrued such as the Sober worm activation set for January 6.)
]]></description>
		<content:encoded><![CDATA[<p>I think you are partly correct.</p>
<p>In the case of WMF there seem to be plenty of anti-virus products that effectively block most known forms of exploits. There is also the issue of client versus server patching. Patching servers is far more serious and expensive than client patching (due to the impact of affecing critical servers). Roling out client patches is often fairly straightforward and even phased roll outs can be automated.</p>
<p>The bit that you don&#8217;t seem to address is the political cost. When an exploit (and patch) such as WMF hits the mainstream press now you are obligated to consider the backlash if you don&#8217;t appear to be doing something effective if the worst case does in fact hit. (Or even something unrelated but likely to be misconstrued such as the Sober worm activation set for January 6.)</p>
]]></content:encoded>
	</item>
</channel>
</rss>
