<?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: TK Maxx and banking regulation</title>
	<atom:link href="http://www.lightbluetouchpaper.org/2007/03/30/tk-maxx-and-banking-regulation/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.lightbluetouchpaper.org/2007/03/30/tk-maxx-and-banking-regulation/</link>
	<description>Security Research, Computer Laboratory, University of Cambridge</description>
	<pubDate>Sun, 27 Jul 2008 09:29:10 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5.1</generator>
		<item>
		<title>By: Ross Anderson</title>
		<link>http://www.lightbluetouchpaper.org/2007/03/30/tk-maxx-and-banking-regulation/#comment-21822</link>
		<dc:creator>Ross Anderson</dc:creator>
		<pubDate>Fri, 04 May 2007 21:50:11 +0000</pubDate>
		<guid isPermaLink="false">http://www.lightbluetouchpaper.org/2007/03/30/tk-maxx-and-banking-regulation/#comment-21822</guid>
		<description>According to today's Wall Street Journal, it's thought that the folks who broke into TK Maxx exploited the vulnerability of WEP:

 http://online.wsj.com/article/SB117824446226991797.html

The article's also interesting in that it shows up how long even the US banking industry took to cope, despite the breach disclosure laws there</description>
		<content:encoded><![CDATA[<p>According to today&#8217;s Wall Street Journal, it&#8217;s thought that the folks who broke into TK Maxx exploited the vulnerability of WEP:</p>
<p> <a href="http://online.wsj.com/article/SB117824446226991797.html" rel="nofollow">http://online.wsj.com/article/SB117824446226991797.html</a></p>
<p>The article&#8217;s also interesting in that it shows up how long even the US banking industry took to cope, despite the breach disclosure laws there</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: TillMonkey</title>
		<link>http://www.lightbluetouchpaper.org/2007/03/30/tk-maxx-and-banking-regulation/#comment-21582</link>
		<dc:creator>TillMonkey</dc:creator>
		<pubDate>Thu, 19 Apr 2007 15:29:57 +0000</pubDate>
		<guid isPermaLink="false">http://www.lightbluetouchpaper.org/2007/03/30/tk-maxx-and-banking-regulation/#comment-21582</guid>
		<description>Re:" I was recently due a refund, and the company needed my credit card number as it had been deleted once the original transaction had been completed. Why don’t they all do the same?"

For all the reasons already stated plus the fact that you could give them an alternate card number for the refund. Which is money laundering, especially with the advent of barely traceable prepaid debit cards......</description>
		<content:encoded><![CDATA[<p>Re:&#8221; I was recently due a refund, and the company needed my credit card number as it had been deleted once the original transaction had been completed. Why don’t they all do the same?&#8221;</p>
<p>For all the reasons already stated plus the fact that you could give them an alternate card number for the refund. Which is money laundering, especially with the advent of barely traceable prepaid debit cards&#8230;&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: giafly</title>
		<link>http://www.lightbluetouchpaper.org/2007/03/30/tk-maxx-and-banking-regulation/#comment-21577</link>
		<dc:creator>giafly</dc:creator>
		<pubDate>Thu, 19 Apr 2007 12:50:21 +0000</pubDate>
		<guid isPermaLink="false">http://www.lightbluetouchpaper.org/2007/03/30/tk-maxx-and-banking-regulation/#comment-21577</guid>
		<description>Brian,

Re: I was recently due a refund, and the company needed my credit card number as it had been deleted once the original transaction had been completed. Why don’t they all do the same?

How do you know who you were talking to? Handling such calls may have been outsourced to a call-centre without full access to the company's CRM system that contained your records. Hence they needed details from you. The call-centre operator had been instructed not to admit this and so misled you.</description>
		<content:encoded><![CDATA[<p>Brian,</p>
<p>Re: I was recently due a refund, and the company needed my credit card number as it had been deleted once the original transaction had been completed. Why don’t they all do the same?</p>
<p>How do you know who you were talking to? Handling such calls may have been outsourced to a call-centre without full access to the company&#8217;s CRM system that contained your records. Hence they needed details from you. The call-centre operator had been instructed not to admit this and so misled you.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ross Anderson</title>
		<link>http://www.lightbluetouchpaper.org/2007/03/30/tk-maxx-and-banking-regulation/#comment-21558</link>
		<dc:creator>Ross Anderson</dc:creator>
		<pubDate>Wed, 18 Apr 2007 07:20:46 +0000</pubDate>
		<guid isPermaLink="false">http://www.lightbluetouchpaper.org/2007/03/30/tk-maxx-and-banking-regulation/#comment-21558</guid>
		<description>The BBC &lt;a href="http://news.bbc.co.uk/1/hi/technology/6559509.stm" rel="nofollow"&gt;reports &lt;/a&gt; a &lt;a href="http://www.secerno.com/?pg=Press&#38;newsid=93" rel="nofollow"&gt;survey&lt;/a&gt; showing that consumers say they will shun hacked stores. Another contribution to the growing literature on the &lt;a href="http://www.cl.cam.ac.uk/~rja14/econsec.html" rel="nofollow"&gt;economics of security&lt;/a&gt;. Interestingly, 82% of respondents believed they should be notified of security breaches affecting them - politicians take note!</description>
		<content:encoded><![CDATA[<p>The BBC <a href="http://news.bbc.co.uk/1/hi/technology/6559509.stm" rel="nofollow">reports </a> a <a href="http://www.secerno.com/?pg=Press&amp;newsid=93" rel="nofollow">survey</a> showing that consumers say they will shun hacked stores. Another contribution to the growing literature on the <a href="http://www.cl.cam.ac.uk/~rja14/econsec.html" rel="nofollow">economics of security</a>. Interestingly, 82% of respondents believed they should be notified of security breaches affecting them - politicians take note!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Clive Robinson</title>
		<link>http://www.lightbluetouchpaper.org/2007/03/30/tk-maxx-and-banking-regulation/#comment-21493</link>
		<dc:creator>Clive Robinson</dc:creator>
		<pubDate>Sat, 14 Apr 2007 11:59:07 +0000</pubDate>
		<guid isPermaLink="false">http://www.lightbluetouchpaper.org/2007/03/30/tk-maxx-and-banking-regulation/#comment-21493</guid>
		<description>Brian E,

"Surely once the transaction has been completed and the retailer has got its money from the Credit Card Company, the card records should be deleted."

Alas not, one fairly common form of fraud as far as retailers are concerned is that some time after the goods have been delivered and payment received the Card Holder noticies the charge and says "not mine" to the card company. The card company then takes the money back out of the merchants account irrespective of the card holders previous record. The merchant then has a very uphill struggle getting either the goods or the money back. 

A lot of small merchants having been stung this way then check transactions with the CC company, unfortunatly as the merchant finds out fairly quickly this has no effect on this. This has prompted more than one company I know of to keep all CC details relating to the transaction in DBs so that they have their own Black/Grey/White lists to work against.</description>
		<content:encoded><![CDATA[<p>Brian E,</p>
<p>&#8220;Surely once the transaction has been completed and the retailer has got its money from the Credit Card Company, the card records should be deleted.&#8221;</p>
<p>Alas not, one fairly common form of fraud as far as retailers are concerned is that some time after the goods have been delivered and payment received the Card Holder noticies the charge and says &#8220;not mine&#8221; to the card company. The card company then takes the money back out of the merchants account irrespective of the card holders previous record. The merchant then has a very uphill struggle getting either the goods or the money back. </p>
<p>A lot of small merchants having been stung this way then check transactions with the CC company, unfortunatly as the merchant finds out fairly quickly this has no effect on this. This has prompted more than one company I know of to keep all CC details relating to the transaction in DBs so that they have their own Black/Grey/White lists to work against.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ross Anderson</title>
		<link>http://www.lightbluetouchpaper.org/2007/03/30/tk-maxx-and-banking-regulation/#comment-21485</link>
		<dc:creator>Ross Anderson</dc:creator>
		<pubDate>Fri, 13 Apr 2007 21:44:41 +0000</pubDate>
		<guid isPermaLink="false">http://www.lightbluetouchpaper.org/2007/03/30/tk-maxx-and-banking-regulation/#comment-21485</guid>
		<description>The banks make the rules, unfortunately

Ross</description>
		<content:encoded><![CDATA[<p>The banks make the rules, unfortunately</p>
<p>Ross</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andy Steingruebl</title>
		<link>http://www.lightbluetouchpaper.org/2007/03/30/tk-maxx-and-banking-regulation/#comment-21484</link>
		<dc:creator>Andy Steingruebl</dc:creator>
		<pubDate>Fri, 13 Apr 2007 21:41:37 +0000</pubDate>
		<guid isPermaLink="false">http://www.lightbluetouchpaper.org/2007/03/30/tk-maxx-and-banking-regulation/#comment-21484</guid>
		<description>Ross,

Can you summarize the protections in UK law for identity and/or credit theft?

In the US I'm only liable for the first $50 of fraudulent charges, and banks often waive this. 

Should me identity get stolen and credit obtained in my name I have a much bigger problem.

What are the rules there?</description>
		<content:encoded><![CDATA[<p>Ross,</p>
<p>Can you summarize the protections in UK law for identity and/or credit theft?</p>
<p>In the US I&#8217;m only liable for the first $50 of fraudulent charges, and banks often waive this. </p>
<p>Should me identity get stolen and credit obtained in my name I have a much bigger problem.</p>
<p>What are the rules there?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rob Newby</title>
		<link>http://www.lightbluetouchpaper.org/2007/03/30/tk-maxx-and-banking-regulation/#comment-21301</link>
		<dc:creator>Rob Newby</dc:creator>
		<pubDate>Fri, 06 Apr 2007 13:51:19 +0000</pubDate>
		<guid isPermaLink="false">http://www.lightbluetouchpaper.org/2007/03/30/tk-maxx-and-banking-regulation/#comment-21301</guid>
		<description>There are so many conflicting issues at stake here that it's hard to get to the bottom, but here it is in a nutshell:
There is no legal requirement for retailers to protect card holder information in the UK. 
The Payment Card Industry Data Security Standard (PCI DSS) exists globally to protect against payment card fraud. This states that Primary Account Number (PAN), Cardholder Name, Service Code and Expiration Date can be stored encrypted, but magnetic strip, CVC2/CVV2/CID and PIN/PIN Block cannot. 
Whether this is sufficient to protect against fraud is a moot point because the enforcement of these standards is performed by 5 credit card companies (VISA, MC, AmEx, JCB and Discover). 
They have to therefore monitor and assess every retailer who accepts credit cards, and detect any breach. In the US, this is made easier by California Senate Bill SB1386, a disclosure ruling which has now been adopted by 37 states and is soon to be made a national law. In the UK and Europe there is no such ruling. The FSA is the only body I am currently aware of that has the power to make disclosures, but they are primarily focused on the Financial Sector rather than Retail.
I heard on the grapevine that disclosure was up for review in Brussels in November, I have no proof of this however. We are very much due for it for our own protection. One thing we need to remember however is that just because we comply with regulations like PCI DSS, it does not automatically mean that we are secure.</description>
		<content:encoded><![CDATA[<p>There are so many conflicting issues at stake here that it&#8217;s hard to get to the bottom, but here it is in a nutshell:<br />
There is no legal requirement for retailers to protect card holder information in the UK.<br />
The Payment Card Industry Data Security Standard (PCI DSS) exists globally to protect against payment card fraud. This states that Primary Account Number (PAN), Cardholder Name, Service Code and Expiration Date can be stored encrypted, but magnetic strip, CVC2/CVV2/CID and PIN/PIN Block cannot.<br />
Whether this is sufficient to protect against fraud is a moot point because the enforcement of these standards is performed by 5 credit card companies (VISA, MC, AmEx, JCB and Discover).<br />
They have to therefore monitor and assess every retailer who accepts credit cards, and detect any breach. In the US, this is made easier by California Senate Bill SB1386, a disclosure ruling which has now been adopted by 37 states and is soon to be made a national law. In the UK and Europe there is no such ruling. The FSA is the only body I am currently aware of that has the power to make disclosures, but they are primarily focused on the Financial Sector rather than Retail.<br />
I heard on the grapevine that disclosure was up for review in Brussels in November, I have no proof of this however. We are very much due for it for our own protection. One thing we need to remember however is that just because we comply with regulations like PCI DSS, it does not automatically mean that we are secure.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andrew</title>
		<link>http://www.lightbluetouchpaper.org/2007/03/30/tk-maxx-and-banking-regulation/#comment-21228</link>
		<dc:creator>Andrew</dc:creator>
		<pubDate>Tue, 03 Apr 2007 03:49:56 +0000</pubDate>
		<guid isPermaLink="false">http://www.lightbluetouchpaper.org/2007/03/30/tk-maxx-and-banking-regulation/#comment-21228</guid>
		<description>The retailers are allowed to store card numbers after authorisation of the transaction if they are enciphered (using good cryptography and key management).  The storage of full track details or the CVV2 values (the three/four digit code on the back of the card used during CNP transactions) is not permitted post authorisation - regardless of how they are stored.</description>
		<content:encoded><![CDATA[<p>The retailers are allowed to store card numbers after authorisation of the transaction if they are enciphered (using good cryptography and key management).  The storage of full track details or the CVV2 values (the three/four digit code on the back of the card used during CNP transactions) is not permitted post authorisation - regardless of how they are stored.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Brian E</title>
		<link>http://www.lightbluetouchpaper.org/2007/03/30/tk-maxx-and-banking-regulation/#comment-21221</link>
		<dc:creator>Brian E</dc:creator>
		<pubDate>Mon, 02 Apr 2007 21:17:13 +0000</pubDate>
		<guid isPermaLink="false">http://www.lightbluetouchpaper.org/2007/03/30/tk-maxx-and-banking-regulation/#comment-21221</guid>
		<description>I just don't understand why a retailer is allowed to keep all this information. Surely once the transaction has been completed and the retailer has got its money from the Credit Card Company, the card records should be deleted. I know some companies do, I was recently due a refund, and the company needed my credit card number as it had been deleted once the original transaction had been completed. Why don't they all do the same?</description>
		<content:encoded><![CDATA[<p>I just don&#8217;t understand why a retailer is allowed to keep all this information. Surely once the transaction has been completed and the retailer has got its money from the Credit Card Company, the card records should be deleted. I know some companies do, I was recently due a refund, and the company needed my credit card number as it had been deleted once the original transaction had been completed. Why don&#8217;t they all do the same?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
