I saw the news that the PCI SSC approved a point-to-point encryption product for the first time, but I'm wondering...
what that means from a practical perspective? How would a company that selects the PCI-approved product benefit, specifically in terms of reducing scope?
With P2PE, the card reader encrypts the credit card information before it enters the PoS.
Point-to-point encryption (P2PE) products present credit card merchants with a unique opportunity to reduce the scope of their PCI DSS compliance efforts by effectively removing sensitive information from their environments. These products are used for point-of-sale (PoS) applications where a customer's credit card is swiped through a credit card reader.
In a traditional PoS system, the reader scans the information stored on the card's magnetic stripe, processes it and then bundles up the credit card and transaction information in an encrypted authorization request, which is sent off to the solution provider who decrypts the request and processes the transaction. Under this model, the PoS system must view the unencrypted credit card information and, therefore, is clearly in scope for PCI DSS compliance.
With P2PE, the card reader encrypts the credit card information before it enters the PoS. The PoS simply takes the encrypted card information, combines it with the transaction information, and then sends it off to the solution provider for processing. The PoS device never sees unencrypted card information and, indeed, the merchant does not even have the ability to decrypt the card information. Under this model, the PoS system may be removed from the scope of PCI DSS compliance, reducing the merchant's burden.
In order to reduce their compliance scope, merchants must meet the following requirements, as outlined in the PCI Security Standard Council's P2PE standard:
Ask the Expert
Got a vexing problem for Mike Chapple or any of our other experts? Ask your enterprise-specific questions today! (All questions are anonymous.)
- Use a validated P2PE product.
- Never store, process or transmit unencrypted account information.
- Implement PCI DSS compliant physical security measures, service provider management and policies/procedures.
- Isolate the P2PE system from any other card processing systems that do not use P2PE (if applicable).
- Remove any legacy cardholder information or systems from the environment.
I expect that we will see many similar announcements to follow, as the PoS industry is now on notice. With the release of the first P2PE-validated product, customers will probably demand similar certification from the products provided by their vendors to achieve a reduction in compliance scope.
Dig Deeper on PCI Data Security Standard
Related Q&A from Mike Chapple, Enterprise Compliance
The HHS security risk assessment tool is designed to help healthcare providers meet the HIPAA security requirement. Expert Mike Chapple explains how ...continue reading
PCI DSS requirement 6.6 demands application security compliance through one of two options: an application firewall or a code review. Expert Mike ...continue reading
Are HIPAA-compliant hosting services a better option for compliance than a secure storage API? Expert Mike Chapple analyzes.continue reading
Have a question for an expert?
Please add a title for your question
Get answers from a TechTarget expert on whatever's puzzling you.