Meet Australian ISM controls with automated evidence and monitoring
The ISM (Information Security Manual) is the Australian Signals Directorate's cyber security framework, setting out principles, guidelines and controls that organisations apply using a risk-based approach to protect systems and data. ASD updates it regularly, and the June 2024 release reorganised the cyber security principles into GOVERN, IDENTIFY, PROTECT, DETECT and RESPOND groups.
Is ISM right for your organisation?
Australian Government entities use the ISM to secure their systems, as Protective Security Policy Framework requirements direct them to apply it. Cloud and service providers that want to host or process government data usually need their systems assessed against the ISM through an IRAP assessment. Other Australian organisations, including critical infrastructure operators, often adopt it voluntarily as a security baseline.
It is usually required by customers, partners or schemes rather than by law.
- Issued by
- Australian Signals Directorate (ASD), through the Australian Cyber Security Centre
- Version on this page
- June 2024 release
- Update cycle
- Revised regularly by ASD, so newer releases exist
- Applies to
- Australian Government entities and their technology suppliers
- Structure
- Cyber security principles plus 22 guideline chapters of numbered controls
- Assessment route
- IRAP assessment by an ASD-endorsed assessor
- Approach
- Risk-based, with controls applied according to system classification
- Type
- Framework (contractual)
- Region
- Australia, Asia-Pacific
- In OneClickComply
- Supported today
OneClickComply makes it simple
OneClickComply maps ISM controls to the same control set you use for ISO 27001, SOC 2 and other frameworks, so evidence collected once counts towards each. Integrations and the Companion AI browser agent gather evidence from your tools automatically, and continuous monitoring alerts you when an ISM control drifts before an IRAP assessor finds it.
Requirements covered
Cyber security principles grouped into GOVERN, IDENTIFY, PROTECT, DETECT and RESPOND, supported by 22 guideline chapters containing individually numbered ISM controls tagged by applicability level.
Manual ISM vs. OneClickComply
- Working through hundreds of ISM controls in spreadsheets to decide which apply to your system
- Chasing screenshots and exports from every tool to prove each control is in place
- Rewriting system security plans and policies every time ASD releases a new ISM version
- Finding out about configuration drift only when an IRAP assessor tests the control
- Duplicating the same evidence for ISM, ISO 27001 and customer questionnaires
- Controls are mapped in the platform, so you can see applicable ISM requirements in one place
- Evidence is collected automatically from connected tools and stored against each control
- Policies are generated from your real environment and updated as your controls change
- Continuous monitoring flags drift as it happens, so issues are fixed before assessment
- One control set covers ISM, ISO 27001 and questionnaires, so evidence is collected once
Everything you need for ISM
Map ISM controls once and reuse evidence across ISO 27001, SOC 2 and the Essential Eight
Collect ISM evidence automatically from cloud, identity and device tools
Fix supported misconfigurations with OneClickFix and log the change as evidence
Generate ISM-aligned security documentation with AutoComplete policies
Monitor controls continuously and get alerts when settings drift
Ask an Auditor for expert guidance when preparing for an IRAP assessment
Three steps to ISM compliance
Connect & scan
Connect your cloud, identity and SaaS tools. OneClickComply checks them against ISM and shows you exactly where you stand.
Fix & generate
OneClickFix remediates technical gaps in one click, and AutoComplete generates ISM-aligned policies from your real environment.
Monitor & evidence
Continuous monitoring keeps you compliant, and our in-house audit team is on hand when you need expert guidance.
Australian Information Security Manual (ISM) requirements
The cyber security principles and the 22 guideline chapters of the June 2024 ISM, which together contain the individually numbered ISM controls (for example ISM-0027).
| Reference | Requirement |
|---|---|
| Principles | Cyber security principles (GOVERN, IDENTIFY, PROTECT, DETECT, RESPOND) |
| Guidelines 1 | Guidelines for cyber security roles |
| Guidelines 2 | Guidelines for cyber security incidents |
| Guidelines 3 | Guidelines for procurement and outsourcing |
| Guidelines 4 | Guidelines for security documentation |
| Guidelines 5 | Guidelines for physical security |
| Guidelines 6 | Guidelines for personnel security |
| Guidelines 7 | Guidelines for communications infrastructure |
| Guidelines 8 | Guidelines for communications systems |
| Guidelines 9 | Guidelines for enterprise mobility |
| Guidelines 10 | Guidelines for evaluated products |
| Guidelines 11 | Guidelines for ICT equipment |
| Guidelines 12 | Guidelines for media |
| Guidelines 13 | Guidelines for system hardening |
| Guidelines 14 | Guidelines for system management |
| Guidelines 15 | Guidelines for system monitoring |
| Guidelines 16 | Guidelines for software development |
| Guidelines 17 | Guidelines for database systems |
| Guidelines 18 | Guidelines for email |
| Guidelines 19 | Guidelines for networking |
Always check the official ISM text for the exact wording.
ISM FAQs
What is the Australian ISM?
The ISM, or Information Security Manual, is a cyber security framework published by the Australian Signals Directorate. It sets out cyber security principles and detailed guidelines with numbered controls that organisations apply using a risk-based approach. Controls are tagged by the classification of the systems they apply to, from non-classified up to top secret, and ASD revises the manual regularly to reflect new threats and technology.
Who must comply with the ISM?
Australian Government entities are the main users, because the Protective Security Policy Framework directs them to apply the ISM to their systems. Private organisations are not bound by law to follow it, but cloud and service providers supplying government are commonly required by contract to have their systems assessed against the ISM through IRAP. Many other organisations adopt it voluntarily as a security baseline.
What is an IRAP assessment?
An IRAP assessment is an independent review of a system's implementation of ISM controls, carried out by an assessor endorsed by the Australian Signals Directorate under the Infosec Registered Assessors Program. Government agencies use the assessment report to understand residual risk before authorising a system or service. It is the usual route for cloud and technology providers that want to handle Australian Government data.
What changed in the June 2024 ISM?
The June 2024 ISM restructured the cyber security principles. The former GOVERN principles were split into separate GOVERN and IDENTIFY groups, separating governance from asset and risk identification, and the RESPOND principles were revised to cover incident reporting, analysis, containment and recovery. Individual controls were also added, amended or rescinded, as happens in each release, so check ASD's change summary for details.
How does the ISM relate to the Essential Eight?
The Essential Eight is a set of prioritised mitigation strategies published by the Australian Signals Directorate, and its requirements are reflected in controls within the ISM. Organisations often implement the Essential Eight first as a baseline, then apply the wider ISM for a full, risk-based security programme covering governance, personnel, physical and technical security.
How does the ISM compare with ISO 27001?
The ISM and ISO 27001 overlap heavily, since both cover governance, access control, cryptography, incident management and physical security. ISO 27001 is an international certifiable management system standard, while the ISM is a prescriptive Australian Government control framework assessed through IRAP. Mapping controls between them lets you reuse much of the same evidence for both.
How do you comply with the ISM?
Start by defining your system and its classification, then select the applicable ISM controls using a risk-based approach. Implement those controls, document them in a system security plan and supporting policies, and collect evidence that they work. Government systems are then authorised to operate, often after an IRAP assessment, and controls should be monitored and reviewed as ASD releases new versions.
Does OneClickComply support the Australian ISM?
Yes. OneClickComply supports the Australian ISM today, with controls mapped to the same control set used for ISO 27001, SOC 2 and other frameworks. The platform automates evidence collection, policy generation and continuous monitoring, and our audit team can advise on IRAP preparation. OneClickComply does not perform IRAP assessments, which must be carried out by an ASD-endorsed assessor.
Related standards
All standards- Australian Privacy PrinciplesLaw · Asia-Pacific
- Australian Privacy Act 1988Law · Asia-Pacific
- Health Information Security Framework (HISF) for Medium to Large Organisations and HospitalsFramework · Asia-Pacific
- Health Information Security Framework Guidance for SuppliersFramework · Asia-Pacific
- APEC Privacy FrameworkFramework · Asia-Pacific
- Essential EightFramework · Asia-Pacific
- Health Information Security Framework Guidance for Micro to Small OrganisationsFramework · Asia-Pacific
- New Zealand Information Security Manual (NZISM) v3.6Standard · Asia-Pacific
Get ISM ready, not stressed
Automate controls, gather evidence continuously and stay audit-ready, all on one platform.