Frequently Asked Question

How should entities complete their ROC or SAQ for PCI DSS v3.1 using the new SSL/TLS migration dates?
This FAQ is intended for entities that need to complete a ROC or SAQ for PCI DSS v3.1 using the updated SSL/early TLS migration dates for Requirements 2.2.3, 2.3 and 4.1.
If using a ROC, the following guidance affects Testing Procedures 2.2.3.c, 2.3.f, and 4.1.i:
- Document the entity's target migration completion date (as provided in their Risk Mitigation and Migration Plan) in the "Reporting Details: Assessor's Response" column for the applicable testing procedures.
- If the entity's completion date is no later than June 30, 2016, and all other elements of the requirement are met, the assessor may check the "In Place" option for that requirement.
- If the entity's completion date falls between June 30, 2016 and June 30, 2018, and all other elements of the requirement are met, the assessor may check the "In Place w/CCW" option for that requirement, and complete a Compensating Control Worksheet (CCW). A CCW is provided in Appendix C of the ROC Reporting Template. In the CCW, document in Section 4 ('Definition of Compensating Controls') that the entity's Risk Mitigation and Migration Plan meets the revised migration deadline date as announced by PCI SSC in December 2015.
- If the entity's completion date is later than June 30, 2018, the assessor may check the "Not in Place" option for that requirement.
If using a SAQ, the following guidance affects Questions 2.2.3, 2.3.f, and 4.1.g:
- If the entity's completion date is no later than June 30, 2016, and all other elements of the question are met, check the "Yes" option for that question.
- If the entity's completion date falls between June 30, 2016 and June 30, 2018, and all other elements of the question are met, check the "Yes with CCW" option for that question, and complete a Compensating Control Worksheet (CCW). A CCW is provided in Appendix B of the SAQ. In the CCW, document in Section 4 ('Definition of Compensating Controls') that the entity's Risk Mitigation and Migration Plan meets the revised migration deadline date as announced by PCI SSC in December 2015.
- If the entity's completion date is later than June 30, 2018, check the "No" option for that question.
Entities should always contact their acquirer or the payment brands directly to confirm their compliance reporting requirements. Contact details for the payment brands can be found in How do I contact the payment card brands?
For additional guidance, refer to How should entities apply the new SSL/TLS migration dates to Requirements 2.2.3, 2.3 and 4.1 for PCI DSS v3.1?
January 2016
Article Number: 1373
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?