AC.8 Passwordless Authentication
Where identity is established without a password, use a recognised passwordless method such as a FIDO2 authenticator or passkey, biometric, hardware security key or token, push notification or one-time code, and manage i
3
artefacts
0
held by a system
1
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
system holds itEvidence a system already holds
none for this control
periodic reviewEvidence produced at each review
- Authenticator registration and revocation records · Identity provider / directory
governing documentDocuments that govern the control
- List of accounts using passwordless authentication and the method in use · Policy repository / GRC workspace
- Policy statement covering accepted passwordless methods · Policy repository / GRC workspace
First move
This control is evidenced by people and documents, not systems. Put the document under version control with an owner and review date, and log each review as a record with reviewer and date. Do not try to automate it.
Common gaps auditors find
- passwordless treated as out of scope so no control is evidenced
- no revocation process when a security key or device is lost
- method claimed as MFA when no user authentication is performed
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 sheetAC.7 MFA for Administrative Accounts · FW.1 Boundary Firewalls Deployed