6.3 Planning changes to the business continuity management system
When change to the BCMS is needed, including change arising from nonconformity and improvement, carry it out in a planned way that considers the purpose and potential consequences of the change, the integrity of the BCMS
3
artefacts
0
held by a system
2
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
none for this control
periodic reviewEvidence produced at each review
- Change records for BCMS changes showing purpose and consequence analysis · Ticketing / ITSM
- Assessment of the effect on BCMS integrity · Ticketing / ITSM
governing documentDocuments that govern the control
- Resource and accountability reallocation recorded with the change · 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
- BCMS changes made informally, visible only as an unexplained document version bump
- Consequence analysis skipped for changes that originated as corrective actions
- Responsibilities left with departed staff after a reorganisation
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 sheet6.2.2 Determining business continuity objectives · 7.1 Resources