<?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: 100%</title>
	<atom:link href="http://spiresecurity.com/?feed=rss2&#038;p=421" rel="self" type="application/rss+xml" />
	<link>http://spiresecurity.com/?p=421</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: Alex Hutton</title>
		<link>http://spiresecurity.com/?p=421&#038;cpage=1#comment-687</link>
		<dc:creator>Alex Hutton</dc:creator>
		<pubDate>Tue, 06 Jun 2006 18:50:15 +0000</pubDate>
		<guid isPermaLink="false">http://spiresecurity.com/blog/?p=421#comment-687</guid>
		<description><![CDATA[I thought about this a little more, and without realizing it, I&#039;m thinking about risk from the perspective of VA.  If you want to think about it from any given Vet, or one of the Vets who actually had their data stolen (two different perspectives to study) - that willingness factor would have to include the number of &quot;identities&quot; we actually expect to be stolen out of the total.  The minimum would be 1, max is what, 240,000? - but what is the most likely?  Let me know what you think and why, and I&#039;ll let you know what I think.

Then we&#039;ll throw out the contact = true part, and use that number as a percentage...
]]></description>
		<content:encoded><![CDATA[<p>I thought about this a little more, and without realizing it, I&#8217;m thinking about risk from the perspective of VA.  If you want to think about it from any given Vet, or one of the Vets who actually had their data stolen (two different perspectives to study) &#8211; that willingness factor would have to include the number of &#8220;identities&#8221; we actually expect to be stolen out of the total.  The minimum would be 1, max is what, 240,000? &#8211; but what is the most likely?  Let me know what you think and why, and I&#8217;ll let you know what I think.</p>
<p>Then we&#8217;ll throw out the contact = true part, and use that number as a percentage&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Alex Hutton</title>
		<link>http://spiresecurity.com/?p=421&#038;cpage=1#comment-686</link>
		<dc:creator>Alex Hutton</dc:creator>
		<pubDate>Tue, 06 Jun 2006 18:14:43 +0000</pubDate>
		<guid isPermaLink="false">http://spiresecurity.com/blog/?p=421#comment-686</guid>
		<description><![CDATA[Good conversation.  I&#039;ve actually been thinking about the subject - but not just ID theft, but % of real compromise for attacks against large amounts of consumers, like Phishing, Bot infection, etc...

If you&#039;re looking for a baseline measurement, we should probably agree on a definition of risk.  I break risk into the following factors: the probable frequency and probable magnitude of loss.  In other words, how much you stand to lose, and how often you&#039;re going to lose it.

I&#039;ve been (un)fortunate enough to be privy to information about a large scale compromise concerning spyware.  Literally thousands of desktops of malware.  It was determined that there was only one instance of the Malware being used at all past the initial infection, and then just a cursory &quot;look around&quot; - no evidence of abuse.  To me, the similarities of the scenarios are interesting - I would guess that the percentage of use of the PII is similar, simply because the level of effort involved to steal from hundreds of thousands of people is so great, not to mention the fact that a smart criminal might figure that if he used more than a certain percentage of those IDs - he&#039;d attract attention.

So my analysis of the subject so far really focuses on aspects of a Threat Community that is interested in inflicting some level of harm using the information.  This, of course, is an assumption. I would love to study the probability that the perp. actually just sold the thing, data and all to a pawn shop or (ahem) associate who blew the contents away and all risk is eliminated.

So when I look at a Threat, I try to estimate a couple of basic things:

1.)  Their Capability, which I break up into a measurement of their skills (knowledge and experience) and resources (time and materials).
2.)  The factors that determine their willingness to act.  In other risk studies, we&#039;ve been using this &quot;willingness&quot; measurement as part of the factors that make up  &quot;Threat Event Frequency&quot;.   TEF is basically how likely it is a threat will act, and part of probability determination on how often we can expect loss.  This willingness I think would  consist of the attackers own determinations of:  a.)  feasibility, a ratio of challenge to the attacker and their (perceived) capability - and b.)  motivation, a function of risk (to them) and reward.

So in an effort for me to give you a &quot;baseline risk&quot; qualification, let me solicit your opinions on the following in percentages from 1-100:

1.)  Threat Capability (assume we&#039;re going to use a threat that is aware that they could use the data on the laptop, not just a quick $200 turn around to go buy some crack).  A rating of 1 would be a complete moron with Windows 3.11 and an IP stack on 14.4, and 99 would be the most elite government agent with government agency resources behind them.  I would assume tons of time to act on their part.

2.)   The frequency with which you would expect them to attack.  Consider this to be a measurement of &quot;willingness&quot;, above.  We don&#039;t need to try to factor in a range for frequency of contact, at this point contact = true.

Once you give me some values for those two factors, we can move onto other factors to consider in the &quot;frequency of loss&quot; part of risk.

Interestingly enough, for the VA or just about any B2C - if you think about magnitude of loss from their perspective, and not the perspective of the consumer, there&#039;s very little loss to consider, IMHO.  Risk to a bank, the VA, Insurance company, hospital, whatever, concerning loss of PII *in a B2C incident* for a large company with plenty of brand equity is pretty low.  The main component of their loss is regulatory fines and judgments, and maybe, just maybe a class action suit.

]]></description>
		<content:encoded><![CDATA[<p>Good conversation.  I&#8217;ve actually been thinking about the subject &#8211; but not just ID theft, but % of real compromise for attacks against large amounts of consumers, like Phishing, Bot infection, etc&#8230;</p>
<p>If you&#8217;re looking for a baseline measurement, we should probably agree on a definition of risk.  I break risk into the following factors: the probable frequency and probable magnitude of loss.  In other words, how much you stand to lose, and how often you&#8217;re going to lose it.</p>
<p>I&#8217;ve been (un)fortunate enough to be privy to information about a large scale compromise concerning spyware.  Literally thousands of desktops of malware.  It was determined that there was only one instance of the Malware being used at all past the initial infection, and then just a cursory &#8220;look around&#8221; &#8211; no evidence of abuse.  To me, the similarities of the scenarios are interesting &#8211; I would guess that the percentage of use of the PII is similar, simply because the level of effort involved to steal from hundreds of thousands of people is so great, not to mention the fact that a smart criminal might figure that if he used more than a certain percentage of those IDs &#8211; he&#8217;d attract attention.</p>
<p>So my analysis of the subject so far really focuses on aspects of a Threat Community that is interested in inflicting some level of harm using the information.  This, of course, is an assumption. I would love to study the probability that the perp. actually just sold the thing, data and all to a pawn shop or (ahem) associate who blew the contents away and all risk is eliminated.</p>
<p>So when I look at a Threat, I try to estimate a couple of basic things:</p>
<p>1.)  Their Capability, which I break up into a measurement of their skills (knowledge and experience) and resources (time and materials).<br />
2.)  The factors that determine their willingness to act.  In other risk studies, we&#8217;ve been using this &#8220;willingness&#8221; measurement as part of the factors that make up  &#8220;Threat Event Frequency&#8221;.   TEF is basically how likely it is a threat will act, and part of probability determination on how often we can expect loss.  This willingness I think would  consist of the attackers own determinations of:  a.)  feasibility, a ratio of challenge to the attacker and their (perceived) capability &#8211; and b.)  motivation, a function of risk (to them) and reward.</p>
<p>So in an effort for me to give you a &#8220;baseline risk&#8221; qualification, let me solicit your opinions on the following in percentages from 1-100:</p>
<p>1.)  Threat Capability (assume we&#8217;re going to use a threat that is aware that they could use the data on the laptop, not just a quick $200 turn around to go buy some crack).  A rating of 1 would be a complete moron with Windows 3.11 and an IP stack on 14.4, and 99 would be the most elite government agent with government agency resources behind them.  I would assume tons of time to act on their part.</p>
<p>2.)   The frequency with which you would expect them to attack.  Consider this to be a measurement of &#8220;willingness&#8221;, above.  We don&#8217;t need to try to factor in a range for frequency of contact, at this point contact = true.</p>
<p>Once you give me some values for those two factors, we can move onto other factors to consider in the &#8220;frequency of loss&#8221; part of risk.</p>
<p>Interestingly enough, for the VA or just about any B2C &#8211; if you think about magnitude of loss from their perspective, and not the perspective of the consumer, there&#8217;s very little loss to consider, IMHO.  Risk to a bank, the VA, Insurance company, hospital, whatever, concerning loss of PII *in a B2C incident* for a large company with plenty of brand equity is pretty low.  The main component of their loss is regulatory fines and judgments, and maybe, just maybe a class action suit.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Spire Security Viewpoint</title>
		<link>http://spiresecurity.com/?p=421&#038;cpage=1#comment-688</link>
		<dc:creator>Spire Security Viewpoint</dc:creator>
		<pubDate>Fri, 02 Jun 2006 18:36:34 +0000</pubDate>
		<guid isPermaLink="false">http://spiresecurity.com/blog/?p=421#comment-688</guid>
		<description><![CDATA[&lt;strong&gt;100% Followup&lt;/strong&gt;

My post about the VA Fiasco of losing 26 million personal records (including mine) has struck a chord with some. I thought I would take the time to clarify some things: 1. Emergent Chaos posted a specific response in The Persistence of SSNs, and The Pe...
]]></description>
		<content:encoded><![CDATA[<p><strong>100% Followup</strong></p>
<p>My post about the VA Fiasco of losing 26 million personal records (including mine) has struck a chord with some. I thought I would take the time to clarify some things: 1. Emergent Chaos posted a specific response in The Persistence of SSNs, and The Pe&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Michael R. Farnum</title>
		<link>http://spiresecurity.com/?p=421&#038;cpage=1#comment-685</link>
		<dc:creator>Michael R. Farnum</dc:creator>
		<pubDate>Fri, 02 Jun 2006 16:54:30 +0000</pubDate>
		<guid isPermaLink="false">http://spiresecurity.com/blog/?p=421#comment-685</guid>
		<description><![CDATA[I think it is more than obvious that the actual percentage chance that I, as a veteran, will get hit with ID theft because of this is low.  That has never been the issue.  The issue is that there are 26 million veterans who now have their ID floating around somewhere, and it was a preventable event.  The sheer stupidity and cluelessness of the VA to not have something in place to prevent this type of problem is the real issue.  If someone is creating FUD around this, then shame on them.  But don&#039;t discount that this is a real problem that needs to be fixed.  By saying that the percentage chance is low is (to some people) tantamount to saying this theft is no big deal and we shouldn&#039;t worry about it.

The VA is making changes, and that is good.  But don&#039;t you think your comments could cause some people to relax and reduce the pressure on elected officials and the VA to make something happen to fix this? This DOES NOT need to disappear, whcih is what I am afraid will happen if people start producing arguments such as yours.
]]></description>
		<content:encoded><![CDATA[<p>I think it is more than obvious that the actual percentage chance that I, as a veteran, will get hit with ID theft because of this is low.  That has never been the issue.  The issue is that there are 26 million veterans who now have their ID floating around somewhere, and it was a preventable event.  The sheer stupidity and cluelessness of the VA to not have something in place to prevent this type of problem is the real issue.  If someone is creating FUD around this, then shame on them.  But don&#8217;t discount that this is a real problem that needs to be fixed.  By saying that the percentage chance is low is (to some people) tantamount to saying this theft is no big deal and we shouldn&#8217;t worry about it.</p>
<p>The VA is making changes, and that is good.  But don&#8217;t you think your comments could cause some people to relax and reduce the pressure on elected officials and the VA to make something happen to fix this? This DOES NOT need to disappear, whcih is what I am afraid will happen if people start producing arguments such as yours.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Emergent Chaos</title>
		<link>http://spiresecurity.com/?p=421&#038;cpage=1#comment-689</link>
		<dc:creator>Emergent Chaos</dc:creator>
		<pubDate>Fri, 02 Jun 2006 16:42:18 +0000</pubDate>
		<guid isPermaLink="false">http://spiresecurity.com/blog/?p=421#comment-689</guid>
		<description><![CDATA[&lt;strong&gt;The Persistence of SSNs, and The Persistence of Theives&lt;/strong&gt;

Pete Lindstrom, who knows a good phrase when he reads one, puts forward the claim that the theft of veterans SSNs doesn&#039;t put them at increased risk of fraud. His basic argument is that there&#039;s a lot of people out...
]]></description>
		<content:encoded><![CDATA[<p><strong>The Persistence of SSNs, and The Persistence of Theives</strong></p>
<p>Pete Lindstrom, who knows a good phrase when he reads one, puts forward the claim that the theft of veterans SSNs doesn&#8217;t put them at increased risk of fraud. His basic argument is that there&#8217;s a lot of people out&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Security Incite: Analysis on Information Security</title>
		<link>http://spiresecurity.com/?p=421&#038;cpage=1#comment-690</link>
		<dc:creator>Security Incite: Analysis on Information Security</dc:creator>
		<pubDate>Fri, 02 Jun 2006 05:45:30 +0000</pubDate>
		<guid isPermaLink="false">http://spiresecurity.com/blog/?p=421#comment-690</guid>
		<description><![CDATA[&lt;strong&gt;The Daily Incite - June 2, 2006&lt;/strong&gt;

June 2, 2006  Good Morning:  First Ill apologize for my lack of blogging this week. Being on the west coast did not give me a lot of time to do much besides meet with folks and do The Daily Incite. But Ill be back in the office next week, so
]]></description>
		<content:encoded><![CDATA[<p><strong>The Daily Incite &#8211; June 2, 2006</strong></p>
<p>June 2, 2006  Good Morning:  First Ill apologize for my lack of blogging this week. Being on the west coast did not give me a lot of time to do much besides meet with folks and do The Daily Incite. But Ill be back in the office next week, so</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Pete</title>
		<link>http://spiresecurity.com/?p=421&#038;cpage=1#comment-684</link>
		<dc:creator>Pete</dc:creator>
		<pubDate>Thu, 01 Jun 2006 10:21:40 +0000</pubDate>
		<guid isPermaLink="false">http://spiresecurity.com/blog/?p=421#comment-684</guid>
		<description><![CDATA[@Chris -

It&#039;s not kooky talk - in fact, I agreed in my posting that risk is *likely* increased simply by having more people with access to these SSNs, though I disagree strongly that this applies solely to &quot;unauthorized&quot; people given that the vast majority of identity fraud comes from &quot;authorized&quot; people. Let&#039;s face it - there are plenty of ways for an identity thief to get SSNs and other PII that are much less risky than breaking into somebody&#039;s house.

What I am suggesting is that the absolute level of increased risk is likely very, very, low. That is, if a typical account has 150,000 people with access and now there are 150,005 (or even 150,100 for that matter) even having an extra 100 people with access is not going to change the risk equation that much.

Your point about unintended positive consequences is an interesting one - not one I&#039;ve seen brought up simply on its merits before. Your idea is a good one: that loss like this may actually reduce identity theft. Now, whether or not it justifies the FUD is an interesting question...

(Btw, this incident has potentially more serious consequences than identity theft that we probably should be looking at closely).
]]></description>
		<content:encoded><![CDATA[<p>@Chris -</p>
<p>It&#8217;s not kooky talk &#8211; in fact, I agreed in my posting that risk is *likely* increased simply by having more people with access to these SSNs, though I disagree strongly that this applies solely to &#8220;unauthorized&#8221; people given that the vast majority of identity fraud comes from &#8220;authorized&#8221; people. Let&#8217;s face it &#8211; there are plenty of ways for an identity thief to get SSNs and other PII that are much less risky than breaking into somebody&#8217;s house.</p>
<p>What I am suggesting is that the absolute level of increased risk is likely very, very, low. That is, if a typical account has 150,000 people with access and now there are 150,005 (or even 150,100 for that matter) even having an extra 100 people with access is not going to change the risk equation that much.</p>
<p>Your point about unintended positive consequences is an interesting one &#8211; not one I&#8217;ve seen brought up simply on its merits before. Your idea is a good one: that loss like this may actually reduce identity theft. Now, whether or not it justifies the FUD is an interesting question&#8230;</p>
<p>(Btw, this incident has potentially more serious consequences than identity theft that we probably should be looking at closely).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chris Walsh</title>
		<link>http://spiresecurity.com/?p=421&#038;cpage=1#comment-683</link>
		<dc:creator>Chris Walsh</dc:creator>
		<pubDate>Thu, 01 Jun 2006 02:30:33 +0000</pubDate>
		<guid isPermaLink="false">http://spiresecurity.com/blog/?p=421#comment-683</guid>
		<description><![CDATA[But Pete -

The whole reason the risk is hypothesized to be increased is that now more people know these 26.5 million SSNs.  Surely it isn&#039;t kooky talk to say that the more unauthorized people that know your PII, the higher the probability it will be misused?

However, your idea about looking at the ID theft rate and determining the increased risk after the fact may not work because the Vets may change their behavior.  For example, large numbers may put freezes on their credit reports.  It may turn out, as a result, that FEWER of them wind up getting hit by an actual ID theft.  To really figure this out, we need to have a good deal more info, and right now I don&#039;t think much of it is being collected.

]]></description>
		<content:encoded><![CDATA[<p>But Pete -</p>
<p>The whole reason the risk is hypothesized to be increased is that now more people know these 26.5 million SSNs.  Surely it isn&#8217;t kooky talk to say that the more unauthorized people that know your PII, the higher the probability it will be misused?</p>
<p>However, your idea about looking at the ID theft rate and determining the increased risk after the fact may not work because the Vets may change their behavior.  For example, large numbers may put freezes on their credit reports.  It may turn out, as a result, that FEWER of them wind up getting hit by an actual ID theft.  To really figure this out, we need to have a good deal more info, and right now I don&#8217;t think much of it is being collected.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
