Skip to content
Communications infrastructure
ASD ISMISM-0249

ASD ISM 0249 Contact ASD on emanation security for deployable SECRET and TOP SECRET systems

What it says

System owners deploying SECRET or TOP SECRET systems in mobile platforms, or as a deployable capability, 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 in a mobile platform or as a deployable capability.

System owners deploying SECRET or TOP SECRET systems in mobile platforms, or as a deployable capability, must contact ASD for an emanation security risk assessment. Either condition is enough. A mobile platform carries the system as it moves, such as a vehicle, ship or aircraft. A deployable capability is moved and set up for a period at different places. Emanations are signals a system gives off, such as radio frequency energy, sound or light, which could be intercepted and analysed. ISM-1137 covers fixed facilities, and ISM-0246 sets how early.

Why it matters

A system on a mobile platform or set up in the field cannot rely on one known, controlled building around it, and its signals could be intercepted and analysed. Contacting ASD gets that risk assessed for how and where the system will be used.

How to implement

  1. Find every SECRET or TOP SECRET system that moves or gets deployed.

    Check the register of systems (ISM-1966), project plans and asset records for vehicles, vessels, aircraft and transportable kit. If you are unsure whether a system counts, ask ASD. One that also runs from a fixed facility falls under ISM-1137 too.

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

    Use ASD's published emanation security contact. Describe the platform or kit, its classification, its equipment and where and how it will be used. A project team can prepare this, but the system owner makes the contact. Where an integrator builds it, request equipment 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

A new platform type, a new kind of location or a change of equipment should trigger a fresh contact with ASD. When deployment plans change, compare them with what the assessment was based on.

Evidence and audit

  1. Check 1 of 2What an auditor asks for

    Ask for

    The register of systems (ISM-1966) and asset records for vehicles, vessels, aircraft and transportable kit, compared with records of contact with ASD.

    Look at

    Whether each SECRET or TOP SECRET system on a mobile platform or used as a deployable capability, including any found only in asset records, has its own contact record.

    Good evidence

    Every SECRET or TOP SECRET system on a mobile platform or used as a deployable capability, 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 and ASD's reply, with a description of how the system is really used.

    Look at

    Whether the request describes that platform or deployable use, and who made it.

    Good evidence

    The request seeks an emanation security risk assessment for that system as it is really used, comes from its system owner, and ASD's reply shows it was received. A request describing only a fixed 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: 1 mapping

  • A.5.5Contact with authoritiesPartially meets

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