A.5.29 Information security during disruption
Plan how to keep information security at the right level during disruption.
12
artefacts
2
held by a system
4
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
- Change Log - Temporary Security Controls During Outage · SIEM / log platform
- Stakeholder Communication Log - Service Interruption · SIEM / log platform
periodic reviewEvidence produced at each review
- Risk Assessment for Disruption Scenarios · Policy repository / GRC workspace
- BCDR Test Report - Simulated Power Outage · Backup / DR tooling
- Tabletop Exercise Minutes - Cyber Attack Disruption · Backup / DR tooling
- Approval Records for Control Relaxation · SIEM / log platform
governing documentDocuments that govern the control
- Disruption Security Management Procedure · Policy repository / GRC workspace
- Roles and Responsibilities Matrix for Disruption Events · Policy repository / GRC workspace
- Post-test Gap Analysis Summary · Policy repository / GRC workspace
- Reinstatement Checklist for Post-Disruption Controls · Policy repository / GRC workspace
- Incident Notification Emails - Disruption Event · Policy repository / GRC workspace
- Media Release Draft - Disruption Announcement · Policy repository / GRC workspace
First move
Mostly documents and reviews. Pull the 2 system-held artefacts from your SIEM / log platform 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
- Plans not updated after tests
- Missing documented approval for temporary control changes
- Insufficient evidence of communication with external parties
- Reliance on informal procedures only
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 sheetA.5.28 Collection of evidence · A.5.30 ICT readiness for business continuity