Cybernion
← Insights

IRAP

ISM Non-Human Identity Controls: Secrets, Tokens and Credentials

4 Sept 2026 · Updated 4 Sept 2026

The September 2026 ISM stopped treating credentials as a human problem. It added a block of controls for the credentials applications, workloads and services use, and it wants them short lived, centrally managed, unique per environment, and revoked the moment they are exposed or idle. Systems that run on long lived API keys pasted into config are exactly what this release is aimed at.

What are the new ISM non-human identity controls?

The new controls cover the credentials that machines use rather than people. Non-human identity is the label the industry now uses for service accounts, application credentials, workload identities, API keys and tokens. The September 2026 ISM added controls that govern them directly, because that is where a growing share of real intrusions start: a leaked key, a shared secret, a token that never expired. The ISM September 2026 changes grouped these alongside the new AI agent controls, and the two belong together, because an AI agent is just one more non-human identity.

The old assumption, that an identity is a person who logs in, is gone.

What are the ISM controls for application and workload credentials?

Six controls, ISM-2141 to ISM-2146, rewrite how machine credentials are issued, stored and retired.

Control What it requires
ISM-2141 Applications and workloads use short-lived, dynamically issued credentials in preference to long-lived static credentials
ISM-2142 Static credentials used by applications and workloads are centrally managed in a secrets management solution
ISM-2143 Applications and workloads use unique credentials, not shared with other workloads or across development, testing, staging and production
ISM-2144 Static credentials are changed or revoked when compromised, found stored in the clear, found crossing a network in the clear, or no longer required
ISM-2145 Credentials for user accounts are revoked when no longer required
ISM-2146 Static credentials used by applications and workloads are revoked when no longer required

The intent reads clearly. Credentials that expire on their own are preferred, and where a static secret has to exist it belongs in a vault rather than in source code or an environment variable. One secret is never reused across environments, because a leaked staging key should not open production, and a credential found in the clear, in a repository or on the wire, is treated as already burned.

Does the ISM require a secrets management solution?

For machine credentials, the ISM does require one. ISM-2142 names it directly: static credentials used by applications and workloads are centrally managed using a credential or secrets management solution. The unstated target is the credential sprawl every mature environment carries, keys in .env files, connection strings in config, tokens in CI pipelines, passwords in scripts. A secrets manager centralises them, controls access, and provides rotation and an audit trail. This pairs with the software development change ISM-2030, which now requires commit scanning to catch plain text or encoded secrets, keys and credentials before they reach the source repository.

What does the ISM say about tokens and sessions now?

The ISM now wants tokens bound to a device and revocable on risk. Two controls close the token theft path that bypasses multi-factor authentication. ISM-2147 requires authentication tokens, session cookies and refresh tokens to be cryptographically bound to the device they were issued on, so a stolen token cannot be replayed from an attacker’s machine. ISM-2148 requires active sessions, refresh tokens and other authentication artefacts to be revoked when credentials are reset or re-enrolled, when they are compromised or suspected of it, when a device stops meeting compliance requirements, or when high risk sign in activity is detected.

Read together with the new risk based access control ISM-2136, which enforces access decisions informed by contextual signals, this is the ISM adopting the logic behind modern conditional access. A valid token is not a permanent pass.

What changed for OAuth applications and Active Directory accounts?

The OAuth consent path got locked down, and two Active Directory cadences tightened. Human users can no longer grant consent to third-party OAuth applications; only an authorised administrator can (ISM-2137). Consents and their granted permissions are reviewed at least every six months, with unused applications and excessive permissions revoked (ISM-2138). Consent grants, token issuance and token use are centrally logged (ISM-2139). The OAuth device code authentication flow, a common phishing vector, is disabled unless required and restricted to authorised accounts and managed devices when it is (ISM-2140).

On Active Directory, the KRBTGT account credential now changes at least every six months rather than annually (ISM-1847), and accounts with DCSync permissions are reviewed at least every six months (ISM-1934). Both cadences doubled. Where a golden ticket mitigation relied on an annual KRBTGT rotation, it is now behind the manual.

Do these ISM identity controls apply to our IRAP assessment?

They apply where the credentials, tokens and identities are inside the IRAP assessment boundary, which for almost any real system means yes. Every ISM control carries an applicability marking across the classifications, so the assessment tailors the set, but non-human identity is not an edge case the way an AI feature can be, because applications, workloads and service accounts exist in every environment. Before the next IRAP assessment, running the baseline through Cybernion Local shows which of the new identity and credential controls fall in scope, and the AI agent controls read as the same idea applied to autonomous software.

Frequently asked questions

What are the new ISM controls for application and workload credentials?

The September 2026 ISM added ISM-2141 to ISM-2146. They require short-lived dynamically issued credentials over long-lived static ones, central secrets management, unique credentials per application and environment, and change or revocation of static credentials when compromised, found in the clear, or no longer needed.

Does the ISM require a secrets management solution?

Yes, for machine credentials. ISM-2142 requires static credentials used by applications and workloads to be centrally managed using a credential or secrets management solution, rather than stored in code, config files or environment variables.

What does the ISM say about OAuth applications now?

ISM-2137 to ISM-2140 require that only an authorised administrator grant consent to third-party OAuth applications, that consents be reviewed at least every six months, that consent and token activity be centrally logged, and that the OAuth device code flow be disabled unless required.

How often must the KRBTGT account credential be changed under the ISM?

At least every six months. ISM-1847 was amended in September 2026 from at least annually to at least every six months, and DCSync permission reviews (ISM-1934) moved to at least every six months as well.


Written by Gaurav Vikash, an ASD endorsed IRAP assessor and senior cyber security leader with 18 years of experience across Australia, the UK and Asia, including CISO and senior security leadership roles. He holds CISSP, CISA, CISM and CRISC and is an ISO 27001 Lead Auditor and ISO 42001 Lead Implementer, and speaks regularly at industry conferences.

Talk to us. We aren’t always chasing a transaction.

Sources:

  1. ISM September 2026 changes document, ASD, September 2026
  2. Information Security Manual, ASD, September 2026

Last updated: 4 September, 2026

Related serviceIRAP AssessmentSee the service →

Talk to us about your engagement

A scoped proposal within one business day.