Cookies on this site. Help us understand what works and improve your experience. Essential cookies keep the site working. With your permission, our visit insights and Google Analytics measure usage, and Google Ads measures advertising. Optional cookies are not required to use the free kit. Change your choice anytime in Cookie settings. Privacy policyCookie policy
New in 2022: delete information when it is no longer needed, in line with retention rules and law.
Is it mandatory? Not automatically. You must consider this control in your Statement of Applicability (6.1.3 d). Include it if your risk assessment, laws, contracts or business needs require it; if you exclude it, write down a justification an auditor will accept.
Why this control matters
Information deletion often fails when teams confuse storage cleanup with governed disposal. Owners should delete data only after retention, legal hold, and contractual checks, while preserving proof that deletion occurred across systems and suppliers. It should also separate secure deletion from media reuse so records remain defensible during review.
Common auditor findings to check for
Potential gaps to test in your own environment, not a claim about observed audit frequency.
Retention labels or disposal triggers exist, but owners cannot show how deleted items are excluded from legal holds, backups, or active case files.
Cloud admin teams purge records, yet supplier-held copies, exports, and downstream replicas remain unmanaged with no confirmation trail.
Deletion requests are ad hoc, so there is no role-based approval, completion evidence, or exception log for delayed destruction.
How you can implement it
Tools and review intervals are examples; choose them according to risk, obligations and your operating environment.
Define an end-of-life decision path owned by the records or data owner, with input from legal, privacy, and service owners before deletion begins. Use the retention schedule, contract terms, and litigation-hold register to decide whether data is eligible, then route exceptions to the ISMS risk owner for documented approval.
Specify deletion methods by data type and location: SaaS recycle bin purge, database record removal, object-store lifecycle rules, endpoint secure wipe, and paper shredding through a locked-chain vendor. The Secure Disposal & Reuse Procedure should state who executes each step, what constitutes completion, and how failed jobs are retried.
Maintain a deletion ticket or register containing dataset name, system, classification, trigger date, approver, execution date, and operator identity. Attach system logs, storage reports, supplier certificates of destruction, and screenshots of lifecycle rule status so reviewers can trace a record from approval to final disposal.
Review deletion activity on an illustrative monthly or quarterly cadence to detect backlog, orphaned repositories, and recurring exceptions. Feed missed deadlines, incomplete supplier returns, and recurring manual work into corrective action and continual improvement so retention logic, tooling, or accountability can be adjusted.
What an auditor will ask to see
Deletion register with dataset, retention basis, owner, approval, execution date, and linked exception notes.
System lifecycle policy screenshots, purge job logs, and secure wipe reports from endpoint or storage tools.
Supplier destruction confirmation, contract return certificate, or signed disposal statement for off-site records.
Baseline documents in the kit
These free kit documents help you document or evidence A.8.10. Each one is tailored to your organization when you build your kit.
Use the SIG and CAIQ questionnaire accelerator to find supporting documents. A mapping is a starting point: verify your actual operating evidence before answering a buyer.
For help adapting this to your environment, explore ISO/IEC 27001 consulting, starting with a free one-hour consultation.
Get these documents tailored to your organization
109 ready-to-edit documents, including all 19 mandatory ones, tailored from a short scoping questionnaire and linked to your risk register and SoA.