03.05.05 Identifier Management
Manage system identifiers by receiving authorization, selecting an identifier, assigning to intended individual/group/role/device, and preventing reuse for a defined period.
3
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
- Username convention · Document repository
- Deprovisioning procedure · Policy repository / GRC workspace
- Identifier reuse policy · 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
- recycling usernames
- no central identifier registry
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 sheet03.05.04 Replay-Resistant Authentication · 03.05.07 Password Management