IDM-09 Authentication mechanisms
Authenticate every user and automated system component, require two-factor or multi-factor authentication to reach the production environment, permit only passwords, signed certificates or equally strong methods inside i
4
artefacts
0
held by a system
0
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
none for this control
governing documentDocuments that govern the control
- Authentication design stating which factors are demanded to reach production · Policy repository / GRC workspace
- Password policy showing the risk assessment from which its parameters were derived · Policy repository / GRC workspace
- Platform settings enforcing those password parameters on in-scope system components · Policy repository / GRC workspace
- Certificate administration records held under the key management guideline · 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
- Break-glass and emergency logins reach production behind a single factor
- Password rules published centrally but not technically enforceable on some platforms
- Machine certificates used for authentication issued outside the governed key management process
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 sheetIDM-08 Confidentiality of authentication information · INQ-01 Legal Assessment of Investigative Inquiries