• White Papers |
• Blogs |
• Video |
• Webcasts |
• Podcasts |
• Events |
• Solution Centers |
• Newsletters |
• Magazine |
• RSS Feeds

PCI Standards Body Moves Ahead on Payment-Application Certification

PCI Security Standards Council releases list of certified payment applications under Payment Application Data Security Standard.

By Ellen Messmer

April 17, 2008 — CIO — The PCI Security Standards Council, which establishes requirements for the payment-card industry, yesterday formally launched its payment-application security program.

The Council announced the Payment Application Data Security Standard (PA-DSS) as an effort distinct from its older Data Security Standard 1.1 (DSS 1.1).

DSS 1.1 comprises a list of 12 broad-based security requirements that the payment-card associations and banks, which enforce compliance mandates, ask any business handling credit or debit cards to follow or face consequences, which could include fines or higher fees.

In contrast, the PA-DSS program is intended to cover testing and certification requirements for payment applications sold, distributed or licensed to third parties and installed off-the-shelf without much customization. The Council has published a frequently-asked questions document emphasizing that payment applications developed in-house by merchants or service providers are not subject to the PA-DSS requirements.

PA-DSS entails the Council assuming responsibility for Visa's Payment Application Best Practices program, with the Council's payment-brand membership, American Express, Discover Financial Services, JCB International and MasterCard, backing what had been only a Visa requirement for vendor-developed payment applications.

But more is on tap from the PCI Security Standards Council, says Bob Russo, its general manager. "Later this year we'll be rolling out a new version of the DSS," says Russo, noting this is expected to be in the September timeframe, with a possible 2.0 version.

Russo points out that the revised DSS will basically seek to clarify the 12-point DSS guidelines to answer questions that have come up, which are impacting decisions that businesses are making to comply with DSS 1.1

And there are many.

One security manager for a large U.S.-based bank, who asked he not be named, says it's not clear whether a requirement for "segmentation" of the network for purposes of protecting card data means you have to use a LAN.

In another instance, the DSS 1.1 requirement for firewalls is subject to question. The Jericho Forum, an international organization of about 60 large multi-national companies dedicated to finding innovative e-commerce security methods, believes network firewalls may not be the best approach in all situations involving online collaboration.

Russo says he would be happy to open a dialog on the question of firewalls in order to hear about what could be viable alternatives. He said the Council is receiving input now to grasp the major questions about DSS.

Another change already envisioned for DSS entails making the so-called "6.6 requirement" for application security, now a voluntary process that calls for either buying a Web application gateway or performing a code review, mandatory this June.

 

Email

Print

Comments

Share [+]

Digg This

SlashDot

LinkedIn