IA.L2-3.5.5 Identifier Reuse
Prevent an identifier from being reissued to a different entity until a defined period has elapsed.
3
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
- Evidence from identifier issuance history · Identity provider / directory
governing documentDocuments that govern the control
- Defined identifier reuse prohibition period · Policy repository / GRC workspace
- Procedure or system setting preventing early reuse · 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 undefined
- Email addresses or usernames recycled for new starters
- Prohibition stated but not enforced by the directory
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.L2-3.5.4 Replay-Resistant Authentication · IA.L2-3.5.6 Identifier Handling