← PCI DSS 4.0.1 · Req 8 — Identify and authenticate
8.2 — Unique IDs and user account lifecycle
Requirement
Every user is assigned a unique ID; group, shared or generic accounts are used only when necessary on an exception basis; access for terminated users is revoked immediately; and inactive accounts are removed or disabled within 90 days.
What the engine looks for
Every group below must be satisfied — by an affirmative statement, not a plan, a hedge or a denial — for the control to count as covered. A term ending in … matches any word it begins. Supporting terms do not change the verdict — they raise confidence and distinguish a policy that names a mechanism from one that gestures at a category.
Finding any of these outranks coverage — a policy that admits the gap is worse than silence.
Equivalent controls elsewhere
Matched on shared topics. Satisfying this control usually moves these too.
| Framework | Control | Title | Shared topics |
|---|---|---|---|
| ISO 27001 | A.6.5 | Responsibilities after termination or change of employment | offboarding access-control |
| HIPAA | 164.308(a)(3)(ii)(C) | Termination procedures (A) | offboarding access-control |
| SOC 2 | CC6.3 | Access modification and removal | access-control offboarding |
| ISO 27001 | A.5.16 | Identity management | access-control offboarding |
| GDPR | Art.29 | Processing under the authority of the controller | access-control |
| CCPA/CPRA | 1798.100(e) & 1798.150 | Reasonable security procedures | access-control |
| SOC 2 | CC6.2 | Registration and authorisation of new users | access-control |
| ISO 27001 | A.5.3 | Segregation of duties | access-control |