EvidenceSheet

8.3.10 Service provider customer password guidance

Service providers only (an additional requirement). If customers' users rely on passwords or passphrases alone as the authentication factor reaching cardholder data (any single-factor implementation), the service provider must give customer users guidance that includes: advice for customers to change their passwords or passphrases periodically; and advice on when, and in what circumstances, passwords or passphrases should be changed. Applicability: applies only when the assessed entity is a service provider; excludes consumers who log in to view their own payment card details. This requirement is superseded by 8.3.10.1 once that requirement takes effect. Objective under the customized approach: passwords and passphrases held by a service provider's customers cannot remain in use indefinitely.

Source: PCI DSS v4.0.1, 8.3.10. 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
0
held by a system
1
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

  • Evidence the guidance covers periodic change and change triggers · Document repository

governing documentDocuments that govern the control

  • Customer-facing password guidance document or help page · Policy repository / GRC workspace
  • Onboarding materials sent to customer users · HR system / LMS
  • Inventory of customer-facing portals relying on password-only access · Policy repository / GRC workspace

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

8.3.9 Single-factor passwords changed every 90 days or dynamic analysis · 8.3.10.1 Service provider customer passwords 90 days or dynamic