The ACSC ISM: how the manual is structured and how to comply
The Information Security Manual is the Australian Government’s detailed control catalogue for protecting systems and data. It underpins IRAP assessments, cloud authorisations and the security plans of every Commonwealth system. This guide explains how it is organised, who it applies to and how to run an ISM programme without drowning in controls.
Where the Essential Eight is eight strategies, the ISM is the full catalogue: hundreds of controls grouped into guidelines that follow the life of a system, from roles and incident management through physical security, personnel, hardening, monitoring, software development, databases, email, networking, cryptography, gateways and data transfers.
Every control carries an identifier, a revision number, the classifications it applies to and whether it is a “must” or “should”. Because the manual changes every quarter, an ISM programme is as much about tracking what changed as about implementing controls.
What an ISM programme has to produce
A system boundary and classification
The ISM is applied per system. You define what the system is, what data it handles and at which classification, and the applicable control set follows from that.
A statement of applicability
For every applicable control: implemented, alternative control, not applicable with justification, or not implemented with risk accepted. Assessors read this first.
A system security plan and plan of action
The SSP describes how each control is met. Gaps go into a plan of action with owners and dates, and the authorising officer accepts the residual risk.
Evidence for each control
Configuration exports, policies, logs, test results and screenshots that an IRAP assessor can trace to a control identifier.
Change tracking against the quarterly release
Each ACSC release adds, amends and withdraws controls. Your SoA and SSP must be reconciled to the current version before an assessment.
Who it applies to
Non-corporate Commonwealth entities apply the ISM to their systems under the PSPF. Cloud and managed service providers that want to host government data undergo IRAP assessment against it. State and territory agencies, Defence industry (DISP) members, critical infrastructure operators and health and education bodies adopt it either by policy or because their government customers require it.
From scope to evidence, in one system
The ISM as a native framework
GRCorb carries the ISM control set with identifiers, applicability by classification and must/should designations, so your statement of applicability is generated from a scoped control list rather than typed into a spreadsheet.
One piece of evidence, several frameworks
The unified crosswalk maps ISM controls to ISO 27001 and the Essential Eight. Evidence collected once from Entra ID, Intune, Defender, AWS or Azure counts toward all three, and the product tells you where a mapping is domain-level rather than clause-level.
Policies written to the ISM
The AI Policy Builder produces the policy set the ISM expects, scoped to your classification and systems, versioned and ready for acknowledgement tracking.
Assessor-ready exports
Control-by-control status with linked evidence, the SoA and the plan of action export as branded documents for an IRAP assessor or an authorising officer.
Frequently asked questions
ISM or Essential Eight: which do we need?
Both, usually. The Essential Eight is a mandated baseline of eight strategies; the ISM is the full catalogue those strategies sit inside. Government entities need the full ISM for their systems; most private organisations start with the Essential Eight and adopt ISM guidelines as customers require.
Do we need an IRAP assessment?
Only if you are seeking government authorisation to hold or process government data, typically as a cloud or managed service provider. Internal government systems are assessed by IRAP assessors too, but a private company using the ISM for its own improvement can self-assess.
How do we keep up with quarterly changes?
Treat each release as a change event: diff the control list, update applicability, reassess affected controls. GRCorb tracks the framework version in scope so changed controls are flagged for review rather than silently drifting.
How does the ISM relate to ISO 27001?
ISO 27001 is a management-system standard with 93 controls in Annex A; the ISM is a prescriptive government catalogue. Many controls overlap and an ISO-certified organisation has a head start, but ISM assessors expect the specific ISM controls, not an ISO certificate.
Related frameworks
Reviewed November 2026. This guide is general information about the published framework and is not legal advice; always check the current official text from the publisher before relying on it.