Skip to content
Enterprise mobility
ASD ISMISM-1400

ASD ISM 1400 Enforce data separation on personal devices

What it says

Personnel using privately owned mobile devices or desktop computers to access OFFICIAL: Sensitive or PROTECTED systems or data have enforced separation of classified data and personal data.

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

In plain English

Personnel reaching OFFICIAL: Sensitive or PROTECTED systems or data from privately owned mobile devices or desktop computers must have classified and personal data technically kept apart.

Personnel using privately owned mobile devices or desktop computers to access OFFICIAL: Sensitive or PROTECTED systems or data must have classified data and personal data kept separate by enforcement. Personal data means the person's own material. Enforced means a technical mechanism stops data crossing between the two, such as being copied into a personal app or account. A rule or signed agreement alone does not qualify. ISM-1866 separately prevents classified data being stored on these devices, so a mechanism that separates data on the device can still fall short there.

Why it matters

On a personal device, classified data can end up in personal email, a personal cloud backup or another app, where the organisation cannot see or remove it. Enforced separation blocks those paths, rather than relying on each person's care.

How to implement

  1. List who uses privately owned devices for these systems.

    Use sign-in logs and device records to find each person and device reaching OFFICIAL: Sensitive or PROTECTED systems or data from a privately owned mobile device or desktop computer. Include contractors. ISM-1297 requires legal advice before this access is allowed.

  2. Choose a mechanism that keeps data apart and off the device.

    A virtual desktop or published app suits both this control and ISM-1866, which bars storing classified data on these devices. A managed work profile or app container separates data on a mobile operating system (ISM-2096), but needs local saving and offline sync turned off.

  3. Block every path between work and personal data.

    Enforce settings for copy and paste, clipboard and drive redirection, printing, sharing between managed and personal apps, saving to personal cloud storage and backups to personal accounts. Cover both directions, and make sure users cannot change these settings.

  4. Refuse access from outside the managed path.

    Set the identity platform or remote access gateway so these systems accept a privately owned device only through the mechanism. For a bought cloud service, use its session or app protection settings. If it has none, do not offer that service on privately owned devices.

Keep it running

Retest after operating system, app or access platform updates, because new sharing or clipboard features can open a path. A new device type, or a new system offered through the mechanism, should trigger the same test.

Evidence and audit

  1. Check 1 of 3What an auditor asks for

    Ask for

    Sign-in logs for OFFICIAL: Sensitive or PROTECTED systems, compared with the list of people and devices using the separation mechanism.

    Look at

    Whether the logs can identify privately owned devices, and whether any reached those systems or data outside the mechanism.

    Good evidence

    The logs identify privately owned devices, and every one that reached those systems or data did so through the mechanism.

  2. Check 2 of 3What an auditor asks for

    Ask for

    A live test with test data and a test account on each privately owned device type in use, including a mobile device and a desktop computer where both are allowed.

    Look at

    Whether test data can be copied, shared, saved, printed or backed up into personal apps or accounts, and whether personal files can move the other way.

    Good evidence

    Every attempt fails because of the mechanism, in both directions, on each device type.

  3. Check 3 of 3What an auditor asks for

    Ask for

    The enforced settings in the management or access platform, and an attempt by the user to remove or turn off the separation.

    Look at

    Whether settings are applied centrally, and what happens when a user removes the profile, changes a setting or signs in from an unmanaged browser.

    Good evidence

    The settings are applied centrally, the user cannot turn off the separation, and removing it or using an unmanaged browser cuts access to those systems. A rule or signed agreement on its own does not pass.

Mappings

Closest match in ISO/IEC 27001: A.7.9, Security of assets off-premises, which this control partially meets.

ISO 27001

ISO/IEC 27001: 4 mappings

  • A.8.1User end point devicesPartially meets
  • A.8.12Data leakage preventionPartially meets
  • A.6.7Remote workingPartially overlaps

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