<?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: The Last of the Heartland Breach</title>
	<atom:link href="http://www.merchant911.org/blog/index.php/2009/03/21/the-last-of-the-heartland-breach/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.merchant911.org/blog/index.php/2009/03/21/the-last-of-the-heartland-breach/</link>
	<description>Comments on credit card fraud from the E-Commerce Merchant point of view by Tom Mahoney, Founder and Director of Merchant911.org</description>
	<lastBuildDate>Fri, 13 Jan 2012 06:40:43 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=</generator>
	<item>
		<title>By: Tom</title>
		<link>http://www.merchant911.org/blog/index.php/2009/03/21/the-last-of-the-heartland-breach/comment-page-1/#comment-1909</link>
		<dc:creator>Tom</dc:creator>
		<pubDate>Tue, 31 Mar 2009 23:12:07 +0000</pubDate>
		<guid isPermaLink="false">http://www.merchant911.org/blog/?p=247#comment-1909</guid>
		<description>&lt;b&gt;Kelvin&lt;/b&gt; wrote:
&lt;blockquote&gt;There are so many opinionated misstatements in this article I don&#039;t even know where to begin.
&lt;/blockquote&gt;
Opinionated - of course.  Most blogs are and I make no claims that mine is not.
&lt;blockquote&gt;
First, the lack of information on the breach is not from a mysterious &quot;shroud&quot; of &quot;corporate secrecy&quot; but due to the lack of hard evidence on how much data was stolen. Data doesn&#039;t sit on the shelf like a physical object. The malware hackers are using is sophisticated enough to hide itself and prevent data forensics experts from knowing what actually happened. Putting the pieces together to determine how much data was stolen is not as simple as you think.
 
This was likely the case with another major data breach that occurred in 2008 in which the processor involved has not even announced the breach.
&lt;/blockquote&gt;
I don&#039;t think for a minute that it&#039;s easy and I&#039;m also well aware that the hackers are more sophisticated than most of the people trying to catch them.  Please don&#039;t tell me that there isn&#039;t a &quot;shroud of corporate security&quot; (your words, not mine) and in the next paragraph tell me that there was another major breach in 2008 that has yet to be disclosed.  I think I see a bit of secrecy there. And then there&#039;s Heartland&#039;s very obvious attempt to withhold information with statements like the breach went on for &quot;more than weeks&quot; and their total silence on the number of accounts &lt;b&gt;potentially exposed&lt;/b&gt; even as the affected issuers are, to some extent, coming clean.  

