Skip to content
Communications infrastructure
ASD ISMISM-1137

ASD ISM 1137 Request risk assessment for emanation security

What it says

System owners deploying SECRET or TOP SECRET systems within fixed facilities contact ASD for an emanation security risk assessment.

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

In plain English

A system owner must contact ASD for an emanation security risk assessment when deploying a SECRET or TOP SECRET system within a fixed facility.

System owners deploying SECRET or TOP SECRET systems within fixed facilities must contact ASD for an emanation security risk assessment. Emanations are signals a system gives off, such as radio frequency energy, sound or light, which could be intercepted and analysed. A fixed facility is a permanent site, such as a building, in Australia or overseas. The duty here is to make contact and seek the assessment. ISM-0246 sets how early, ISM-0249 covers mobile platforms and deployable capabilities, and ISM-1885 requires the resulting recommended actions to be implemented.

Why it matters

A SECRET or TOP SECRET system in a fixed facility can give off signals that could be intercepted and analysed. Contacting ASD gets that risk assessed for the actual system and site, and gives the owner advice on reducing it.

How to implement

  1. Find every SECRET or TOP SECRET system in or bound for a fixed facility.

    Check the register of systems (ISM-1966) and project plans, including systems still being proposed. Note the site and the designated system owner (ISM-1071). Treat mobile and deployable systems under ISM-0249.

  2. Contact ASD as early as possible in the system's life cycle (ISM-0246).

    Use ASD's published emanation security contact. Give the system, its classification, the facility and what is known of the equipment. A project team can prepare this, but the system owner makes the contact. Where a provider hosts the system, request site details and send them later.

  3. Keep the request and follow it through.

    Store the dated request and ASD's reply with the system's records, and chase any request left unanswered. When the assessment ends, ISM-1885 requires the recommended actions in its advice to be implemented.

Keep it running

Keep the contact record with the system's records. A move to another fixed facility, a change of classification to SECRET or TOP SECRET, or a major equipment change should trigger a fresh contact with ASD.

Evidence and audit

  1. Check 1 of 2What an auditor asks for

    Ask for

    The register of systems (ISM-1966) and deployment or project records, compared with records of contact with ASD.

    Look at

    Whether each SECRET or TOP SECRET system in a fixed facility, including any that appear only in project records, has its own contact record.

    Good evidence

    Every SECRET or TOP SECRET system deployed or being deployed in a fixed facility, on either list, has a dated record of contact with ASD for an emanation security risk assessment.

  2. Check 2 of 2What an auditor asks for

    Ask for

    A sampled request with any details sent later, and ASD's reply.

    Look at

    What was asked for, which system and site it names, and who made the request.

    Good evidence

    The request seeks an emanation security risk assessment for that system at that facility, comes from its system owner, and ASD's reply shows it was received. A general enquiry or a request for another site does not count.

Mappings

Closest match in ISO/IEC 27001: A.5.5, Contact with authorities, which this control partially meets.

ISO 27001

ISO/IEC 27001: 3 mappings

  • A.5.5Contact with authoritiesPartially meets
  • A.7.1Physical security perimetersPartially overlaps
  • A.7.6Working in secure areasPartially overlaps

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