Skip to content
ISM releases
ASD ISMMarch 2026 release

March 2026 ISM changes

Everything ASD added, changed and rescinded in the March 2026 Information Security Manual, in plain English. Open any control for its full guidance.

Reviewed 15 November 2026 · Compared with the December 2025 ISM · 1,081 controls in force

At a glance

New controls
9
Added in this release
Changed
12
The requirement changed
Reworded only
5
Wording only, as ASD lists them
Rescinded
1
No longer in the ISM
In force
1,081
Up 8 on December 2025

In plain English

ASD added 9 controls, changed 12 and rescinded 1. Mobile devices and connected vehicles get new rules, and system owners now plan for resilience as well as security.

The release brings the ISM to 1,081 controls. Mobile devices keep work and personal apps and data apart, run an always-on VPN and block data transfers over USB. Three controls limit what staff do in and near connected vehicles. System owners now set resilience objectives and manage, not just monitor, cyber threats, security risks and controls. Four emanation security controls move to ASD's new terms, and five other controls are reworded only. ISM-1837, on password never expires and password not required settings, was rescinded.

Why it matters

What this release means if you assess, run or build systems against the ISM.

Review mobile device settings

Check that mobile device management keeps work and personal apps and data apart, runs an always-on VPN, blocks USB data transfers and requires password-based lock screens.

ISM-2096ISM-2097ISM-2098ISM-1888

Plan for resilience, not only security

System owners now set resilience objectives alongside security objectives, based on the impact if a system were compromised or attacked, and tailor controls to both.

ISM-1633ISM-1634

Brief staff about connected vehicles

Keep mobile devices off connected vehicles' infotainment systems. In or near a connected vehicle, do not view sensitive or classified data on a mobile device or hold sensitive or classified calls and conversations.

ISM-2099ISM-2100ISM-2101

Ask before training AI on application data

Organisational data that AI applications generate, collect or process is used to train, fine-tune or improve AI models only with its data owners' informed, explicit consent, obtained in advance.

ISM-2103

Grouped by theme. Open a control for its plain-English guidance, steps and audit checks.

Mobile and privately owned devices

4 new

Mobile devices keep organisational and personal apps and data apart, run an always-on VPN and block data transfers over USB. Staff using privately owned mobile devices or desktop computers to access OFFICIAL: Sensitive or PROTECTED systems or data cannot give unapproved AI agents access.

Connected vehicles

3 new

Mobile devices never connect to a connected vehicle's infotainment system. In or near connected vehicles, sensitive or classified data is not viewed on mobile devices, and sensitive or classified calls and conversations are not held.

Software and AI development

2 new

Existing software artefacts in the authoritative source for software are tested periodically for known weaknesses, using SAST, DAST or SCA to suit each artefact type. Organisational data that AI applications generate, collect or process is used to train, fine-tune or improve AI models only with its data owners' informed, explicit consent, obtained in advance.

What changed 12

Controls whose requirement changed. Open "Compare ASD's wording" to see the statement with removed words struck through and added words highlighted.

Emanation security terms

4 changed

Four controls use ASD's new emanation security terms.

  • ISM-0246
    Seek emanation security risk assessments as early as possible

    Now an emanation security risk assessment, not a threat assessment.

    Compare ASD's wording for ISM-0246

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

  • ISM-0249
    Contact ASD on emanation security for deployable SECRET and TOP SECRET systems

    Now an emanation security risk assessment, not a threat assessment.

    Compare ASD's wording for ISM-0249

    System owners deploying SECRET or TOP SECRET systems in mobile platforms, or as a deployable capability, contact ASD for an emanation security Removed: threat Added: risk assessment.

  • ISM-1137
    Request risk assessment for emanation security

    Now an emanation security risk assessment, not a threat assessment.

    Compare ASD's wording for ISM-1137

    System owners deploying SECRET or TOP SECRET systems within fixed facilities contact ASD for an emanation security Removed: threat Added: risk assessment.

  • ISM-1885
    Implement emanation security measures for systems

    Now refers to emanation security mitigation advice instead of TEMPEST requirements statements.

    Compare ASD's wording for ISM-1885

    Recommended actions contained within Removed: TEMPEST requirements statements Added: emanation security mitigation advice issued for systems are implemented by system owners.

System owners

3 changed

System owners now manage risks as well as monitoring them, and plan for resilience.

  • ISM-1526
    System owners continuously monitor security and manage threats, risks and controls

    System owners continuously monitor each system's security and now also manage its cyber threats, security risks and controls.

    Compare ASD's wording for ISM-1526

    System owners Added: continuously monitor Added: the security of each system, and Added: manage associated cyber threats, security risks and Removed: controls, on an ongoing basis.Added: controls.

  • ISM-1633
    Determine system boundary, criticality and security objectives

    Adds resilience objectives, based on the impact if the system were compromised or attacked.

    Compare ASD's wording for ISM-1633

    System owners, in consultation with each system's authorising officer, determine the system boundary, business Removed: criticality Added: criticality, and security Added: and resilience objectives for each system based on an assessment of the impact if it were to be Removed: compromised.Added: compromised or attacked.

  • ISM-1634
    System owners select and tailor controls in consultation with authorising officer

    Controls are tailored to resilience objectives as well as security objectives.

    Compare ASD's wording for ISM-1634

    System owners, in consultation with each system's authorising officer, select controls for each system and tailor them to achieve desired security Added: and resilience objectives.

