Skip to content
Enterprise mobility
ASD ISMISM-1866

ASD ISM 1866 Prevent storing classified data on privately owned devices

What it says

Personnel using privately owned mobile devices or desktop computers to access OFFICIAL: Sensitive or PROTECTED systems or data are prevented from storing classified data on their privately owned mobile devices and desktop computers.

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 be technically unable to store classified data on them.

Personnel using privately owned mobile devices or desktop computers to access OFFICIAL: Sensitive or PROTECTED systems or data must be prevented from storing classified data on those devices. Prevented means the setup stops it happening, so telling people not to save files does not qualify. Storing includes downloads, synced files, offline email and app caches, even when encrypted or inside a managed work profile. ISM-1400 separately requires classified data and personal data to be kept apart.

Why it matters

Classified data stored on a personal device stays there when the device is lost, sold or repaired, or when its owner leaves the organisation. Keeping it off the device means those events cannot expose what was never stored.

How to implement

  1. Serve these systems through a remote session.

    Give privately owned devices a virtual desktop or published app, so data stays on the organisation's systems and only the display reaches the device. A browser session needs the controls below as well. Where only a native app exists, confirm it can run without saving data locally, or do not offer it.

  2. Turn off every way of saving locally.

    In the session or app policy, block downloads, save-as, print to file, clipboard and drive redirection, offline mode, file sync and opening attachments in local apps. Block screen capture where the platform allows it.

  3. Find and clear what sessions leave behind.

    Turn off local caching in the session client and browser where settings allow, and clear remaining session data at sign-out. Inspect a test device's download folders, app data and browser cache to see what is actually left, including after a session closed without signing out.

  4. Refuse access from any route that can store data locally.

    Set the identity platform or remote access gateway to block these systems from privately owned devices on such routes, including native email and file sync clients. For a bought cloud service, use its session or app settings. If it cannot stop local saving, do not offer it on these devices.

Keep it running

Retest after any change to the session client, app version or access policy, because an update can add offline or sync features. A new system or app offered to these devices should trigger the same test first.

Evidence and audit

  1. Check 1 of 3What an auditor asks for

    Ask for

    A search of a test privately owned device of each type allowed, after a normal working session with marked test data and after a session closed without signing out.

    Look at

    Download folders, app data, browser cache, mail stores and sync folders, searched for the marked test data.

    Good evidence

    The search finds none of the test data on any of the devices after either session.

  2. Check 2 of 3What an auditor asks for

    Ask for

    Attempts on those same devices to download, save, sync, print to file and open an attachment locally.

    Look at

    Whether each attempt is technically blocked, rather than only warned against, and whether a different app or browser gets round it.

    Good evidence

    Every attempt fails with a technical block, whichever app or browser is used. A warning or a rule the user could ignore does not pass.

  3. Check 3 of 3What an auditor asks for

    Ask for

    Sign-in logs for those systems, compared with the allowed access paths.

    Look at

    Whether the logs can identify privately owned devices, and whether any used a native app, sync client or other path that can store data locally.

    Good evidence

    The logs identify privately owned devices, and none used a path that can store data locally.

Mappings

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

ISO 27001

ISO/IEC 27001: 6 mappings

  • A.6.7Remote workingPartially meets
  • A.7.10Storage mediaPartially meets
  • A.8.1User end point devicesPartially meets
  • A.8.12Data leakage preventionPartially meets
  • A.5.14Information transferPartially overlaps
  • A.8.3Information access restrictionPartially overlaps

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