Dark Reading is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.


PCI Standards Expanded to Include Unattended Devices

New specs respond to emerging threats posed at kiosks, ATM devices

The PCI Security Standards Council is looking to put more needles in PINs.

In an announcement made yesterday, the standards group, which sets the guidelines for complying with the retail Payment Card Industry Data Security Standard, said it is expanding the standards to include guidelines for protecting unattended kiosks, ATM-type devices, and other systems that require the input of a personal identification number (PIN).

The extension of the security requirements is a significant one, because it requires the retailer not only to secure data at its stores and warehouses, but also in any location where the customer may enter a PIN, such as self-service ticketing machines, kiosks, automated fuel pumps, and other devices that might not be operated solely by the retailer's employees.

"PIN-entry devices go well beyond the typical [point of sale (POS)] terminals we are all familiar with, and we are continually expanding into more and more areas," said Bob Russo, general manager, PCI Security Standards Council. "Any device that processes [PINs] is an important link in the transaction chain."

The Council did not make any reference to recent hacker exploits, but it is likely that the new standards were developed at least partly because of some highly publicized attacks on unattended systems and POS devices over the past two years. The infamous TJX security breach reportedly began at a store kiosk, and more recently, attackers have exploited flaws in unattended fuel pumps. (See Hacking the Real TJX Story and Gas Station ATM/Card Reader Likely Rigged in New ID Theft Case .)

The new PIN Entry Device (PED) Security Requirements are designed to ensure the security of devices that accept PIN entry, the Council said. Until now, the PCI requirements focused on traditional POS devices that operate in an environment attended by a merchant, cashier, or sales clerk.

The PED requirements will extend those requirements to unattended payment terminals (UPTs). Up until now, vendors have been manufacturing and having the encrypted PIN pads (EPPs) that go into UPTs evaluated by approved labs, and the payment card brands have been requiring the use of PCI SSC-approved EPPs. Having new and overarching UPT testing requirements will further protect the payment card industry, the Council said.

The PCI standards also will now extend to include host security modules (HSMs), secure cryptographic devices that can be used for PIN translation, card personalization, electronic commerce, or data protection and do not include any type of cardholder interface.

Have a comment on this story? Please click "Discuss" below. If you'd like to contact Dark Reading's editors directly, send us a message.

Tim Wilson is Editor in Chief and co-founder of Dark Reading.com, UBM Tech's online community for information security professionals. He is responsible for managing the site, assigning and editing content, and writing breaking news stories. Wilson has been recognized as one ... View Full Bio

Comment  | 
Print  | 
More Insights
Newest First  |  Oldest First  |  Threaded View
Mobile Banking Malware Up 50% in First Half of 2019
Kelly Sheridan, Staff Editor, Dark Reading,  1/17/2020
7 Tips for Infosec Pros Considering A Lateral Career Move
Kelly Sheridan, Staff Editor, Dark Reading,  1/21/2020
For Mismanaged SOCs, The Price Is Not Right
Kelly Sheridan, Staff Editor, Dark Reading,  1/22/2020
Register for Dark Reading Newsletters
White Papers
Cartoon Contest
Write a Caption, Win a Starbucks Card! Click Here
Latest Comment:   It's a PEN test of our cloud security.
Current Issue
IT 2020: A Look Ahead
Are you ready for the critical changes that will occur in 2020? We've compiled editor insights from the best of our network (Dark Reading, Data Center Knowledge, InformationWeek, ITPro Today and Network Computing) to deliver to you a look at the trends, technologies, and threats that are emerging in the coming year. Download it today!
Flash Poll
How Enterprises are Attacking the Cybersecurity Problem
How Enterprises are Attacking the Cybersecurity Problem
Organizations have invested in a sweeping array of security technologies to address challenges associated with the growing number of cybersecurity attacks. However, the complexity involved in managing these technologies is emerging as a major problem. Read this report to find out what your peers biggest security challenges are and the technologies they are using to address them.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
PUBLISHED: 2020-01-23
Incorrect username validation in the registration processes of CTFd through 2.2.2 allows a remote attacker to take over an arbitrary account after initiating a password reset. This is related to register() and reset_password() in auth.py. To exploit the vulnerability, one must register with a userna...
PUBLISHED: 2020-01-23
A flaw was found in the JBoss EAP Vault system in all versions before 7.2.6.GA. Confidential information of the system property's security attribute value is revealed in the JBoss EAP log file when executing a JBoss CLI 'reload' command. This flaw can lead to the exposure of confidential information...
PUBLISHED: 2020-01-23
An untrusted deserialization was found in the org.apache.xmlrpc.parser.XmlRpcResponseParser:addResult method of Apache XML-RPC (aka ws-xmlrpc) library. A malicious XML-RPC server could target a XML-RPC client causing it to execute arbitrary code. Apache XML-RPC is no longer maintained and this issue...
PUBLISHED: 2020-01-23
Philips Hue Bridge model 2.X prior to and including version 1935144020 contains a Heap-based Buffer Overflow when handling a long ZCL string during the commissioning phase, resulting in a remote code execution.
PUBLISHED: 2020-01-23
Citrix XenServer 4.1, 6.0, 5.6 SP2, 5.6 Feature Pack 1, 5.6 Common Criteria, 5.6, 5.5, 5.0, and 5.0 Update 3 contains a Local Privilege Escalation Vulnerability which could allow local users with access to a guest operating system to gain elevated privileges.