EvidenceSheet

8.2.3 Service provider unique factors per customer

Service providers only (an additional requirement). A service provider with remote access to customer premises must use distinct authentication factors for each customer premises. The guidance explains the risk (one compromised shared factor could expose many customers) and notes that technologies giving a unique credential per connection, such as single-use passwords, could also meet the intent. Applicability: applies only when the assessed entity is a service provider; it does not cover a provider reaching its own shared services environments that host multiple customer environments. If provider staff use shared factors for remote access to customer premises, those factors must differ for each customer and be handled under Requirement 8.2.2. Objective under the customized approach: a service provider credential used at one customer is unusable at every other customer.

Source: PCI DSS v4.0.1, 8.2.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
1
held by a system
1
at each review
moderate
to go live
Identity provider / directory
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

  • Password vault or PAM configuration segregating credentials by customer · Identity provider / directory

periodic reviewEvidence produced at each review

  • Sample of remote session records showing distinct credentials per customer · Identity provider / directory

governing documentDocuments that govern the control

  • Per-customer credential inventory for remote support access · Policy repository / GRC workspace
  • Remote access procedure for support staff requiring customer-specific factors · Policy repository / GRC workspace

First move

Start with the 1 of 4 artefacts that already live in a system (Identity provider / directory); keep the periodic reviews but log each one as a dated record with a named reviewer.

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.2.2 Shared and generic IDs only by exception · 8.2.4 User ID lifecycle changes authorized