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.

Application Security

12/12/2019
01:30 PM
Dark Reading
Dark Reading
Products and Releases
50%
50%

PCI Security Standards Council Publishes V3.0 of Point-To-Point Encryption (P2PE) Standard and Program

Changes Driven by Stakeholder Feedback and Will Ultimately Result in More PCI P2PE(R) Solutions Available to The Marketplace

WAKEFIELDMass., 12 December 2019 — The PCI Security Standards Council (PCI SSC) has updated the PCI Point-to-Point Encryption (P2PE) Standard and supporting program. PCI P2PE Version 3.0 simplifies the process for component and solution providers to validate their P2PE products for cardholder data protection efforts. 

“The Council is committed to evolving its standards, programs and resources to help the industry innovate for payment acceptance in a secure manner,” said PCI SSC Senior Vice President Troy Leach. “It’s important to note that P2PE technology that protects payment data isn’t changing. The changes focus instead on providing the opportunity for new approaches in meeting the standard and will ultimately result in more PCI P2PE Solutions available for merchants to use in protecting payment data and simplifying their PCI DSS efforts.”

For more information on what merchants need to know about PCI P2PE v3.0, read PCI Perspectives blog post: P2PE v3.0: What Merchants Need to Know.

PCI P2PE Version 3.0 maintains the same approach to security as version 2.0, with only minor changes to the security requirements. Key updates focus on updating the validation program to add flexibility for P2PE solution providers designing and validating their solutions to the standard. These include:

  • Enhancing the modular approach first introduced in P2PE v2.0 by introducing four additional component provider types
  • Streamlining the processes used by P2PE Assessors when validating P2PE Solutions, Components and Applications

“Driven by industry feedback given during an extensive request for comments (RFC) process, the program changes in version 3.0 will streamline the assessment process and provide more flexibility for component and solution providers,” said PCI SSC Vice President, Global Head of Programs Gill Woodcock. For more information on the what P2PE Solution Providers need to know about the program changes read PCI Perspectives blog post: P2PE v3.0: What Vendors and Assessors Need to Know.

Merchants considering a PCI P2PE Solution are encouraged to use the current list of PCI P2PE Solutions on the PCI SSC website and do not need to wait for a P2PE v3.0 validation solution, as solutions validated against v2.0 provide the same level of security assurance. 

The updated P2PE v3.0 Standard and Program documents are available in the PCI SSC document library.

About PCI Point-to-Point Encryption Solutions

A PCI Point-to-Point Encryption (P2PE) Solution cryptographically protects account data from the point where a merchant accepts the payment card to the secure point of decryption. By using P2PE, account data is unreadable until it reaches the secure decryption environment, which makes it less valuable if the data is stolen in a breach. A PCI P2PE Solution can significantly help merchants reduce the PCI DSS validation effort of their cardholder data environment.

 

P2PE v3.0: What Merchants Need to Know

The updates to the P2PE Standard and supporting program is part of the Council’s mission to evolve security standards and validation programs to support a range of environments, technologies and methodologies for achieving security. Ultimately, the updated PCI Point-to-Point Encryption (P2PE) ® Standard and supporting program will result in more PCI P2PE ® Solutions available to the marketplace. 

 

Can you provide an overview of what P2PE is and how it helps merchants protect payment card data? 

A point-to-point encryption (P2PE) solution cryptographically protects account data from the point where a merchant accepts the payment card to the secure point of decryption. By using P2PE, account data (cardholder data and sensitive authentication data) is unreadable until it reaches a secure decryption environment, which makes it less valuable if the data is stolen in a breach. A PCI P2PE solution can significantly help to reduce the PCI DSS validation effort of a merchant’s cardholder data environment. However, it does not completely remove the need for PCI DSS validation in the merchant environment. 

 

Can you talk about the changes to the P2PE Standard and Program? 

PCI P2PE v3.0 maintains the same approach to security as v2.0. The feedback garnered from the PCI's RFC process helped improve the P2PE Standard in terms of adding clarity, providing additional guidance, making errata changes, resolving ambiguity, as well as restructuring the Standard to eliminate redundancy and improve its overall readability. In addition, there are beneficial program changes. These changes will ultimately result in more P2PE solutions available to the marketplace for merchant use.    

In 2015, the PCI SSC first introduced the ability to validate P2PE solution components, which are services that fulfill specific P2PE requirements. Version 3.0 of the Standard maintains the same approach to protecting payment data but doubles the amount of component providers which can validate against the Standard. The listing of individual components makes it easier for a solution provider to be aware of and select validated components for integration into their P2PE solution. This will allow for more outsourcing for the solution and component providers, which will facilitate more available PCI P2PE Solutions for merchants.   

 