Related to the undisclosed breach, If you read my March 3rd entry (http://www.merchant911.org/blog/index.php/2009/03/03/data-breach-double-talk-spin/) 
you&#039;ll see that I&#039;m aware of a lot of speculation on that incident.  Visa did a (opinionated) very poor job of (/opinionated) denying that there was one.  If I assume that you are someone in the industry rather than another blogger with &quot;opinionated misinformation,&quot; then I can consider your comment as a verification of that breach - and a confirmation of my opinion that Visa is lying about it.  A legitimate question for you, if you will, why &lt;b&gt;hasn&#039;t&lt;/b&gt; that processor disclosed?  
&lt;blockquote&gt;
Then, you talk about the card &quot;companies&quot;, in which you mean the CARD ASSOCIATIONS, Visa, Mastercard, Discover, etc. and their relationship with acquirers such as Heartland and issuing banks.
&lt;/blockquote&gt;
You are quite correct but, for the record, I&#039;m quite aware of it.  I couldn&#039;t help but absorb that distinction in the 8 1/2 years I&#039;ve been working with e-commerce merchants.  I used those words with the idea that some of my readers might not know what I meant when I referred to the Association.  A matter of semantics in this case.  If you look at most of the pres releases out there, you will see that the Associations are usually referred to as &#039;credit card companies.&#039;  I&#039;m certainly not alone on that one.
&lt;blockquote&gt;
This is all wrong.
Card associations do not fine issuing banks for fraudulent activity or data compromises. Fines for data compromises affect the acquirer and the acquirer may pass these fines on to the merchant when the merchant is responsible. In this instance, no merchant was responsible for the data breach so the fines (when they are announced) will be absorbed by Heartland. The issuing banks deal with fraudulent activity as a result of any data compromise between the card holder and the merchant. Chargebacks may affect some merchants, but most likely, the distribution of these card numbers around the world will make the impact on US businesses almost non-existent. The effects have been felt mainly by card holders.
Everything you said in that paragraph is wrong. You might consider deleting this entire post or checking ALL of your facts first.
&lt;/blockquote&gt;
I do stand corrected on the &quot;issuing bank&quot; statement and will shortly edit the paragraph accordingly.  What I should have said is that &lt;i&gt;fines are being issued to Heartland&#039;s sponsoring banks.&lt;/i&gt;

You are also correct that effects have been felt by cardholders but I refuse to consider them as victims in all this.  Just last week I received a new debit card telling me that my old one may have been breached in the Heartland incident (yes, my bank named names.)  That hardly makes me a victim.  Even if my card had been used fraudulently I wouldn&#039;t consider myself a victim of anything but the inconvenience of calling my bank to report the fraud.

Bu then again, I didn&#039;t make any statement about who&#039;s a victim of what, only that the mess wil be very expensive.
&lt;blockquote&gt;
There&#039;s enough blogging and news media on this topic already. Do some research and get your facts straight.
&lt;/blockquote&gt;

I do a lot of research but the sources that I have are a bit limited.  They are, after all, pretty much limited to blogs and the press.  We certainly are not getting a hell of a lot from the industry.</description>
		<content:encoded><![CDATA[<p><b>Kelvin</b> wrote:</p>
<blockquote><p>There are so many opinionated misstatements in this article I don&#8217;t even know where to begin.
</p></blockquote>
<p>Opinionated &#8211; of course.  Most blogs are and I make no claims that mine is not.</p>
<blockquote><p>
First, the lack of information on the breach is not from a mysterious &#8220;shroud&#8221; of &#8220;corporate secrecy&#8221; but due to the lack of hard evidence on how much data was stolen. Data doesn&#8217;t sit on the shelf like a physical object. The malware hackers are using is sophisticated enough to hide itself and prevent data forensics experts from knowing what actually happened. Putting the pieces together to determine how much data was stolen is not as simple as you think.</p>
<p>This was likely the case with another major data breach that occurred in 2008 in which the processor involved has not even announced the breach.
</p></blockquote>
<p>I don&#8217;t think for a minute that it&#8217;s easy and I&#8217;m also well aware that the hackers are more sophisticated than most of the people trying to catch them.  Please don&#8217;t tell me that there isn&#8217;t a &#8220;shroud of corporate security&#8221; (your words, not mine) and in the next paragraph tell me that there was another major breach in 2008 that has yet to be disclosed.  I think I see a bit of secrecy there. And then there&#8217;s Heartland&#8217;s very obvious attempt to withhold information with statements like the breach went on for &#8220;more than weeks&#8221; and their total silence on the number of accounts <b>potentially exposed</b> even as the affected issuers are, to some extent, coming clean.  </p>
<p>Related to the undisclosed breach, If you read my March 3rd entry (<a href="http://www.merchant911.org/blog/index.php/2009/03/03/data-breach-double-talk-spin/" rel="nofollow">http://www.merchant911.org/blog/index.php/2009/03/03/data-breach-double-talk-spin/</a>)<br />
you&#8217;ll see that I&#8217;m aware of a lot of speculation on that incident.  Visa did a (opinionated) very poor job of (/opinionated) denying that there was one.  If I assume that you are someone in the industry rather than another blogger with &#8220;opinionated misinformation,&#8221; then I can consider your comment as a verification of that breach &#8211; and a confirmation of my opinion that Visa is lying about it.  A legitimate question for you, if you will, why <b>hasn&#8217;t</b> that processor disclosed?  </p>
<blockquote><p>
Then, you talk about the card &#8220;companies&#8221;, in which you mean the CARD ASSOCIATIONS, Visa, Mastercard, Discover, etc. and their relationship with acquirers such as Heartland and issuing banks.
</p></blockquote>
<p>You are quite correct but, for the record, I&#8217;m quite aware of it.  I couldn&#8217;t help but absorb that distinction in the 8 1/2 years I&#8217;ve been working with e-commerce merchants.  I used those words with the idea that some of my readers might not know what I meant when I referred to the Association.  A matter of semantics in this case.  If you look at most of the pres releases out there, you will see that the Associations are usually referred to as &#8216;credit card companies.&#8217;  I&#8217;m certainly not alone on that one.</p>
<blockquote><p>
This is all wrong.<br />
Card associations do not fine issuing banks for fraudulent activity or data compromises. Fines for data compromises affect the acquirer and the acquirer may pass these fines on to the merchant when the merchant is responsible. In this instance, no merchant was responsible for the data breach so the fines (when they are announced) will be absorbed by Heartland. The issuing banks deal with fraudulent activity as a result of any data compromise between the card holder and the merchant. Chargebacks may affect some merchants, but most likely, the distribution of these card numbers around the world will make the impact on US businesses almost non-existent. The effects have been felt mainly by card holders.<br />
Everything you said in that paragraph is wrong. You might consider deleting this entire post or checking ALL of your facts first.
</p></blockquote>
<p>I do stand corrected on the &#8220;issuing bank&#8221; statement and will shortly edit the paragraph accordingly.  What I should have said is that <i>fines are being issued to Heartland&#8217;s sponsoring banks.</i></p>
<p>You are also correct that effects have been felt by cardholders but I refuse to consider them as victims in all this.  Just last week I received a new debit card telling me that my old one may have been breached in the Heartland incident (yes, my bank named names.)  That hardly makes me a victim.  Even if my card had been used fraudulently I wouldn&#8217;t consider myself a victim of anything but the inconvenience of calling my bank to report the fraud.</p>
<p>Bu then again, I didn&#8217;t make any statement about who&#8217;s a victim of what, only that the mess wil be very expensive.</p>
<blockquote><p>
There&#8217;s enough blogging and news media on this topic already. Do some research and get your facts straight.
</p></blockquote>
<p>I do a lot of research but the sources that I have are a bit limited.  They are, after all, pretty much limited to blogs and the press.  We certainly are not getting a hell of a lot from the industry.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kelvin</title>
		<link>http://www.merchant911.org/blog/index.php/2009/03/21/the-last-of-the-heartland-breach/comment-page-1/#comment-1908</link>
		<dc:creator>Kelvin</dc:creator>
		<pubDate>Tue, 31 Mar 2009 18:03:05 +0000</pubDate>
		<guid isPermaLink="false">http://www.merchant911.org/blog/?p=247#comment-1908</guid>
		<description>There are so many opinionated misstatements in this article I don&#039;t even know where to begin.

First, the lack of information on the breach is not from a mysterious &quot;shroud&quot; of &quot;corporate secrecy&quot; but due to the lack of hard evidence on how much data was stolen.  Data doesn&#039;t sit on the shelf like a physical object.  The malware hackers are using is sophisticated enough to hide itself and prevent data forensics experts from knowing what actually happened.  Putting the pieces together to determine how much data was stolen is not as simple as you think.

This was likely the case with another major data breach that occurred in 2008 in which the processor involved has not even announced the breach.

Then, you talk about the card &quot;companies&quot;, in which you mean the CARD ASSOCIATIONS, Visa, Mastercard, Discover, etc. and their relationship with acquirers such as Heartland and issuing banks.

This is all wrong.

Card associations do not fine issuing banks for fraudulent activity or data compromises.  Fines for data compromises affect the acquirer and the acquirer may pass these fines on to the merchant when the merchant is responsible.  In this instance, no merchant was responsible for the data breach so the fines (when they are announced) will be absorbed by Heartland. The issuing banks deal with fraudulent activity as a result of any data compromise between the card holder and the merchant.  Chargebacks may affect some merchants, but most likely, the distribution of these card numbers around the world will make the impact on US businesses almost non-existent.  The effects have been felt mainly by card holders.

Everything you said in that paragraph is wrong.  You might consider deleting this entire post or checking ALL of your facts first.

There&#039;s enough blogging and news media on this topic already.  Do some research and get your facts straight.</description>
		<content:encoded><![CDATA[<p>There are so many opinionated misstatements in this article I don&#8217;t even know where to begin.</p>
<p>First, the lack of information on the breach is not from a mysterious &#8220;shroud&#8221; of &#8220;corporate secrecy&#8221; but due to the lack of hard evidence on how much data was stolen.  Data doesn&#8217;t sit on the shelf like a physical object.  The malware hackers are using is sophisticated enough to hide itself and prevent data forensics experts from knowing what actually happened.  Putting the pieces together to determine how much data was stolen is not as simple as you think.</p>
<p>This was likely the case with another major data breach that occurred in 2008 in which the processor involved has not even announced the breach.</p>
<p>Then, you talk about the card &#8220;companies&#8221;, in which you mean the CARD ASSOCIATIONS, Visa, Mastercard, Discover, etc. and their relationship with acquirers such as Heartland and issuing banks.</p>
<p>This is all wrong.</p>
<p>Card associations do not fine issuing banks for fraudulent activity or data compromises.  Fines for data compromises affect the acquirer and the acquirer may pass these fines on to the merchant when the merchant is responsible.  In this instance, no merchant was responsible for the data breach so the fines (when they are announced) will be absorbed by Heartland. The issuing banks deal with fraudulent activity as a result of any data compromise between the card holder and the merchant.  Chargebacks may affect some merchants, but most likely, the distribution of these card numbers around the world will make the impact on US businesses almost non-existent.  The effects have been felt mainly by card holders.</p>
<p>Everything you said in that paragraph is wrong.  You might consider deleting this entire post or checking ALL of your facts first.</p>
<p>There&#8217;s enough blogging and news media on this topic already.  Do some research and get your facts straight.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tom</title>
		<link>http://www.merchant911.org/blog/index.php/2009/03/21/the-last-of-the-heartland-breach/comment-page-1/#comment-1894</link>
		<dc:creator>Tom</dc:creator>
		<pubDate>Mon, 23 Mar 2009 11:33:19 +0000</pubDate>
		<guid isPermaLink="false">http://www.merchant911.org/blog/?p=247#comment-1894</guid>
		<description>*Michel

That&#039;s true for on-line merchants.  Fortunately for us, the Heartland breach involved track 2 data which allows cloning of the mag strip and I think we&#039;ll see more Card Present fraud.  

Also, since this DID involve track data, the banks have been more proactive in replacing cards - as you would expect them to do when they can&#039;t pass the loss on to the merchant.</description>
		<content:encoded><![CDATA[<p>*Michel</p>
<p>That&#8217;s true for on-line merchants.  Fortunately for us, the Heartland breach involved track 2 data which allows cloning of the mag strip and I think we&#8217;ll see more Card Present fraud.  </p>
<p>Also, since this DID involve track data, the banks have been more proactive in replacing cards &#8211; as you would expect them to do when they can&#8217;t pass the loss on to the merchant.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Michel Fahed</title>
		<link>http://www.merchant911.org/blog/index.php/2009/03/21/the-last-of-the-heartland-breach/comment-page-1/#comment-1893</link>
		<dc:creator>Michel Fahed</dc:creator>
		<pubDate>Mon, 23 Mar 2009 11:04:08 +0000</pubDate>
		<guid isPermaLink="false">http://www.merchant911.org/blog/?p=247#comment-1893</guid>
		<description>&quot;The Card Companies are now fining the issuing banks as a result of the losses. That may sound a bit strange since the banks are victims in this whole mess.&quot;

But aren&#039;t the banks charging the merchants at the end with chargebacks, or they&#039;re eating up the losses?</description>
		<content:encoded><![CDATA[<p>&#8220;The Card Companies are now fining the issuing banks as a result of the losses. That may sound a bit strange since the banks are victims in this whole mess.&#8221;</p>
<p>But aren&#8217;t the banks charging the merchants at the end with chargebacks, or they&#8217;re eating up the losses?</p>
]]></content:encoded>
	</item>
</channel>
</rss>

