<?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: 2008 Data Breach Investigations Report</title>
	<atom:link href="http://securityblog.verizonbusiness.com/2008/06/10/2008-data-breach-investigations-report/feed/" rel="self" type="application/rss+xml" />
	<link>http://securityblog.verizonbusiness.com/2008/06/10/2008-data-breach-investigations-report/</link>
	<description>Risk Intelligence from Verizon Business Security Solutions powered by Cybertrust</description>
	<pubDate>Wed, 03 Dec 2008 21:43:49 +0000</pubDate>
	<generator>http://wordpress.org/?v=</generator>
		<item>
		<title>By: Russ Cooper</title>
		<link>http://securityblog.verizonbusiness.com/2008/06/10/2008-data-breach-investigations-report/#comment-31</link>
		<dc:creator>Russ Cooper</dc:creator>
		<pubDate>Thu, 07 Aug 2008 16:37:19 +0000</pubDate>
		<guid isPermaLink="false">http://securityblog.verizonbusiness.com/?p=80#comment-31</guid>
		<description>Kyle,

Given that there are absolutely no known's in "unknown unknown", speculating that anything represents the majority of those cases is, well, wild speculation. Honestly, its as likely to be use of graphic card memory for tools or violation of VM boundaries. It could be anything.

Also, from a risk calculation perspective, the simple cost of purchasing drives, let alone drives from Nigeria, would make this an unlikely option for criminals. It’s far easier to compromise a system electronically via no-cost bots across no-cost network links than to purchase anything from anywhere.

Regardless whether you agree that IT disposal represents the "biggest hidden risk," it does represent a risk that should be considered. Local disposal (or loss via 3rd parties) of unencrypted data tapes has been widely reported on, regardless whether that lost data was ever used in a crime. The reputation losses that can incur as a result should make businesses aware there is real risk involved.

That all said, it has been repeatedly demonstrated that a concerted effort can reassemble data from even the most damaged drives (the Space Shuttle drive data reconstruction being but one example), so if data is going to be left unencrypted on any physical device the furnace becomes your only safe bet.

Applying data sensitivity identification can mitigate some risk. If your data is valuable for, at most, 6 months then simply keep the old drives that long before disposing of them. If the data has value for a longer period, adjust accordingly. If the storage time becomes too long, or the risk of using 3rd parties for such storage, then encryption becomes a cheaper option (despite it costing more than not using it, providing its cheaper than storing the data.) If, however, your data is sensitive for a period that makes brute force decryption viable, then we're back to the furnace.

Personally, I would be more concerned about the entity who accepts the drives directly from me, than from whomever they ship those drives to. That first party has knowledge of who I am and which drives are mine, and therefore are in the position to pick and choose drives that might be valuable. Whoever is receiving these drives in, for example, Nigeria has far less knowledge and ends up having to go through a far greater volume of noise to get to a signal. That alone reduces the likelihood, and therefore the risk.

We have long recommended that sensitive data should be encrypted at rest. If it is, then it is likely to be encrypted in transit (e.g. via Internet backup or physical tape transfers.) This mitigates many issues brought up in the media, and should satisfy most regulatory requirements. Keeping data encrypted in memory (or while in use by an application) can be desirable and may reduce some specific risks, but has far less overall risk reducing benefits than encrypting at rest.

None of this is meant to suggest that the outsourcing of IT disposal shouldn't involve investigating how that entity handles the data/devices, or, that there aren't differences between providers of such services. All outsourcing should involve investigation of all pertinent details.

Thanks for pointing this out, Kyle.

