Frequently Asked Question

Does P2PE Requirement 2A-2.1 mean that PIN data (which is an element of SAD) must be encrypted by the SRED functions of the PCI-approved POI device? How does this impact PIN Security Requirements for PTS devices processing PINs?
This is a Technical FAQ for P2PE versions 1.x. This is a "normative" FAQ that is considered to be part of the P2PE requirements and shall be considered during a P2PE assessment in the same light as the published P2PE standard. These technical FAQs are also published together in "Technical FAQs for use with P2PE Versions 1.x" available in the Documents Library of this website.
The definition of "account data" is aligned across the various PCI standards, and does include any elements of SAD that are present. With respect to P2PE requirements and PIN Security Requirements (which must be met by PTS devices processing PINs), SRED covers account data (with the exception of PIN) and does not interfere with any PIN functions. PINs are encrypted separately from other SAD elements using a key specific and unique to PIN encryption. Note that if the PIN is encrypted a second time as part of the encipherment of other SAD elements (for example, via SRED), this secondary encryption is neither required by P2PE nor is it a violation of PIN Security Requirements. Refer to the section entitled "Relationship between P2PE and other PCI standards (PCI DSS, PA-DSS, PTS, and PIN," on page 3 of the P2PE standard.
The definition of "account data" is aligned across the various PCI standards, and does include any elements of SAD that are present. With respect to P2PE requirements and PIN Security Requirements (which must be met by PTS devices processing PINs), SRED covers account data (with the exception of PIN) and does not interfere with any PIN functions. PINs are encrypted separately from other SAD elements using a key specific and unique to PIN encryption. Note that if the PIN is encrypted a second time as part of the encipherment of other SAD elements (for example, via SRED), this secondary encryption is neither required by P2PE nor is it a violation of PIN Security Requirements. Refer to the section entitled "Relationship between P2PE and other PCI standards (PCI DSS, PA-DSS, PTS, and PIN," on page 3 of the P2PE standard.
September 2015
Article Number: 1344
Related
-
Are Approved Scanning Vendors and Qualified Security Assessors considered third-party service providers for PCI DSS Requirements 12.8 and 12.9?
-
What are the expectations for entities when assigning risk rankings to vulnerabilities and resolving or addressing those vulnerabilities?
-
Is phishing-resistant authentication alone acceptable as multi-factor authentication for PCI DSS Requirements 8.4.1 and 8.4.3?
Featured FAQ Articles
Featured
-
Do PCI DSS requirements for keyed cryptographic hashing apply to previously hashed PANs?
-
Is the PCI DSS Attestation of Compliance intended to be shared?
-
How does an entity report the results of a PCI DSS assessment for new requirements that are noted in PCI DSS as best practices until a future date?
-
Where do I direct questions about complying with PCI standards?
-
Can SAQ eligibility criteria be used as a guide for determining applicability of PCI DSS requirements for merchant assessments documented in a Report on Compliance?
Most Popular
-
Are Approved Scanning Vendors and Qualified Security Assessors considered third-party service providers for PCI DSS Requirements 12.8 and 12.9?
-
What are the expectations for entities when assigning risk rankings to vulnerabilities and resolving or addressing those vulnerabilities?
-
Is phishing-resistant authentication alone acceptable as multi-factor authentication for PCI DSS Requirements 8.4.1 and 8.4.3?
-
Are passkeys synced across devices, implemented according to the FIDO2 requirements, acceptable for use as phishing-resistant authentication to meet PCI DSS Requirement 8.4.2?
-
How should PCI DSS v4.x requirements noted as superseded by another requirement be reported after 31 March 2025?
Most Recently Updated
-
Are Approved Scanning Vendors and Qualified Security Assessors considered third-party service providers for PCI DSS Requirements 12.8 and 12.9?
-
Can a compensating control be used for requirements with a periodic or defined frequency, where an entity did not perform the activity within the required timeframe?
-
How often must service providers test penetration testing segmentation controls under PCI DSS?
-
Are merchants allowed to request card-verification codes/values from cardholders?
-
What is the maximum period of time that cardholder data can be stored?