Skip to content
Enterprise mobility
ASD ISMISM-2096

ASD ISM 2096 Separate organisational and personal mobile data

What it says

Mobile devices are configured to enforce separation between organisational and personal mobile applications and data.

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

In plain English

Configure mobile devices to enforce separation of organisational and personal applications and data, using device settings rather than relying on users to keep them apart.

Mobile devices must be configured to enforce separation between organisational and personal mobile applications and data. Enforce means the device itself keeps them apart, so a rule is not enough. Both applications and data count, in both directions: for example, a personal application must not open organisational files, organisational data must not reach personal storage, and personal files must not enter organisational applications. Mobile devices here are those on a mobile operating system, such as smartphones and tablets. ISM-1400 and ISM-1482 separately require enforced separation of classified and personal data.

Why it matters

Without enforced separation, a personal application can read organisational data, or a user can move it to personal storage or a personal account, where the organisation cannot protect or remove it. Separation set on the device blocks those routes.

How to implement

  1. Choose the separation method for each platform.

    Use a work profile or managed container (a separate managed area of the device), or the platform's rules between managed and unmanaged applications, to hold organisational applications and data apart from personal ones. On devices with no personal use, block personal accounts and keep every application managed, so nothing personal can enter.

  2. Put organisational applications on the organisational side only.

    Install them through device management and tie them to organisational accounts. Block personal sign-in inside them, because a user can otherwise switch a managed application to a personal account. An application with no such block is a known shortfall until replaced.

  3. Block data crossing the boundary in both directions.

    Turn off copy and paste, file sharing and share menus between the two sides, and stop files opening in the other side's applications. Keep organisational data out of personal cloud accounts, personal backups and personal email.

  4. Test the boundary as an ordinary user.

    On a test device of each platform, try to open a work attachment in a personal application, paste work text into a personal note and save a work file to personal storage. Then try the reverse. Fix whatever succeeds.

  5. Deal with devices that cannot enforce separation.

    Replace the model, or block it from organisational systems with a compliance rule at sign-in. A recorded exception stays a known shortfall until then. Privately owned devices need the same setup, after the legal advice ISM-1297 requires, and ISM-1866 still bars storing classified data on them.

Keep it running

Retest the boundary after operating system or management tool upgrades, and when a new organisational application, account type or sharing feature appears, because each can open a new route between the two sides.

Evidence and audit

  1. Check 1 of 3What an auditor asks for

    Ask for

    The list of mobile devices with the separation method applied to each, and an independent list of devices on a mobile operating system, from sources such as the asset register, carrier bills or sign-in logs.

    Look at

    Whether every device on the independent list is enrolled and has the separation settings applied.

    Good evidence

    Every device on the independent list has the separation settings applied and reports them in force, including any privately owned devices allowed to connect. A recorded exception does not pass.

  2. Check 2 of 3What an auditor asks for

    Ask for

    A live test as an ordinary user on a device of each platform sampled from the independent list: opening an organisational file in a personal application, pasting organisational text into one, saving to personal storage, and the reverse of each.

    Look at

    Whether each device blocks each attempt in each direction, including through share menus, and whether the user can turn the block off.

    Good evidence

    Each device blocks every attempt in both directions, including through share menus, and the user cannot turn the block off.

  3. Check 3 of 3What an auditor asks for

    Ask for

    The applications, accounts and backup settings on a device of each platform sampled from the independent list.

    Look at

    Whether each organisational application is managed and tied to an organisational account, and where its data is backed up.

    Good evidence

    Organisational applications are managed, sit only on the organisational side and cannot switch to a personal account, and no organisational data is backed up to a personal account or computer. On a device with no personal side, no personal account or application can be added.

Mappings

Closest match in ISO/IEC 27001: A.6.7, Remote working, which this control supports.

ISO 27001

ISO/IEC 27001: 1 mapping

  • A.6.7Remote workingSupports

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