Risk
10/7/2010
12:55 PM
Connect Directly
RSS
E-Mail
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
Current Issue
Dark Reading Must Reads - September 25, 2014
Dark Reading's new Must Reads is a compendium of our best recent coverage of identity and access management. Learn about access control in the age of HTML5, how to improve authentication, why Active Directory is dead, and more.
Flash Poll
Video
Slideshows
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2003-1598
Published: 2014-10-01
SQL injection vulnerability in log.header.php in WordPress 0.7 and earlier allows remote attackers to execute arbitrary SQL commands via the posts variable.

CVE-2011-4624
Published: 2014-10-01
Cross-site scripting (XSS) vulnerability in facebook.php in the GRAND FlAGallery plugin (flash-album-gallery) before 1.57 for WordPress allows remote attackers to inject arbitrary web script or HTML via the i parameter.

CVE-2012-0811
Published: 2014-10-01
Multiple SQL injection vulnerabilities in Postfix Admin (aka postfixadmin) before 2.3.5 allow remote authenticated users to execute arbitrary SQL commands via (1) the pw parameter to the pacrypt function, when mysql_encrypt is configured, or (2) unspecified vectors that are used in backup files gene...

CVE-2014-2640
Published: 2014-10-01
Cross-site scripting (XSS) vulnerability in HP System Management Homepage (SMH) before 7.4 allows remote attackers to inject arbitrary web script or HTML via unspecified vectors.

CVE-2014-2641
Published: 2014-10-01
Cross-site request forgery (CSRF) vulnerability in HP System Management Homepage (SMH) before 7.4 allows remote authenticated users to hijack the authentication of unspecified victims via unknown vectors.

Best of the Web
Dark Reading Radio
Archived Dark Reading Radio
Chris Hadnagy, who hosts the annual Social Engineering Capture the Flag Contest at DEF CON, will discuss the latest trends attackers are using.