CCC-04 Unauthorized Change Protection
Prevent assets from being added, removed, updated or administered by anyone who has not been authorised to do so.
4
artefacts
1
held by a system
1
at each review
moderate
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
- Technical controls restricting who may change assets, such as pipeline permissions and console roles · Identity provider / directory
periodic reviewEvidence produced at each review
- Detection records for unauthorised change attempts · Document repository
governing documentDocuments that govern the control
- The authorised changer list and how it is kept current · Document repository
- Evidence of enforcement in production, not only in policy · Policy repository / GRC workspace
First move
Start with the 1 of 4 artefacts that already live in a system (Identity provider / directory); keep the periodic reviews but log each one as a dated record with a named reviewer.
Common gaps auditors find
- Broad standing administrative rights that make the restriction notional
- Restriction enforced in the pipeline but bypassable through direct console access
- No detection, so an unauthorised change would not be noticed
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 sheetCCC-03 Change Management Technology · CCC-05 Change Agreements