What evidence do auditors commonly ask for on 8.2.1 Unique ID assigned to every user?

User account listings from in-scope systems showing one ID per person; Account naming standard and provisioning procedure requiring unique IDs; Audit log samples showing actions tied to named individual IDs; HR-to-directory reconciliation confirming each account maps to one person.

What is the most common gap auditors find on 8.2.1?

Several operators share one login on a management console

PCI DSS v4.0.1 · Req 8: Identify and Authenticate Users

`8.2.1` Unique ID assigned to every user

Each user must be given a unique ID before being permitted to reach any system component or cardholder data. The guidance explains that unique identification keeps actions traceable to one person, supports individual accountability and an effective audit trail, and helps resolve and contain misuse. Applicability: not intended for point-of-sale terminal user accounts that are limited to a single card number per transaction. Customized approach objective: every action by every user can be attributed to an individual.

Source: PCI DSS v4.0.1, 8.2.1. 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.

artefacts

held by a system

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

Audit log samples showing actions tied to named individual IDs · SIEM / log platform
HR-to-directory reconciliation confirming each account maps to one person · Identity provider / directory

governing documentDocuments that govern the control

User account listings from in-scope systems showing one ID per person · Policy repository / GRC workspace
Account naming standard and provisioning procedure requiring unique IDs · 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

Several operators share one login on a management console
Contractors reuse IDs of staff who have left
Logs show generic accounts that cannot be traced to a person

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.1.2 Requirement 8 roles and responsibilities assigned · 8.2.2 Shared and generic IDs only by exception