Frequently Asked Question

What is the process to use previously-deployed POI devices in a PCI P2PE Solution?
(Note the term "solution provider" below can be used interchangeably with "component provider," depending on the entity managing the POI devices.)
Please refer to the latest P2PE glossary for definitions of terms used in this FAQ.
This FAQ provides guidance concerning previously-deployed POI devices that can be followed by a P2PE solution provider and a P2PE Assessor as a means to help meet the applicable PCI P2PE requirements.
The P2PE standard contains various requirements regarding the establishment and enablement of POI devices in merchant locations for use in a validated P2PE solution. If these requirements are not specifically adhered to, it may be difficult or impossible for a P2PE Assessor to verify the applicable requirements in P2PE Domains 1, 2, and 5 have been satisfied, especially when the POI devices were deployed either without knowledge of the requirements and/or prior to a P2PE assessment. POI devices already deployed as part of a PCI-listed P2PE v2 solution that are being assessed to the current P2PE Standard should still adhere to this guidance, though, the effort and/or concern is likely minimal.
P2PE solution providers should engage a P2PE Assessor as soon as possible to assess the status of the previously-deployed POI devices. The P2PE Assessor can assess the solution provider's documented processes for POI deployment and note any potential deficiencies requiring remediation.
The following table depicts various scenarios and associated guidance for both a P2PE solution provider and a P2PE Assessor.
"NOTE: It is acceptable for the POI devices to retain the necessary keying material to facilitate remote loading (including firmware loading and remote key injection.) If, however, there is any indication there has been a compromise of these keys or the firmware itself, the POI devices must be sent back for re-initialization." | |
SCENARIO | PROCESS |
NEW P2PE ASSESSMENTS
A P2PE Assessor has been engaged to perform an initial assessment of a solution provider's new P2PE solution. There are POI device type(s) that need to be assessed that have already been deployed to merchant locations.
|
The P2PE solution provider engages a P2PE Assessor to assess their solution as required by the PCI P2PE Standard and Program Guide.
|
ADDING A NEW MERCHANT WITH THE SAME POI DEVICE TYPES TO A PCI-LISTED SOLUTION
A solution provider with a PCI-listed P2PE solution wants to add a merchant that has already deployed POI devices of the same POI device type as those approved for use in their P2PE solution (as shown as device dependencies on the P2PE approval listing).
|
The P2PE solution provider follows their documented processes that were assessed previously as part of their P2PE solution assessment.
|
ADDING A NEW MERCHANT WITH DIFFERENT POI DEVICE TYPES TO A PCI-LISTED SOLUTION
A solution provider with a PCI-listed P2PE solution wants to add a merchant that has already deployed POI devices of a different POI device type as those approved for use in their P2PE solution. |
|
Related
-
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?
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
-
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?
-
Do PCI DSS Requirements 8.3.9 and 8.3.10.1 apply to all system components?
-
Is the cardholder in scope for PCI DSS?
Most Recently Updated
-
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?
-
Do PCI DSS Requirements 8.3.9 and 8.3.10.1 apply to all system components?
-
Is the cardholder in scope for PCI DSS?