7.1 Resources
Determine and provide the resources needed to establish, implement, maintain and continually improve the BCMS.
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
- Evidence of provision, such as budget allocation, headcount or contracted capacity · Cloud console / configuration management
- Evidence resourcing is revisited as the BCMS matures · Document repository
governing documentDocuments that govern the control
- Documented determination of the resources the BCMS requires · 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
- Resource need never determined, so provision is whatever was left over
- Provision covers implementation only and lapses at maintenance
- Resource shortfalls known to the BCMS owner but never escalated to top management
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 sheet6.3 Planning changes to the business continuity management system · 7.2 Competence