<?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: PA-DSS, and you thought PCI was a mess!</title>
	<atom:link href="http://www.merchantequip.com/merchant-account-blog/735/pa-dss-and-you-thought-pci-was-a-mess/feed" rel="self" type="application/rss+xml" />
	<link>http://www.merchantequip.com/merchant-account-blog/735/pa-dss-and-you-thought-pci-was-a-mess</link>
	<description>Merchant Accounts, Ecommerce, Processing Equipment</description>
	<lastBuildDate>Fri, 23 Sep 2011 22:04:18 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: DSSReader</title>
		<link>http://www.merchantequip.com/merchant-account-blog/735/pa-dss-and-you-thought-pci-was-a-mess/comment-page-1#comment-21232</link>
		<dc:creator>DSSReader</dc:creator>
		<pubDate>Wed, 02 Dec 2009 18:05:22 +0000</pubDate>
		<guid isPermaLink="false">http://www.merchantaccountblog.com/?p=735#comment-21232</guid>
		<description>See pg11 of the PCI DSS (v1.2.1)document.  It clearly states it is *NOT* a PCI-DSS requirement to use PA-DSS validated applications.  The sky is really not falling.</description>
		<content:encoded><![CDATA[<p>See pg11 of the PCI DSS (v1.2.1)document.  It clearly states it is *NOT* a PCI-DSS requirement to use PA-DSS validated applications.  The sky is really not falling.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dave</title>
		<link>http://www.merchantequip.com/merchant-account-blog/735/pa-dss-and-you-thought-pci-was-a-mess/comment-page-1#comment-21036</link>
		<dc:creator>Dave</dc:creator>
		<pubDate>Fri, 23 Oct 2009 06:03:33 +0000</pubDate>
		<guid isPermaLink="false">http://www.merchantaccountblog.com/?p=735#comment-21036</guid>
		<description>It seems that somebody wants to earn more money on this situation.

It is nightmare for ecommerce.</description>
		<content:encoded><![CDATA[<p>It seems that somebody wants to earn more money on this situation.</p>
<p>It is nightmare for ecommerce.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dave</title>
		<link>http://www.merchantequip.com/merchant-account-blog/735/pa-dss-and-you-thought-pci-was-a-mess/comment-page-1#comment-21035</link>
		<dc:creator>Dave</dc:creator>
		<pubDate>Fri, 23 Oct 2009 06:01:52 +0000</pubDate>
		<guid isPermaLink="false">http://www.merchantaccountblog.com/?p=735#comment-21035</guid>
		<description>&gt; Are they trying to shut down the Internet or what?

I agree. 

It seems that somebody wants to earn more money.</description>
		<content:encoded><![CDATA[<p>&gt; Are they trying to shut down the Internet or what?</p>
<p>I agree. </p>
<p>It seems that somebody wants to earn more money.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mike</title>
		<link>http://www.merchantequip.com/merchant-account-blog/735/pa-dss-and-you-thought-pci-was-a-mess/comment-page-1#comment-20690</link>
		<dc:creator>Mike</dc:creator>
		<pubDate>Fri, 04 Sep 2009 21:01:40 +0000</pubDate>
		<guid isPermaLink="false">http://www.merchantaccountblog.com/?p=735#comment-20690</guid>
		<description>Can this really be true? This would essentially kill ecommerce! Think of how many people use ZenCart, OSCommerce, Virtuemart. And even several of the commercial carts that would never be able to afford a 100k validation procedure. Are they trying to shut down the Internet or what?</description>
		<content:encoded><![CDATA[<p>Can this really be true? This would essentially kill ecommerce! Think of how many people use ZenCart, OSCommerce, Virtuemart. And even several of the commercial carts that would never be able to afford a 100k validation procedure. Are they trying to shut down the Internet or what?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: jestep</title>
		<link>http://www.merchantequip.com/merchant-account-blog/735/pa-dss-and-you-thought-pci-was-a-mess/comment-page-1#comment-20634</link>
		<dc:creator>jestep</dc:creator>
		<pubDate>Fri, 07 Aug 2009 22:51:53 +0000</pubDate>
		<guid isPermaLink="false">http://www.merchantaccountblog.com/?p=735#comment-20634</guid>
		<description>This is half the problem... 

Acquirers have no idea how to, nor the means to police the situation. This is exactly why we&#039;ve all seen the emergence of the PCI compliance fee, that most level 4 merchants are now subject to. Even FDR added a PCI fee for non-compliant level 4 merchants. Many ISO&#039;s charge an additional fee if their customer&#039;s don&#039;t use their prefered PCI scanning vendor...

I&#039;ve worked with about 8 ISO&#039;s related to the PCI mess, and none of them have any real idea on what PCI is, or who it actually applies to, or why we have it, or what it actually is.

They simply add a PCI compliance fee to their customer&#039;s accounts because it somehow removes their liability from a data breach. 

And Visa... Visa is so far removed from the situation that they have no idea what is actually happening on the merchants level. The whole situation is out of control...</description>
		<content:encoded><![CDATA[<p>This is half the problem&#8230; </p>
<p>Acquirers have no idea how to, nor the means to police the situation. This is exactly why we&#8217;ve all seen the emergence of the PCI compliance fee, that most level 4 merchants are now subject to. Even FDR added a PCI fee for non-compliant level 4 merchants. Many ISO&#8217;s charge an additional fee if their customer&#8217;s don&#8217;t use their prefered PCI scanning vendor&#8230;</p>
<p>I&#8217;ve worked with about 8 ISO&#8217;s related to the PCI mess, and none of them have any real idea on what PCI is, or who it actually applies to, or why we have it, or what it actually is.</p>
<p>They simply add a PCI compliance fee to their customer&#8217;s accounts because it somehow removes their liability from a data breach. </p>
<p>And Visa&#8230; Visa is so far removed from the situation that they have no idea what is actually happening on the merchants level. The whole situation is out of control&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: A Mous</title>
		<link>http://www.merchantequip.com/merchant-account-blog/735/pa-dss-and-you-thought-pci-was-a-mess/comment-page-1#comment-20633</link>
		<dc:creator>A Mous</dc:creator>
		<pubDate>Fri, 07 Aug 2009 18:08:40 +0000</pubDate>
		<guid isPermaLink="false">http://www.merchantaccountblog.com/?p=735#comment-20633</guid>
		<description>What you wrote here is not exactly true. People need to have a better understanding of the things they chooose to write about. 
&quot;If there is not a mass-movement to get software PA-DSS compliant in the next year, almost every single online store will be out of compliance and subject to fines, or being shut down. This is only a small part of the problem. There’s still thousands of retail businesses using older payment software and the cost of upgrading would be in the millions, assuming it’s even possible.&quot; This is according to Visa: &quot;Payment Application Security Mandates
On January 1, 2008, Visa implemented a series of mandates to eliminate the use of vulnerable payment applications from the Visa payment system. These mandates require acquirers to ensure that their merchants and agents do not use payment applications known to retain sensitive cardholder data (i.e. full magnetic stripe data, CVV2 or PIN data) and require the use of payment applications that are compliant to the PA-DSS. 

While the use of PA-DSS validated payment applications is recommended, a payment application need not be included on Visa’s list of PABP validated payment applications or PCI SSC’s list of PA-DSS validated payment applications in order to comply with Phase 2, Phase 3 and Phase 5 requirements for use of PA-DSS compliant applications. Acquirers may determine the PA-DSS compliancy of a payment application through alternate validation processes, which should confirm that payment applications meet PA-DSS requirements and should facilitate compliance with the PCI DSS.&quot;</description>
		<content:encoded><![CDATA[<p>What you wrote here is not exactly true. People need to have a better understanding of the things they chooose to write about.<br />
&#8220;If there is not a mass-movement to get software PA-DSS compliant in the next year, almost every single online store will be out of compliance and subject to fines, or being shut down. This is only a small part of the problem. There’s still thousands of retail businesses using older payment software and the cost of upgrading would be in the millions, assuming it’s even possible.&#8221; This is according to Visa: &#8220;Payment Application Security Mandates<br />
On January 1, 2008, Visa implemented a series of mandates to eliminate the use of vulnerable payment applications from the Visa payment system. These mandates require acquirers to ensure that their merchants and agents do not use payment applications known to retain sensitive cardholder data (i.e. full magnetic stripe data, CVV2 or PIN data) and require the use of payment applications that are compliant to the PA-DSS. </p>
<p>While the use of PA-DSS validated payment applications is recommended, a payment application need not be included on Visa’s list of PABP validated payment applications or PCI SSC’s list of PA-DSS validated payment applications in order to comply with Phase 2, Phase 3 and Phase 5 requirements for use of PA-DSS compliant applications. Acquirers may determine the PA-DSS compliancy of a payment application through alternate validation processes, which should confirm that payment applications meet PA-DSS requirements and should facilitate compliance with the PCI DSS.&#8221;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Robert Jackson</title>
		<link>http://www.merchantequip.com/merchant-account-blog/735/pa-dss-and-you-thought-pci-was-a-mess/comment-page-1#comment-20593</link>
		<dc:creator>Robert Jackson</dc:creator>
		<pubDate>Tue, 14 Jul 2009 11:32:56 +0000</pubDate>
		<guid isPermaLink="false">http://www.merchantaccountblog.com/?p=735#comment-20593</guid>
		<description>Merchants processing payment transactions must be PCI DSS compliant.  However, they are NOT required to use PA-DSS compliant applications.

If they do not then they must demonstrate that the payment applications they use are compliant with the PCI DSS which won&#039;t need to do if the apps are PA-DSS certified.

Having said this, a merchant cannot use an application that would fail the PA-DSS (eg if it stored CVV2 permanently or stored CHD unencrypted) without compensating controls.

The long and the short of it is that PA-DSS is not mandatory but not having it is a major drawback for payment application vendors.</description>
		<content:encoded><![CDATA[<p>Merchants processing payment transactions must be PCI DSS compliant.  However, they are NOT required to use PA-DSS compliant applications.</p>
<p>If they do not then they must demonstrate that the payment applications they use are compliant with the PCI DSS which won&#8217;t need to do if the apps are PA-DSS certified.</p>
<p>Having said this, a merchant cannot use an application that would fail the PA-DSS (eg if it stored CVV2 permanently or stored CHD unencrypted) without compensating controls.</p>
<p>The long and the short of it is that PA-DSS is not mandatory but not having it is a major drawback for payment application vendors.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Al</title>
		<link>http://www.merchantequip.com/merchant-account-blog/735/pa-dss-and-you-thought-pci-was-a-mess/comment-page-1#comment-20562</link>
		<dc:creator>Al</dc:creator>
		<pubDate>Tue, 23 Jun 2009 07:38:30 +0000</pubDate>
		<guid isPermaLink="false">http://www.merchantaccountblog.com/?p=735#comment-20562</guid>
		<description>So if we all comply and get a PA-DSS audit complete at great expense and in three years time fraud is still on the rise can we fine MasterCard &amp; Visa? :)</description>
		<content:encoded><![CDATA[<p>So if we all comply and get a PA-DSS audit complete at great expense and in three years time fraud is still on the rise can we fine MasterCard &amp; Visa? <img src='http://www.merchantequip.com/merchant-account-blog/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: VISA PA DSS - The fall of small to medium ecommerce businesses? &#124; Global Hosting Talk</title>
		<link>http://www.merchantequip.com/merchant-account-blog/735/pa-dss-and-you-thought-pci-was-a-mess/comment-page-1#comment-20557</link>
		<dc:creator>VISA PA DSS - The fall of small to medium ecommerce businesses? &#124; Global Hosting Talk</dc:creator>
		<pubDate>Fri, 19 Jun 2009 20:39:57 +0000</pubDate>
		<guid isPermaLink="false">http://www.merchantaccountblog.com/?p=735#comment-20557</guid>
		<description>[...] http://www.merchantaccountblog.com/7&#8230;pci-was-a-mess [...]</description>
		<content:encoded><![CDATA[<p>[...] <a href="http://www.merchantaccountblog.com/7&#8230;pci-was-a-mess" rel="nofollow">http://www.merchantaccountblog.com/7&#8230;pci-was-a-mess</a> [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ber2</title>
		<link>http://www.merchantequip.com/merchant-account-blog/735/pa-dss-and-you-thought-pci-was-a-mess/comment-page-1#comment-20554</link>
		<dc:creator>Ber2</dc:creator>
		<pubDate>Fri, 19 Jun 2009 11:15:39 +0000</pubDate>
		<guid isPermaLink="false">http://www.merchantaccountblog.com/?p=735#comment-20554</guid>
		<description>I agree with you. It will lead to a big mesh.</description>
		<content:encoded><![CDATA[<p>I agree with you. It will lead to a big mesh.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

