<?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: A Primer on Risk Quantification</title>
	<atom:link href="http://spiresecurity.com/?feed=rss2&#038;p=58" rel="self" type="application/rss+xml" />
	<link>http://spiresecurity.com/?p=58</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: Sem'on</title>
		<link>http://spiresecurity.com/?p=58&#038;cpage=1#comment-58</link>
		<dc:creator>Sem'on</dc:creator>
		<pubDate>Sat, 05 Sep 2009 11:21:55 +0000</pubDate>
		<guid isPermaLink="false">http://spiresecurity.com/blog/?p=58#comment-58</guid>
		<description><![CDATA[Greeting. So many of our dreams at first seem impossible, then they seem improbable, and then, when we summon the will, they soon become inevitable.
I am from Azerbaijan and now teach English, tell me right I wrote the following sentence: &quot;Dave and lisa transplantation over a northeastern show.&quot;

Thank 8) Sem&#039;on.
]]></description>
		<content:encoded><![CDATA[<p>Greeting. So many of our dreams at first seem impossible, then they seem improbable, and then, when we summon the will, they soon become inevitable.<br />
I am from Azerbaijan and now teach English, tell me right I wrote the following sentence: &#8220;Dave and lisa transplantation over a northeastern show.&#8221;</p>
<p>Thank 8) Sem&#8217;on.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Spire Security Viewpoint</title>
		<link>http://spiresecurity.com/?p=58&#038;cpage=1#comment-59</link>
		<dc:creator>Spire Security Viewpoint</dc:creator>
		<pubDate>Thu, 30 Apr 2009 17:56:21 +0000</pubDate>
		<guid isPermaLink="false">http://spiresecurity.com/blog/?p=58#comment-59</guid>
		<description><![CDATA[&lt;strong&gt;There is no risk in Pseudo-Risk&lt;/strong&gt;

The folks at Verizon are doing a great job with their Data Breach Investigation Reports. Their latest edition is their second and it warrants a thorough review. My biggest concern involves their &quot;pseudo-risk&quot; calculation. Regardless of whether it is pr...
]]></description>
		<content:encoded><![CDATA[<p><strong>There is no risk in Pseudo-Risk</strong></p>
<p>The folks at Verizon are doing a great job with their Data Breach Investigation Reports. Their latest edition is their second and it warrants a thorough review. My biggest concern involves their &#8220;pseudo-risk&#8221; calculation. Regardless of whether it is pr&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Pete</title>
		<link>http://spiresecurity.com/?p=58&#038;cpage=1#comment-57</link>
		<dc:creator>Pete</dc:creator>
		<pubDate>Tue, 28 Apr 2009 12:24:53 +0000</pubDate>
		<guid isPermaLink="false">http://spiresecurity.com/blog/?p=58#comment-57</guid>
		<description><![CDATA[Yes, consequences are necessary to &quot;frame&quot; the likelihood statement and make it a risk statement. I believe we are in agreement.

Now, on to &quot;pseudo-risk&quot;... ;-)

Pete
]]></description>
		<content:encoded><![CDATA[<p>Yes, consequences are necessary to &#8220;frame&#8221; the likelihood statement and make it a risk statement. I believe we are in agreement.</p>
<p>Now, on to &#8220;pseudo-risk&#8221;&#8230; <img src='http://spiresecurity.com/blog/wp-includes/images/smilies/icon_wink.gif' alt=';-)' class='wp-smiley' /> </p>
<p>Pete</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jack</title>
		<link>http://spiresecurity.com/?p=58&#038;cpage=1#comment-56</link>
		<dc:creator>Jack</dc:creator>
		<pubDate>Tue, 28 Apr 2009 00:16:23 +0000</pubDate>
		<guid isPermaLink="false">http://spiresecurity.com/blog/?p=58#comment-56</guid>
		<description><![CDATA[@Pete

You&#039;re right.  A &quot;qualified&quot; consequence statement can be very useful.  You said early in the post, however, that frequency was the only necessary component, which was what I was disagreeing with.

So, are we in agreement that some statement of consequence significance is necessary for a risk statement?

Thanks,
Jack


]]></description>
		<content:encoded><![CDATA[<p>@Pete</p>
<p>You&#8217;re right.  A &#8220;qualified&#8221; consequence statement can be very useful.  You said early in the post, however, that frequency was the only necessary component, which was what I was disagreeing with.</p>
<p>So, are we in agreement that some statement of consequence significance is necessary for a risk statement?</p>
<p>Thanks,<br />
Jack</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Pete</title>
		<link>http://spiresecurity.com/?p=58&#038;cpage=1#comment-55</link>
		<dc:creator>Pete</dc:creator>
		<pubDate>Mon, 27 Apr 2009 13:39:27 +0000</pubDate>
		<guid isPermaLink="false">http://spiresecurity.com/blog/?p=58#comment-55</guid>
		<description><![CDATA[@Jack -

I think we are getting ahead of ourselves here... Don&#039;t forget that qualitative risk analysis is alive and well and employ risk statements all the time.

I don&#039;t see how the info provided above and also books such as &quot;Calculated Risks&quot; by Gerd Gigerenzer and &quot;Risk!&quot; from the folks at the Harvard Center for Risk Analysis can all have it wrong. They rarely, if ever, quantify consequences.
]]></description>
		<content:encoded><![CDATA[<p>@Jack -</p>
<p>I think we are getting ahead of ourselves here&#8230; Don&#8217;t forget that qualitative risk analysis is alive and well and employ risk statements all the time.</p>
<p>I don&#8217;t see how the info provided above and also books such as &#8220;Calculated Risks&#8221; by Gerd Gigerenzer and &#8220;Risk!&#8221; from the folks at the Harvard Center for Risk Analysis can all have it wrong. They rarely, if ever, quantify consequences.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jack</title>
		<link>http://spiresecurity.com/?p=58&#038;cpage=1#comment-54</link>
		<dc:creator>Jack</dc:creator>
		<pubDate>Sat, 25 Apr 2009 13:42:02 +0000</pubDate>
		<guid isPermaLink="false">http://spiresecurity.com/blog/?p=58#comment-54</guid>
		<description><![CDATA[BTW -- quantification of consequences provides the &quot;so what&quot; within an analysis.  Absent that, people will infer their own expectations/beliefs about consequence, which often will vary based upon their individual biases and levels of understanding.
]]></description>
		<content:encoded><![CDATA[<p>BTW &#8212; quantification of consequences provides the &#8220;so what&#8221; within an analysis.  Absent that, people will infer their own expectations/beliefs about consequence, which often will vary based upon their individual biases and levels of understanding.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jack</title>
		<link>http://spiresecurity.com/?p=58&#038;cpage=1#comment-53</link>
		<dc:creator>Jack</dc:creator>
		<pubDate>Sat, 25 Apr 2009 12:25:11 +0000</pubDate>
		<guid isPermaLink="false">http://spiresecurity.com/blog/?p=58#comment-53</guid>
		<description><![CDATA[@Pete

I guess I misunderstood your question.  Sorry.

I can&#039;t argue with the notion of not quantifying consequences -- but it isn&#039;t then a risk statement.  It&#039;s a likelihood/frequency statement, and they aren&#039;t the same thing.  Without at least roughly quantified consequences, we can&#039;t understand the true significance of an issue.  We also sure as heck can&#039;t compare the significance of on issue where consequences have been quantified with one where it hasn&#039;t.

Thanks,
Jack


]]></description>
		<content:encoded><![CDATA[<p>@Pete</p>
<p>I guess I misunderstood your question.  Sorry.</p>
<p>I can&#8217;t argue with the notion of not quantifying consequences &#8212; but it isn&#8217;t then a risk statement.  It&#8217;s a likelihood/frequency statement, and they aren&#8217;t the same thing.  Without at least roughly quantified consequences, we can&#8217;t understand the true significance of an issue.  We also sure as heck can&#8217;t compare the significance of on issue where consequences have been quantified with one where it hasn&#8217;t.</p>
<p>Thanks,<br />
Jack</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Pete</title>
		<link>http://spiresecurity.com/?p=58&#038;cpage=1#comment-52</link>
		<dc:creator>Pete</dc:creator>
		<pubDate>Sat, 25 Apr 2009 03:40:53 +0000</pubDate>
		<guid isPermaLink="false">http://spiresecurity.com/blog/?p=58#comment-52</guid>
		<description><![CDATA[@Jack -

You don&#039;t really answer my question, but I agree with your allusion that there are varying magnitudes of consequences that are worth paying attention to.

I think we are much more likely to ignore the likelihood, not the consequence.

I guess I should continue to repeat myself that I think quantifying consequences is better than not doing it, but I think it is still legitimate not to do it.

Thanks,

Pete
]]></description>
		<content:encoded><![CDATA[<p>@Jack -</p>
<p>You don&#8217;t really answer my question, but I agree with your allusion that there are varying magnitudes of consequences that are worth paying attention to.</p>
<p>I think we are much more likely to ignore the likelihood, not the consequence.</p>
<p>I guess I should continue to repeat myself that I think quantifying consequences is better than not doing it, but I think it is still legitimate not to do it.</p>
<p>Thanks,</p>
<p>Pete</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jack</title>
		<link>http://spiresecurity.com/?p=58&#038;cpage=1#comment-51</link>
		<dc:creator>Jack</dc:creator>
		<pubDate>Fri, 24 Apr 2009 01:35:01 +0000</pubDate>
		<guid isPermaLink="false">http://spiresecurity.com/blog/?p=58#comment-51</guid>
		<description><![CDATA[@Pete

Perhaps here&#039;s an answer to your question about the medical use-case:  Not all heart attacks are fatal, not all cancer kills.  Our industry&#039;s tendency to avoid quantification of consequence, and often to assume worst-case, is a key contributor to our &quot;chicken little&quot; image.

As for how to arrive at a well-reasoned probable loss magnitude estimate, there are methods and principles that make it feasible -- and not as difficult as we tend to make it out to be.  For one thing, you need to get the appropriate SME&#039;s involved (and they ain&#039;t the infosec team).  It also helps to use an effective taxonomy for loss.  Last but not least, there&#039;s more data available than we tend to recognize -- you just need to know where to look (which the taxonomy helps with).  Will the estimates be precise?  No.  Will they be accurate and useful?  Yes.

Thanks,
Jack




]]></description>
		<content:encoded><![CDATA[<p>@Pete</p>
<p>Perhaps here&#8217;s an answer to your question about the medical use-case:  Not all heart attacks are fatal, not all cancer kills.  Our industry&#8217;s tendency to avoid quantification of consequence, and often to assume worst-case, is a key contributor to our &#8220;chicken little&#8221; image.</p>
<p>As for how to arrive at a well-reasoned probable loss magnitude estimate, there are methods and principles that make it feasible &#8212; and not as difficult as we tend to make it out to be.  For one thing, you need to get the appropriate SME&#8217;s involved (and they ain&#8217;t the infosec team).  It also helps to use an effective taxonomy for loss.  Last but not least, there&#8217;s more data available than we tend to recognize &#8212; you just need to know where to look (which the taxonomy helps with).  Will the estimates be precise?  No.  Will they be accurate and useful?  Yes.</p>
<p>Thanks,<br />
Jack</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Pete</title>
		<link>http://spiresecurity.com/?p=58&#038;cpage=1#comment-50</link>
		<dc:creator>Pete</dc:creator>
		<pubDate>Fri, 24 Apr 2009 00:26:59 +0000</pubDate>
		<guid isPermaLink="false">http://spiresecurity.com/blog/?p=58#comment-50</guid>
		<description><![CDATA[@Brooke -

Yours is certainly a reasonable opinion to have, but I wonder if you are a victim of your own experience. The literature on risk is much, much broader than simply its use in insurance, so why must everyone conform to your model?

I should note that I agree that quantifying losses in dollars (or other currency) is more beneficial, however, there are many skeptics in the infosec world that believe information asset value (and corresponding losses) cannot be quantified very well.

I would love to understand whether you think the medical community is using the term incorrectly when they talk about, for example, the risk of heart attack.

Neither you nor Chris have addressed this use case.

Thanks,

Pete

[Btw, what does profit have to do with this issue?]
]]></description>
		<content:encoded><![CDATA[<p>@Brooke -</p>
<p>Yours is certainly a reasonable opinion to have, but I wonder if you are a victim of your own experience. The literature on risk is much, much broader than simply its use in insurance, so why must everyone conform to your model?</p>
<p>I should note that I agree that quantifying losses in dollars (or other currency) is more beneficial, however, there are many skeptics in the infosec world that believe information asset value (and corresponding losses) cannot be quantified very well.</p>
<p>I would love to understand whether you think the medical community is using the term incorrectly when they talk about, for example, the risk of heart attack.</p>
<p>Neither you nor Chris have addressed this use case.</p>
<p>Thanks,</p>
<p>Pete</p>
<p>[Btw, what does profit have to do with this issue?]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
