Skip to content
Data transfers
ASD ISMISM-1535

ASD ISM 1535 Prevent unsuitable foreign data exports

What it says

Processes, and supporting procedures, are developed, implemented and maintained to prevent AUSTEO, AGAO and REL data in textual and non-textual formats from being exported to unsuitable foreign systems.

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

What it means

In plain English

Ensure processes are in place to block export of sensitive data to foreign systems.

This control ensures that sensitive Australian data doesn't end up in the wrong hands overseas. If we don't have good processes to stop this, our confidential information could be misused, leading to serious security risks and trust issues both domestically and internationally.

Why it matters

Exporting AUSTEO, AGAO or REL data to unsuitable foreign systems can expose classified information, harm national security, and damage partner trust.

How to implement

  1. System owners should identify where sensitive data is stored and accessed within their organisation.

    They can map out information flows using simple diagrams and mark areas where data might be transferred internationally. This helps pinpoint potential vulnerabilities.

  2. IT teams should set up systems to block unauthorised data exports.

    They can configure network settings to prevent data from being sent to select international locations or use secure transfer tools that have built-in restrictions.

  3. Managers need to train staff on data handling policies about foreign transfers.

    They can organise regular workshops with clear examples of what's allowed and what isn't, ensuring staff know the importance of compliance.

  4. Procurement teams should vet vendors for their data handling capabilities.

    They can ask vendors to commit to Australian data protection standards and check their track record in handling sensitive information.

  5. The organisation's legal advisor should regularly review data transfer policies.

    They should ensure these policies align with both Australian laws and the laws of countries where data might be accessed, updating them as needed.

Keep it running

Implement export checks to block AUSTEO/AGAO/REL data from transfer to foreign services not approved; monitor egress and review exceptions regularly.

Evidence and audit

  1. Check 1 of 5What an auditor asks for

    Ask for

    The data export policy document: Request the organisation's documented policy on data transfers to foreign systems.

    Look at

    The sections detailing restrictions on foreign transfers.

    Good evidence

    Includes clear instructions on what data cannot be exported and the consequences for non-compliance.

  2. Check 2 of 5What an auditor asks for

    Ask for

    Training records: Request records of staff training sessions related to data transfer.

    Look at

    Attendance lists and training content.

    Good evidence

    Shows regular, comprehensive training is provided to all relevant staff.

  3. Check 3 of 5What an auditor asks for

    Ask for

    System configurations: Request documentation on network or system configurations that prevent unauthorised exports.

    Look at

    Technical details demonstrating export restrictions.

    Good evidence

    Shows concrete evidence of systems blocking unwanted data leaks.

  4. Check 4 of 5What an auditor asks for

    Ask for

    Vendor agreements: Request contracts or agreements with third-party vendors.

    Look at

    Clauses related to data handling and export permissions.

    Good evidence

    Includes vendor agreements explicitly committing to Australian standards.

  5. Check 5 of 5What an auditor asks for

    Ask for

    Legal review summaries: Request summaries of legal reviews on data transfer policies.

    Look at

    The frequency and outcomes of these reviews.

    Good evidence

    Includes regular reviews resulting in policy updates reflecting current laws and risks.

Mappings

Closest match in ISO/IEC 27001: A.5.14, Information transfer policies and procedures, which this control partially meets.

ISO 27001

ISO/IEC 27001: 3 mappings

  • A.8.12Data leakage prevention measuresPartially overlaps
  • A.5.13Labelling of informationDepends on

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