Skip to content
Mappings
Essential EightASD ISM

Essential Eight to ASD ISM

Every Essential Eight requirement, across all maturity levels, with the ASD ISM controls that implement the same mitigation. Both frameworks come from ASD, so the relationships here are unusually direct.

Essential Eight controls mapped (100%)
152 of 152
Control-to-control relationships
1,218
Distinct ASD ISM controls reached
318 of 1,143

152 of the 152 Essential Eight controls (100%) have at least one ASD ISM counterpart, giving 1,218 control-to-control relationships across 318 distinct ASD ISM controls. Coverage runs one way: nearly every Essential Eight requirement has ISM controls behind it, while most of the ISM sits outside the Essential Eight entirely.

These relationships are generated from the Control Stack catalogue and reviewed for topic fidelity, then labelled with how the two controls relate rather than asserted as equivalent. Where no counterpart exists, the row says so plainly instead of stretching for a match. Some rows are read from the other framework’s own mappings, so the wording of those summaries leads with that side.

Control Stack is a free Australian reference covering 1,484 cyber security controls: all 1,143 ASD ISM controls, 152 Essential Eight controls across three maturity levels, all 93 ISO/IEC 27001:2022 Annex A controls, 58 ASD Essentials for enterprise IT actions and all 38 ISO/IEC 42001:2023 Annex A controls. Every one of them is cross-mapped between the five frameworks and readable in full without an account.

Reviewed 16 September 2026 · Maps the ASD Essential Eight Maturity Model to the September 2026 ASD ISM

Control by control

What the labels mean

One card per Essential Eight control, grouped by strategy, with every ASD ISM control mapped to it, strongest relationship first.

Showing all 152 Essential Eight controls

Application control

19 controls, 19 mapped

Patch applications

14 controls, 14 mapped

E8-PA-ML1.1ML17 ASD ISM controls

Automated asset discovery at least fortnightly

E8-PA-ML1.9ML19 ASD ISM controls

Removal of unsupported software and applications

Configure macro settings

11 controls, 11 mapped

E8-RM-ML1.2ML18 ASD ISM controls

Block Microsoft Office macros from the internet

User application hardening

27 controls, 27 mapped

E8-AH-ML1.1ML18 ASD ISM controls

Disable or remove Internet Explorer 11

Restrict admin privileges

29 controls, 29 mapped

E8-RA-ML2.6ML214 ASD ISM controls

Privileged access events are centrally logged

E8-RA-ML2.11ML211 ASD ISM controls

Report cyber incidents to the CISO promptly

Patch operating systems

17 controls, 17 mapped

E8-PO-ML1.8ML19 ASD ISM controls

Replace unsupported operating systems

E8-PO-ML3.5ML38 ASD ISM controls

Apply critical driver patches within 48 hours

E8-PO-ML3.7ML37 ASD ISM controls

Apply critical firmware patches within 48 hours

Multi-factor authentication

24 controls, 24 mapped

E8-MF-ML2.7ML26 ASD ISM controls

Protect event logs from unauthorised changes

Regular backups

11 controls, 11 mapped

E8-RB-ML1.1ML17 ASD ISM controls

Backups aligned with business continuity needs

E8-RB-ML1.3ML18 ASD ISM controls

Backups retained securely and resiliently

How to use this mapping

Read it in whichever direction you are being assessed. If Essential Eight is your primary framework, use the cards to find the ASD ISM controls that cover the same ground, so evidence you already hold can be reused instead of rebuilt. If ASD ISM is what you are being held to, search for a ASD ISM ID to see which Essential Eight controls contribute. A mapping means the two controls address related risk, not that satisfying one satisfies the other, so always read the relationship label before relying on it.

What the relationship labels mean

Read each row as the Essential Eight control, then the label, then the ASD ISM control.

Equivalent
Both controls ask for the same thing. Rare, and kept for genuinely matching requirements. 161 pairings on this page
Broader than
The source control covers everything the mapped control asks for, and more. 57 pairings on this page
Partially meets
The source control covers part of what the mapped control asks for. 159 pairings on this page
Partially overlaps
The two share ground, but neither contains the other. 456 pairings on this page
Supports
The source control helps achieve the mapped control. 148 pairings on this page
Depends on
The source control relies on the mapped control being in place. 237 pairings on this page

Frequently asked questions

How do the Essential Eight and the ASD ISM relate?

Both are published by the Australian Signals Directorate. The Essential Eight is a prioritised set of eight mitigation strategies drawn from ASD’s Strategies to Mitigate Cyber Security Incidents, and the ISM carries controls that implement those strategies in detail. This mapping shows which ISM controls sit behind each Essential Eight requirement.

If I reach Maturity Level Two, how much of the ISM have I covered?

A small share. The Essential Eight concentrates on eight technical areas, mostly patching, application control, macros, hardening, administrative privileges, multi-factor authentication and backups. The ISM spans governance, personnel security, physical security, cryptography, gateways, software development and data transfers as well, so most ISM controls have no Essential Eight counterpart at all.

Why are Essential Eight controls numbered by maturity level?

Control Stack renders the Essential Eight Maturity Model as separate, testable controls, one per requirement per level, using keys such as E8-AC-ML2.3. That makes each requirement individually trackable and lets a mapping point at the exact maturity level a given ISM control supports, rather than at a whole strategy.

Is this mapping official?

No. ASD does not publish a control-level crosswalk between the Essential Eight Maturity Model and the ISM. This mapping is produced by Control Stack from the control text of both and reviewed for topic fidelity. Use it for planning and evidence reuse rather than as an authoritative statement from ASD.