Also on the blog: 3 Things to Know About P2PE v3.0  

 

How do these changes impact merchants? 

PCI Point-to-Point Encryption solutions help merchants by encrypting cardholder data at the earliest point of acceptance, making that data less valuable to attackers even if compromised in a breach. Use of a PCI P2PE Solution can also allow merchants to reduce where and how the PCI Data Security Standard (PCI DSS) applies within their retail environment, increasing security of customer data while simplifying compliance with the PCI DSS. 

It’s important to note that the P2PE technology that protects their payment data isn’t changing- the changes are aimed to provide more solutions for merchants. Therefore, merchants considering a P2PE solution should not wait for a P2PE v3.0 validated solution. Solutions validated against v2.0 of the Standard will provide the same level of security. Merchants should talk with their acquirer about selecting and using a PCI P2PE v2.0 solution. 

 

What are the changes to the PIM in P2PE v3.0 and how do those changes affect merchants? 

PCI SSC provides a template that P2PE Solution Providers must use when producing the PIM, or P2PE Instruction Manual for their solution. The PIM provides useful information from a solution provider for their merchant customers to effectively and securely manage their encryption environments and the POI devices within their purview: e.g., the secure installation of POI devices, monitoring POI devices for signs of tampering, and appropriate incident response procedures for security incidents. For v3.0, the PIM template has been reorganized in a more logical manner as well as being updated with improved clarity and guidance, especially in terms of POI device tamper and modification. This will help the solution provider populate the appropriate information for merchants in their PIM, serving as a useful tool that complements the P2PE solution implementation.  

 

Why should a merchant consider implementing a PCI P2PE solution? 

There are certain critical payment security aspects that PCI P2PE Solutions will check for. PCI P2PE Solutions have been validated to demonstrate that all the critical security components are being addressed so that an assessor reviewing a merchant’s card data environment has confidence those security controls are in place, which helps minimize the review process. Non-validated solutions require the assessor to do their due diligence to assess that the solution is providing the same level of security that a PCI P2PE Solution would.  

 

 

Recommended Reading:

Comment  | 
Print  | 
More Insights
Comments
Threaded  |  Newest First  |  Oldest First
COVID-19: Latest Security News & Commentary
Dark Reading Staff 9/25/2020
Hacking Yourself: Marie Moe and Pacemaker Security
Gary McGraw Ph.D., Co-founder Berryville Institute of Machine Learning,  9/21/2020
Startup Aims to Map and Track All the IT and Security Things
Kelly Jackson Higgins, Executive Editor at Dark Reading,  9/22/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
Special Report: Computing's New Normal
This special report examines how IT security organizations have adapted to the "new normal" of computing and what the long-term effects will be. Read it and get a unique set of perspectives on issues ranging from new threats & vulnerabilities as a result of remote working to how enterprise security strategy will be affected long term.
Flash Poll
How IT Security Organizations are Attacking the Cybersecurity Problem
How IT Security Organizations are Attacking the Cybersecurity Problem
The COVID-19 pandemic turned the world -- and enterprise computing -- on end. Here's a look at how cybersecurity teams are retrenching their defense strategies, rebuilding their teams, and selecting new technologies to stop the oncoming rise of online attacks.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-15208
PUBLISHED: 2020-09-25
In tensorflow-lite before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, when determining the common dimension size of two tensors, TFLite uses a `DCHECK` which is no-op outside of debug compilation modes. Since the function always returns the dimension of the first tensor, malicious attackers can ...
CVE-2020-15209
PUBLISHED: 2020-09-25
In tensorflow-lite before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, a crafted TFLite model can force a node to have as input a tensor backed by a `nullptr` buffer. This can be achieved by changing a buffer index in the flatbuffer serialization to convert a read-only tensor to a read-write one....
CVE-2020-15210
PUBLISHED: 2020-09-25
In tensorflow-lite before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, if a TFLite saved model uses the same tensor as both input and output of an operator, then, depending on the operator, we can observe a segmentation fault or just memory corruption. We have patched the issue in d58c96946b and ...
CVE-2020-15211
PUBLISHED: 2020-09-25
In TensorFlow Lite before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, saved models in the flatbuffer format use a double indexing scheme: a model has a set of subgraphs, each subgraph has a set of operators and each operator has a set of input/output tensors. The flatbuffer format uses indices f...
CVE-2020-15212
PUBLISHED: 2020-09-25
In TensorFlow Lite before versions 2.2.1 and 2.3.1, models using segment sum can trigger writes outside of bounds of heap allocated buffers by inserting negative elements in the segment ids tensor. Users having access to `segment_ids_data` can alter `output_index` and then write to outside of `outpu...