On New PCI Point-to-Point Encryption Solution Requirements
October 10, 2011 | POSTED BY DOMINIC SCHULTE IN COMPLIANCE, PCI
In case you missed it, the PCI Security Standards Council (SSC) published the initial release of the much anticipated Point-to-Point Encryption Solution (P2PE) Requirements document
last month. Many of you are probably asking, "Why do I care?" - a good question in a day and age with so much information and noise. If you'll allow me, I'd like to answer two better questions! But first, to answer, this document is significant because it is at the heart of the fiery topic of PCI scope.
Now, on to better question numero uno: "Can I use encryption to reduce PCI scope?" The answer to that question has been ? and still is ? "no," with one key exception
. In the PCI SSC's FAQ
entitled, "Is encrypted cardholder data considered cardholder data that must be protected in accordance with PCI DSS?" the SSC presents their reasoning for why encrypted cardholder data needs to be in scope. The abbreviated version is that encryption only ensures confidentiality if you don't have the keys. If someone can gain access to the decryption keys, then they can get the cardholder data. By keeping the encrypted data and the systems and segments on which it resides in scope, the organization is forced to implement and maintain all of the controls that protect access to those keys.
"So, what's the exception?" you ask. Great question! In the FAQ
, the Council states an organization may deem encrypted data out of scope "if, and only if, it has been validated that the entity that possesses encrypted cardholder data does not have the means to decrypt it." In other words, you may treat encrypted cardholder data as out of scope if you use a managed solution from a service provider that encrypts the cardholder data before it touches your environment and the service provider maintains sole possession of the key to decrypt it. The most basic example of this scenario is an encrypting card reader.
Prior to the release of the new requirements document, no real guidance for service providers and merchants existed on how to implement a compliant solution to this exception. This document provides the needed guidance and makes some significant changes to the PCI program in the process, including the following:
- The development of a new P2PE Requirements Standard (the document referenced above)
- P2PE QSAs to validate the P2PE solutions
- P2PE PA QSAs to evaluate applications on PCI-approved POI devices for point-to-point encryption solutions
- A training and certifications process for P2PE QSAs and PA QSAs and their companies
The Council plans to roll out these new programs, training and certifications throughout the remainder of 2011 and 2012.
The P2PE solution requirements have the greatest impact on the service providers who have already rolled out P2PE solutions. Merchants who are using or considering such solutions should also stay tuned. Now that the requirements have been released, some providers may decide their P2PE solutions are not worth the annual audit compliance costs they must incur for merchant use.
Unless there are any more questions, I'll close with that!