Skip to content
Communications infrastructure
ASD ISMISM-0246

ASD ISM 0246 Seek emanation security risk assessments as early as possible

What it says

When an emanation security risk assessment is required, it is sought as early as possible in a system's life cycle.

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

In plain English

Whenever an emanation security risk assessment is required, seek it as early as possible in the system's life cycle, rather than once the design is settled.

When an emanation security risk assessment is required, it must be sought as early as possible in the system's life cycle. ISM-1137 and ISM-0249 say which system owners must contact ASD for one. Such an assessment looks at the risk from signals a system gives off, such as radio frequency energy, sound or light. The life cycle runs from first proposing a system through design, build, operation and disposal. The statement names no date or stage, so early is judged from when the system's plans first showed the need.

Why it matters

Changing a system after it has been designed and built takes longer and costs far more than changing a plan. An assessment sought early lets its advice shape the design, site and equipment, rather than forcing rework later.

How to implement

  1. Work out at the start of every new system whether an assessment is needed.

    In the system proposal or project start form, ask whether the system will fall under ISM-1137 or ISM-0249, and repeat the question when its site, platform or classification changes.

  2. Seek the assessment as soon as the need is known.

    Do not wait for a finished design. Send ASD what is known, such as the intended classification, site or platform and equipment types, and update ASD as details firm up.

  3. Hold back decisions the advice could change.

    Where you can, leave the final design, site fit-out and equipment purchase open until the advice arrives. For a bought service or hosted site, seek the assessment before signing, while terms can still change.

  4. Seek the assessment now if the system is already past design.

    Send the request straight away rather than waiting for a later milestone, and record when the need became known and why it was not raised sooner, so the same delay is not repeated.

Keep it running

Keep the question in whatever process starts a new system. A change of site, platform or intended classification can create a new need for an assessment, so seek one as soon as that change is proposed.

Evidence and audit

  1. Check 1 of 2What an auditor asks for

    Ask for

    The dated assessment request for each system that needed one, with that system's proposal, design approval, site selection and equipment purchase dates.

    Look at

    The order of those dates, and the first date the project's own papers show the need.

    Good evidence

    Each request was sent with no unexplained gap after the first date the system's plans showed the need, and before design approval, site selection and equipment purchase. A later request passes only if project records show why it could not have been sought sooner, such as a later change of site or classification.

  2. Check 2 of 2What an auditor asks for

    Ask for

    Systems now being proposed or designed that ISM-1137 or ISM-0249 will cover, taken from the register of systems (ISM-1966) and project plans, with any requests sent.

    Look at

    Whether each has already sought an assessment or is waiting for a later stage.

    Good evidence

    Every such system already has its request with ASD, and none is waiting for a finished design, a signed contract or deployment.

Mappings

Closest match in ISO/IEC 27001: A.8.27, Secure system architecture and engineering principles, which this control supports.

ISO 27001

ISO/IEC 27001: 1 mapping

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