 |
PA DSS: What To Do When Best Practices Become Mandatory
Written by David Taylor
September 18, 2008
Guest Columnist David Taylor is the Founder of the PCI Knowledge Base, Research Director of the PCI Alliance and a former E-Commerce and Security analyst with Gartner.
What's the difference between mandates and PCI best practices? Best practices sounds nicer.
It's an important—and potentially the only—distinction that will be critical in less than two weeks. Just when you thought PCI was solidifying, when perhaps it was safe to swim again in your POS waters, there's a major PCI-related deadline coming up on October 1, and most merchants aren't aware of the details. That's true even though they've been given an entire year to get up to speed.
Known as "Phase III" of the PA DSS compliance mandates, it is the first major push to get Level 3 and 4 merchants to wake up to the importance of PCI. Like other PCI-related mandates, it's driven by Visa, through the card acquirers, and it requires that the acquirers not board (sign up) any new merchants that are not either PCI compliant or running PA DSS-compliant payment applications. This is designed to stop merchants from switching from "tough" to "easy" acquirers, among other objectives. What's interesting is that only last year these were Visa's "best practices," for merchants and vendors, and they are now becoming the toughest and most comprehensive of the standards designed to secure the payment process.
There's a big difference between best practices and mandates. The study of PCI Best Practices that the PCI Knowledge Base is doing for the National Retail Federation would be very different if they were all mandates—and we'd get a lot of merchants pretty ticked off. Well, that's the sort of impact we're expecting among the merchant community as the Payment Application Best Practices (PABP) becomes a powerful mandate in 2009 and 2010.
The power of PA DSS is contained in just a couple of sentences: As of October 1, 2009, the payment networks and their agents must "de-certify" vulnerable (non-compliant) payment applications and on July 1, 2010, non-compliant payment applications will no longer be processed by the payment networks. Get it? Transactions from non-compliant applications won't be processed. Period.
All merchants, listen up: This is not a mandate just for Level 1 merchants. It applies to all merchants, everywhere. Now I'm not a betting man (anymore—long story), but I'm willing to bet that about 99 percent of retailers haven't thought this through and started making plans to change out (or upgrade) their software, which will involve much more than creating a bunch of reports for the PCI assessor's annual visit.
It turns out that when you upgrade or switch your payment applications, a bunch of other applications may not work so well. Even though the deadlines are a year or two away, when you add in the PED device deadlines (don't get me started on those), merchants simply cannot wait to plan the upgrade for another six months.
One of the biggest differences between PCI DSS and PA DSS is that although there's no list of PCI-compliant merchants, there is a list of PA DSS-compliant vendors and products. Actually, there's a list of PABP-compliant vendors and products that is being upgraded during this "transition period" to be a list of PA DSS vendors and products. The object is to provide a list to make it easier for merchants to select compliant products.
That's handy. We love lists. However, by creating such a list, Visa (now the PCI SSC) has provided a huge incentive to vendors to get on that list, since it can impact company revenues by millions of dollars, more or less. Add to this that the PCI (and PA DSS) assessment market has become very price-competitive and the potential to "cut corners" in the name of cost effectiveness is growing and will continue to grow substantially as these new "make or break" PA DSS deadlines approach.
To combat this, the PCI SSC has put into place a new quality assurance (QA) process. That's also good. We love quality. But then again, who is going to report "questionable" assessments of the vendors, when neither of the parties to the process (the vendor and the assessor) have any motivation to do so? (See related column about the phoned-in assessment.)
That's where retailers come in. Merchants simply cannot assume that just because a payment application product is on some long list that there has been a thorough and complete review, comparable to a Level 1 merchant's PCI DSS assessment. Merchants must review the detailed audit reports and even be directly involved in their vendor's PA DSS assessment. Merchants must own this process, simply because they own the resulting liability and brand damage.
Several weeks ago, we wrote a column on why and how payment outsourcing will become a huge opportunity. This column is a partial explanation of why we take that position. Currently, this is only common among Level 4 merchants. But the PA DSS mandates will, we argue, drive interest in payment application outsourcing among Level 3 merchants.
On the other hand, the pricing of these services is a common source of complaints in our PCI Best Practices research. We expect that as the popularity grows, the average transaction fees will be reduced significantly due to competition. The question for many merchants is when is the right time, if any, to consider outsourcing to minimize both transition costs and transaction fees?
By the way, if you're a retailer, we want to get you involved in both PCI Knowledge Base and the best practices study we're doing for the National Retail Federation. If you'd like to participate, please send me an E-mail at David.Taylor@KnowPCI.com. |
|
 |
Advertisement
 |
Evan Schuman is the former retail technology editor for eWEEK.com, PCMagazine, CIOInsight and retail reporter for RISNews and Consumer Goods Technology. Having covered IT issues for 21 years - and other stuff like legal affairs, politics, Wall Street and the environment for about eight years before that - Schuman is in a good position to gripe about technology trends and sometimes accidentally make a good point.
|
 |
 |
Sears.com Melts Down On Black Friday, But Costco, Walmart, Saks and Kmart Have Issues, Too
Sears.com suffered the worst Web problems on Black Friday (Nov. 28), experiencing a series of complete site crashes for much of the day. Although no other major retailer came close, according to preliminary reports, many of the industry's largest merchants suffered site slowdowns or other Web problems, including Walmart, Kmart, Saks, Overstock, Amazon, Target, Kohl's, Costco and Buy.com.
|
|
 |
|
 |