<?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/"
	xmlns:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd"
	>
<channel>
	<title>Comments on: Selective Notification</title>
	<atom:link href="http://www.securitycatalyst.com/selective-notification/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.securitycatalyst.com/selective-notification/</link>
	<description>Michael Santarcangelo turns insiders into allies who reduce business risk</description>
	<lastBuildDate>Wed, 17 Feb 2010 03:27:05 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: The Security Catalyst &#187; In Defense of Breach Notification Laws (sort of)</title>
		<link>http://www.securitycatalyst.com/selective-notification/comment-page-1/#comment-382</link>
		<dc:creator>The Security Catalyst &#187; In Defense of Breach Notification Laws (sort of)</dc:creator>
		<pubDate>Thu, 18 Dec 2008 14:22:40 +0000</pubDate>
		<guid isPermaLink="false">http://www.securitycatalyst.com/blog/?p=548#comment-382</guid>
		<description>[...] five years of breach notification law experience, it is essential to ask, &#8220;Are they working?&#8221; My shorthand answer is &#8220;yes, sort [...]</description>
		<content:encoded><![CDATA[<p>[...] five years of breach notification law experience, it is essential to ask, &#8220;Are they working?&#8221; My shorthand answer is &#8220;yes, sort [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: benjaminwright</title>
		<link>http://www.securitycatalyst.com/selective-notification/comment-page-1/#comment-379</link>
		<dc:creator>benjaminwright</dc:creator>
		<pubDate>Sat, 25 Oct 2008 16:53:05 +0000</pubDate>
		<guid isPermaLink="false">http://www.securitycatalyst.com/blog/?p=548#comment-379</guid>
		<description>Aaron:

I admire your honest, hard work in this area!  I have a point of view that is different from yours, and I&#039;ll express some of it here.  But as I do so I admit that I don&#039;t know everything, and I do not claim my judgment is flawless.

My feeling is that these breach notices and announcements have little if any practical effect in the battle against identity theft.  They are an exercise in politics.  On the whole, they are just noise.  And thus, we have companies like Anheuser-Busch giving notice in New Hampshire about encrypted data on a stolen laptop, even though New Hampshire law does not require notice if data are encrypted. &lt;a href=&quot;http://legal-beagle.typepad.com/wrights_legal_beagle/2008/08/encrypted-perso.html&quot; rel=&quot;nofollow&quot;&gt;http://legal-beagle.typepad.com/wrights_legal_beagle/2008/08/encrypted-perso.html&lt;/a&gt;

If firms must give notice about encrypted data, then every firm should transmit multiple notices to all its consumers &amp; constituents every day.  That would be ridiculous.

My feeling is that the breach-notice/announcement noise distracts and confuses the public.  A premise behind notices &amp; announcements is that a consumer should be on special alert (take special precautions, monitor her credit report more carefully and so on) when her data are the subject of a notice or announcement.  I believe that premise is wrong . . . and harmful for two reasons:

1.  All personally identifiable data have been exposed numerous times and are at serious risk of further exposure, virtually all the time.  A consumer&#039;s data reside in innumerable records scattered all over the globe.  The number of ways for bad guys to access that data are infinite.  Modern information technology, viewed as a whole global system, is incapable of effectively preventing bad guys from accessing the data.  The technology for system-wide access denial does not exist.  Therefore: the well-informed consumer must operate on the assumption that all of her data are exposed all the time. She should be on red alert for identity theft every, single day.

2.  The fact that a given consumer has received no notice of breach, and can find no public announcement of breach by someone she does business with, is meaningless to her.  The fact that a consumer has heard nothing about a breach should give her absolutely zero comfort.  She should be on utter red alert for identity theft every day.  Thus, her receipt of a notice about a breach should change nothing for her.  The notice is just noise.

I argue we need different thinking about identity theft.  &lt;a href=&quot;http://legal-beagle.typepad.com/wrights_legal_beagle/2008/08/credit-card-iss.html&quot; rel=&quot;nofollow&quot;&gt;http://legal-beagle.typepad.com/wrights_legal_beagle/2008/08/credit-card-iss.html&lt;/a&gt;

I&#039;d be honored to hear more of what you think, Aaron.

–Ben</description>
		<content:encoded><![CDATA[<p>Aaron:</p>
<p>I admire your honest, hard work in this area!  I have a point of view that is different from yours, and I&#8217;ll express some of it here.  But as I do so I admit that I don&#8217;t know everything, and I do not claim my judgment is flawless.</p>
<p>My feeling is that these breach notices and announcements have little if any practical effect in the battle against identity theft.  They are an exercise in politics.  On the whole, they are just noise.  And thus, we have companies like Anheuser-Busch giving notice in New Hampshire about encrypted data on a stolen laptop, even though New Hampshire law does not require notice if data are encrypted. <a href="http://legal-beagle.typepad.com/wrights_legal_beagle/2008/08/encrypted-perso.html" rel="nofollow">http://legal-beagle.typepad.com/wrights_legal_beagle/2008/08/encrypted-perso.html</a></p>
<p>If firms must give notice about encrypted data, then every firm should transmit multiple notices to all its consumers &amp; constituents every day.  That would be ridiculous.</p>
<p>My feeling is that the breach-notice/announcement noise distracts and confuses the public.  A premise behind notices &amp; announcements is that a consumer should be on special alert (take special precautions, monitor her credit report more carefully and so on) when her data are the subject of a notice or announcement.  I believe that premise is wrong . . . and harmful for two reasons:</p>
<p>1.  All personally identifiable data have been exposed numerous times and are at serious risk of further exposure, virtually all the time.  A consumer&#8217;s data reside in innumerable records scattered all over the globe.  The number of ways for bad guys to access that data are infinite.  Modern information technology, viewed as a whole global system, is incapable of effectively preventing bad guys from accessing the data.  The technology for system-wide access denial does not exist.  Therefore: the well-informed consumer must operate on the assumption that all of her data are exposed all the time. She should be on red alert for identity theft every, single day.</p>
<p>2.  The fact that a given consumer has received no notice of breach, and can find no public announcement of breach by someone she does business with, is meaningless to her.  The fact that a consumer has heard nothing about a breach should give her absolutely zero comfort.  She should be on utter red alert for identity theft every day.  Thus, her receipt of a notice about a breach should change nothing for her.  The notice is just noise.</p>
<p>I argue we need different thinking about identity theft.  <a href="http://legal-beagle.typepad.com/wrights_legal_beagle/2008/08/credit-card-iss.html" rel="nofollow">http://legal-beagle.typepad.com/wrights_legal_beagle/2008/08/credit-card-iss.html</a></p>
<p>I&#8217;d be honored to hear more of what you think, Aaron.</p>
<p>–Ben</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: aaron.titus</title>
		<link>http://www.securitycatalyst.com/selective-notification/comment-page-1/#comment-381</link>
		<dc:creator>aaron.titus</dc:creator>
		<pubDate>Fri, 24 Oct 2008 21:17:35 +0000</pubDate>
		<guid isPermaLink="false">http://www.securitycatalyst.com/blog/?p=548#comment-381</guid>
		<description>Ben:  I think you&#039;re right, but that there are two issues here.  I think that breach notifications serve at least two purposes.  The first is to (hopefully) embarass organizations into not making breaches.  The second is to empower victims of breaches.  Breach notifications are woefully deficient on both accounts.

I will make two initial observations about the effect of breach notification laws on organizations: 1. Breach notification laws do not appear to have embarassed organizations into being careful.  2. My personal experience tells me that breaches are under-reported (ie, many are never reported).

On victims, you are correct to point out that breach notifications are not very effective at empowering victims for a few of reasons: 1. Most people never hear about the breach because they miss the press release. 2. Even if they hear about the breach, they may not self-identify as a victim. 3. Even if they hear about the breach and self-identify themselves as a victim, they won&#039;t get the whole story because the press release was issued by the organization with the most incentive to hide or skew the facts. 4. They do not accurately describe the actual risk of any given breach.

That&#039;s why I created &lt;a href=&quot;http://www.ssnbreach.org&quot; rel=&quot;nofollow&quot;&gt;ssnbreach.org&lt;/a&gt;.  There, I document individual &quot;Identity Exposure Reports&quot; (here is an &lt;a href=&quot;https://ssnbreach.org/search.php?action=showInd&amp;iid=288083&quot; rel=&quot;nofollow&quot;&gt;example IXR&lt;/a&gt;). Here are the purposes: 1. I write a press release explaining exactly what happened, what pieces of information were exposed (the database does not contain sensitive personal information), how it happened, when, who is responsible, and how to contact the responsible person.  2. Individuals can effectively self-identify. 3. They get the whole story and are able to measure their own subjective risks.  For example, for most people, a breach of an address is not a big deal and is not covered by any breach notification laws.  However, a breach of an address is important for someone with an abusive boyfriend to know whether her address has been breached.

I have also developed four rough indicators of breach severity: &lt;strong&gt;Sensitivity, Duration, Distribution, and Size&lt;/strong&gt;.  For example, a backup tape with SSNs, DOBs, and creditcard numbers which was lost in the mail, and then found on a mail truck the following week may have the following severity indicators:
Sensitivity: Extreme (ie, the information breached is objectively sensitive)
Duration: Less than One Week
Distribution: No Known Access
Size: 1.2 Million Records

So in this case we have a breach of massive proportion and extremely sensitive data, but the objective risks of actual harm are very low because the duration and distribution factors mitigate the potential for loss.  From an individual&#039;s standpoint, the size of the breach doesn&#039;t really matter in determining personal risk, but may have legal consequenses (and make for better headlines).

Though there are many additional ways to sub-categorize breaches, I have found that this way is efficient and understandable, and would solve many of the problems with notifications in general.  What do you think?</description>
		<content:encoded><![CDATA[<p>Ben:  I think you&#8217;re right, but that there are two issues here.  I think that breach notifications serve at least two purposes.  The first is to (hopefully) embarass organizations into not making breaches.  The second is to empower victims of breaches.  Breach notifications are woefully deficient on both accounts.</p>
<p>I will make two initial observations about the effect of breach notification laws on organizations: 1. Breach notification laws do not appear to have embarassed organizations into being careful.  2. My personal experience tells me that breaches are under-reported (ie, many are never reported).</p>
<p>On victims, you are correct to point out that breach notifications are not very effective at empowering victims for a few of reasons: 1. Most people never hear about the breach because they miss the press release. 2. Even if they hear about the breach, they may not self-identify as a victim. 3. Even if they hear about the breach and self-identify themselves as a victim, they won&#8217;t get the whole story because the press release was issued by the organization with the most incentive to hide or skew the facts. 4. They do not accurately describe the actual risk of any given breach.</p>
<p>That&#8217;s why I created <a href="http://www.ssnbreach.org" rel="nofollow">ssnbreach.org</a>.  There, I document individual &#8220;Identity Exposure Reports&#8221; (here is an <a href="https://ssnbreach.org/search.php?action=showInd&amp;iid=288083" rel="nofollow">example IXR</a>). Here are the purposes: 1. I write a press release explaining exactly what happened, what pieces of information were exposed (the database does not contain sensitive personal information), how it happened, when, who is responsible, and how to contact the responsible person.  2. Individuals can effectively self-identify. 3. They get the whole story and are able to measure their own subjective risks.  For example, for most people, a breach of an address is not a big deal and is not covered by any breach notification laws.  However, a breach of an address is important for someone with an abusive boyfriend to know whether her address has been breached.</p>
<p>I have also developed four rough indicators of breach severity: <strong>Sensitivity, Duration, Distribution, and Size</strong>.  For example, a backup tape with SSNs, DOBs, and creditcard numbers which was lost in the mail, and then found on a mail truck the following week may have the following severity indicators:<br />
Sensitivity: Extreme (ie, the information breached is objectively sensitive)<br />
Duration: Less than One Week<br />
Distribution: No Known Access<br />
Size: 1.2 Million Records</p>
<p>So in this case we have a breach of massive proportion and extremely sensitive data, but the objective risks of actual harm are very low because the duration and distribution factors mitigate the potential for loss.  From an individual&#8217;s standpoint, the size of the breach doesn&#8217;t really matter in determining personal risk, but may have legal consequenses (and make for better headlines).</p>
<p>Though there are many additional ways to sub-categorize breaches, I have found that this way is efficient and understandable, and would solve many of the problems with notifications in general.  What do you think?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: benjaminwright</title>
		<link>http://www.securitycatalyst.com/selective-notification/comment-page-1/#comment-380</link>
		<dc:creator>benjaminwright</dc:creator>
		<pubDate>Fri, 24 Oct 2008 14:22:40 +0000</pubDate>
		<guid isPermaLink="false">http://www.securitycatalyst.com/blog/?p=548#comment-380</guid>
		<description>Aaron: Data breach notices have a scalability problem. As the number of notices soars, we need to better define what is a serious breach and what is not. Otherwise, the public drowns in breach notices, many of which are insignificant. --Ben &lt;a href=&quot;http://hack-igations.blogspot.com/2007/12/does-lost-tape-equate-to-lost-data.html&quot; rel=&quot;nofollow&quot;&gt;http://hack-igations.blogspot.com/2007/12/does-lost-tape-equate-to-lost-data.html&lt;/a&gt;</description>
		<content:encoded><![CDATA[<p>Aaron: Data breach notices have a scalability problem. As the number of notices soars, we need to better define what is a serious breach and what is not. Otherwise, the public drowns in breach notices, many of which are insignificant. &#8211;Ben <a href="http://hack-igations.blogspot.com/2007/12/does-lost-tape-equate-to-lost-data.html" rel="nofollow">http://hack-igations.blogspot.com/2007/12/does-lost-tape-equate-to-lost-data.html</a></p>
]]></content:encoded>
	</item>
</channel>
</rss>
