<?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: Visa&#8217;s Retail Token Advice Of Token Value</title>
	<atom:link href="http://storefrontbacktalk.com/securityfraud/visas-retail-token-advice-of-token-value/feed/" rel="self" type="application/rss+xml" />
	<link>http://storefrontbacktalk.com/securityfraud/visas-retail-token-advice-of-token-value/</link>
	<description>Techniques, Tools and Tirades about Retail Technology and E-Commerce</description>
	<lastBuildDate>Wed, 08 Feb 2012 16:02:40 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: Michael Cherry</title>
		<link>http://storefrontbacktalk.com/securityfraud/visas-retail-token-advice-of-token-value/comment-page-1/#comment-64040</link>
		<dc:creator>Michael Cherry</dc:creator>
		<pubDate>Sun, 11 Oct 2009 09:11:45 +0000</pubDate>
		<guid isPermaLink="false">http://www.storefrontbacktalk.com/?p=3956#comment-64040</guid>
		<description>Does VISA realize that lawsuits are coming and psychologists don’t get sued? I believe both of the following almost contradictory statements:
1. Customer submitted credit cards are radioactive and they need to be immediately encrypted as they are swiped.
2. Data centers that store data-at-rest can be designed to automatically identify and block breach attempts.  Database encryption and the associated key management headaches are unnecessary.

Michael Cherry, Cherry Biometrics Inc.
Vice Chair, Digital Technology Committee
National Association of Criminal Defense Lawyers</description>
		<content:encoded><![CDATA[<p>Does VISA realize that lawsuits are coming and psychologists don’t get sued? I believe both of the following almost contradictory statements:<br />
1. Customer submitted credit cards are radioactive and they need to be immediately encrypted as they are swiped.<br />
2. Data centers that store data-at-rest can be designed to automatically identify and block breach attempts.  Database encryption and the associated key management headaches are unnecessary.</p>
<p>Michael Cherry, Cherry Biometrics Inc.<br />
Vice Chair, Digital Technology Committee<br />
National Association of Criminal Defense Lawyers</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Steven Kendus</title>
		<link>http://storefrontbacktalk.com/securityfraud/visas-retail-token-advice-of-token-value/comment-page-1/#comment-64031</link>
		<dc:creator>Steven Kendus</dc:creator>
		<pubDate>Thu, 08 Oct 2009 16:34:56 +0000</pubDate>
		<guid isPermaLink="false">http://www.storefrontbacktalk.com/?p=3956#comment-64031</guid>
		<description>The best practices for data field encryption announced by Visa work toward developing a standard approach while offering guidance to payment solution providers. As Schuman points out, the document rehashed conventional wisdom and long-standing Visa and PCI best practices. However, there is definite value in the fact that Visa is actually weighing in and looking to provide some guidance. The five key implementation objectives outlined in the document provide some validation to tokenization approaches that are currently in production. Likewise, their stance that no single technology can completely solve for fraud has merit. Existing solutions that use both end-to-end encryption to encrypt card data from the point of sale, and tokenization on the back end of the transaction support their stance.</description>
		<content:encoded><![CDATA[<p>The best practices for data field encryption announced by Visa work toward developing a standard approach while offering guidance to payment solution providers. As Schuman points out, the document rehashed conventional wisdom and long-standing Visa and PCI best practices. However, there is definite value in the fact that Visa is actually weighing in and looking to provide some guidance. The five key implementation objectives outlined in the document provide some validation to tokenization approaches that are currently in production. Likewise, their stance that no single technology can completely solve for fraud has merit. Existing solutions that use both end-to-end encryption to encrypt card data from the point of sale, and tokenization on the back end of the transaction support their stance.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

