IAM-01 Identity and Access Management Policy and Procedures
Keep approved identity and access management policies and procedures, put them into effect, and review them at least annually.
4
artefacts
0
held by a system
2
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
- Annual review record · Document repository
- Evidence of communication to the teams that grant access · Policy repository / GRC workspace
governing documentDocuments that govern the control
- The approved identity and access management policy with approver and date · Policy repository / GRC workspace
- The procedures implementing it, such as provisioning and review procedures · 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
- Policy written and never implemented in the systems it governs
- Annual review missed
- Procedures exist for the main directory only, leaving cloud and application identity ungoverned
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 sheetHRS-13 Compliance User Responsibility · IAM-02 Strong Password Policy and Procedures