Zum Hauptinhalt springen
Starter Kit · Register

Deletion Evidence Log

Updated on 2 min Reviewed by: Cenedril-Redaktion
A.8.10 ISO 27001GDPR Art. 17

The deletion evidence log documents every secure data deletion and media destruction in your organisation. It proves that confidential data was actually destroyed — according to a defined standard, by an identifiable person, with independent confirmation.

ISO 27001 A.8.10 (Information Deletion) requires that information is deleted when no longer needed and that deletion is documented. The GDPR adds in Art. 17 the right to erasure of personal data. The deletion evidence log serves both requirements.

What does it contain?

Each row represents one deletion or destruction event. The columns:

  • ID / Data or Media — unique identifier and description of the deleted object (e.g. “12 retired laptops”, “backup tapes Q3 2024”)
  • Reason / Method / Standard — deletion reason, applied method and referenced standard (e.g. NIST SP 800-88 Purge)
  • Performed By / Verified By — person (or external service provider) who carried out the deletion and person who confirmed it
  • Date / Evidence / Status — date of execution, reference to destruction certificate and current status

How to use it

Initial setup: Define which deletion events require logging (typically everything classified as “Confidential” or above). Agree with IT operations on who documents execution and who provides confirmation.

Execution: For every deletion or media destruction, create a row in the log — before execution (with the planned date) or immediately after. Archive the evidence (destruction certificate, screenshot of the cloud audit log) and link it in the Evidence column.

Audit preparation: Auditors sample-check whether retired assets have a corresponding deletion record and whether the referenced evidence actually exists. A complete log with archived proof answers these questions immediately.

Register Template

Deletion Evidence Log

IDData / MediaReasonMethodStandardPerformed ByVerified ByDateEvidenceStatus
DEL-2026-00112 retired laptops (AST-006 fleet)End of lifeCryptographic erase + physical shreddingNIST SP 800-88 Rev.1 PurgeCertified vendor SecureIT GmbHIT Operations Lead2026-02-20Certificate of destruction CDS-26-0214Completed
DEL-2026-0025 TB backup tapes (2019-2022)Retention expiryDegaussing + shreddingNIST SP 800-88 Rev.1 DestroyCertified vendor SecureIT GmbHIT Operations Lead2026-03-05Certificate CDS-26-0301Completed
DEL-2026-003Customer record (SAR erasure request)GDPR Art. 17DB row soft-delete + backup tombstone + 30-day purgeGDPR compliant deletion procedureDPOISO2026-03-12SAR-2026-007 closure logCompleted
DEL-2026-004Former employee M365 mailbox (J. Schmidt)Leaver 90 days pastDelete mailbox + retention policy removalM365 retention procedureIT OperationsHR Lead2026-04-02M365 audit log entryCompleted
DEL-2026-005Test database (staging snapshot 2025-Q4)Old test dataDatabase drop + S3 object deleteInternal deletion procedureHead of EngineeringIT Operations Lead2026-03-18Pipeline log DEL-2026-005Completed
DEL-2026-00620 USB sticks (inventory clean-up)ReassignmentCryptographic eraseNIST SP 800-88 ClearIT OperationsIT Operations Lead2026-01-15Erase script logCompleted
DEL-2026-007Marketing campaign data (2023 event)Retention expiryS3 object delete + CRM segment purgeRetention scheduleMarketing LeadDPO2026-02-28S3 lifecycle policy logCompleted

Sources

ISO 27001 Controls Covered

A.8.10 Information deletion

Frequently asked questions

When do I need a deletion evidence log?

For every planned destruction of storage media (hard drives, SSDs, USB sticks, tapes) and for deletion of data that has exceeded its retention period. Cloud resources (virtual machines, storage buckets) also belong in the log when they contain confidential data.

Which sanitisation standard should I use?

NIST SP 800-88 Rev. 1 distinguishes three levels: Clear (logical overwrite), Purge (cryptographic erase or degaussing) and Destroy (physical destruction). For most organisations, Purge for SSDs and Destroy for hard drives at end of life is appropriate. The choice depends on the data classification.

Does deletion need to be confirmed by a second person?

ISO 27001 does not explicitly require dual control, but A.8.10 demands verifiable deletion. In practice, a Verified By field (as in our template) is the simplest way to provide this evidence. For external service providers, a certificate of destruction replaces the personal confirmation.