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
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
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.
Russo said the Council will issue guidance on this in the form of a White Paper next month. It will cover the topics of requirement
for application security and explain how “payment application qualified security assessors” (PAQSA) will be named through
an accreditation process.
These PAQSAs would be expected to play a role in evaluating applications at businesses handling credit- and debit-card information.
Some companies are taking novel approaches to tackling PCI requirements.
At the RSA Conference last week, security professionals from office-supply store chain Staples presented a session on masking the 13 to 19 digit
codes on a credit card — what’s known as the “Primary Account Numbers” — as they’re used in business operations and across
This data masking was begun after a lengthy effort to map PCI compliance to how Staples business operations really work to
find out where card data is really used.
Christopher Dunning, director of enterprise information security at Staples, described an ongoing internal effort that involves
using technology which RSA, the security division of EMC, helped develop with Staples to scramble live card data as a one-way
Dunning called it “Data Aliasing Technology” that works by having applications make use of specialized tokens called “alias
numbers” for credit cards. These card aliases have the impact of “limiting the scope of PCI,” says Dunning because the real
card numbers aren’t in use.