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

A2.1.2 Risk Mitigation and Migration Plan for SSL/early TLS connections

Service providers with existing connection points serving POS POI terminals that rely on SSL or early TLS must maintain a formally documented Risk Mitigation and Migration Plan covering: a description of how the protocols are used, including the data transmitted, which kinds of systems use or support SSL/early TLS and how many, and the kind of environment; the results of risk assessment and the risk-reducing controls in place; how the provider monitors for new SSL/early TLS vulnerabilities; the change control processes that stop SSL/early TLS from being introduced into new environments; and a summary of the planned project for migrating away from SSL/early TLS. Guidance: providers should also make customers that still use SSL/early TLS aware of the risks and the need to migrate. 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.2. 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.

6
artefacts
0
held by a system
0
at each review
hard
to go live
Policy repository / GRC workspace
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

none for this control

periodic reviewEvidence produced at each review

none for this control

governing documentDocuments that govern the control

  • Formal Risk Mitigation and Migration Plan document · Policy repository / GRC workspace
  • Inventory of SSL/early TLS termination points and connected terminal counts · HR system / LMS
  • Risk assessment report and list of compensating risk-reduction controls · Policy repository / GRC workspace
  • Change control rule or gate blocking SSL/early TLS in new builds · Document repository
  • Migration project plan with target dates · Policy repository / GRC workspace
  • Customer communications on SSL/early TLS risk · Document repository

First move

No system holds this evidence for you: it is people and documents. Reminders and routing to the owner still save time. Put the document under version control with an owner and review date, and log each review as a record with reviewer and date.

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.1 Confirm SSL/early TLS POS POI devices resist known exploits · A2.1.3 Service providers offer a secure protocol option