Frequently Asked Question

How do the updated SSL/early TLS migration dates apply to service providers?
The deadline for all entities, including service providers, to migrate away from SSL and insecure versions of TLS is June 30, 2018. In order to support merchants and other customers who have already completed their migration and wish to begin using a secure protocol, service providers are also required to offer a secure alternative to SSL/early TLS by June 30, 2016. This applies even if the service provider has not yet completed their own migration by that date.
The requirement for a secure service offering applies to all in-scope services offered by the service provider. The requirement does not mean that all SSL/Early TLS must be disabled by June 2016, only that a secure alternative also be made available for that service. Service providers offering both insecure and secure protocol options should provide clear instructions on how to use the secure service for those customers wishing to do so.
Additional guidance on migrating away from SSL/early TLS can be found in the Information Supplement: Migrating from SSL and Early TLS, available in the PCI SSC Document Library.
The requirement for a secure service offering applies to all in-scope services offered by the service provider. The requirement does not mean that all SSL/Early TLS must be disabled by June 2016, only that a secure alternative also be made available for that service. Service providers offering both insecure and secure protocol options should provide clear instructions on how to use the secure service for those customers wishing to do so.
Additional guidance on migrating away from SSL/early TLS can be found in the Information Supplement: Migrating from SSL and Early TLS, available in the PCI SSC Document Library.
September 2016
Article Number: 1441
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?