<?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: Hannaford Brothers hacked, but there&#8217;s a silver lining</title>
	<atom:link href="http://www.mckeay.net/2008/03/18/hannaford-brothers-hacked-but-theres-a-silver-lining/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.mckeay.net/2008/03/18/hannaford-brothers-hacked-but-theres-a-silver-lining/</link>
	<description>The views of one man on security, privacy and anything else that catches his attention</description>
	<pubDate>Sat, 11 Oct 2008 23:43:56 +0000</pubDate>
	<generator>http://wordpress.org/?v=abc</generator>
		<item>
		<title>By: anonymous</title>
		<link>http://www.mckeay.net/2008/03/18/hannaford-brothers-hacked-but-theres-a-silver-lining/#comment-1454</link>
		<dc:creator>anonymous</dc:creator>
		<pubDate>Sat, 22 Mar 2008 22:48:50 +0000</pubDate>
		<guid isPermaLink="false">http://www.mckeay.net/2008/03/18/hannaford-brothers-hacked-but-theres-a-silver-lining/#comment-1454</guid>
		<description>You bring up an interesting point. But that is only if the attackers got into a database at  Hannaford. Since it was during the auth process, that seems highly unlikely - and what may have happened may be a sniffer in action. Sniffing just the initial part of the POS messages should give the account number and expiration date only with no names. Lets not give credit to Hannaford till we know what happened. But I do agree with your silver lining theory _if_ we can find store, that is! 

