8.3.5 Implementation of solutions
Implement and maintain the selected business continuity solutions so that they can be activated when they are needed.
3
artefacts
0
held by a system
2
at each review
hard
to go live
Document repository
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
- Implementation records per selected solution · Document repository
- Readiness evidence such as a successful activation test or standby verification · Document repository
governing documentDocuments that govern the control
- Maintenance regime keeping the solution in an activatable state · Document 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
- Solution implemented then left to decay as systems, sites and contracts change around it
- Activation never verified, so readiness is an assumption
- Maintenance responsibility unassigned after the implementation project closed
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.3.4 Resource requirements · 8.4 Business continuity plans and procedures