5.30 ICT readiness for business continuity
Requires ICT readiness to be planned, implemented, maintained and tested against business continuity objectives and ICT continuity requirements. Supporting material frames this as ICT infrastructure and resources being r
5
artefacts
0
held by a system
1
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
- Records of gaps found in testing and their remediation · Document repository
governing documentDocuments that govern the control
- ICT continuity requirements derived from the business impact analysis, expressed as recovery time and recovery point objectives per service · Policy repository / GRC workspace
- The ICT continuity plans and the technical capability supporting them, such as replication, failover and alternative capacity · Policy repository / GRC workspace
- Test plans and results for the period, showing objectives were measured against the requirement rather than assumed · Policy repository / GRC workspace
- Evidence of maintenance, including plan updates after infrastructure or supplier change · Vendor register / contract repository
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
- Recovery objectives set by IT with no business impact analysis behind them
- Tests performed as a walkthrough or a partial failover that never proves the objective is achievable
- Dependencies on third parties and cloud regions excluded from the test scope
- Plans not updated after significant infrastructure change, so they describe an environment that no longer exists
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 sheet5.29 Information security during disruption · 5.31 Legal, statutory, regulatory and contractual requirements