8.4.1 General
Implement and maintain a response structure enabling timely warning and communication to relevant interested parties, with plans and procedures to manage the organization through a disruption and to activate continuity s
4
artefacts
0
held by a system
0
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
none for this control
governing documentDocuments that govern the control
- Documented response structure · Document repository
- Procedures stating immediate steps and the roles that take them · Policy repository / GRC workspace
- Traceability from selected strategies and solutions to the documented plans · Policy repository / GRC workspace
- Evidence procedures accommodate changing conditions rather than a single scenario · 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
- Procedures written for one rehearsed scenario, brittle against anything else
- Immediate steps missing, so the first hour is left to judgement under pressure
- Roles assigned to job titles that no longer exist
- Plans not traceable to any strategy, so their assumptions are untested
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 sheet8.4 Business continuity plans and procedures · 8.4.2 Response structure