IA-4 Identifier management
Requires identifiers for individuals, groups, roles, services and devices to be assigned only on authorization from defined personnel, chosen to identify the right subject, assigned to that subject, and prevented from be
4
artefacts
0
held by a system
1
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
- Authorization records preceding identifier assignment · Identity provider / directory
governing documentDocuments that govern the control
- Naming standard covering individual, group, role, service and device identifiers · Policy repository / GRC workspace
- Configuration or procedure preventing identifier reuse for the defined period · Policy repository / GRC workspace
- Sample checks confirming no identifier was reissued inside that period · 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
- Reuse period never defined, so a leaver username is reissued to a new starter
- Service and device identifiers assigned by engineers without any authorization step
- Naming conventions inconsistent across systems so the same person appears as several subjects
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-3 Device identification and authentication · IA-5 Authenticator management