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
Comments
Newest First  |  Oldest First  |  Threaded View
Printers: The Weak Link in Enterprise Security
Kelly Sheridan, Associate Editor, Dark Reading,  10/16/2017
20 Questions to Ask Yourself before Giving a Security Conference Talk
Joshua Goldfarb, Co-founder & Chief Product Officer, IDDRA,  10/16/2017
Why Security Leaders Can't Afford to Be Just 'Left-Brained'
Bill Bradley, SVP, Cyber Engineering and Technical Services, CenturyLink,  10/17/2017
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Current Issue
Security Vulnerabilities: The Next Wave
Just when you thought it was safe, researchers have unveiled a new round of IT security flaws. Is your enterprise ready?
Flash Poll
The State of Ransomware
The State of Ransomware
Ransomware has become one of the most prevalent new cybersecurity threats faced by today's enterprises. This new report from Dark Reading includes feedback from IT and IT security professionals about their organization's ransomware experiences, defense plans, and malware challenges. Find out what they had to say!
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2017-0290
Published: 2017-05-09
NScript in mpengine in Microsoft Malware Protection Engine with Engine Version before 1.1.13704.0, as used in Windows Defender and other products, allows remote attackers to execute arbitrary code or cause a denial of service (type confusion and application crash) via crafted JavaScript code within ...

CVE-2016-10369
Published: 2017-05-08
unixsocket.c in lxterminal through 0.3.0 insecurely uses /tmp for a socket file, allowing a local user to cause a denial of service (preventing terminal launch), or possibly have other impact (bypassing terminal access control).

CVE-2016-8202
Published: 2017-05-08
A privilege escalation vulnerability in Brocade Fibre Channel SAN products running Brocade Fabric OS (FOS) releases earlier than v7.4.1d and v8.0.1b could allow an authenticated attacker to elevate the privileges of user accounts accessing the system via command line interface. With affected version...

CVE-2016-8209
Published: 2017-05-08
Improper checks for unusual or exceptional conditions in Brocade NetIron 05.8.00 and later releases up to and including 06.1.00, when the Management Module is continuously scanned on port 22, may allow attackers to cause a denial of service (crash and reload) of the management module.

CVE-2017-0890
Published: 2017-05-08
Nextcloud Server before 11.0.3 is vulnerable to an inadequate escaping leading to a XSS vulnerability in the search module. To be exploitable a user has to write or paste malicious content into the search dialogue.