ASD ISM 1885 Implement emanation security measures for systems
What it says
Recommended actions contained within emanation security mitigation advice issued for systems are implemented by system owners.
Quoted as published. Everything else on this page is written by Control Stack.
In plain English
System owners must implement the recommended actions in emanation security mitigation advice issued for their systems; recommended does not mean optional, and holding the advice is not enough.
System owners must implement the recommended actions contained in emanation security mitigation advice issued for their systems. This advice follows an emanation security risk assessment (ISM-1137, ISM-0249) and lists actions to reduce the risk from signals a system gives off, such as radio frequency energy, sound or light. Although the actions are called recommended, the statement requires them to be implemented, and by the system owner. It sets no deadline, so the owner sets the dates. Receiving or filing the advice does not meet this.
Free. Save your status, tasks and notes.
Why it matters
An assessment only identifies emanation risk. If its recommended actions stay undone, the system can keep giving off signals that could be intercepted and analysed, even though the organisation holds advice on how to reduce them.
How to implement
List every recommended action from the advice.
Give each action its own line, with the system it applies to, who will do it and a date. The statement sets no deadline, so the system owner sets the dates, ahead of deployment where an action affects design or installation.
Agree the work with whoever controls it.
Where an action falls to a landlord, integrator or provider, agree it in writing before changing anything. If a contract or building cannot be changed, move the equipment, choose another site or go back to ASD about an alternative.
Carry out each action and check the result.
Inspect or test what was done against the words of the advice, then record the date and who checked. A contractor's sign-off alone is not the check.
Take any action you cannot implement to the authorising officer.
Explain the risk and ask the authorising officer for that system to decide whether to accept it. Accepting the risk does not close the action, so keep it open as a shortfall until it is implemented.
Keep it running
Later changes such as new equipment, a refit or a move can undo an action, so recheck the actions after any such change and contact ASD if the basis of the advice has changed. New advice reopens the list.
Evidence and audit
- Check 1 of 3What an auditor asks for
Look at
Whether any system with advice has no action list, and whether every recommended action in the advice appears on the list with its wording intact.
Good evidence
Every recommended action in every piece of advice is on the list, with nothing dropped or softened, and each assessment in the ASD contact records has its advice accounted for.
- Check 2 of 3What an auditor asks for
Ask for
An on-site inspection or test of actions sampled from the advice itself rather than from the list.
Look at
Whether what is in place matches what the advice recommended, and whether later changes have undone it.
Good evidence
Each sampled action is in place as the advice describes, not only marked complete.
- Check 3 of 3What an auditor asks for
Ask for
Actions still open, with any risk acceptance by the authorising officer.
Look at
How many are open, why, and whether the officer for that system accepted each one.
Good evidence
Every recommended action is implemented. One still open is a shortfall until closed, even where the authorising officer has accepted the risk or a date is set, and it is not reported as met.
Mappings
Closest match in ISO/IEC 27001: A.8.27, Secure system architecture and engineering principles, which this control partially meets.
ISO/IEC 27001: 2 mappings
This control partially meets A.8.27.
ISM-1885 requires implementation of specific emanation security measures as prescribed by ASD mitigation advice for systems. ISO/IEC 27001:2022 Annex A 8.27 sets broader secure architecture and engineering principles that would include designing for side-channel/emanation resistance where relevant. ISM-1885 is therefore a specific, domain-focused application of secure engineering principles rather than a general architecture control.
This control partially overlaps A.8.12.
ISM-1885 requires system owners to implement emanation security mitigation advice to reduce the risk of information leakage via electromagnetic/physical emissions from systems. ISO/IEC 27001:2022 Annex A 8.12 relates by requiring data leakage prevention measures across systems, networks, and devices handling sensitive information, which can include controls to prevent unintended disclosure through technical channels. However, ISM-1885 is specifically focused on emanations (e.g., TEMPEST-style controls, zoning/shielding/separation) whereas Annex A 8.12 is broader and typically focuses on logical/endpoint/network DLP rather than side-channel emanation risks.
Mappings show how controls relate across frameworks. They do not imply full equivalence or certification.




