Frequently Asked Question

Why does the PCI P2PE standard require SRED for PCI approved Point-of-Interaction (POI) devices?
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 PCI PIN Transaction Security (PTS) standard was originally intended to provide physical and logical protection for PIN entry devices (PEDs). This protection only focused on PIN data, and all sensitive items associated with PIN data (e.g., electronic components, pathways, cryptographic keys, etc.) The additional SRED (Secure Reading and Exchange of Data) module was introduced in v3.0 of the PTS POI standard. The SRED module provides a standardized approach to protecting account data, thereby enhancing the baseline protection provided by the PTS POI core requirements. Securing account data extends well beyond just using encryption. SRED requirements include protecting the PAN during its entire existence within the POI device, protecting any associated sensitive data or functions, and encrypting account data transmissions as they leave the POI device. For these reasons, a PCI P2PE solution requires that plaintext account data be captured, processed and encrypted only by PCI approved POI devices with SRED.
The PCI PIN Transaction Security (PTS) standard was originally intended to provide physical and logical protection for PIN entry devices (PEDs). This protection only focused on PIN data, and all sensitive items associated with PIN data (e.g., electronic components, pathways, cryptographic keys, etc.) The additional SRED (Secure Reading and Exchange of Data) module was introduced in v3.0 of the PTS POI standard. The SRED module provides a standardized approach to protecting account data, thereby enhancing the baseline protection provided by the PTS POI core requirements. Securing account data extends well beyond just using encryption. SRED requirements include protecting the PAN during its entire existence within the POI device, protecting any associated sensitive data or functions, and encrypting account data transmissions as they leave the POI device. For these reasons, a PCI P2PE solution requires that plaintext account data be captured, processed and encrypted only by PCI approved POI devices with SRED.
June 2016
Article Number: 1342
Related
-
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?
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 for determining applicability of PCI DSS requirements for assessments documented in a Report on Compliance?
Most Popular
-
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?
-
Are providers of third-party scripts for e-commerce environments considered third-party service providers for PCI DSS Requirements 12.8 and 12.9?
-
Why do requirements 8.3.9 and 8.3.10.1 focus on passwords/passphrases used for single-factor authentication, when multi-factor authentication is required for all access into the CDE?
Most Recently Updated
-
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?
-
Are providers of third-party scripts for e-commerce environments considered third-party service providers for PCI DSS Requirements 12.8 and 12.9?
-
Why do requirements 8.3.9 and 8.3.10.1 focus on passwords/passphrases used for single-factor authentication, when multi-factor authentication is required for all access into the CDE?