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
Why Cyber-Risk Is a C-Suite Issue
Marc Wilczek, Digital Strategist & CIO Advisor,  11/12/2019
6 Small-Business Password Managers
Curtis Franklin Jr., Senior Editor at Dark Reading,  11/8/2019
Unreasonable Security Best Practices vs. Good Risk Management
Jack Freund, Director, Risk Science at RiskLens,  11/13/2019
Register for Dark Reading Newsletters
White Papers
Cartoon Contest
Write a Caption, Win a Starbucks Card! Click Here
Latest Comment: This comment is waiting for review by our moderators.
Current Issue
Navigating the Deluge of Security Data
In this Tech Digest, Dark Reading shares the experiences of some top security practitioners as they navigate volumes of security data. We examine some examples of how enterprises can cull this data to find the clues they need.
Flash Poll
Rethinking Enterprise Data Defense
Rethinking Enterprise Data Defense
Frustrated with recurring intrusions and breaches, cybersecurity professionals are questioning some of the industrys conventional wisdom. Heres a look at what theyre thinking about.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
PUBLISHED: 2019-11-14
fs/btrfs/volumes.c in the Linux kernel before 5.1 allows a btrfs_verify_dev_extents NULL pointer dereference via a crafted btrfs image because fs_devices->devices is mishandled within find_device, aka CID-09ba3bc9dd15.
PUBLISHED: 2019-11-14
Scanguard through 2019-11-12 on Windows has Insecure Permissions for the installation directory, leading to privilege escalation via a Trojan horse executable file.
PUBLISHED: 2019-11-14
Microstrategy Library in MicroStrategy before 2019 before 11.1.3 has reflected XSS.
PUBLISHED: 2019-11-14
STMicroelectronics ST33TPHF2ESPI TPM devices before 2019-09-12 allow attackers to extract the ECDSA private key via a side-channel timing attack because ECDSA scalar multiplication is mishandled, aka TPM-FAIL.
PUBLISHED: 2019-11-14
SnowHaze before 2.6.6 is sometimes too late to honor a per-site JavaScript blocking setting, which leads to unintended JavaScript execution via a chain of webpage redirections targeted to the user's browser configuration.