CC8.1 Change management processes are in place
Authorizes, designs, develops or acquires, configures, documents, tests, approves, and implements changes to infrastructure, data, software, and procedures to meet its objectives.
5
artefacts
1
held by a system
3
at each review
hard
to go live
Ticketing / ITSM
where the evidence lives
teal = a system already holds it · olive = produced at each review
system holds itEvidence a system already holds
- Change records for the period showing design, development or acquisition, configuration, documentation, testing, approval and implementation · Ticketing / ITSM
periodic reviewEvidence produced at each review
- Evidence of segregation between those who develop, approve and implement changes · Ticketing / ITSM
- Testing evidence per change proportionate to its risk, including security testing where relevant · Ticketing / ITSM
- Evidence of rollback capability and of post implementation verification · Ticketing / ITSM
governing documentDocuments that govern the control
- The change management process covering infrastructure, data, software and procedures, including the emergency change route · Policy repository / GRC workspace
First move
Mostly documents and reviews. Pull the 1 system-held artefact from your Ticketing / ITSM on a schedule; put the documents under version control with an owner and review date, and log each review as a dated record with a named reviewer.
Common gaps auditors find
- Emergency changes used routinely, with retrospective approval that is never withheld
- Approval and implementation performed by the same person, so the approval is not independent
- Automated deployment pipelines outside the documented process, so most changes are untested against it
- Infrastructure and configuration change treated as out of scope because the process was written for application code
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 sheetCC7.5 Identifies the root cause of security incidents · CC9.1 Identifies, selects and develops risk mitigation activities