Check out my theory at http://securitycoin.blogspot.com/2008/03/hannaford-supermarkets.html</description>
		<content:encoded><![CDATA[<p>You bring up an interesting point. But that is only if the attackers got into a database at  Hannaford. Since it was during the auth process, that seems highly unlikely - and what may have happened may be a sniffer in action. Sniffing just the initial part of the POS messages should give the account number and expiration date only with no names. Lets not give credit to Hannaford till we know what happened. But I do agree with your silver lining theory _if_ we can find store, that is! </p>
<p>Check out my theory at <a href="http://securitycoin.blogspot.com/2008/03/hannaford-supermarkets.html" rel="nofollow">http://securitycoin.blogspot.com/2008/03/hannaford-supermarkets.html</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Joshua Gruber</title>
		<link>http://www.mckeay.net/2008/03/18/hannaford-brothers-hacked-but-theres-a-silver-lining/#comment-1450</link>
		<dc:creator>Joshua Gruber</dc:creator>
		<pubDate>Sat, 22 Mar 2008 00:56:15 +0000</pubDate>
		<guid isPermaLink="false">http://www.mckeay.net/2008/03/18/hannaford-brothers-hacked-but-theres-a-silver-lining/#comment-1450</guid>
		<description>This makes me sad in part because Hannafords makes a point of not forcing customers to join a club and give them loads of personal information to be tracked in order to get discounts.</description>
		<content:encoded><![CDATA[<p>This makes me sad in part because Hannafords makes a point of not forcing customers to join a club and give them loads of personal information to be tracked in order to get discounts.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: The data breach that hit home &#8212; Security Bytes</title>
		<link>http://www.mckeay.net/2008/03/18/hannaford-brothers-hacked-but-theres-a-silver-lining/#comment-1426</link>
		<dc:creator>The data breach that hit home &#8212; Security Bytes</dc:creator>
		<pubDate>Thu, 20 Mar 2008 14:25:52 +0000</pubDate>
		<guid isPermaLink="false">http://www.mckeay.net/2008/03/18/hannaford-brothers-hacked-but-theres-a-silver-lining/#comment-1426</guid>
		<description>[...] Security blogger Martin McKeay wrote of a silver lining in the Hannaford&#8217;s breach. [...]</description>
		<content:encoded><![CDATA[<p>[...] Security blogger Martin McKeay wrote of a silver lining in the Hannaford&#8217;s breach. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David Navetta</title>
		<link>http://www.mckeay.net/2008/03/18/hannaford-brothers-hacked-but-theres-a-silver-lining/#comment-1408</link>
		<dc:creator>David Navetta</dc:creator>
		<pubDate>Tue, 18 Mar 2008 20:30:20 +0000</pubDate>
		<guid isPermaLink="false">http://www.mckeay.net/2008/03/18/hannaford-brothers-hacked-but-theres-a-silver-lining/#comment-1408</guid>
		<description>This perfectly illustrates how the ambiguities of the PCI can get you into big trouble. The legal implications of giving a stamp of PCI approval based on a loose interpretation of PCI are enormous (you can read more here at my blog, I am an infosec attroney: http://infoseccompliance.blogspot.com/2008/02/legal-implications-risks-and-problems.html)

Anyway, in this case if the ambiguity is in section 4.1 of the PCI Standard, which requires "Encrypt transmission of cardholder data across open, public networks" and also states "Sensitive information must be encrypted during transmission over networks that are easy and common for a hacker to intercept, modify, and divert data while in transit"

Examples are provided, the Internet, WiFI, global systems for mobile communications and GPRS.

So the question is, does this include open "internal" networks of a merchant that may be "easy and common" for a hacker to intercept.

If all of the supposition is true, it appears that Hannaford (or its Qualified Security Assessor) interpreted this to mean only "public" networks like the Internet...</description>
		<content:encoded><![CDATA[<p>This perfectly illustrates how the ambiguities of the PCI can get you into big trouble. The legal implications of giving a stamp of PCI approval based on a loose interpretation of PCI are enormous (you can read more here at my blog, I am an infosec attroney: <a href="http://infoseccompliance.blogspot.com/2008/02/legal-implications-risks-and-problems.html" rel="nofollow">http://infoseccompliance.blogspot.com/2008/02/legal-implications-risks-and-problems.html</a>)</p>
<p>Anyway, in this case if the ambiguity is in section 4.1 of the PCI Standard, which requires &#8220;Encrypt transmission of cardholder data across open, public networks&#8221; and also states &#8220;Sensitive information must be encrypted during transmission over networks that are easy and common for a hacker to intercept, modify, and divert data while in transit&#8221;</p>
<p>Examples are provided, the Internet, WiFI, global systems for mobile communications and GPRS.</p>
<p>So the question is, does this include open &#8220;internal&#8221; networks of a merchant that may be &#8220;easy and common&#8221; for a hacker to intercept.</p>
<p>If all of the supposition is true, it appears that Hannaford (or its Qualified Security Assessor) interpreted this to mean only &#8220;public&#8221; networks like the Internet&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Benjamin Wright</title>
		<link>http://www.mckeay.net/2008/03/18/hannaford-brothers-hacked-but-theres-a-silver-lining/#comment-1407</link>
		<dc:creator>Benjamin Wright</dc:creator>
		<pubDate>Tue, 18 Mar 2008 18:09:09 +0000</pubDate>
		<guid isPermaLink="false">http://www.mckeay.net/2008/03/18/hannaford-brothers-hacked-but-theres-a-silver-lining/#comment-1407</guid>
		<description>Martin:  Spectacular announcements about massive data security breaches do the public little good.  The implication of these announcements is that some data (i.e., that which are the subject of the announcements) are more exposed than other data.  As a practical matter that is false.  All personally identifiable data are more or less exposed all the time.  And successful exploitation of that data by an identity thief requires a lot of work and luck.  Socially responsible data-holders should set a high threshold of proof before concluding that a &lt;a href="http://hack-igations.blogspot.com/2007/09/definition-of-data-security-breach.html" rel="nofollow"&gt;"data security breach"&lt;/a&gt; worthy of announcement has occurred for any given unit of data.  (Data-holders should of course consult their attorneys.)</description>
		<content:encoded><![CDATA[<p>Martin:  Spectacular announcements about massive data security breaches do the public little good.  The implication of these announcements is that some data (i.e., that which are the subject of the announcements) are more exposed than other data.  As a practical matter that is false.  All personally identifiable data are more or less exposed all the time.  And successful exploitation of that data by an identity thief requires a lot of work and luck.  Socially responsible data-holders should set a high threshold of proof before concluding that a <a href="http://hack-igations.blogspot.com/2007/09/definition-of-data-security-breach.html" rel="nofollow">&#8220;data security breach&#8221;</a> worthy of announcement has occurred for any given unit of data.  (Data-holders should of course consult their attorneys.)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: EJ</title>
		<link>http://www.mckeay.net/2008/03/18/hannaford-brothers-hacked-but-theres-a-silver-lining/#comment-1406</link>
		<dc:creator>EJ</dc:creator>
		<pubDate>Tue, 18 Mar 2008 17:46:57 +0000</pubDate>
		<guid isPermaLink="false">http://www.mckeay.net/2008/03/18/hannaford-brothers-hacked-but-theres-a-silver-lining/#comment-1406</guid>
		<description>So I'm hoping that if they reported it on 2/27 then they had it all under control by then.  I never typically shop at Hannaford's, but I stopped in March 7th to pick up a few sundries while out and about.  Sounds like I dodged a bullet.  

And if the attackers are listening, I bough croûtons.  ;)</description>
		<content:encoded><![CDATA[<p>So I&#8217;m hoping that if they reported it on 2/27 then they had it all under control by then.  I never typically shop at Hannaford&#8217;s, but I stopped in March 7th to pick up a few sundries while out and about.  Sounds like I dodged a bullet.  </p>
<p>And if the attackers are listening, I bough croûtons.  <img src='http://mckeay.net/wp-includes/images/smilies/icon_wink.gif' alt=';)' class='wp-smiley' /></p>
]]></content:encoded>
	</item>
</channel>
</rss>
