PI-03 Secure deletion of data
Erase customer data at the end of the contractual relationship in line with the agreed terms, covering the customer environment, metadata and backup copies, using methods that defeat recovery by forensic means.
4
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
- Erasure procedure spanning the live environment, metadata stores and backup media · Policy repository / GRC workspace
- Completion confirmation issued for a terminated customer within the agreed period · Document repository
- Technical description of the wiping or key destruction method relied upon · Policy repository / GRC workspace
- Backup retention schedule showing when residual copies finally expire · 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
- Live data removed while backup copies persist to the end of an unchanged retention cycle
- Metadata, audit trails and derived indexes retained after the content itself is gone
- Removal limited to deleting pointers, leaving content readable from the underlying media
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 sheetPI-02 Contractual agreements for the provision of data · PS-01 Physical Security and Environmental Control Requirements