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
7 Old IT Things Every New InfoSec Pro Should Know
Joan Goodchild, Staff Editor,  4/20/2021
Cloud-Native Businesses Struggle With Security
Robert Lemos, Contributing Writer,  5/6/2021
Defending Against Web Scraping Attacks
Rob Simon, Principal Security Consultant at TrustedSec,  5/7/2021
Register for Dark Reading Newsletters
White Papers
Current Issue
2021 Top Enterprise IT Trends
We've identified the key trends that are poised to impact the IT landscape in 2021. Find out why they're important and how they will affect you today!
Flash Poll
How Enterprises are Developing Secure Applications
How Enterprises are Developing Secure Applications
Recent breaches of third-party apps are driving many organizations to think harder about the security of their off-the-shelf software as they continue to move left in secure software development practices.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
PUBLISHED: 2021-05-15
A XSS Vulnerability in /uploads/dede/action_search.php in DedeCMS V5.7 SP2 allows an authenticated user to execute remote arbitrary code via the keyword parameter.
PUBLISHED: 2021-05-15
DedeCMS V5.7 SP2 contains a CSRF vulnerability that allows a remote attacker to send a malicious request to to the web manager allowing remote code execution.
PUBLISHED: 2021-05-14
The Linux kernel before 5.11.14 has a use-after-free in cipso_v4_genopt in net/ipv4/cipso_ipv4.c because the CIPSO and CALIPSO refcounting for the DOI definitions is mishandled, aka CID-ad5d07f4a9cd. This leads to writing an arbitrary value.
PUBLISHED: 2021-05-14
In the Linux kernel before 5.12.4, net/bluetooth/hci_event.c has a use-after-free when destroying an hci_chan, aka CID-5c4c8c954409. This leads to writing an arbitrary value.
PUBLISHED: 2021-05-14
The block subsystem in the Linux kernel before 5.2 has a use-after-free that can lead to arbitrary code execution in the kernel context and privilege escalation, aka CID-c3e2219216c9. This is related to blk_mq_free_rqs and blk_cleanup_queue.