← NIST CSF 2.0 · PROTECT — Identity, Authentication and Access Control

PR.AA-03 — Users, services and hardware are authenticated

critical authenticationmfa

Requirement

Users, services and hardware are authenticated, with the strength of authentication commensurate with risk.

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.

Required element 1 — any one of
authenticat…
Required element 2 — any one of
mfamulti-factor2fatwo-factorpasskeycertificatemutual tls
Supporting terms — specificity signals
phishing-resistantfidoconditional accessrisk-basedstep-upworkload identity
Contradiction markers

Finding any of these outranks coverage — a policy that admits the gap is worse than silence.

no mfa password only

Equivalent controls elsewhere

Matched on shared topics. Satisfying this control usually moves these too.

FrameworkControlTitleShared topics
ISO 27001 A.5.17 Authentication information authentication mfa
ISO 27001 A.8.5 Secure authentication authentication mfa
PCI DSS 4.0.1 8.4 Multi-factor authentication into the CDE and for remote access mfa authentication
HIPAA 164.312(d) Person or entity authentication (R) authentication mfa
GLBA 314.4(c)(5) Multi-factor authentication for any individual accessing information systems mfa authentication
ISO 27001 A.5.15 Access control authentication
PCI DSS 4.0.1 8.3 Strong authentication factors authentication
PCI DSS 4.0.1 8.6 System and application accounts are managed authentication