Skip to content
Data transfers
ASD ISMISM-1187

ASD ISM 1187 Check data for improper markings before export

What it says

When manually exporting data from systems, the data is checked for unsuitable protective markings.

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

In plain English

During any manual export, check the data for protective markings that show it must not go to its destination, such as a classification the destination is not authorised for.

When manually exporting data from any system, such as by copying it to removable media, the data must be checked for unsuitable protective markings before it leaves. A protective marking is the label showing data's classification or sensitivity and any caveats on its handling. Unsuitable means the marking shows the data must not go to its destination, such as a classification above what the destination is authorised for. Data that fails is quarantined (ISM-1779). Exports through gateways or cross domain solutions are outside this control.

Why it matters

Exporting data with a marking the destination cannot accept, such as a classification above what that system may hold, is a data spill: the data lands somewhere not protected to its level. Checking markings during export lets this be stopped before the data leaves.

How to implement

  1. Record what each destination may receive.

    For every system or party that data is manually exported to, note the highest classification and the caveats it is authorised for, so whoever checks knows which markings are unsuitable.

  2. Build the check into the export procedure.

    Write it into the data transfer procedures (ISM-0663), and keep manual exports to points where it is done; ISM-0343 already requires writing to removable media to be disabled where there is no business need.

  3. Check every file's markings before it is copied out.

    Look at headers, footers, document properties and email markings, and inside archives and embedded files. A tool that searches for marking text helps with volume; have a person check anything it cannot read, such as scanned images.

  4. Hold back data with an unsuitable marking.

    Do not export it; quarantine it for review under ISM-1779. Changing the marking so the data passes is a reclassification, a separate administrative decision, not an edit made at the point of export.

Keep it running

Update the destination rules when a destination's authorisation changes or a new caveat comes into use. If a spill is traced to a manual export, advise the data owners and restrict access to the data (ISM-0133), then find out why the check missed the marking.

Evidence and audit

  1. Check 1 of 3What an auditor asks for

    Ask for

    Records of manual exports for a recent period from the data transfer logs (ISM-1586), compared with the removable media register and device access control events.

    Look at

    Whether every manual export found in any of these records has a marking check recorded before the data left, and what happened when one failed.

    Good evidence

    Every manual export found in any of the records had its markings checked before release, and where an unsuitable marking was found, none went ahead without the review and approval ISM-1779 requires.

  2. Check 2 of 3What an auditor asks for

    Ask for

    A walk-through of a manual export using harmless test files marked above what the destination may hold, with one marking only in the document properties and one file inside an archive.

    Look at

    Whether the check finds each unsuitable marking and what then happens to the files.

    Good evidence

    The check finds every unsuitable marking, including the hidden ones, and the files are quarantined rather than exported or relabelled.

  3. Check 3 of 3What an auditor asks for

    Ask for

    The destination rules used for the check, compared with each destination system's authorisation.

    Look at

    Whether the rules match the classification and caveats each destination is authorised to hold.

    Good evidence

    The rules for each destination match its authorisation, so no marking above what it may hold is treated as suitable.

Mappings

Closest match in ISO/IEC 27001: A.5.10, Acceptable use of information and other associated assets, which this control partially meets.

ISO 27001

ISO/IEC 27001: 2 mappings

  • A.8.12Data leakage preventionPartially overlaps

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