<?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: National Retail Federation takes aim at PCI DSS Council</title>
	<atom:link href="http://itknowledgeexchange.techtarget.com/security-bytes/national-retail-federation-takes-aim-at-pci-dss-council/feed/" rel="self" type="application/rss+xml" />
	<link>http://itknowledgeexchange.techtarget.com/security-bytes/national-retail-federation-takes-aim-at-pci-dss-council/</link>
	<description>A SearchSecurity.com blog</description>
	<pubDate>Thu, 26 Nov 2009 08:38:25 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.2</generator>
		<item>
		<title>By: Home Security Systems</title>
		<link>http://itknowledgeexchange.techtarget.com/security-bytes/national-retail-federation-takes-aim-at-pci-dss-council/#comment-413</link>
		<dc:creator>Home Security Systems</dc:creator>
		<pubDate>Thu, 27 Mar 2008 05:42:46 +0000</pubDate>
		<guid isPermaLink="false">http://security.blogs.techtarget.com/2007/10/05/national-retail-federation-takes-aim-at-pci-dss-council/#comment-413</guid>
		<description>&lt;strong&gt;Home Security Systems&lt;/strong&gt;

This takes on special significance given Al Qaeda’ s recent pattern of strikes associated with elections or political transitions. The United States faces increased risk of another attack over the next year and a half, which will make the transition ...</description>
		<content:encoded><![CDATA[<p>&lt;strong&gt;Home Security Systems&lt;/strong&gt;</p>
<p>This takes on special significance given Al Qaeda’ s recent pattern of strikes associated with elections or political transitions. The United States faces increased risk of another attack over the next year and a half, which will make the transition &#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: PCI DSS Compliance Demystified &#187; Blog Archive &#187; Retailers do not need to store credit card data</title>
		<link>http://itknowledgeexchange.techtarget.com/security-bytes/national-retail-federation-takes-aim-at-pci-dss-council/#comment-412</link>
		<dc:creator>PCI DSS Compliance Demystified &#187; Blog Archive &#187; Retailers do not need to store credit card data</dc:creator>
		<pubDate>Thu, 11 Oct 2007 23:55:51 +0000</pubDate>
		<guid isPermaLink="false">http://security.blogs.techtarget.com/2007/10/05/national-retail-federation-takes-aim-at-pci-dss-council/#comment-412</guid>
		<description>[...] There has been a lot of conversation about what David Hogan, CIO of the National Retail Federation (NRF), has said in his letter to the PCI SSC. The famous quote people have been carrying is (copy of letter): All of us — merchants, banks, credit card companies and our customers — want to eliminate credit card fraud. But if the goal is to make credit card data less vulnerable, the ultimate solution is to stop requiring merchants to store card data in the first place. [...]</description>
		<content:encoded><![CDATA[<p>[...] There has been a lot of conversation about what David Hogan, CIO of the National Retail Federation (NRF), has said in his letter to the PCI SSC. The famous quote people have been carrying is (copy of letter): All of us — merchants, banks, credit card companies and our customers — want to eliminate credit card fraud. But if the goal is to make credit card data less vulnerable, the ultimate solution is to stop requiring merchants to store card data in the first place. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Network Security Podcast: Episode 80 &#124; securosis.com</title>
		<link>http://itknowledgeexchange.techtarget.com/security-bytes/national-retail-federation-takes-aim-at-pci-dss-council/#comment-411</link>
		<dc:creator>Network Security Podcast: Episode 80 &#124; securosis.com</dc:creator>
		<pubDate>Wed, 10 Oct 2007 15:54:35 +0000</pubDate>
		<guid isPermaLink="false">http://security.blogs.techtarget.com/2007/10/05/national-retail-federation-takes-aim-at-pci-dss-council/#comment-411</guid>
		<description>[...] Techtarget: National Retail Federation takes aim at PCI DSS Council [...]</description>
		<content:encoded><![CDATA[<p>[...] Techtarget: National Retail Federation takes aim at PCI DSS Council [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Security News &#187; Merchants mad about credit card retention</title>
		<link>http://itknowledgeexchange.techtarget.com/security-bytes/national-retail-federation-takes-aim-at-pci-dss-council/#comment-410</link>
		<dc:creator>Security News &#187; Merchants mad about credit card retention</dc:creator>
		<pubDate>Tue, 09 Oct 2007 19:04:04 +0000</pubDate>
		<guid isPermaLink="false">http://security.blogs.techtarget.com/2007/10/05/national-retail-federation-takes-aim-at-pci-dss-council/#comment-410</guid>
		<description>[...] The latest complaint against PCI and the PCI Security Standards Council is that securing the data is too hard, too expensive and that PCI requires them to retain the data for too long.&#160; Their logic is that if they didn&#8217;t have to keep credit card data in the first place, then the hackers would have no reason to be attacking merchants in the first place.&#160; And their logic is good, at least in part; if they could remove credit card data from their systems, then attackers would see a lot less value in targeting merchants.&#160; Of course, we&#8217;d still be seeing at least some of the attacks, since hackers have been attacking large networks for their resources as long as there&#8217;s been an Internet. [...]</description>
		<content:encoded><![CDATA[<p>[...] The latest complaint against PCI and the PCI Security Standards Council is that securing the data is too hard, too expensive and that PCI requires them to retain the data for too long.&nbsp; Their logic is that if they didn&#8217;t have to keep credit card data in the first place, then the hackers would have no reason to be attacking merchants in the first place.&nbsp; And their logic is good, at least in part; if they could remove credit card data from their systems, then attackers would see a lot less value in targeting merchants.&nbsp; Of course, we&#8217;d still be seeing at least some of the attacks, since hackers have been attacking large networks for their resources as long as there&#8217;s been an Internet. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Karl</title>
		<link>http://itknowledgeexchange.techtarget.com/security-bytes/national-retail-federation-takes-aim-at-pci-dss-council/#comment-409</link>
		<dc:creator>Karl</dc:creator>
		<pubDate>Mon, 08 Oct 2007 17:27:20 +0000</pubDate>
		<guid isPermaLink="false">http://security.blogs.techtarget.com/2007/10/05/national-retail-federation-takes-aim-at-pci-dss-council/#comment-409</guid>
		<description>If anything, PCI doesn't go far enough. For starters, security breach reporting isn't law at the Federal level (yet). The US is behind most of the civilized world in this respect. 

PCI is another attempt at self-regulation by the very companies that ignored the problem for years in the name of profit. PCI is better than nothing, but still not required by law. 

In the US, if  the threat of fines or jail time aren't present, many will ignore such efforts. When consumer protections become law, business inevitably cries foul.

Merchants will experience some pain and anger as a result of years of disregard for privacy &#38; security. While it is true that Consumers frequently do not follow even basic identity theft guidelines, they place only themselves and their families at risk.

Merchants, banks, transaction processors &#38; card issuers who don't encrypt and/or follow good security practices endanger the trust required for the concept of credit cards to work in the first place. 

While I like profit as much as the next person, there are some issues that transcend our right to make money at all costs.

Some states have introduced bills that go further, to extend requirements on merchants. For example, California has introduced:

AB 779 – Data Breach Notification, Identification, and Restitution – As consumer data breaches and identity theft grow in scope and quantity, consumers need to know exactly who is failing to adequately protect their personal information.  For example, TJ Maxx stores parent company allowed 45.6 million credit card numbers to be stolen electronically.  AB 779 would enhance consumer protection by properly identifying the entity responsible for the data breach, require better data protection by retailers and allow for reimbursement of relevant costs to credit unions and community banks stemming from the data breach.

AB 1298 – Omnibus Privacy Protection – AB 1298 would protect consumers’ medical records by extending the state’s existing medical privacy laws to the emerging electronic medical records industry.  AB 1298 also requires businesses and state agencies that release a consumer’s medical information or health insurance information to an unauthorized person to notify the consumer of that data breach. 

If PCI requirements are recalled or softened, it is likely that the Feds would be pressed to finally take action - and that would make more of an impact (good and bad).

Sorry to be blunt - but NRF Chief Information Officer David Hogan should tell his constituents to suck it up and work to improve their systems, and stop whining!</description>
		<content:encoded><![CDATA[<p>If anything, PCI doesn&#8217;t go far enough. For starters, security breach reporting isn&#8217;t law at the Federal level (yet). The US is behind most of the civilized world in this respect. </p>
<p>PCI is another attempt at self-regulation by the very companies that ignored the problem for years in the name of profit. PCI is better than nothing, but still not required by law. </p>
<p>In the US, if  the threat of fines or jail time aren&#8217;t present, many will ignore such efforts. When consumer protections become law, business inevitably cries foul.</p>
<p>Merchants will experience some pain and anger as a result of years of disregard for privacy &amp; security. While it is true that Consumers frequently do not follow even basic identity theft guidelines, they place only themselves and their families at risk.</p>
<p>Merchants, banks, transaction processors &amp; card issuers who don&#8217;t encrypt and/or follow good security practices endanger the trust required for the concept of credit cards to work in the first place. </p>
<p>While I like profit as much as the next person, there are some issues that transcend our right to make money at all costs.</p>
<p>Some states have introduced bills that go further, to extend requirements on merchants. For example, California has introduced:</p>
<p>AB 779 – Data Breach Notification, Identification, and Restitution – As consumer data breaches and identity theft grow in scope and quantity, consumers need to know exactly who is failing to adequately protect their personal information.  For example, TJ Maxx stores parent company allowed 45.6 million credit card numbers to be stolen electronically.  AB 779 would enhance consumer protection by properly identifying the entity responsible for the data breach, require better data protection by retailers and allow for reimbursement of relevant costs to credit unions and community banks stemming from the data breach.</p>
<p>AB 1298 – Omnibus Privacy Protection – AB 1298 would protect consumers’ medical records by extending the state’s existing medical privacy laws to the emerging electronic medical records industry.  AB 1298 also requires businesses and state agencies that release a consumer’s medical information or health insurance information to an unauthorized person to notify the consumer of that data breach. </p>
<p>If PCI requirements are recalled or softened, it is likely that the Feds would be pressed to finally take action - and that would make more of an impact (good and bad).</p>
<p>Sorry to be blunt - but NRF Chief Information Officer David Hogan should tell his constituents to suck it up and work to improve their systems, and stop whining!</p>
]]></content:encoded>
	</item>
</channel>
</rss>
<!-- dynamic -->