Skip to content
Enterprise mobility
ASD ISMISM-1533

ASD ISM 1533 Establish mobile device management policies

What it says

A mobile device management policy is developed, implemented and maintained.

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

What it means

In plain English

Create and maintain policies to manage and control mobile devices within the organisation.

Creating and maintaining a policy to manage mobile devices is like setting ground rules for how these devices are used in your organisation. This matters because without clear rules, mobile devices could become easy targets for cyber attacks or data leaks, leading to loss of sensitive information and potentially harming your business reputation.

Why it matters

Without an enforced MDM policy, lost or unmanaged mobiles may expose sensitive data and allow unauthorised access to corporate systems.

How to implement

  1. Business owner should task an IT consultant to draft a mobile device management policy.

    This document should outline what types of mobile devices can be used, how they can access company data, and the security measures that must be in place. Once drafted, review the policy with key staff to ensure it is clear and practical.

  2. IT manager should work with the HR team to ensure the mobile device policy is included in employee induction training.

    This involves explaining the rules clearly and providing examples of acceptable and unacceptable use. Ensure all employees sign that they understand and will comply with the policy.

  3. Security officer should regularly review and update the mobile device management policy.

    This can be done by scheduling bi-annual reviews to incorporate new risks and technology changes, ensuring that the policy remains effective and relevant.

  4. Office manager should implement a system to track all mobile devices accessing organisational data.

    This can be accomplished by maintaining a simple inventory list using a spreadsheet, recording device type, user details, and date of last security review.

  5. IT team should set up technical measures to enforce the policy.

    This includes configuring devices to enforce password protection, remote wipe abilities, and regular updates. Utilise mobile device management software to automate these settings where possible.

Keep it running

Review the MDM policy regularly to cover enrolment, PIN/biometrics, encryption, patching, app controls and remote wipe for lost or stolen devices.

Evidence and audit

  1. Check 1 of 5What an auditor asks for

    Ask for

    A copy of the current mobile device management policy document.

    Look at

    Whether it includes clear rules about acceptable use, security requirements, and consequences for policy violations.

    Good evidence

    Will be a comprehensive, up-to-date document with clear sections and sign-off from leadership.

  2. Check 2 of 5What an auditor asks for

    Look at

    Attendance records and training materials provided.

    Good evidence

    Is evidence of regular training sessions where all new and existing employees have attended and understood the policy.

  3. Check 3 of 5What an auditor asks for

    Look at

    Whether the list includes all devices accessing company data and is updated regularly.

    Good evidence

    Is a current and detailed inventory, with checks showing recent reviews of device status and compliance.

  4. Check 4 of 5What an auditor asks for

    Ask for

    Reports showing how technical control measures are enforced.

    Look at

    Whether mobile devices are configured to follow security settings such as passwords and remote wipe.

    Good evidence

    Includes dated logs or screenshots showing settings applied across devices.

  5. Check 5 of 5What an auditor asks for

    Look at

    When the policy was last reviewed and what changes were discussed.

    Good evidence

    Provides a documented review process with clear reasons for updates reflecting changing risks or organisational needs.

Mappings

Closest match in ISO/IEC 27001: A.8.1, Protection of user endpoint devices, which this control partially meets.

ISO 27001

ISO/IEC 27001: 1 mapping

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