IM-2 Protect identity and authentication systems
Treat the identity and authentication system as a high priority asset, restricting privileged roles, requiring strong authentication for privileged access and monitoring high risk activity.
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
- Privileged directory role assignment list and review records · Identity provider / directory
governing documentDocuments that govern the control
- Strong authentication enforcement for all privileged roles · Policy repository / GRC workspace
- Identity secure score or equivalent posture measurement · Document repository
- Alerting on high risk identity activity · 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
- directory admin roles held permanently by many accounts
- privileged accounts exempt from strong authentication for convenience
- identity system telemetry not monitored separately from workload logs
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 sheetIM-1 Use centralized identity and authentication system · IM-3 Manage application identities securely and automatically