Skip to content
Enterprise mobility
ASD ISMISM-1887

ASD ISM 1887 Implement remote locate and wipe for mobile security

What it says

Mobile devices are configured with remote locate and wipe functionality.

Quoted as published. Everything else on this page is written by Control Stack.

What it means

In plain English

Mobile devices should be set up to be located and wiped remotely to ensure security.

This control ensures that mobile devices are set up so they can be located or wiped clean remotely if they are lost or stolen. This is crucial because if a device with sensitive information falls into the wrong hands, it could lead to data breaches, loss of privacy, or financial harm. By enabling remote wipe and location tracking, you can protect against these risks by locking down devices immediately.

Why it matters

If remote locate/wipe is not enabled, a lost or stolen mobile can leak sensitive data and increase breach and compliance risk.

How to implement

  1. IT team should configure devices: Ensure every mobile device used for work is registered with the company's mobile device management system.

    This involves enrolling the device in software that allows you to track it and erase its data if necessary.

  2. Office manager to maintain an inventory: Keep an updated list of all mobile devices in use, including who uses them and their current status.

    Regularly review and verify that each device is properly registered for remote tracking and wiping.

  3. Procurement staff should choose compatible devices: Ensure any new mobile phones or tablets purchased can support remote locate and wipe features.

    This means checking with suppliers or the manufacturer for these capabilities before buying.

  4. System owner to review settings: Periodically check that remote locate and wipe functions are correctly set up on each device.

    This involves testing the functionalities to confirm they work as expected and making updates if needed.

  5. HR to educate employees: Conduct training sessions for staff on the importance of mobile security and what to do if their device is lost or stolen.

    Provide them with simple guides on initiating a remote wipe via the company's software.

Keep it running

Periodically validate remote locate and wipe works (including offline/MDM-triggered wipe) and confirm location services are enabled per device policy.

Evidence and audit

  1. Check 1 of 5What an auditor asks for

    Ask for

    The mobile device inventory list: Verify that there is a document listing all mobile devices in use and check that each is linked to the management system.

    Look at

    Details like the device ID and user information.

    Good evidence

    Is a comprehensive, updated list showing successful registration of devices.

  2. Check 2 of 5What an auditor asks for

    Look at

    How the system initiates a wipe and how fast it executes.

    Good evidence

    Demonstration shows the device being wiped and then restored to a clean state.

  3. Check 3 of 5What an auditor asks for

    Ask for

    Records of recent device wipe incidents: Review reports showing when devices were remotely wiped and why.

    Look at

    Documented evidence of lost or stolen devices and the actions taken.

    Good evidence

    Report includes incident details, times, and confirmation emails of wipe actions.

  4. Check 4 of 5What an auditor asks for

    Look at

    Clear instructions and roles defined for staff in charge of managing devices.

    Good evidence

    Policy outlines steps taken in case of loss or theft.

  5. Check 5 of 5What an auditor asks for

    Ask for

    The employee training records: Verify that staff have been trained on mobile security, focusing on device loss protocols.

    Look at

    Schedules, attendance records, and training materials.

    Good evidence

    Record shows regular sessions with comprehensive content on remote wipe procedures.

Mappings

Closest match in ISO/IEC 27001: A.6.7, Remote working security measures, which this control partially meets.

ISO 27001

ISO/IEC 27001: 3 mappings

Mappings show how controls relate across frameworks. They do not imply full equivalence or certification.