Frequently Asked Question

For P2PE Requirement 3B-5, is it the responsibility of the solution provider to "push" patches to all affected POI devices, or is it sufficient for them to make it available for download and advise the merchant how to download and install the patches?
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.
In a P2PE solution, the solution provider is responsible for managing the application, including the deployment of application updates. Solution providers should work with their merchants to schedule updates at appropriate times—for example, the solution provider could make the patch available, provide instructions for the merchant on how to trigger the update process, and notify merchants that the patch needs to be installed within a defined period of time. If the patch is not installed during this required timeframe, the provider may need to follow-up with merchant to ensure the application is updated. Alternatively, the solution provider may push the patch to devices at a time that is pre-agreed with the merchant. Whatever process the solution provider uses to manage the update process, they are ultimately responsible for ensuring that P2PE applications are kept up-to-date with required patches and security updates.
In a P2PE solution, the solution provider is responsible for managing the application, including the deployment of application updates. Solution providers should work with their merchants to schedule updates at appropriate times—for example, the solution provider could make the patch available, provide instructions for the merchant on how to trigger the update process, and notify merchants that the patch needs to be installed within a defined period of time. If the patch is not installed during this required timeframe, the provider may need to follow-up with merchant to ensure the application is updated. Alternatively, the solution provider may push the patch to devices at a time that is pre-agreed with the merchant. Whatever process the solution provider uses to manage the update process, they are ultimately responsible for ensuring that P2PE applications are kept up-to-date with required patches and security updates.
December 2015
Article Number: 1351
Related
-
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?
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
-
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?
-
Are providers of third-party scripts for e-commerce environments considered third-party service providers for PCI DSS Requirements 12.8 and 12.9?
Most Recently Updated
-
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?
-
How can an entity ensure that hashed and truncated versions cannot be correlated?
-
Are point-of-interaction devices required to be physically secured (for example, with a cable or tether) to prevent removal or substitution to meet PCI DSS Requirement 9.5?