BCR-01 Business Continuity Management Policy and Procedures
Keep approved business continuity and operational resilience policies and procedures, communicate them to the people who must act on them, and review them at least once a year.
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 response teams and business owners · Policy repository / GRC workspace
governing documentDocuments that govern the control
- The approved continuity and resilience policy with approver and date · Policy repository / GRC workspace
- The procedures the policy requires, held current · 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 approved once at programme launch and never reviewed
- Response teams have never seen the policy that names them
- Procedures referenced by the policy do not exist
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 sheetAIS-07 Application Vulnerability Remediation · BCR-02 Risk Assessment and Impact Analysis