Processes for Sanitising Memory in Network Devices
Network devices should be cleared of data using specific steps to ensure memory is secure.
Plain language
This control is about making sure sensitive information isn't left behind on your network devices when they're being retired or re-used. If you don't properly clear data from these devices, confidential information could accidentally end up in the wrong hands, potentially leading to data breaches and loss of trust.
Framework
ASD Information Security Manual (ISM)
Control effect
Preventative
Classifications
NC, OS, P, S, TS
ISM last updated
Aug 2018
Control Stack last updated
19 Mar 2026
E8 maturity levels
N/A
Official control statement
Printers and MFDs are checked to ensure no pages are trapped in the paper path due to a paper jam.
Why it matters
If jam-trapped pages aren’t checked, sensitive printouts may be left in the paper path and later accessed by others, risking data leakage and breaches.
Operational notes
After any paper jam or service, open covers and visually check the paper path/output trays on printers and MFDs; remove all trapped pages and dispose of securely.
Implementation tips
- The IT team should first check for any device-specific guidance on how to clear data. They can usually find this in the instruction manuals or online support documents provided by the device manufacturer. Following these steps ensures the highest level of data erasure.
- For devices without specific guidance, the IT team should refer to the vendor's general instructions for clearing memory. This often includes steps like resetting the device and overwriting existing data, which can usually be found on the vendor's official website or support channels.
- In cases where device or vendor guidance isn't available, the IT team should load a basic, harmless configuration file onto the device, reset it to factory settings, and then reinstall the firmware. This helps remove any sensitive information stored in the device's memory.
- The IT team should maintain documentation of the sanitisation process for each device. This can include recording the date, the person responsible, and the steps taken, ensuring there's a clear record of data removal.
- System owners should arrange regular audits or reviews to ensure that all devices leaving the organisation have been properly wiped. Having a checklist or protocol in place makes this process easier and more consistent.
Audit / evidence tips
- AskThe device sanitisation procedures document: Request to see the written procedures that the IT team follows when clearing devices GoodIs a document that outlines the specific procedures and references official guidance
- AskRecords of recently sanitised devices: Request logs or records that show which devices have been wiped recently GoodShows a list matching inventory records, with recent dates and clear actions taken
- AskHow the IT team verifies data removal: Request evidence of any tests or checks performed after a device is erased to confirm data sanitisation GoodIncludes documentation of tests confirming no recoverable data
- AskAbout staff training on sanitisation processes: Request training records for staff responsible for data erasure GoodIncludes attendance records and recent training materials
- AskTo see the policy on device end-of-life: Request the organisation's policy regarding device retirement and data clearing GoodDetails the actions required before retiring or repurposing any device
Cross-framework mappings
How ISM-1221 relates to controls across ISO/IEC 27001, ISO/IEC 42001, Essential Eight, and ASD ISM.
ISO 27001
| Control | Notes | Details |
|---|---|---|
| layers Partially meets (1) expand_less | ||
| Annex A 8.10 | ISM-1221 requires organisations to clear residual information from printers and MFDs, including ensuring no pages are trapped after jams ... | |
| handshake Supports (1) expand_less | ||
| Annex A 7.14 | Annex A 7.14 requires verification that sensitive data is removed prior to disposal or re-use of equipment containing storage media | |
These mappings show relationships between controls across frameworks. They do not imply full equivalence or certification.