ASD ISM 0701 Establish mobile device emergency sanitisation processes and procedures
What it says
Mobile device emergency sanitisation processes, and supporting mobile device emergency sanitisation procedures, are developed, implemented and maintained.
Quoted as published. Everything else on this page is written by Control Stack.
In plain English
Develop, use and maintain a process and step-by-step procedures for sanitising mobile devices, meaning erasing their data, in an emergency.
Mobile device emergency sanitisation processes, and the procedures that support them, must be developed, implemented and maintained. The process sets out what happens and when, and the procedures give the steps. Sanitising means erasing or overwriting data so it cannot be retrieved. Implemented means people can and do follow them. The control does not name the emergencies or the methods, so the organisation sets them. As cyber security documentation, they are reviewed at least annually (ISM-0888) and approved as ISM-0047 requires. They cover organisation-owned and privately owned devices.
Free. Save your status, tasks and notes.
Why it matters
A mobile device lost, stolen or seized in an emergency may still hold data a malicious actor can reach. A process and procedures people already know how to run let them erase that data quickly, which reduces the chance of it being compromised.
How to implement
Decide which emergencies trigger sanitisation.
The ISM does not list them, so name your own, such as a device lost, stolen, seized or about to be taken. Decide who can order it, including out of hours, and how people report the event.
Write the process and a procedure for each device type.
Give exact steps for each method available: remote wipe (ISM-1887 requires it for devices on a mobile operating system), a cryptographic key zeroise or sanitise function where the device has one (ISM-0702 requires its use on SECRET and TOP SECRET devices), or a reset by the person holding it.
Plan for a device you cannot reach or do not own.
A remote wipe usually runs only once the device connects, so also revoke its access and credentials. For a privately owned device, state what can be erased, using the legal advice ISM-1297 requires and, if it uses a mobile operating system, the separation ISM-2096 requires.
Test each procedure on a spare device.
Have the person who would run it in an emergency use only the written steps. Confirm the data can no longer be reached, note how long it took, and fix whatever slowed them down.
Keep it running
Retest after a new device type, operating system version or management platform, and after any real emergency. Review the documents at least annually (ISM-0888), each with a 'current as at' date or equivalent statement.
Evidence and audit
- Check 1 of 4What an auditor asks for
Ask for
The process and supporting procedures, with their approval and 'current as at' details.
Look at
Whether both exist and name the triggering emergencies and steps, who approved them and when they were last reviewed.
- Check 2 of 4What an auditor asks for
Ask for
The mobile device types in the management console and IT equipment register (ISM-0336), compared with the device types in the procedures.
Look at
Whether any device type in use has no procedure, including privately owned devices.
Good evidence
Every device type in those sources has a procedure that works for that type, including privately owned devices allowed to reach organisation data.
- Check 3 of 4What an auditor asks for
Ask for
A live run of a sampled procedure on a spare device, by the person who would do it, using only the written steps.
Look at
Whether they can find and complete the procedure, and whether the test data can still be reached afterwards.
Good evidence
The person completes the procedure using only the written steps, and the test data cannot be reached afterwards.
- Check 4 of 4What an auditor asks for
Ask for
Reports of lost or stolen mobile devices from the incident register (ISM-0125) and asset records, compared with wipe logs from the management console.
Look at
Whether each event that met a trigger has sanitisation recorded, and what happened where it could not run.
Good evidence
Every report that met a trigger shows sanitisation was run, or shows why it could not run and what was done instead, such as revoking access.
Mappings
Closest match in ISO/IEC 27001: A.8.1, User end point devices, which this control partially meets.
ISO/IEC 27001: 1 mapping
This control partially meets A.8.1.
ISM-0701 requires mobile device emergency sanitisation processes and procedures to be developed, implemented and maintained. Emergency sanitisation (for example wiping a device at risk of compromise or loss) is a specific measure for protecting information stored on or accessible via endpoint devices as required by Annex A 8.1. Annex A 8.1 covers all protections for user endpoint devices, while ISM-0701 addresses only emergency sanitisation of mobile devices.
Mappings show how controls relate across frameworks. They do not imply full equivalence or certification.




