A.5.30 ICT readiness for business continuity
Plan, implement, maintain and test ICT readiness against business continuity objectives.
12
artefacts
1
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
- Test execution logs · SIEM / log platform
periodic reviewEvidence produced at each review
- Test result summary report · Source control / CI pipeline
- Tabletop exercise minutes · Policy repository / GRC workspace
governing documentDocuments that govern the control
- ICT Business Continuity Plan document · Policy repository / GRC workspace
- Recovery Time Objective (RTO) matrix · Policy repository / GRC workspace
- Critical system inventory with dependency mapping · Policy repository / GRC workspace
- ICT readiness test schedule · Policy repository / GRC workspace
- Staff assignment matrix for continuity roles · Policy repository / GRC workspace
- Third‑party service SLA copies · Vendor register / contract repository
- Hardware and software inventory for backup sites · Policy repository / GRC workspace
- Full‑scale simulation after‑action report · Document repository
- Lessons learned register · Policy repository / GRC workspace
First move
Mostly documents and reviews. Pull the 1 system-held artefact 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
- Testing frequency not aligned with risk
- Plans not updated after infrastructure changes
- Insufficient documentation of test outcomes
- Lack of coordination with third‑party providers
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.29 Information security during disruption · A.5.31 Legal, statutory, regulatory and contractual requirements