Risk
10/7/2010
12:55 PM
50%
50%

Credit Industry Pitches Card Encryption

The Payment Card Industry council has released new guidance on security standards.




Strategic Security Survey: Global Threat, Local Pain
(click for larger image and for full photo gallery)
On Tuesday, the Payment Card Industry (PCI) Security Standards Council released new guidance on the use of point-to-point encryption and EMV card security standards. The guidance takes the form of two new white papers, produced by a collaboration of the council's technical working group, special interest groups, as well as various industry and security experts and vendors.

The new guidance is designed to help organizations "understand how they can better secure their payment card data and how specific technologies may assist them in meeting the requirements of the PCI Data Security Standard (DSS)," said Troy Leach, chief standards architect for the PCI Security Standards Council.

The EMV card security feature, also known as "chip and PIN," requires consumers to enter a personal identification number when paying with a credit or debit card in person. But while EMV (which was named for the companies that developed the standard, Eurocard, Mastercard, and Visa) was designed to cryptographically protect the purchasing process, card data -- including routing data -- still gets sent to processors in clear text. "If this data is obtained by criminals at some stage of the process, it can be used to create 'card not present' fraud," said Jeremy King, European regional director for PCI.

Accordingly, the council is exploring point-to-point encryption, which it purposefully avoids calling end-to-end encryption, since data would only be encrypted at certain points. "We've been looking at creating a road map, and this is what we've released with the white paper, which lays out how point-to-point encryption can work, and how it will work," said King.

One upside to such encryption would be that merchants would no longer have to ensure that customer data stays secure, since it would already be encrypted, thus easing their PCI DSS compliance requirements and hopefully enticing more companies to comply with the standard.

While official compliance statistics haven't been released, some studies suggest that many organizations don't treat PCI compliance as a requirement. However, according to one recent study, complying with PCI improves security and reduces an organization's risk of data breaches.

Introducing PCI changes, however, takes time. "The devil is in the details, and there are a lot of technical issues around how you introduce point-to-point encryption," said King, not least of which is key management. In addition, "we're introducing global standards for adoption anywhere in the world, and that creates challenges in different parts of the world," he said.

In other PCI news, on October 28, the PCI Council will release new versions of the PCI DSS, PIN Transaction Security requirements, and the Payment Application Data Security Standard. The new versions will now be refreshed every three years, instead of two, and the simultaneous update is designed to keep future versions in sync.

"The updates to the standards are certainly going to help the merchants," said King. "They're designed with the new three-year lifecycle to give them more time and give them more time to understand how they've matured, and that's a key phrase, because the standards have been around for some time. They're quite mature."

Comment  | 
Print  | 
More Insights
Register for Dark Reading Newsletters
White Papers
Cartoon
Latest Comment: nice one
Current Issue
Flash Poll
Video
Slideshows
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2015-0845
Published: 2015-04-17
Format string vulnerability in Movable Type Pro, Open Source, and Advanced before 5.2.13 and Pro and Advanced 6.0.x before 6.0.8 allows remote attackers to execute arbitrary code via vectors related to localization of templates.

CVE-2015-0967
Published: 2015-04-17
Multiple cross-site scripting (XSS) vulnerabilities in SearchBlox before 8.2 allow remote attackers to inject arbitrary web script or HTML via (1) the search field in plugin/index.html or (2) the title field in the Create Featured Result form in admin/main.jsp.

CVE-2015-0968
Published: 2015-04-17
Unrestricted file upload vulnerability in admin/uploadImage.html in SearchBlox before 8.2 allows remote attackers to execute arbitrary code by uploading a file with an executable extension and the image/jpeg content type, a different vulnerability than CVE-2013-3590.

CVE-2015-0969
Published: 2015-04-17
SearchBlox before 8.2 allows remote attackers to obtain sensitive information via a pretty=true action to the _cluster/health URI.

CVE-2015-0970
Published: 2015-04-17
Cross-site request forgery (CSRF) vulnerability in SearchBlox before 8.2 allows remote attackers to hijack the authentication of arbitrary users.

Dark Reading Radio
Archived Dark Reading Radio
Join security and risk expert John Pironti and Dark Reading Editor-in-Chief Tim Wilson for a live online discussion of the sea-changing shift in security strategy and the many ways it is affecting IT and business.