4.1 Understanding the organization and its context
Identify the external and internal issues bearing on the organization's purpose that could stop its business continuity management system from delivering the outcomes it is meant to deliver, taking account of its objecti
4
artefacts
0
held by a system
1
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 the analysis was reviewed when the organization or its market changed · Document repository
governing documentDocuments that govern the control
- Documented context analysis naming external and internal issues · Document repository
- Link from each issue to the BCMS outcome it threatens · Document repository
- Statement of the risk appetite the analysis was judged against · 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
- Context recorded once at certification and never revisited after reorganisation, acquisition or a change of product mix
- Issues listed generically (economic conditions, cyber threat) with no traceable effect on a BCMS outcome
- Internal issues omitted entirely, so the analysis reads as an external threat scan
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 sheet4.2 Understanding the needs and expectations of interested parties