Cheers,
Russ</description>
		<content:encoded><![CDATA[<p>Kyle,</p>
<p>Given that there are absolutely no known&#8217;s in &#8220;unknown unknown&#8221;, speculating that anything represents the majority of those cases is, well, wild speculation. Honestly, its as likely to be use of graphic card memory for tools or violation of VM boundaries. It could be anything.</p>
<p>Also, from a risk calculation perspective, the simple cost of purchasing drives, let alone drives from Nigeria, would make this an unlikely option for criminals. It’s far easier to compromise a system electronically via no-cost bots across no-cost network links than to purchase anything from anywhere.</p>
<p>Regardless whether you agree that IT disposal represents the &#8220;biggest hidden risk,&#8221; it does represent a risk that should be considered. Local disposal (or loss via 3rd parties) of unencrypted data tapes has been widely reported on, regardless whether that lost data was ever used in a crime. The reputation losses that can incur as a result should make businesses aware there is real risk involved.</p>
<p>That all said, it has been repeatedly demonstrated that a concerted effort can reassemble data from even the most damaged drives (the Space Shuttle drive data reconstruction being but one example), so if data is going to be left unencrypted on any physical device the furnace becomes your only safe bet.</p>
<p>Applying data sensitivity identification can mitigate some risk. If your data is valuable for, at most, 6 months then simply keep the old drives that long before disposing of them. If the data has value for a longer period, adjust accordingly. If the storage time becomes too long, or the risk of using 3rd parties for such storage, then encryption becomes a cheaper option (despite it costing more than not using it, providing its cheaper than storing the data.) If, however, your data is sensitive for a period that makes brute force decryption viable, then we&#8217;re back to the furnace.</p>
<p>Personally, I would be more concerned about the entity who accepts the drives directly from me, than from whomever they ship those drives to. That first party has knowledge of who I am and which drives are mine, and therefore are in the position to pick and choose drives that might be valuable. Whoever is receiving these drives in, for example, Nigeria has far less knowledge and ends up having to go through a far greater volume of noise to get to a signal. That alone reduces the likelihood, and therefore the risk.</p>
<p>We have long recommended that sensitive data should be encrypted at rest. If it is, then it is likely to be encrypted in transit (e.g. via Internet backup or physical tape transfers.) This mitigates many issues brought up in the media, and should satisfy most regulatory requirements. Keeping data encrypted in memory (or while in use by an application) can be desirable and may reduce some specific risks, but has far less overall risk reducing benefits than encrypting at rest.</p>
<p>None of this is meant to suggest that the outsourcing of IT disposal shouldn&#8217;t involve investigating how that entity handles the data/devices, or, that there aren&#8217;t differences between providers of such services. All outsourcing should involve investigation of all pertinent details.</p>
<p>Thanks for pointing this out, Kyle.</p>
<p>Cheers,<br />
Russ</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Retire-IT</title>
		<link>http://securityblog.verizonbusiness.com/2008/06/10/2008-data-breach-investigations-report/#comment-30</link>
		<dc:creator>Retire-IT</dc:creator>
		<pubDate>Tue, 05 Aug 2008 20:28:59 +0000</pubDate>
		<guid isPermaLink="false">http://securityblog.verizonbusiness.com/?p=80#comment-30</guid>
		<description>The biggest hidden risk of data security involves IT disposal. Often companies rely on electronics recyclers to protect them by destroying data on retired hard drives. 

Sadly, 80% of unwanted US computer equipment is exported to developing countries by these so-called recyclers - often with confidential data still on hard drives.  

As the Verizon study states “criminals prefer to exploit weaknesses rather than strengths.” What could be easier than buying old hard drives from an e-scrap dealer in Nigeria? 

Outsourcing IT disposal makes sense. But if an organization fails to maintain proper oversight, outsourcing actually increases the risks, provides a false sense of security, and is likely the majority of the 90% of breaches that involve some type of "unknown unknown."

Kyle Marks
President &#38; CEO
Retire-IT, LLC
kmarks@retire-it.com</description>
		<content:encoded><![CDATA[<p>The biggest hidden risk of data security involves IT disposal. Often companies rely on electronics recyclers to protect them by destroying data on retired hard drives. </p>
<p>Sadly, 80% of unwanted US computer equipment is exported to developing countries by these so-called recyclers - often with confidential data still on hard drives.  </p>
<p>As the Verizon study states “criminals prefer to exploit weaknesses rather than strengths.” What could be easier than buying old hard drives from an e-scrap dealer in Nigeria? </p>
<p>Outsourcing IT disposal makes sense. But if an organization fails to maintain proper oversight, outsourcing actually increases the risks, provides a false sense of security, and is likely the majority of the 90% of breaches that involve some type of &#8220;unknown unknown.&#8221;</p>
<p>Kyle Marks<br />
President &amp; CEO<br />
Retire-IT, LLC<br />
<a href="mailto:kmarks@retire-it.com">kmarks@retire-it.com</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ma petite parcelle d'Internet...</title>
		<link>http://securityblog.verizonbusiness.com/2008/06/10/2008-data-breach-investigations-report/#comment-15</link>
		<dc:creator>Ma petite parcelle d'Internet...</dc:creator>
		<pubDate>Sun, 22 Jun 2008 18:28:06 +0000</pubDate>
		<guid isPermaLink="false">http://securityblog.verizonbusiness.com/?p=80#comment-15</guid>
		<description>&lt;strong&gt;...&lt;/strong&gt;

...</description>
		<content:encoded><![CDATA[<p><strong>&#8230;</strong></p>
<p>&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Verizon Business Security Blog &#187; Blog Archive &#187; Bryan Sartin on the Data Breach Investigations Report</title>
		<link>http://securityblog.verizonbusiness.com/2008/06/10/2008-data-breach-investigations-report/#comment-12</link>
		<dc:creator>Verizon Business Security Blog &#187; Blog Archive &#187; Bryan Sartin on the Data Breach Investigations Report</dc:creator>
		<pubDate>Fri, 20 Jun 2008 15:59:28 +0000</pubDate>
		<guid isPermaLink="false">http://securityblog.verizonbusiness.com/?p=80#comment-12</guid>
		<description>[...] Part I of this two-podcast series, Bryan Sartin provides a general overview of the 2008 Data Breach Investigations Report and describes the methodology used to compile the findings of this ground-breaking analytical [...]</description>
		<content:encoded><![CDATA[<p>[...] Part I of this two-podcast series, Bryan Sartin provides a general overview of the 2008 Data Breach Investigations Report and describes the methodology used to compile the findings of this ground-breaking analytical [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Russ Cooper</title>
		<link>http://securityblog.verizonbusiness.com/2008/06/10/2008-data-breach-investigations-report/#comment-11</link>
		<dc:creator>Russ Cooper</dc:creator>
		<pubDate>Mon, 16 Jun 2008 14:32:22 +0000</pubDate>
		<guid isPermaLink="false">http://securityblog.verizonbusiness.com/?p=80#comment-11</guid>
		<description>This is a question we've been asked quite a bit during webinars and other discussions on the study. The answer is that many cases (30%) involved more than one source. For instance, the scenario described in the paper where an external entity compromised a partner and then used the partner's connection to attack the victim would get a check next to both 'external' and 'partner' sources. You'll note that the 30% figure is mentioned on page 2 of the report as being "multiple parties."</description>
		<content:encoded><![CDATA[<p>This is a question we&#8217;ve been asked quite a bit during webinars and other discussions on the study. The answer is that many cases (30%) involved more than one source. For instance, the scenario described in the paper where an external entity compromised a partner and then used the partner&#8217;s connection to attack the victim would get a check next to both &#8216;external&#8217; and &#8216;partner&#8217; sources. You&#8217;ll note that the 30% figure is mentioned on page 2 of the report as being &#8220;multiple parties.&#8221;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Neal Krawetz</title>
		<link>http://securityblog.verizonbusiness.com/2008/06/10/2008-data-breach-investigations-report/#comment-10</link>
		<dc:creator>Neal Krawetz</dc:creator>
		<pubDate>Mon, 16 Jun 2008 13:15:17 +0000</pubDate>
		<guid isPermaLink="false">http://securityblog.verizonbusiness.com/?p=80#comment-10</guid>
		<description>73% + 18% + 39% = 130%. What accounts for the 30% overlap?</description>
		<content:encoded><![CDATA[<p>73% + 18% + 39% = 130%. What accounts for the 30% overlap?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
