RemoteASD ISM guide
The ISM in plain English: what changed in September 2026, and whether it applies to you.
ASD published the September 2026 Information Security Manual on 7 September. It has 44 new controls, and two of them are about how your IT provider is allowed to connect to your systems. Most businesses are not legally required to follow the ISM, but the new controls are some of the most practical ASD has written for anyone running Microsoft 365.
Counts checked against ASD's ISM catalogue on 30 October 2026.
- 49 principles, 1,143 controls
- 44 new controls
- All 44 apply to non-classified systems
Reviewed by Blake Bath, General Manager, on 30 October 2026.
Does the ISM apply to you?
Four questions before you read 1,143 controls.
The ISM is a framework, not a law. Whether you need it depends on who you work for and what information you hold.
Does a law or direction require it?
ASD says an organisation is not required by law to comply with the ISM unless legislation, a direction under legislation or another lawful authority compels it. The ISM also does not override any law.
- Not a legal requirement on its own
- Law wins if the two conflict
- Privacy and SOCI obligations still apply separately
Does a contract name it?
Government agencies and their suppliers are where the ISM usually turns up, written into a contract or security schedule. If a contract names a release or baseline, that is what you meet.
- Read the security schedule first
- Note which ISM release it names
- Ask which classification applies
What information does the system hold?
Every control carries applicability markings: NC for non-classified, OS for OFFICIAL: Sensitive, P for PROTECTED, S for SECRET and TS for TOP SECRET. You select controls for the classification the system handles.
- 1,017 of 1,143 controls apply to NC
- Higher classifications add controls
- Supplying government does not make you PROTECTED
Do you just want a strong framework?
For most small businesses, the ASD Essentials and SMB1001 are the practical starting point. The ISM is the deep reference behind them, and worth mining for specific controls.
- Start with the ASD Essentials
- Certify with SMB1001 if clients ask
- Use ISM controls where they fit
New controls self-check
How many of the September 2026 controls do you already meet?
Ten of the 44 new controls that matter most for a small or mid-sized business. Tick what is true today and copy the gaps for your IT provider.
Ten of the 44 new controls from the September 2026 ISM. Tick what is true at your business today.
Where you stand
0of 10 controls in place
10 gaps to close.
- Your MSP can only connect through tools, addresses and times you approvedNew in September 2026. Service provider access is limited to approved remote tools, source addresses and time windows.
- You keep your own log of your MSP's access, which they cannot changeThe log has to be yours and analysed in a timely way, not a report your provider sends you.
- You have a list of approved remote access and RMM tools, and others are blockedAttackers use legitimate remote support tools. Unapproved ones should be blocked at the gateway.
- Bank detail and account changes are confirmed through a known channelA voice or video request can now be faked. Confirm on a number or channel you already trust.
- Staff cannot approve third-party apps into Microsoft 365 or GoogleOnly an admin grants app consent, and consents are reviewed at least every six months.
- Device code sign-in is blocked unless you need itDevice code phishing tricks people into signing an attacker in on a real Microsoft page.
- Sessions and tokens are revoked when a password is reset or an account is suspectedResetting a password does not help if the attacker's session stays alive.
- Backups cannot be changed or deleted during their retention periodImmutable backups, on infrastructure separated from production with separate admin sign-in.
- You keep a register of AI agents with their own identitiesEach agent gets its own identity, owner, purpose and a record of what it can access.
- Network gear is managed only from a separate management networkManagement interfaces should not be reachable from the user network or the internet.
What changed in September 2026
The 44 new controls, by topic.
We compared ASD's machine-readable ISM catalogues for June 2026 (v2026.06.18) and September 2026 (v2026.09.4). These are the control IDs that are new. Two June controls, ISM-0521 on IPv6 and ISM-1448 on TLS configuration, are no longer listed.
| Topic | New controls | What it asks |
|---|---|---|
| Access by service providers | 2 | MSP access limited to approved tools, addresses and times, and logged by you |
| Administrative tools | 2 | A list of approved RMM and remote access tools; others blocked at the gateway |
| Synthetic impersonation | 1 | Confirm account, bank detail and payment requests through a trusted channel |
| Third-party apps and device code sign-in | 4 | Admin-only app consent, six-monthly consent reviews, logging, device code flow off |
| Tokens and sessions | 2 | Tokens bound to the device; sessions revoked on reset or compromise |
| Application and workload credentials | 6 | Short-lived, unique, centrally managed secrets, changed and revoked properly |
| Authentication | 1 | Risk-based access decisions using contextual signals |
| AI agents | 7 | Unique agent identities, an agent register, least privilege, untrusted content handling, logging |
| Backups | 2 | Immutable for the retention period; backup systems segregated with separate admin sign-in |
| Threat hunting | 1 | Threat hunting informed by threat intelligence at least every three months |
| Windows hardening | 3 | Signed drivers enforced, kernel code limited, WMI activity logged centrally |
| Active Directory Certificate Services | 3 | Web enrolment locked down, templates reviewed every three months, events logged |
| Network devices | 3 | Separate management network, firmware integrity, unneeded features off |
| MACsec | 5 | Settings for wired network encryption where MACsec is used |
| Software development | 2 | Pinned dependencies and reproducible builds |
Counts from ASD's ISM OSCAL catalogues, compared on 30 October 2026. ASD also publishes a change summary PDF with the September release.
Our view
Two of the new controls are about us, and we think they are right.
ISM-2124 says a service provider's access is restricted to remote management tools, source network addresses and time windows the organisation has explicitly approved. ISM-2125 says all of that access is logged by the organisation, in a way the provider cannot change or delete, and analysed quickly.
For an MSP, that is a fair standard. Your provider holds some of the most powerful access in your business. You should know which tools they use, be able to see every session, and own the log. ISM-2149 and ISM-2150 go with them: keep a list of approved RMM and remote access tools, and block the rest at the gateway, because attackers like to use legitimate remote support software.
If you use an MSP, ask them three things: which remote tools they use on your systems, where their connections come from, and where you can see a log of their access that they cannot edit. That includes asking us.
Identity controls
The identity controls you can switch on in Microsoft 365.
Several new controls map directly to settings in Microsoft Entra ID. Conditional Access needs Entra ID P1, which comes with Business Premium.
- Admin-only app consent (ISM-2137)
Turn off user consent to third-party apps so only an administrator can approve them. Then review existing consents at least every six months (ISM-2138).
- Block device code flow (ISM-2140)
Microsoft recommends blocking device code flow wherever possible, using a Conditional Access authentication flows policy. Teams Rooms and some shared devices need a scoped exception.
- Revoke sessions on reset (ISM-2148)
When a password is reset or an account looks compromised, revoke its sessions and refresh tokens too, or the attacker stays signed in.
- Risk-based access (ISM-2136)
Access decisions use signals such as location, device compliance and sign-in risk. Sign-in risk policies need Entra ID P2.
AI agents
AI agents now need identities, a register and limits.
Seven new controls cover AI agents and agentic AI applications, alongside the GOV-08 principle that the board or executive is accountable for AI being secure, controllable and human-supervised.
- A unique identity for every agentSeparate from staff accounts and from other agents (ISM-2133).
- An AI agent registerEach agent's identifier, owner, business purpose, identities, credentials, and the tools, permissions and data it can reach (ISM-2134, ISM-2135).
- Least privilegeAgents get only the tools and permissions their purpose needs, checked against both the user's and the agent's own access (ISM-2156, ISM-2157).
- Outside content stays untrustedWeb pages and documents an agent reads are treated as untrusted data, kept apart from its instructions (ISM-2158).
- Everything loggedTool calls, external requests and outputs are logged (ISM-2159).
How the ISM is used
ASD's six steps, in order.
From ASD's Using the cyber security framework chapter.
- 1Define the systemBoundary, business criticality, and security and resilience objectives, written into a system security plan.
- 2Select security controlsChoose and tailor controls using their applicability markings and your risks. Record them in the system security plan annex.
- 3Implement security controlsPut them in place, and record any differences from the plan.
- 4Assess security controlsCheck they are in place and working, by your own assessors or IRAP assessors, depending on the classification.
- 5Authorise the systemThe authorising officer decides whether the remaining risk is acceptable.
- 6Monitor the systemKeep checking controls, threats and changes, and go back a step when something material changes.
ISM, Essentials, SMB1001
Where the ISM sits next to the frameworks you hear about.
| Framework | What it is | Best for |
|---|---|---|
| ASD ISM | ASD's full framework: 49 principles and 1,143 controls, selected per system | Government systems and contracts that name it |
| ASD Essentials | ASD's new baseline published in October 2026, replacing the Essential Eight over time | Most businesses wanting ASD's priorities |
| Essential Eight | Eight mitigation strategies with maturity levels; still current while the Essentials transition is set | Existing programs and contracts that name it |
| SMB1001 | A tiered certification standard for smaller businesses, from Dynamic Standards International | Showing clients and insurers a certified level |
Mistakes we see
Five ways businesses get the ISM wrong.
- Assuming government work makes you PROTECTEDThe classification of the information sets the controls, not the customer's name.
- Treating an assessment as approvalThe assessor reports. The authorising officer decides.
- Implementing everything1,143 controls are a catalogue to select from, not a to-do list.
- Ignoring the MSP controlsYour provider's access is in scope. Ask how they meet ISM-2124 and ISM-2125.
- Evidence that is a screenshot from day oneAssessors want to see controls still working: logs, reviews and restore tests.
How we help
Control mapping and evidence, priced by the hour.
We map your Microsoft 365, devices and network against the controls a contract asks for, set up what is missing and keep the evidence. We quote at our published rate of $195 an hour ex GST. Independent assessment and authorisation are separate: an assessor checks, and your authorising officer decides.
How we work through it
From contract clause to evidence, in five steps.
- Step 1Read the requirement
Which ISM release, classification and baseline your contract or customer names.
- Step 2Draw the boundary
Tenants, devices, networks, people and suppliers in scope.
- Step 3Map the controls
Each applicable control marked as in place, inherited from a supplier, or a gap.
- Step 4Close the gaps
Settings changed, processes written, and new controls like MSP access logging put in place.
- Step 5Keep the evidence
Logs, reviews and restore tests kept with the control, ready for an assessor.
Related guides
The ISM is the reference. These are the practical steps.
Most of the new controls land in identity, backup, monitoring and Microsoft 365.
- ASD Essentials trackerThe Essential Eight replacement, as it lands.
- Essential Eight guideMaturity levels, and what still applies.
- Conditional Access libraryWhere most new identity controls are set.
- Backup and recoveryImmutable, segregated backups.
- Detection and responseLogging, alerts and threat hunting.
- Managed Microsoft 365The tenant most of these controls live in.
Get help your way
Six ways to reach us. Pick whichever suits you.
Helpdesk hours are Monday to Friday, 8am to 5pm AEST. On Advantage and above, emergencies get a response within 1 hour and outages within 2, with 24/7 best-effort escalation.
- Call 07 3114 2808
An engineer answers Monday to Friday, 8am to 5pm AEST. After hours, weekends and public holidays, Chip, our AI agent, answers on the same number or on 07 3180 0965, logs it and escalates urgent incidents to the on-call engineer.
Call now - Email the helpdesk
Send it to helpdesk@realbytes.com.au and a ticket is logged straight away, with a reference number you can quote.
Email us - Client portal
Log and follow your tickets, see what we are working on and who has it.
Open the portal - Remote support
When an engineer asks to see your screen, start a secure session here. You start it, so nobody sees your screen until you do.
Start a session - Chat in Microsoft Teams
Clients can message Chip, our AI assistant, in Teams to log a request without leaving their desk.
How clients reach us - Service status
Check whether Microsoft 365 or another cloud service is down before you lose an hour troubleshooting.
See live status
Questions
What people ask about the ISM.
Is the ISM mandatory for Australian businesses?
No, not as a matter of law. ASD says an organisation is not required to comply with the ISM unless legislation, a direction given under legislation or another lawful authority requires it. A government contract or agency can require it, and then you meet what the contract specifies.
What changed in the September 2026 ISM?
ASD published it on 7 September 2026. Comparing ASD's machine-readable catalogues, it has 44 controls that were not in the June 2026 release, and 2 June controls are no longer listed. The new controls cover service provider access, RMM tools, OAuth app consent and device code sign-in, tokens and sessions, application credentials, AI agents, immutable backups, threat hunting, network device management and MACsec.
How many controls are in the ISM?
The September 2026 catalogue has 49 cyber security principles and 1,143 controls. Of those controls, 1,017 are marked as applying to non-classified systems.
What do NC, OS, P, S and TS mean?
They are applicability markings: non-classified, OFFICIAL: Sensitive, PROTECTED, SECRET and TOP SECRET. Each control shows which kinds of system it applies to. All 44 new controls in the September 2026 release apply to non-classified systems as well.
Does an IRAP assessment certify our system?
No. An assessment checks whether controls are in place and working, and its report goes to the authorising officer, who decides whether to accept the remaining risk and authorise the system. For non-classified, OFFICIAL: Sensitive, PROTECTED and SECRET systems, ASD says assessments can be done by the organisation's own assessors or IRAP assessors.
Should a small business use the ISM or the ASD Essentials?
Unless a contract names the ISM, most small businesses get more from the ASD Essentials and a standard like SMB1001. The ISM is the deeper reference. The new controls are still worth reading, because several of them, like blocking device code sign-in and locking down MSP access, are cheap to do in Microsoft 365.
Next step
Has a contract asked you for the ISM?
Send us the security schedule. An engineer will tell you which controls apply, what you already meet and what it will take to close the rest.
Keep reading
- ASD Essentials tracker ASD's new baseline.
- Essential Eight guide Maturity levels explained.
- SMB1001 certification A certified level for smaller businesses.
- Microsoft 365 licensing Which plan includes Conditional Access.
Reviewed by Blake Bath, General Manager, on 30 October 2026. Control wording and counts from ASD's ISM OSCAL catalogues (September and June 2026). Legal standing, applicability markings, the six steps and assessments from ASD's Using the cyber security framework. Device code guidance from Microsoft Learn. ASD, Information security manual (September 2026); ASD, Using the cyber security framework (September 2026); ASD, Cyber security principles (September 2026); ASD, ISM OSCAL v2026.09.4; Microsoft Learn, Block authentication flows with Conditional Access