CM-5 Access restrictions for change
Requires physical and logical access restrictions on who may make changes to the system to be defined, documented, approved and actually enforced, so that only authorized personnel can alter the system.
4
artefacts
2
held by a system
1
at each review
easy
to go live
Identity provider / directory
where the evidence lives
teal = a system already holds it · olive = produced at each review
system holds itEvidence a system already holds
- Access control configuration for production change paths and deployment pipelines · Identity provider / directory
- Records showing enforcement, for example rejected unauthorized deployments · Source control / CI pipeline
periodic reviewEvidence produced at each review
- Review of privileged change access against the approved list · Identity provider / directory
governing documentDocuments that govern the control
- Documented and approved restrictions on who may change what · Policy repository / GRC workspace
First move
Automate the pull from your Identity provider / directory. Scheduled export of users, roles and MFA state from the directory; access-review completion pulled from the IdP, not a spreadsheet.
Common gaps auditors find
- Developers hold standing write access to production alongside the pipeline
- Restrictions documented but not enforced, so the pipeline can be bypassed manually
- Physical access to equipment rooms not treated as a change path
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 sheet