7.5 Documented information
Hold the documented information the BCMS depends on, create and update it to a defined standard, and control it throughout its life.
3
artefacts
0
held by a system
0
at each review
hard
to go live
Policy repository / GRC workspace
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
none for this control
governing documentDocuments that govern the control
- Document register covering BCMS documentation · Policy repository / GRC workspace
- Defined creation, update and approval route · Document repository
- Access, retention and disposition rules in force · 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
- Register incomplete, so documents exist that nothing controls
- External origin documents excluded from control
- Retention rules stated but never applied
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