7.5.1 General
The BCMS must include both the documented information the standard requires and whatever further documented information the organization itself judges necessary for the BCMS to be effective.
3
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 set is proportionate to the size and complexity of the organization · Document repository
governing documentDocuments that govern the control
- Mapping from each documentation requirement of the standard to the document that satisfies it · Policy repository / GRC workspace
- Rationale for additional documentation the organization chose to hold · 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
- Documentation assembled to a template with no mapping back to requirements
- Organization specific documentation absent, leaving gaps the standard does not name explicitly
- Volume mistaken for effectiveness, with documents nobody uses
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 sheet