<?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: In the land of the blind..</title>
	<atom:link href="http://emergentchaos.com/archives/2008/06/in-the-land-of-the-blind.html/feed" rel="self" type="application/rss+xml" />
	<link>http://emergentchaos.com/archives/2008/06/in-the-land-of-the-blind.html</link>
	<description>The Emergent Chaos Jazz Combo</description>
	<lastBuildDate>Wed, 01 Feb 2012 19:20:40 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Adam</title>
		<link>http://emergentchaos.com/archives/2008/06/in-the-land-of-the-blind.html/comment-page-1#comment-4829</link>
		<dc:creator>Adam</dc:creator>
		<pubDate>Tue, 01 Jul 2008 11:39:34 +0000</pubDate>
		<guid isPermaLink="false">http://emergentchaos.com/?p=2814#comment-4829</guid>
		<description>Hi Russ,
Thanks for your comments, and I&#039;ll follow up more after I&#039;ve looked at the additional data.  I did want to clarify that I&#039;m not claiming the CSOs were unaware of their own state, but of the state of others.  I&#039;ve added update 2 to explain that.
</description>
		<content:encoded><![CDATA[<p>Hi Russ,<br />
Thanks for your comments, and I&#8217;ll follow up more after I&#8217;ve looked at the additional data.  I did want to clarify that I&#8217;m not claiming the CSOs were unaware of their own state, but of the state of others.  I&#8217;ve added update 2 to explain that.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Russ Cooper</title>
		<link>http://emergentchaos.com/archives/2008/06/in-the-land-of-the-blind.html/comment-page-1#comment-4828</link>
		<dc:creator>Russ Cooper</dc:creator>
		<pubDate>Tue, 01 Jul 2008 10:30:59 +0000</pubDate>
		<guid isPermaLink="false">http://emergentchaos.com/?p=2814#comment-4828</guid>
		<description>Adam,
First, thanks for the kind words about our study. It is definitely our intention to make more data available, and on a more regular basis.
With regard to our measuring CSO response,I think CSO’s are being done a disservice by typifying them as not knowing, in adequate detail, their patching solutions. In our experience, they are not so far removed from the front lines that they are as subjective as is being suggested in your post. Further, our contact wasn’t always, or only, CSOs. We asked to speak to the &lt;i&gt;“key person responsible???&lt;/i&gt;, and in most cases we felt we did.
As for defining 1 – 5 differently, we don’t think it would have necessarily been any better. We have consistently found that key responsible people often think they’ve achieved 100% deployment when, in fact, they haven’t. Consider both the &lt;i&gt;“unknown unknowns???&lt;/i&gt; and &lt;i&gt;“Error???&lt;/i&gt; sections of the study as explanations of why they think they’ve achieved 100%. Knowing whether you’re “truly??? a 1 or a 5 will always be subjective, even if it’s based on reports your patching solution spit out for you. You can’t blame a patching solution for telling you 100% deployed if it is unaware of the 6 computers over there that no one knew existed.
Further, consider that we have three separate studies coming to the same conclusion. The &lt;i&gt;“Countermeasures Effectiveness Study???&lt;/i&gt; you referenced is but one. In each of the three we found similar results despite asking the question in three different ways (via the different surveys or analysis of the investigator.) The &lt;i&gt;“Sasser Study,???&lt;/i&gt; also referenced in my article, asked what percentage of systems were patched before the outbreak. The &lt;i&gt;“Data Breach Investigations Report???&lt;/i&gt; used forensics for its determination.
As for more information about the &lt;i&gt;“Countermeasures Effectiveness Study???&lt;/i&gt; itself, I’d invite you to examine it in more detail via the IEEE Security &amp; Privacy published article: &lt;i&gt;“Is Information Security Under Control????&lt;/i&gt; This article can be found in the January/February 2007 edition, written by Wade Baker and Linda Wallace. Wade was also a co-author of the Data Breach Investigations Report, and is a member of the Verizon Business RISK Team. The Survey Methodology is more fully explained there.
Our goal, however, wasn’t to be the most precise in terms of comparing reality to what a CSO thinks, but to demonstrate that the perceived effectiveness of patching may be misplaced, or not even clearly understood. If you think that AV alone is going to solve your malware problem, then you’ve misplaced your trust. If you think that a Firewall is all that you need to prevent intrusions, think again. If you think that purchasing a “patching solution??? is better than implementing relatively simple controls (that don’t require a new product); you’re overlooking a great chance to reduce risk and save money.
Cheers,
Russ Cooper
</description>
		<content:encoded><![CDATA[<p>Adam,<br />
First, thanks for the kind words about our study. It is definitely our intention to make more data available, and on a more regular basis.<br />
With regard to our measuring CSO response,I think CSO’s are being done a disservice by typifying them as not knowing, in adequate detail, their patching solutions. In our experience, they are not so far removed from the front lines that they are as subjective as is being suggested in your post. Further, our contact wasn’t always, or only, CSOs. We asked to speak to the <i>“key person responsible???</i>, and in most cases we felt we did.<br />
As for defining 1 – 5 differently, we don’t think it would have necessarily been any better. We have consistently found that key responsible people often think they’ve achieved 100% deployment when, in fact, they haven’t. Consider both the <i>“unknown unknowns???</i> and <i>“Error???</i> sections of the study as explanations of why they think they’ve achieved 100%. Knowing whether you’re “truly??? a 1 or a 5 will always be subjective, even if it’s based on reports your patching solution spit out for you. You can’t blame a patching solution for telling you 100% deployed if it is unaware of the 6 computers over there that no one knew existed.<br />
Further, consider that we have three separate studies coming to the same conclusion. The <i>“Countermeasures Effectiveness Study???</i> you referenced is but one. In each of the three we found similar results despite asking the question in three different ways (via the different surveys or analysis of the investigator.) The <i>“Sasser Study,???</i> also referenced in my article, asked what percentage of systems were patched before the outbreak. The <i>“Data Breach Investigations Report???</i> used forensics for its determination.<br />
As for more information about the <i>“Countermeasures Effectiveness Study???</i> itself, I’d invite you to examine it in more detail via the IEEE Security &#038; Privacy published article: <i>“Is Information Security Under Control????</i> This article can be found in the January/February 2007 edition, written by Wade Baker and Linda Wallace. Wade was also a co-author of the Data Breach Investigations Report, and is a member of the Verizon Business RISK Team. The Survey Methodology is more fully explained there.<br />
Our goal, however, wasn’t to be the most precise in terms of comparing reality to what a CSO thinks, but to demonstrate that the perceived effectiveness of patching may be misplaced, or not even clearly understood. If you think that AV alone is going to solve your malware problem, then you’ve misplaced your trust. If you think that a Firewall is all that you need to prevent intrusions, think again. If you think that purchasing a “patching solution??? is better than implementing relatively simple controls (that don’t require a new product); you’re overlooking a great chance to reduce risk and save money.<br />
Cheers,<br />
Russ Cooper</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Pete</title>
		<link>http://emergentchaos.com/archives/2008/06/in-the-land-of-the-blind.html/comment-page-1#comment-4827</link>
		<dc:creator>Pete</dc:creator>
		<pubDate>Mon, 30 Jun 2008 21:02:23 +0000</pubDate>
		<guid isPermaLink="false">http://emergentchaos.com/?p=2814#comment-4827</guid>
		<description>I was under the impression that there were two separate sets of data at play here. One was the 1 through 5 rating, but Jeff&#039;s point was in regards to the length of time that a patch was available prior to exploit for the incidents in question, wasn&#039;t it?
</description>
		<content:encoded><![CDATA[<p>I was under the impression that there were two separate sets of data at play here. One was the 1 through 5 rating, but Jeff&#8217;s point was in regards to the length of time that a patch was available prior to exploit for the incidents in question, wasn&#8217;t it?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Davi Ottenheimer</title>
		<link>http://emergentchaos.com/archives/2008/06/in-the-land-of-the-blind.html/comment-page-1#comment-4826</link>
		<dc:creator>Davi Ottenheimer</dc:creator>
		<pubDate>Mon, 30 Jun 2008 19:39:51 +0000</pubDate>
		<guid isPermaLink="false">http://emergentchaos.com/?p=2814#comment-4826</guid>
		<description>Yes, very annoying that the &quot;data&quot; is really just a measure of self-perception.
I have run numerous engagements where the perception of executives is so far removed from the reality of security, that the PCI DSS is a welcome breath of fresh air to the conversation.
Patching not only makes a lot of sense, but the PCI incident response/investigation teams obviously ferret out the root cause (pun not intended) on their own. When breaches are no longer due to missing patches then they will surely update the PCI DSS appropriately.
</description>
		<content:encoded><![CDATA[<p>Yes, very annoying that the &#8220;data&#8221; is really just a measure of self-perception.<br />
I have run numerous engagements where the perception of executives is so far removed from the reality of security, that the PCI DSS is a welcome breath of fresh air to the conversation.<br />
Patching not only makes a lot of sense, but the PCI incident response/investigation teams obviously ferret out the root cause (pun not intended) on their own. When breaches are no longer due to missing patches then they will surely update the PCI DSS appropriately.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Blake</title>
		<link>http://emergentchaos.com/archives/2008/06/in-the-land-of-the-blind.html/comment-page-1#comment-4825</link>
		<dc:creator>Blake</dc:creator>
		<pubDate>Mon, 30 Jun 2008 08:14:31 +0000</pubDate>
		<guid isPermaLink="false">http://emergentchaos.com/?p=2814#comment-4825</guid>
		<description>Sounds like one could as well make the argument that CSO&#039;s who are happy with their patching programs don&#039;t have a better security outcome than CSO&#039;s who feel their programs could be improved.  The lesson has nothing to do with patching and everything to do with CSO attitudes, which is what Verizon measured.
</description>
		<content:encoded><![CDATA[<p>Sounds like one could as well make the argument that CSO&#8217;s who are happy with their patching programs don&#8217;t have a better security outcome than CSO&#8217;s who feel their programs could be improved.  The lesson has nothing to do with patching and everything to do with CSO attitudes, which is what Verizon measured.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