Mobile devices and desktop computers

2 changed

Internet access through the gateway no longer names a VPN, and mobile lock screens must be password-based.

  • ISM-0874
    Ensure internet access via organisation's gateway

    Mobile devices and desktop computers still reach the internet through the organisation's gateway, but the control no longer names a VPN connection, so other technical solutions can meet it. Mobile devices still need always-on VPN functionality under the new ISM-2097.

    Compare ASD's wording for ISM-0874

    Mobile devices and desktop computers access the internet via Removed: a VPN connection to an organisation's internet gateway rather than via a direct connection to the internet.

  • ISM-1888
    Ensure mobile devices have secure lock screens

    Lock screens must be password-based.

    Compare ASD's wording for ISM-1888

    Mobile devices are configured with secure Added: password-based lock screens.

Software artefacts

2 changed

Testing now covers every software artefact, using the method that suits it, and scanning looks for malicious content, not only malicious code.

  • ISM-2026
    Scan software artefacts for malicious content

    Scanning now looks for malicious content, not only malicious code.

    Compare ASD's wording for ISM-2026

    All software artefacts are scanned for malicious Removed: code Added: content before being imported into the authoritative source for Removed: software, including all compiled code, third-party libraries and software components.Added: software.

  • ISM-2028
    Test software artefacts for security weaknesses

    Covers all software artefacts, not only third-party ones, and uses SAST, DAST or SCA to suit each artefact type rather than all three. Periodic retesting moved to the new ISM-2102.

    Compare ASD's wording for ISM-2028

    All Removed: imported or referenced third-party software artefacts are tested Added: to detect known weaknesses using static application security testing (SAST), dynamic application security testing (DAST) Removed: and Added: or software composition analysis Removed: (SCA) Added: (SCA), depending on the software artefact type, before being imported into the authoritative source for Removed: software and periodically throughout the software development life cycle.Added: software.

Post-quantum cryptography

1 changed

When ML-DSA and ML-KEM are used, the preferred prerequisite is now FIPS 140-3 validation.

  • ISM-1990
    Prefer FIPS 140-3 validated ML-DSA and ML-KEM implementations

    Now prefers FIPS 140-3 validation, instead of adherence to prerequisite FIPS publications.

    Compare ASD's wording for ISM-1990

    When using ML-DSA and ML-KEM, as per FIPS 204 and FIPS 203 respectively, adherence to pre-requisite FIPS Removed: publications Added: 140-3 validation is preferred.

Reworded only 5

Changes ASD lists as wording only, keeping each control's intent. Check any policy or plan that quotes these controls, and compare the wording wherever it is shown.

Authorisation to operate, reworded for clarity2
  • ISM-0027
    Mandatory authorisation for system operation

    System owners obtain Added: an authorisation to operate Added: for each non-classified, OFFICIAL: Sensitive, PROTECTED and SECRET system from its authorising Removed: officer based on the acceptance of the security risks associated with its operation.Added: officer.

  • ISM-1968
    Obtain authorisation for TOP SECRET systems

    System owners obtain Added: an authorisation to operate Added: for each TOP SECRET system, including Added: for each sensitive compartmented information system, from Director-General ASD (or their Removed: delegate) based on the acceptance of the security risks associated with its operation.Added: delegate).

Device data separation and storage controls, reworded for consistency3
  • ISM-1400
    Enforce data separation on personal devices

    Personnel Removed: accessing OFFICIAL: Sensitive or PROTECTED systems or data using privately-owned mobile devices or desktop computers Added: to access OFFICIAL: Sensitive or PROTECTED systems or data have enforced separation of classified data Removed: from Added: and personal data.

  • ISM-1482
    Ensure separation of classified and personal data on devices

    Personnel Removed: accessing systems or data using Removed: an organisation-owned mobile Removed: device Added: devices or desktop Removed: computer Added: computers to access classified systems or data have enforced separation of classified data Removed: from Added: and personal data.

  • ISM-1866
    Prevent storing classified data on privately owned devices

    Personnel Removed: accessing OFFICIAL: Sensitive or PROTECTED systems or data using privately-owned mobile devices or desktop computers Added: to access OFFICIAL: Sensitive or PROTECTED systems or data are prevented from storing classified data on their privately-owned mobile devices and desktop computers.

Rescinded 1

No longer part of the ISM. Each keeps its page, marked as rescinded, for anyone still working to an earlier release.

Other releases

All ISM releases

Source: ASD's Information Security Manual, March 2026, compared control by control with the December 2025 release. Control statements are quoted as published. Everything else on this page is written by Control Stack.