AU.L2-3.3.2 User Accountability
Ensure actions taken on the system can be traced uniquely to the individual user responsible so users can be held accountable.
3
artefacts
1
held by a system
1
at each review
moderate
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
- Audit records showing the individual user attributed to actions · Policy repository / GRC workspace
periodic reviewEvidence produced at each review
- Evidence of unique user identifiers with no shared accounts · Identity provider / directory
governing documentDocuments that govern the control
- Controls tying privileged and service account use back to a person · Policy repository / GRC workspace
First move
Start with the 1 of 3 artefacts that already live in a system (Policy repository / GRC workspace); keep the periodic reviews but log each one as a dated record with a named reviewer.
Common gaps auditors find
- Shared or generic administrative accounts break attribution
- Privileged actions logged under a role rather than a person
- Service accounts used interactively
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 sheet