From the Blogosphere
Payment Data Security | @CloudExpo #BigData #DataCenter #Storage #InfoSec
Making PCI requirements common practice is what will help reduce the risk of sensitive payment data breaches
By: Jose Diaz
May. 22, 2016 12:30 AM
The EMV liability shift that began in October 2015 is likely to reduce card present payment card fraud. That's a double-edged sword for retailers with an online presence and those who accept mobile payments, as fraudsters are seeking easier routes to ill-gotten gain. Add to this the ongoing data breach environment that has become the new normal, and securing payment transactions has never been more significant.
Why can't businesses seem to get security right? It's not a technology problem, to be sure. Solutions that provide increased protection for cardholder data, while maintaining the highest levels of performance - up to millions of transactions per day - were defined and developed after the highly publicized breaches in 2009. The Payment Card Industry (PCI) released solution requirements for point-to-point encryption (P2PE) to assist merchants in protecting cardholder data and reducing the scope of their environment for PCI DSS assessments. However, these approaches still seem to be a concept rather than common practice.
Making PCI requirements common practice is what will help reduce the risk of sensitive payment data breaches - encrypting sensitive data at the point of swipe (or dip in the case of EMV cards) in the payment device and only decrypting it at the processor. Direct attacks on devices in the payment acceptance process have become increasingly common and highly sophisticated, but strongly encrypted cardholder data is useless to cyber criminals. To understand the approaches, and the benefits, of implementing sensitive data protection, let's focus on two key areas: traditional payment acceptance terminals and mobile.
Encryption and HSMs
Encrypting data at the point of swipe device is one thing; encrypting the data in the POS system - more specifically the retail terminal - is another. POI devices go through a PCI certification process, thereby providing high-assurance cryptography and key management functionality. Retail terminals, on the other hand, are typically PC/tablet-based devices that usually only offer software-based encryption and do not have the security controls of PCI-certified devices.
Hardware security modules (HSMs) are an important element of the encryption process. At the point of processing, data decryption takes place using HSMs for secure key management, as required by PCI-P2PE requirements. HSMs perform secure key exchanges and, in most applications, key management that produces a unique key to protect each and every payment transaction. Taking advantage of these security capabilities, solution providers can build high-capacity and redundant secure systems so that multiple servers and multiple HSMs, deployed at multiple data centers, can combine seamlessly to service high transaction volumes with automated load balancing and failover.
An example of a secure system of this kind comes from Verifone, a provider of secure payment acceptance solutions. The company uses a distinctive combination of strong security and risk mitigation against malicious capture of cardholder data, while at the same time ensuring performance and availability for transactions. That's a win-win for retailers. The Verifone VeriShield solution was specifically designed to enable retailers to implement Best Practices for Data Field Encryption, providing security that helps reduce the scope of PCI-DSS audits.
Here's how these mobile point-of-sale, or mPOS, systems work: an affordable card reader ("dongle") is connected to a mobile device to accept payments from both EMV and magnetic stripe payment cards. As with traditional POS, it is critical that the card reader encrypt the sensitive payment data it receives.
Securing mPOS solutions can be difficult. Here's how two payment services providers, CreditCall and ROYAL GATE, handled it. They used point-to-point encryption (P2PE) to protect the sensitive payment data from their mobile acceptance offerings. They integrated HSMs with their processing application as a critical component to manage keys and secure customer data following PCI P2PE solution requirements. The use of HSMs enables them to defend against external data extraction threats and to protect against compromise by a malicious insider.
Tokenization and Key Management
To transact payments with a contactless POS terminal, HCE-based applications leverage the NFC (near field communications) controller that are already on mobile devices. However, since the application cannot rely on secure hardware embedded in the phone for protection of the payment credentials, alternative approaches for protecting sensitive data and transaction security have to be used. These approaches include tokenizing payment credential numbers as well as actively managing and rotating keys used for transaction authorization. This enables issuers to manage the risk introduced by having a less secure mobile device environment for payment credential data.
Using HSMs in the issuer environment is necessary for effective key management and tokenization. They not only create the rotating keys but also to send them securely to the mobile device. In addition, the HSMs are also a critical part of the tokenization and transaction authorization process. The HCE infrastructure does not actually introduce any new security processes or procedures for retailers and processors; it just enables issuers to combine their existing strong security practices-comprising key generation/distribution, data encryption and message authentication-into a cohesive offering to enable payments with mobile devices.
A Multi-Layered Security Strategy
Merchants are well served by a multi-layered approach to payment data security. PCI developed and promotes P2PE for a reason; encrypting sensitive data at the point of swipe or dip in the payment device and only decrypting it at the processor protects the data from direct attacks on devices in the acquiring process. Adding HSMs to the mix helps overcome the challenge of securing implementations and ensures secure key management and sensitive operations are performed in secure hardware. Merchants who deploy these best practices will manage risk on their various payment approaches, remain compliant and rest easier knowing that they have made it nearly impossible for criminals to steal or use their customers' payment data.
Reader Feedback: Page 1 of 1
Latest Cloud Developer Stories
Subscribe to the World's Most Powerful Newsletters
Subscribe to Our Rss Feeds & Get Your SYS-CON News Live!
SYS-CON Featured Whitepapers
Most Read This Week