<?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: Security theater and the value of information</title>
	<atom:link href="http://peter.evans-greenwood.com/2010/01/08/security-theater-and-the-value-of-information/feed/" rel="self" type="application/rss+xml" />
	<link>http://peter.evans-greenwood.com/2010/01/08/security-theater-and-the-value-of-information/</link>
	<description>Trying to understand the intersection between business and technology</description>
	<lastBuildDate>Thu, 01 Dec 2011 14:45:43 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Peter Evans-Greenwood</title>
		<link>http://peter.evans-greenwood.com/2010/01/08/security-theater-and-the-value-of-information/comment-page-1/#comment-925</link>
		<dc:creator>Peter Evans-Greenwood</dc:creator>
		<pubDate>Mon, 11 Jan 2010 08:07:47 +0000</pubDate>
		<guid isPermaLink="false">http://peter.evans-greenwood.com/2010/01/08/security-theater-and-the-value-of-information/#comment-925</guid>
		<description>I found Bruce Schneier&#039;s post interesting due to his response to this problem of finding a needle in a haystack.&lt;br&gt;&lt;br&gt;What he doesn&#039;t recommend is taking a piecewise operational approach (which is something like a conventional BI approach), characterising the scenario and then formalising a response, as this doesn&#039;t scale, nor does it find new threats (disruptions). His solution is more organisational than operational, reorienting the response around a longitudinal (rather than operational) view of whats happening across the value-chain, and then looking for relationships between unusual data points.&lt;br&gt;&lt;br&gt;It&#039;s really a question of changing how you view and use the data, which ties back the whole &lt;a href=&quot;http://peter.evans-greenwood.com/2009/12/21/innovation-and-the-art-of-random/&quot; rel=&quot;nofollow&quot;&gt;&quot;art of random&quot;&lt;/a&gt; thing; hence my thought on OODA and John Boyd.&lt;br&gt;&lt;br&gt;r.&lt;br&gt;&lt;br&gt;PEG</description>
		<content:encoded><![CDATA[<p>I found Bruce Schneier&#39;s post interesting due to his response to this problem of finding a needle in a haystack.</p>
<p>What he doesn&#39;t recommend is taking a piecewise operational approach (which is something like a conventional BI approach), characterising the scenario and then formalising a response, as this doesn&#39;t scale, nor does it find new threats (disruptions). His solution is more organisational than operational, reorienting the response around a longitudinal (rather than operational) view of whats happening across the value-chain, and then looking for relationships between unusual data points.</p>
<p>It&#39;s really a question of changing how you view and use the data, which ties back the whole <a href="http://peter.evans-greenwood.com/2009/12/21/innovation-and-the-art-of-random/" rel="nofollow">&#8220;art of random&#8221;</a> thing; hence my thought on OODA and John Boyd.</p>
<p>r.</p>
<p>PEG</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: andymulholland</title>
		<link>http://peter.evans-greenwood.com/2010/01/08/security-theater-and-the-value-of-information/comment-page-1/#comment-924</link>
		<dc:creator>andymulholland</dc:creator>
		<pubDate>Fri, 08 Jan 2010 17:34:52 +0000</pubDate>
		<guid isPermaLink="false">http://peter.evans-greenwood.com/2010/01/08/security-theater-and-the-value-of-information/#comment-924</guid>
		<description>Peter - it seems that they had information on the bomber but the right people didnt know at the right time to link to the execution process that should have stopped him. That seems to me to link back to some of your earlier blogs about its not having information - in fact we have too much information - its finding ways to reduce the information to levels that allow it to be usable</description>
		<content:encoded><![CDATA[<p>Peter &#8211; it seems that they had information on the bomber but the right people didnt know at the right time to link to the execution process that should have stopped him. That seems to me to link back to some of your earlier blogs about its not having information &#8211; in fact we have too much information &#8211; its finding ways to reduce the information to levels that allow it to be usable</p>
]]></content:encoded>
	</item>
</channel>
</rss>

