<?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: The data breach that hit home</title>
	<atom:link href="http://itknowledgeexchange.techtarget.com/security-bytes/the-data-breach-that-hit-home/feed/" rel="self" type="application/rss+xml" />
	<link>http://itknowledgeexchange.techtarget.com/security-bytes/the-data-breach-that-hit-home/</link>
	<description>A SearchSecurity.com blog</description>
	<pubDate>Sun, 29 Nov 2009 02:50:25 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.2</generator>
		<item>
		<title>By: News about Mortages and depts &#187; Archive &#187; The data breach that hit bhome/b - Security Bytes</title>
		<link>http://itknowledgeexchange.techtarget.com/security-bytes/the-data-breach-that-hit-home/#comment-596</link>
		<dc:creator>News about Mortages and depts &#187; Archive &#187; The data breach that hit bhome/b - Security Bytes</dc:creator>
		<pubDate>Thu, 12 Feb 2009 05:27:57 +0000</pubDate>
		<guid isPermaLink="false">http://security.blogs.techtarget.com/2008/03/20/the-data-breach-that-hit-home/#comment-596</guid>
		<description>[...] Bill Brenner placed an interesting blog post on The data breach that hit bhome/b - Security BytesHere&#8217;s a brief overviewJay McGillicuddy &#124; Mar 20 2008 11:14AM GMT. Living in Hampstead this story really hit bhome/b as we shop there all the time. I check my bdebit/b account all the time and so far so good. Can’t be too careful can we. b&#8230;/b [...]</description>
		<content:encoded><![CDATA[<p>[...] Bill Brenner placed an interesting blog post on The data breach that hit bhome/b - Security BytesHere&#8217;s a brief overviewJay McGillicuddy | Mar 20 2008 11:14AM GMT. Living in Hampstead this story really hit bhome/b as we shop there all the time. I check my bdebit/b account all the time and so far so good. Can’t be too careful can we. b&#8230;/b [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: F. Lee Powers</title>
		<link>http://itknowledgeexchange.techtarget.com/security-bytes/the-data-breach-that-hit-home/#comment-517</link>
		<dc:creator>F. Lee Powers</dc:creator>
		<pubDate>Tue, 25 Mar 2008 18:02:03 +0000</pubDate>
		<guid isPermaLink="false">http://security.blogs.techtarget.com/2008/03/20/the-data-breach-that-hit-home/#comment-517</guid>
		<description>Re:  PCI DSS validity

What about the PCI Assessor?  I'll lay odds it's not the PCI DSS, it's the assessor who either was incompetent or very lazy in determining compliance.  If there are holes a mile wide in PCI DSS compliance, even though an assessor provided a compliant Report of Compliance, then it's the assessor that failed and not the standards.

If this turns out to be the case, when they name the Assessment Consultancy, that company should not be allowed to do any more PCI DSS work.</description>
		<content:encoded><![CDATA[<p>Re:  PCI DSS validity</p>
<p>What about the PCI Assessor?  I&#8217;ll lay odds it&#8217;s not the PCI DSS, it&#8217;s the assessor who either was incompetent or very lazy in determining compliance.  If there are holes a mile wide in PCI DSS compliance, even though an assessor provided a compliant Report of Compliance, then it&#8217;s the assessor that failed and not the standards.</p>
<p>If this turns out to be the case, when they name the Assessment Consultancy, that company should not be allowed to do any more PCI DSS work.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: shrikant raman</title>
		<link>http://itknowledgeexchange.techtarget.com/security-bytes/the-data-breach-that-hit-home/#comment-516</link>
		<dc:creator>shrikant raman</dc:creator>
		<pubDate>Sat, 22 Mar 2008 22:54:29 +0000</pubDate>
		<guid isPermaLink="false">http://security.blogs.techtarget.com/2008/03/20/the-data-breach-that-hit-home/#comment-516</guid>
		<description>Nice summary Bill - Wide range of theories there! I've got mine at securitycoin.blogspot.com and I think Rich Mogull's theory comes the closest!</description>
		<content:encoded><![CDATA[<p>Nice summary Bill - Wide range of theories there! I&#8217;ve got mine at&nbsp;&lt;a href="http://securitycoin.blogspot.com" title="http://securitycoin.blogspot. " target="_blank"&gt;securitycoin.blogspot.com&lt;/a&gt; and I think Rich Mogull&#8217;s theory comes the closest!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Angry Customer</title>
		<link>http://itknowledgeexchange.techtarget.com/security-bytes/the-data-breach-that-hit-home/#comment-515</link>
		<dc:creator>Angry Customer</dc:creator>
		<pubDate>Thu, 20 Mar 2008 19:20:45 +0000</pubDate>
		<guid isPermaLink="false">http://security.blogs.techtarget.com/2008/03/20/the-data-breach-that-hit-home/#comment-515</guid>
		<description>I think you are being too forgiving...calling Hannaford a victim rather than a villain.

It took Hannaford nearly 3 weeks to inform the public of the breach. Further, Hannaford irresponsibly let customers continue to use plastic between Feb 27 and March 10 on a network that was NOT secure. To me, this is unforgiveable and an eggregious "breach" of customer trust. I loved the store (compared to the options) but will never shop there again. And, I will be helping the class action lawyers in any way that I can, since I was the true victim.</description>
		<content:encoded><![CDATA[<p>I think you are being too forgiving&#8230;calling Hannaford a victim rather than a villain.</p>
<p>It took Hannaford nearly 3 weeks to inform the public of the breach. Further, Hannaford irresponsibly let customers continue to use plastic between Feb 27 and March 10 on a network that was NOT secure. To me, this is unforgiveable and an eggregious &#8220;breach&#8221; of customer trust. I loved the store (compared to the options) but will never shop there again. And, I will be helping the class action lawyers in any way that I can, since I was the true victim.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jay McGillicuddy</title>
		<link>http://itknowledgeexchange.techtarget.com/security-bytes/the-data-breach-that-hit-home/#comment-514</link>
		<dc:creator>Jay McGillicuddy</dc:creator>
		<pubDate>Thu, 20 Mar 2008 15:14:35 +0000</pubDate>
		<guid isPermaLink="false">http://security.blogs.techtarget.com/2008/03/20/the-data-breach-that-hit-home/#comment-514</guid>
		<description>Living in Hampstead this story really hit home as we shop there all the time. I check my debit account all the time and so far so good.
Can't be too careful can we.</description>
		<content:encoded><![CDATA[<p>Living in Hampstead this story really hit home as we shop there all the time. I check my debit account all the time and so far so good.<br />
Can&#8217;t be too careful can we.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: &#187; The data breach that hit home Credit Card on Credit Speak: Find Info, News and More on Credit Card</title>
		<link>http://itknowledgeexchange.techtarget.com/security-bytes/the-data-breach-that-hit-home/#comment-513</link>
		<dc:creator>&#187; The data breach that hit home Credit Card on Credit Speak: Find Info, News and More on Credit Card</dc:creator>
		<pubDate>Thu, 20 Mar 2008 15:02:38 +0000</pubDate>
		<guid isPermaLink="false">http://security.blogs.techtarget.com/2008/03/20/the-data-breach-that-hit-home/#comment-513</guid>
		<description>[...] The data breach that hit home “The fraud was detected by the banks or credit card companies, then it took a little under two weeks to contain,” he wrote. “Not great, and indicative of either a little sophistication on the attacker’s part, or a lack of sophistication &#8230; [...]</description>
		<content:encoded><![CDATA[<p>[...] The data breach that hit home “The fraud was detected by the banks or credit card companies, then it took a little under two weeks to contain,” he wrote. “Not great, and indicative of either a little sophistication on the attacker’s part, or a lack of sophistication &#8230; [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
<!-- dynamic -->