Frequently Asked Question

For P2PE solutions, can you use PCI approved POI devices with SRED, where the PTS listing indicates "Non CTLS"?
This is a "normative" FAQ - It 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.
(a) Was validated under PTS POI v3.0, including the SRED module, prior to release of criteria for evaluating contactless (CTLS) interfaces in PTS POI v3.1, and (b) Successfully completes required annual supplemental contactless evaluations ('SCE') by the originating PTS lab, validating compliance with a subset of PTS POI requirements relating to vulnerability to common logical security attacks. PCI PTS-approved POI devices meeting the requirements of item 2(a) above and identified as "Non-CTLS" on the listing of PTS Approved Devices are considered to be "Permitted Non-CTLS Devices." Permitted Non-CTLS Devices that meet (and continue to meet) Requirement 2(b) above are acceptable for use in P2PE solutions and are listed in the table below. Once these devices are evaluated as part of a P2PE Solution, they will be included on the list of Validated P2PE Solutions with an explanatory note. A Permitted Non-CTLS Device that no longer meets Requirement 2(b) per the annual SCE may be delisted from the list of Validated P2PE Solutions if the contactless interface cannot be disabled. |
IMPORTANT NOTES:
|
The following are the only Permitted Non-CTLS Devices currently allowed in
P2PE Solutions:
Model |
Firmware Number noted as 'SRED (Non-CTLS)' |
PTS Approval |
SCE Expiry Date |
Ingenico IWL220, IWL250 |
820528v02.xx |
4-20181 |
December 31, 2016 |
Ingenico iSMP |
820528V02.xx |
4-20183 |
December 31, 2016 |
Ingenico iCT220, iCT250 |
820528V02.xx |
4-20196 |
November 30, 2016 |
Ingenico iPP310, iPP320, iPP350 |
820528V02.xx |
4-20184 |
October 31, 2016 |
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?