IAM-13 Uniquely Identifiable Users
Give every user a unique identifier, or otherwise be able to tie the use of an account back to a named individual.
4
artefacts
0
held by a system
3
at each review
hard
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
none for this control
periodic reviewEvidence produced at each review
- Evidence that accounts map one to one with individuals · Identity provider / directory
- Records attributing shared account use to individuals · Identity provider / directory
- Review of shared accounts for elimination · Identity provider / directory
governing documentDocuments that govern the control
- The list of shared or generic accounts and the controls that attribute their use · 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
- Shared administrative accounts used with no attribution mechanism
- Generic accounts created for convenience and never reviewed
- Attribution possible in theory but the supporting logs are not retained
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 sheetIAM-12 Safeguard Logs Integrity · IAM-14 Strong Authentication