8.4.2 Response structure
Implement and maintain a structure of one or more teams responsible for responding to disruptions, with roles, responsibilities and inter team relationships clearly stated, collectively competent to assess a disruption a
5
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
- Named team members and alternates with competence evidence · HR system / LMS
- Exercise evidence that the teams performed the listed competences · HR system / LMS
governing documentDocuments that govern the control
- Team structure chart with roles, responsibilities and inter team relationships · Policy repository / GRC workspace
- Pre defined activation thresholds and the authority to invoke them · Document repository
- Documented team procedures for activation, operation, coordination and communication · 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
- Alternates named on paper but never included in an exercise
- Activation thresholds undefined, so invocation waits on consensus
- Life safety priority stated in policy but absent from the team procedures
- Media and authority communication left to a role with no delegated authority to speak
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 sheet