← PCI DSS 4.0.1 · Req 8 — Identify and authenticate
8.3 — Strong authentication factors
Requirement
User authentication factors are strong: passwords are at least 12 characters (or 8 where the system does not support 12) with numeric and alphabetic characters, accounts lock out after no more than 10 invalid attempts, and where passwords are the only factor they are changed at least every 90 days or access is analysed dynamically.
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.5.15 | Access control | authentication |
| ISO 27001 | A.5.17 | Authentication information | authentication |
| ISO 27001 | A.8.5 | Secure authentication | authentication |
| HIPAA | 164.312(a)(1) | Access control — unique identification and emergency access (R/A) | authentication |
| HIPAA | 164.312(d) | Person or entity authentication (R) | authentication |
| GLBA | 314.4(c)(5) | Multi-factor authentication for any individual accessing information systems | authentication |
| NIST CSF 2.0 | PR.AA-01 | Identities and credentials are managed | authentication |
| NIST CSF 2.0 | PR.AA-03 | Users, services and hardware are authenticated | authentication |