<?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"
	>
<channel>
	<title>Comments on: Insider Breach Stats: Bogus, Biased, or Believable?</title>
	<atom:link href="http://securityblog.verizonbusiness.com/2008/07/07/bogus-biased-or-believable/feed/" rel="self" type="application/rss+xml" />
	<link>http://securityblog.verizonbusiness.com/2008/07/07/bogus-biased-or-believable/</link>
	<description>Risk Intelligence from Verizon Business Security Solutions powered by Cybertrust</description>
	<pubDate>Tue, 06 Jan 2009 07:10:14 +0000</pubDate>
	<generator>http://wordpress.org/?v=</generator>
		<item>
		<title>By: Russ Cooper</title>
		<link>http://securityblog.verizonbusiness.com/2008/07/07/bogus-biased-or-believable/#comment-23</link>
		<dc:creator>Russ Cooper</dc:creator>
		<pubDate>Mon, 21 Jul 2008 14:49:37 +0000</pubDate>
		<guid isPermaLink="false">http://securityblog.verizonbusiness.com/?p=126#comment-23</guid>
		<description>@Hawke: You bring up an interesting point and, to a certain extent, we agree - managing risk is clearly the right focus. We do not, however, think the number of breaches is the “wrong” statistic. Since risk is the product of likelihood (number of incidents) and impact, statistics on both parameters are necessary. Concentrating solely on impact or damage quickly leads to a form of decision making we like to call “WIBiHI” (Wouldn’t It Be Horrible If…”) and can often result in gross overspending. As you suggest, managing security based on likelihood, alone, isn’t a winning strategy either.

Keep in mind the original blog post is in response to public reaction to our findings regarding the percentage of breaches involving insiders. We’re not suggesting likelihood is more important than impact (or damage); it’s just that nobody seemed to argue against or misconstrue the latter parameter.</description>
		<content:encoded><![CDATA[<p>@Hawke: You bring up an interesting point and, to a certain extent, we agree - managing risk is clearly the right focus. We do not, however, think the number of breaches is the “wrong” statistic. Since risk is the product of likelihood (number of incidents) and impact, statistics on both parameters are necessary. Concentrating solely on impact or damage quickly leads to a form of decision making we like to call “WIBiHI” (Wouldn’t It Be Horrible If…”) and can often result in gross overspending. As you suggest, managing security based on likelihood, alone, isn’t a winning strategy either.</p>
<p>Keep in mind the original blog post is in response to public reaction to our findings regarding the percentage of breaches involving insiders. We’re not suggesting likelihood is more important than impact (or damage); it’s just that nobody seemed to argue against or misconstrue the latter parameter.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Hawke</title>
		<link>http://securityblog.verizonbusiness.com/2008/07/07/bogus-biased-or-believable/#comment-19</link>
		<dc:creator>Hawke</dc:creator>
		<pubDate>Fri, 11 Jul 2008 15:45:28 +0000</pubDate>
		<guid isPermaLink="false">http://securityblog.verizonbusiness.com/?p=126#comment-19</guid>
		<description>Is number of breaches indider vs. outsider relevant, or are we looking at the wrong statistic.

If I'm managing risk instead of metrics, I want to know the amount of damage (exposure) done by one or the other. The data clearly shows that the insiders _do the most damage_ to an organization in terms of data exposure.

My experience is that it is also more costly to clean up after an insider.</description>
		<content:encoded><![CDATA[<p>Is number of breaches indider vs. outsider relevant, or are we looking at the wrong statistic.</p>
<p>If I&#8217;m managing risk instead of metrics, I want to know the amount of damage (exposure) done by one or the other. The data clearly shows that the insiders _do the most damage_ to an organization in terms of data exposure.</p>
<p>My experience is that it is also more costly to clean up after an insider.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
