EvidenceSheet

5.33 Protection of records

Requires records to be protected against loss, destruction, falsification, unauthorised access and unauthorised release.

5
artefacts
0
held by a system
3
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

  • Evidence of protection appropriate to each record type against loss, destruction, falsification and unauthorised access or release · Source control / CI pipeline
  • Evidence of authorised and recorded destruction at the end of retention · Data governance / DLP tooling
  • Access controls and audit trails over records systems, especially where records support legal or regulatory obligations · Policy repository / GRC workspace

governing documentDocuments that govern the control

  • The records retention schedule, showing retention periods and their legal or business basis per record type · Policy repository / GRC workspace
  • Controls over the storage medium including its readability over the retention period · 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

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

5.32 Intellectual property rights · 5.34 Privacy and protection of PII