EvidenceSheet
PCI DSS v4.0.1 · Appendix A2: Entities using SSL/early TLS for card-present POS POI terminal connections

A2.1.3 Service providers offer a secure protocol option

Every service provider must provide a secure service offering. The testing procedure reads this as offering customers a secure protocol choice for the service. Guidance: customers need the option of upgrading and often migrate their POS POI estate gradually, so they need the provider to support a secure offering. Applicability: only when the assessed entity is a service provider. Objective under the customized approach: not eligible for the customized approach.

Source: PCI DSS v4.0.1, A2.1.3. The statement above is our statement of the clause, read from the published text and cited so you can check it against the official text, not the instrument verbatim. Open PCI DSS v4.0.1 in the compliance library.

Version 4.0.1 is the active version; 4.0 has been retired. Appendix A1 applies only to multi-tenant service providers, A2 only to card-present POS POI terminals that still use SSL or early TLS, and A3 only when a payment brand or acquirer requires it. Which requirements apply to you follows your validation type.

4
artefacts
2
held by a system
0
at each review
easy
to go live
Endpoint management (MDM / EDR)
where the evidence lives
teal = a system already holds it · olive = produced at each review. To go live: easy when half or more of the artefacts are already held by a system, moderate from a quarter to a half, hard below a quarter.

These are the artefacts auditors commonly ask for on this requirement, our guidance rather than text from the standard. Your assessor decides what is sufficient in your context, and asks for samples across the period when a report covers one.

system holds itEvidence a system already holds

  • Service endpoint configurations showing modern TLS support · Endpoint management (MDM / EDR)
  • TLS scan output for termination endpoints · Vulnerability scanner / patch tooling

periodic reviewEvidence produced at each review

none for this control

governing documentDocuments that govern the control

  • Service catalogue or customer documentation describing the secure option · Document repository
  • Customer migration statistics by protocol · Document repository

First move

Automate the pull from your Endpoint management (MDM / EDR). Device compliance report from the MDM (encryption, EDR agent, OS version) on a daily pull.

Common gaps auditors find

Do this for your whole sheet

Paste the rows you run your controls from and get this mapping for every control at once, with the periodic-review ones flagged and a first move per row. No account for the first run.

Build my evidence sheet

A2.1.2 Risk Mitigation and Migration Plan for SSL/early TLS connections · A3.1.1 Executive management responsibility for the PCI DSS compliance program