IA.L2-3.5.1 Identification
Identify system users, the processes acting on their behalf, and devices, so each is distinguishable before any access decision is made.
3
artefacts
0
held by a system
2
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
- Identifier assignment process and records · Identity provider / directory
- Evidence identifiers are unique and not shared · Identity provider / directory
governing documentDocuments that govern the control
- Inventory of user, process and device identifiers · 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
- Devices and process accounts unidentified while users are covered
- Shared identifiers in use
- Identifier issuance undocumented
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 sheetCM.L2-3.4.9 User-Installed Software · IA.L2-3.5.2 Authentication