Cybernion
← Insights

IRAP

ISM Synthetic Impersonation Control: Verifying Requestors (ISM-2126)

4 Sept 2026 · Updated 4 Sept 2026

The September 2026 ISM added a control aimed squarely at deepfakes. ISM-2126 says staff must positively verify who is asking, through a pre-arranged method or an independent channel, before they change account details, change banking details or move money. It does not care how real the voice on the phone sounds. That is the point.

What is ISM-2126, the synthetic impersonation control?

ISM-2126 is a new personnel security control that puts identity verification in front of sensitive actions. It recommends personnel positively identify a requestor, using a pre-established authentication method or an independent trusted communication channel, before actioning a request to modify user account details, modify banking details or conduct financial transactions. It appears for the first time in the ISM September 2026 changes, under a new heading the manual calls synthetic impersonation.

The control names a specific class of attack and a specific defence. The attack is a convincing impersonation of a trusted person. The defence is a verification step that does not rely on recognising the person.

Why did the ISM add a synthetic impersonation control?

The reason is that the thing staff used to trust, a familiar voice or face, can now be faked well enough to fool them. Voice cloning needs seconds of audio. Video deepfakes are good enough to carry a live call. The scam writes itself: a call from the “CFO” telling finance to redirect a payment, or from “IT” asking the service desk to reset an executive’s account and change the recovery number. The deepfake and voice clone fraud threat is no longer emerging; it is operational, and it targets the exact actions ISM-2126 lists.

The ISM’s answer is blunt: stop treating recognition as authentication, because a familiar voice is not proof of who is calling.

How do we comply with ISM-2126?

Set up a verification method in advance, and make staff use it for the actions the control names. Compliance has two parts: define the method, then enforce it at the point of the request.

Requirement What it looks like in practice
A pre-established authentication method A shared code word, a challenge tied to something only the real person holds, or verification through a system the requestor is already authenticated to
An independent trusted channel A call back to a known internal number, a message through an established platform, or confirmation from a second known person
Applied to the right actions Changes to user account details, changes to banking details, and financial transactions, every time

The judgement call is where to draw the line on financial transactions, since verifying every routine payment is not workable. The control leaves that to be scoped to the organisation’s risk, but the account and banking detail changes are the ones attackers chase, so those are where the verification step earns its place.

Does ISM-2126 apply to our IRAP assessment?

It applies as a personnel security control, so it is in scope for most assessments regardless of the technology in the boundary, because it governs a human process rather than a system feature. An assessor will look for a defined verification method and evidence that staff who handle account changes, banking changes and payments actually use it. A written policy that no one follows will not pass; the control is about the action, not the document.

Before the next IRAP assessment, run the baseline through Cybernion Local to see ISM-2126 alongside the rest of the September 2026 changes, and pair it with staff awareness so the verification step is second nature, not a form.

Frequently asked questions

What is ISM-2126?

ISM-2126 is a new September 2026 ISM control under personnel security. It recommends personnel positively identify requestors using a pre-established authentication method or an independent trusted communication channel before actioning requests to modify user account details, modify banking details or conduct financial transactions.

Why did the ISM add a synthetic impersonation control?

Because voice cloning and video deepfakes now let an attacker convincingly impersonate a known person over a call or video. ISM-2126 puts a verification step between a request and a sensitive action, so a realistic fake is not enough on its own to trigger an account change or a payment.

How do we comply with ISM-2126?

Define a pre-established authentication method or an independent trusted channel for sensitive requests, such as a call back to a known number, a code word, or verification through a separate system. Require staff to use it before changing account or banking details or moving money, regardless of how genuine the request seems.


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.