IM-1 Use centralized identity and authentication system
Standardise on Microsoft Entra ID as the central identity system for Azure resources and integrated applications.
3
artefacts
1
held by a system
0
at each review
moderate
to go live
Cloud console / configuration management
where the evidence lives
teal = a system already holds it · olive = produced at each review
system holds itEvidence a system already holds
- Federation configuration · Cloud console / configuration management
periodic reviewEvidence produced at each review
none for this control
governing documentDocuments that govern the control
- Entra ID tenant inventory · Policy repository / GRC workspace
- Local account exception list with justification · Policy repository / GRC workspace
First move
Start with the 1 of 3 artefacts that already live in a system (Cloud console / configuration management); keep the periodic reviews but log each one as a dated record with a named reviewer.
Common gaps auditors find
- Local accounts on VMs not inventoried
- Multiple disconnected tenants
- Legacy authentication still allowed
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 sheetGS-10 Define and implement DevOps security strategy · IM-2 Protect identity and authentication systems