7.5.2 Creating and updating
When creating or updating documented information, ensure appropriate identification and description, an appropriate format and medium, and review and approval for suitability and adequacy.
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
- Review and approval records showing who approved and when · Document repository
governing documentDocuments that govern the control
- Documents carrying title, date, author or reference and version · Document repository
- Format and media choices suited to how the document is used in a disruption · 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
- Approval evidenced by a name in a footer with no date or record
- Format unsuited to use, such as plans available only on the systems a disruption takes out
- Updates issued without re-approval
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