7.5.3 Control of documented information
Control the documented information the BCMS and the standard require so it is available and suitable for use where and when needed and adequately protected, addressing distribution, access, retrieval and use, storage and
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
- Access and distribution controls with evidence of enforcement · Document repository
governing documentDocuments that govern the control
- Storage and preservation arrangements including offline or alternate site availability · Document repository
- Version control history and retention and disposition schedule · Policy repository / GRC workspace
- Register of controlled external origin documents · Policy repository / GRC workspace
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
- Plans stored only on the corporate network, so they are unavailable in the scenario they exist for
- External origin documents such as supplier contracts and regulator guidance left uncontrolled
- Protection considered for confidentiality but not for integrity or loss
- Superseded plans still in circulation at response team locations
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 sheet7.5.2 Creating and updating · 8.1 Operational planning and control