<?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: Cleaning Up</title>
	<atom:link href="http://emergentchaos.com/archives/2007/04/cleaning-up.html/feed" rel="self" type="application/rss+xml" />
	<link>http://emergentchaos.com/archives/2007/04/cleaning-up.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: Iang</title>
		<link>http://emergentchaos.com/archives/2007/04/cleaning-up.html/comment-page-1#comment-3485</link>
		<dc:creator>Iang</dc:creator>
		<pubDate>Mon, 09 Apr 2007 16:30:42 +0000</pubDate>
		<guid isPermaLink="false">http://emergentchaos.com/?p=2306#comment-3485</guid>
		<description>Cat, I think you are basically right.  Snow was working in a time where data analysis to support conclusions was a new idea, now it is an old idea.
What is left is critical thought.  I do not believe we have mastered that, as yet.  Two examples:
Last year the Nobel for Medicine went to a pair of Australian looney doctors who thought that stomach ulcers were caused by bacteria not stress.  Well, everyone knows they are stress.  The two doctors saw different data, but still nobody was convinced.  It was only when one of the doctors infected himself with the bacteria, created an ulcer, and then cured it with penicillin, that people started to take notice.
The issue is not the data, that was easy to look at and repeat.  It was the thought process;  It took a crazy circus trick to get people to re-assess their beliefs.
2nd example:  we&#039;ve known all about phishing since 2003-2004.  And before, because it was a straightforward, well-known, historical and predicted weakness.  If you asked around, you could find people who would tell you what it was.  The data was pouring in ... and yet ... here we are in 2007, and you still can&#039;t find 2 security experts (?!) to agree on how to solve it.
Why not?  I surmise that it is because to do that, we as a security industry have to look at that flagship product -- secure browsing to protect ecommerce -- and we basically have to say &quot;we failed.&quot;  We basically put in place the wrong product at the wrong time, and it failed when attacked.  Then we did nothing.
Until we cross that hurdle, we&#039;ll not get anywhere ... I surmise ... because none of us want to go where it is darkest.  But you won&#039;t get anyone to agree with me :)
</description>
		<content:encoded><![CDATA[<p>Cat, I think you are basically right.  Snow was working in a time where data analysis to support conclusions was a new idea, now it is an old idea.<br />
What is left is critical thought.  I do not believe we have mastered that, as yet.  Two examples:<br />
Last year the Nobel for Medicine went to a pair of Australian looney doctors who thought that stomach ulcers were caused by bacteria not stress.  Well, everyone knows they are stress.  The two doctors saw different data, but still nobody was convinced.  It was only when one of the doctors infected himself with the bacteria, created an ulcer, and then cured it with penicillin, that people started to take notice.<br />
The issue is not the data, that was easy to look at and repeat.  It was the thought process;  It took a crazy circus trick to get people to re-assess their beliefs.<br />
2nd example:  we&#8217;ve known all about phishing since 2003-2004.  And before, because it was a straightforward, well-known, historical and predicted weakness.  If you asked around, you could find people who would tell you what it was.  The data was pouring in &#8230; and yet &#8230; here we are in 2007, and you still can&#8217;t find 2 security experts (?!) to agree on how to solve it.<br />
Why not?  I surmise that it is because to do that, we as a security industry have to look at that flagship product &#8212; secure browsing to protect ecommerce &#8212; and we basically have to say &#8220;we failed.&#8221;  We basically put in place the wrong product at the wrong time, and it failed when attacked.  Then we did nothing.<br />
Until we cross that hurdle, we&#8217;ll not get anywhere &#8230; I surmise &#8230; because none of us want to go where it is darkest.  But you won&#8217;t get anyone to agree with me :)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: John Snow's Ghost</title>
		<link>http://emergentchaos.com/archives/2007/04/cleaning-up.html/comment-page-1#comment-3484</link>
		<dc:creator>John Snow's Ghost</dc:creator>
		<pubDate>Mon, 09 Apr 2007 16:10:51 +0000</pubDate>
		<guid isPermaLink="false">http://emergentchaos.com/?p=2306#comment-3484</guid>
		<description>Overview
Do you cringe at the subjectivity applied to security in every manner? If so, MetriCon 2.0 may be your antidote to change security from an artistic &quot;matter of opinion&quot; into an objective, quantifiable science. The time for adjectives and adverbs has gone; the time for hard facts and data has come.
&lt;a href=&quot;http://securitymetrics.org/content/Wiki.jsp?page=Welcome_blogentry_090407_1&quot; rel=&quot;nofollow&quot;&gt;MetriCon 2.0&lt;/a&gt; is intended as a forum for lively, practical discussion in the area of security metrics. It is a forum for quantifiable approaches and results to problems afflicting information security today, with a bias towards practical, specific implementations. Topics and presentations will be selected for their potential to stimulate discussion in the Workshop.
MetriCon 2.0 will be a one-day event, Tuesday, August 7, 2007, ...
</description>
		<content:encoded><![CDATA[<p>Overview<br />
Do you cringe at the subjectivity applied to security in every manner? If so, MetriCon 2.0 may be your antidote to change security from an artistic &#8220;matter of opinion&#8221; into an objective, quantifiable science. The time for adjectives and adverbs has gone; the time for hard facts and data has come.<br />
<a href="http://securitymetrics.org/content/Wiki.jsp?page=Welcome_blogentry_090407_1" rel="nofollow">MetriCon 2.0</a> is intended as a forum for lively, practical discussion in the area of security metrics. It is a forum for quantifiable approaches and results to problems afflicting information security today, with a bias towards practical, specific implementations. Topics and presentations will be selected for their potential to stimulate discussion in the Workshop.<br />
MetriCon 2.0 will be a one-day event, Tuesday, August 7, 2007, &#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: cat</title>
		<link>http://emergentchaos.com/archives/2007/04/cleaning-up.html/comment-page-1#comment-3483</link>
		<dc:creator>cat</dc:creator>
		<pubDate>Mon, 09 Apr 2007 02:53:14 +0000</pubDate>
		<guid isPermaLink="false">http://emergentchaos.com/?p=2306#comment-3483</guid>
		<description>&lt;i&gt;Data was also part of the problem, as Johnson points out, because the larger problem was sorting through the data. However, when it comes to computer security, we don&#039;t yet have the luxury of too much data.&lt;/i&gt;
&lt;i&gt;Everyone&#039;s data center has its own little cesspool. Mine does, yours does. We have to figure out how to clean them up. We need to have more data. We therefore need to remove the stigma of disclosing data as well as insisting on it.&lt;/i&gt;
I think you&#039;ve got a dubious link here.  John Snow (not to belittle his contributions) had a specific issue (cholera), occuring in a specific area (Soho), causing specific problems (illness/death).  He could gather specific data about location of illness/death, and plot it on a map.
Just addressing information leaks (and not security in general), we&#039;ve got a general issue, occuring in many areas, causing a variety of problems.
While I&#039;m certainly not going to claim that more information might not be helpful, I remain decidedly unconvinced that more information would turn out to be anything more than - well - more information.
How would you structure the analysis of breach data, to provide meaningful information?
As a trivial example, if we take information leaked from laptops being stolen as an example, we might conclude that laptops are most often stolen from vehicles parked near stadiums - so information breaches can be prevented by not parking near stadiums...
</description>
		<content:encoded><![CDATA[<p><i>Data was also part of the problem, as Johnson points out, because the larger problem was sorting through the data. However, when it comes to computer security, we don&#8217;t yet have the luxury of too much data.</i><br />
<i>Everyone&#8217;s data center has its own little cesspool. Mine does, yours does. We have to figure out how to clean them up. We need to have more data. We therefore need to remove the stigma of disclosing data as well as insisting on it.</i><br />
I think you&#8217;ve got a dubious link here.  John Snow (not to belittle his contributions) had a specific issue (cholera), occuring in a specific area (Soho), causing specific problems (illness/death).  He could gather specific data about location of illness/death, and plot it on a map.<br />
Just addressing information leaks (and not security in general), we&#8217;ve got a general issue, occuring in many areas, causing a variety of problems.<br />
While I&#8217;m certainly not going to claim that more information might not be helpful, I remain decidedly unconvinced that more information would turn out to be anything more than &#8211; well &#8211; more information.<br />
How would you structure the analysis of breach data, to provide meaningful information?<br />
As a trivial example, if we take information leaked from laptops being stolen as an example, we might conclude that laptops are most often stolen from vehicles parked near stadiums &#8211; so information breaches can be prevented by not parking near stadiums&#8230;</p>
]]></content:encoded>
	</item>
</channel>
</rss>

