IA-2 Identification and authentication of organizational users
Requires organizational users to be uniquely identified and authenticated, and requires that unique identity to be carried through to the processes that act on their behalf, so that system activity is attributable to a s
4
artefacts
1
held by a system
1
at each review
moderate
to go live
Identity provider / directory
where the evidence lives
teal = a system already holds it · olive = produced at each review
system holds itEvidence a system already holds
- Authentication configuration including multi-factor where required · Identity provider / directory
periodic reviewEvidence produced at each review
- Evidence that process and session activity carries the initiating user identity · Identity provider / directory
governing documentDocuments that govern the control
- Directory or identity store showing unique accounts per organizational user · Policy repository / GRC workspace
- Register of any shared accounts with justification and compensating attribution · Policy repository / GRC workspace
First move
Start with the 1 of 4 artefacts that already live in a system (Identity provider / directory); keep the periodic reviews but log each one as a dated record with a named reviewer.
Common gaps auditors find
- Shared administrative accounts destroy attribution at exactly the highest privilege
- Automation runs under a generic identity that hides who initiated the action
- Legacy applications authenticate locally and outside the central identity store
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 sheetIA-1 Policy and procedures for identification and authentication · IA-3 Device identification and authentication