EvidenceSheet

8.10 Information deletion

Requires information held in information systems, devices or any other storage media to be deleted once it is no longer required. Supporting material frames this as procedures for secure deletion at the point the informa

5
artefacts
1
held by a system
2
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

  • Evidence of deletion actually performed, such as job records, deletion logs or reports of records removed · SIEM / log platform

periodic reviewEvidence produced at each review

  • Evidence covering copies, including backups, archives, replicas, test environments and third party held data · Backup / DR tooling
  • Records of deletion requests handled, including data subject erasure requests where privacy law applies · Data governance / DLP tooling

governing documentDocuments that govern the control

  • Deletion rules tied to retention requirements, per information type and per system · Policy repository / GRC workspace
  • The method used for each medium, and evidence it renders the information unrecoverable to the required standard · Policy repository / GRC workspace

First move

Mostly documents and reviews. Pull the 1 system-held artefact from your SIEM / log platform on a schedule; put the documents under version control with an owner and review date, and log each review as a dated record with a named reviewer.

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

8.9 Configuration management · 8.11 Data masking