ISO 27001 Annex A 8.10 Secure deletion of information when no longer needed
What it says
Information stored in information systems, devices or in any other storage media shall be deleted when no longer required.
Quoted as published. Everything else on this page is written by Control Stack.
What it means
In plain EnglishDelete data you don't need anymore to reduce risk and comply with laws.
This control is about securely deleting information you no longer need, to protect your business from data breaches and to comply with the law. If you keep old or unnecessary data, it could be exposed or stolen, leading to legal troubles or financial loss.
Free. Save your status, tasks and notes.
Why it matters
Failing to securely delete unneeded data can lead to data breaches and legal non-compliance, risking penalties and reputational damage.
How to implement
The IT manager should develop a data retention policy that specifies when information needs to be deleted.
This policy should take into account business needs and comply with laws like the Privacy Act 1988.
The operations team should ensure all systems and applications are configured to automatically delete obsolete data.
Use secure deletion methods like electronic overwriting in line with ISO 27002:2022 guidance.
Procurement officers should include data deletion requirements in contracts with third-party services that handle your data.
Make sure these agreements specify how and when your data will be deleted.
HR should train staff on the importance of deleting unnecessary data.
Employees should know how to identify data that is no longer needed and how to securely delete it.
The IT department should verify that any cloud service providers are using acceptable data deletion methods.
Regularly review these processes to ensure they align with your organisation's data protection policies.
Keep it running
Regularly review retention schedules and deletion workflows; use verified sanitisation tools and destruction methods for media, and keep evidence of deletion.
Evidence and audit
- Check 1 of 5What an auditor asks for
Ask for
The data retention and deletion policy.
Look at
The specific guidelines for data deletion and retention periods.
Good evidence
A clear policy aligned with legal and business requirements.
- Check 2 of 5What an auditor asks for
Ask for
Evidence of data deletion activities, such as deletion logs.
Look at
Timestamps and the methods used for deletion.
Good evidence
Records showing timely and secure deletions.
- Check 3 of 5What an auditor asks for
Ask for
Contracts with third-party service providers.
Look at
Clauses related to data deletion upon contract termination or at regular intervals.
Good evidence
Contracts with clear data deletion obligations.
- Check 4 of 5What an auditor asks for
Ask for
Training records for employees on data deletion practices.
Look at
Attendance records and training content.
Good evidence
Regular training sessions on secure data handling and deletion.
- Check 5 of 5What an auditor asks for
Ask for
To see the configuration of systems used for storing sensitive data.
Look at
Settings for automatic data deletion and encryption.
Good evidence
Secure configurations that ensure automatic and secure deletion processes.
Mappings
Closest match in ASD Information Security Manual: ISM-0317, Ensuring data erasure on printer cartridges and drums, which this control covers in full and more.
ISO/IEC 42001: 1 mapping
This control partially overlaps A.5.3.
Annex A 5.3 requires the organisation to document AI system impact assessment results and retain them for a defined period. Annex A 8.10 overlaps by requiring secure deletion of information when no longer needed, which complements retention by ensuring impact assessment records are disposed of securely once the defined retention period expires. Annex A 5.3 is primarily about documenting and keeping the assessment results, whereas Annex A 8.10 is about end-of-life handling and secure disposal across all information types.
ASD Information Security Manual: 24 mappings
This control is broader than ISM-0317.
Annex A 8.10 requires deletion of information from devices and storage media when it is no longer required. ISM-0317 mandates a specific erasure approach for residual data on printer cartridges and MFD drums, which is a niche but direct subset of secure deletion. ISM-0317 is narrower and technology-specific, whereas Annex A 8.10 applies broadly to all systems and media types.
This control is broader than ISM-0351.
ISM-0351 requires sanitisation of volatile media by removing power for at least 10 minutes. Annex A 8.10 requires secure deletion of information from systems, devices or any storage media when it is no longer needed. ISM-0351 is a specific implementation approach for one category of media (volatile memory), whereas Annex A 8.10 is broader and covers deletion needs across many media types and use cases.
This control is broader than ISM-0357.
ISM-0357 mandates a specific secure-erasure technique for non-volatile EPROM media (extended UV exposure, overwrite, and verification). Annex A 8.10 requires secure deletion of information from systems, devices, or any storage media when no longer needed, without prescribing a specific technique. ISM-0357 is a concrete implementation option that fits within Annex A 8.10's broader secure-deletion requirement and goes deeper on method and verification for EPROM.
This control is broader than ISM-0359.
ISM-0359 specifies how to sanitise non-volatile flash memory by overwriting it twice with random data and verifying via read-back. Annex A 8.10 requires information to be deleted when no longer needed across systems, devices and storage media, without prescribing a particular sanitisation standard or verification method. ISM-0359 is therefore a concrete, auditable implementation approach that can be used to satisfy deletion requirements for flash media under Annex A 8.10, but it does not cover broader retention decisioning or all media types.
This control is broader than ISM-0361.
Annex A 8.10 requires secure deletion of unneeded data, while ISM-0361 supports this by specifying the use of rated degaussers for magnetic media, aligning with Annex A 8.10's goals for secure deletion.
This control is broader than ISM-0947.
Annex A 8.10 requires deletion of information from storage media once it is no longer required. ISM-0947 mandates sanitising rewritable media after each manual transfer between different security domains, which is a specific case of deletion to prevent residual data exposure. ISM-0947 is narrower because it applies to cross-domain manual transfers and rewritable media, whereas Annex A 8.10 applies to all contexts where data is no longer needed.
This control is broader than ISM-1065.
ISM-1065 requires resetting HPA and DCO on magnetic hard drives before sanitisation so that deletion activities apply to all addressable and previously hidden disk areas. Annex A 8.10 requires secure deletion of information when no longer needed, and ISM-1065 supports this by preventing incomplete deletion caused by drive-level configuration that hides sectors from standard wiping tools. Annex A 8.10 is broader in scope (all media and systems), whereas ISM-1065 is a targeted control for a specific sanitisation failure mode on magnetic drives.
This control is broader than ISM-1160.
ISM-1160 requires that where degaussing is used as the secure destruction method, the organisation uses NSA-evaluated degaussers to ensure effective sanitisation. Annex A 8.10 requires secure deletion of information from systems, devices, or any storage media when no longer required, which may be met through deletion, overwriting, cryptographic erasure, or physical destruction such as degaussing. Annex A 8.10 is broader and outcome-focused on secure deletion, while ISM-1160 is a specific implementation constraint for one physical sanitisation technique.
This control is broader than ISM-1223.
Annex A 8.10 requires organisations to delete information from devices and storage media when it is no longer needed. ISM-1223 specifies approved methods to sanitise network device memory, which is one concrete subset of securely deleting information from particular device types. ISM-1223 is technical and device-specific, while Annex A 8.10 is broader and technology-agnostic across all storage locations.
This control is broader than ISM-1722.
ISM-1722 addresses secure destruction of electrostatic memory devices via physical destruction techniques to ensure information cannot be recovered. Annex A 8.10 requires information in systems and storage media to be securely deleted when no longer required, covering a broad range of deletion/sanitisation approaches. ISM-1722 is a specific, high-assurance physical destruction method that fits within the broader secure deletion objective of Annex A 8.10.
This control is broader than ISM-1723.
ISM-1723 addresses preventing information recovery by requiring physical destruction of magnetic floppy disks using specific approved methods. Annex A 8.10 requires information to be securely deleted from systems, devices, or any storage media when no longer needed, which can be achieved via deletion, overwriting, or destruction depending on the medium and risk. ISM-1723 is a specific destruction-based way to meet secure deletion objectives for a particular legacy medium, whereas Annex A 8.10 is broader and technology-agnostic.
This control is broader than ISM-2021.
ISM-2021 requires system owners to implement and maintain data minimisation practices for each system, limiting collection and storage to what is necessary. Annex A 8.10 specifically requires secure deletion of information when it is no longer required, which is a key mechanism to reduce retained data volume over time. ISM-2021 is broader because it covers minimising data at collection, processing, and storage decisions, whereas Annex A 8.10 focuses on end-of-life deletion only.
This control is broader than ISM-2111.
ISM-2111 requires removing temporary installation files after user applications are installed to reduce residual artefacts on systems. ISO/IEC 27001:2022 Annex A 8.10 requires secure deletion of information when no longer needed, which can include installation leftovers that are no longer required once installation completes. Annex A 8.10 applies broadly to all information types and retention contexts, whereas ISM-2111 is focused specifically on installer-generated temporary files and the post-installation step.
This control is broader than ISM-2123.
ISM-2123 requires that all prompts and outputs associated with AI chat sessions are securely deleted when the chat session is removed from the application. This directly aligns with ISO/IEC 27001:2022 Annex A 8.10, which requires secure deletion of information when it is no longer needed, and chat prompts/outputs are a specific class of stored information. Annex A 8.10 is broader because it applies to all information across systems and media, not just AI chat session artefacts.
This control partially overlaps ISM-0307.
Annex A 8.10 mandates deletion of unnecessary information. ISM-0307 requires data sanitisation before third-party maintenance, preventing unintended disclosure, aligning with secure deletion practices.
This control partially overlaps ISM-0311.
Annex A 8.10 requires deletion of information when not needed to reduce risk, while ISM-0311 mandates media sanitisation either by removal or in-situ, aligning with secure deletion for repurposing or disposal.
This control partially overlaps ISM-0330.
ISM-0330 requires that before media is reclassified to a lower sensitivity or classification, it is sanitised or destroyed and a formal administrative decision is made to reclassify it. ISO/IEC 27001:2022 Annex A 8.10 overlaps by requiring secure deletion of information from systems, devices or other storage media when it is no longer required, which is one common method used to sanitise media. However, Annex A 8.10 is driven by retention/need-to-keep considerations rather than reclassification, and it does not address the administrative approval/decision process that ISM-0330 mandates.
This control partially overlaps ISM-0363.
Annex A 8.10 mandates that unused information be securely deleted, while ISM-0363 requires documented procedures for media destruction, supporting Annex A 8.10 by enhancing process maturity and consistency.
This control partially overlaps ISM-0371.
ISM-0371 requires supervised handling of media up to the point of destruction and confirmation that destruction completes successfully. Annex A 8.10 relates because it requires secure deletion of information from systems/devices/media when no longer needed, which can be implemented via destruction or sanitisation. Annex A 8.10 is broader about deletion triggers and scope (information lifecycle), while ISM-0371 is narrower and procedural, targeting supervision of physical/media destruction execution.
This control partially overlaps ISM-0375.
ISM-0375 requires an authorised administrative decision before media (or its waste) can be released publicly after sanitisation, destruction or declassification. Annex A 8.10 requires information to be securely deleted when no longer needed, which is one of the actions that may occur before any disposal or release decision. Annex A 8.10 addresses the deletion requirement itself, while ISM-0375 adds the post-treatment governance step specifically for public release of the media/waste.
This control partially overlaps ISM-1600.
ISM-1600 requires media to be sanitised before first use so it does not contain unwanted data that could create security or integrity issues. Annex A 8.10 requires secure deletion of information when it is no longer needed across systems, devices and storage media. Both controls involve sanitisation/secure removal of data on media, but ISM-1600 is focused on preventing pre-existing data at onboarding, while Annex A 8.10 is focused on end-of-life or end-of-need deletion.
This control partially overlaps ISM-2053.
Annex A 8.10 requires information to be deleted from systems, devices or media when it is no longer required. ISM-2053 requires software end-of-life procedures that include removing software and archiving or destroying associated user accounts and data, which directly includes secure deletion/disposal activities at decommissioning time. ISM-2053 is narrower in trigger (software end-of-life) but broader in lifecycle packaging (procedural decommissioning steps beyond deletion).
This control supports ISM-0348.
Annex A 8.10 requires organisations to ensure information is deleted when no longer required. ISM-0348 supports Annex A 8.10 by requiring media sanitisation processes and procedures to be developed, implemented and maintained, which provides the operational capability to perform secure deletion. ISM-0348 focuses on procedural governance for sanitisation and does not itself set the retention/deletion trigger of 'no longer required'.
This control supports ISM-0362.
Annex A 8.10 requires deletion of unneeded information. ISM-0362 supports this by ensuring effective degaussing, a specific destruction method, which complements Annex A 8.10's broader scope.
Mappings show how controls relate across frameworks. They do not imply full equivalence or certification.
Get help with this control
ISO 27001 training
Mindset Cyber runs PECB-accredited ISO/IEC 27001 training that maps directly to the controls in this library.