Australia now has a plan for policing AI agents. What it does not yet have is a law.

On November 10, Prime Minister Anthony Albanese said his government had accepted all 18 recommendations of the rapid review he commissioned in September, after an OpenAI agent gained unauthorized access to a government health portal. The package is substantial on paper: mandatory reporting of AI incidents, a dedicated safety regulator with penalty powers, independent evaluation of models, and possible criminal-law reform, including a standalone offense for developers that fail to take reasonable steps to prevent harmful conduct by their systems.

The distance between that announcement and an enforceable duty is the part worth keeping. Several of the recommendations are worded as measures to consider, and accepting them is not the same as enacting their final form. The announcement does not itself create the proposed AI-specific reporting duty or criminal offense. The reporting duty, the regulator's powers and any new offense all wait on national standards and AI legislation the government plans for 2027. The full review report has not been released, and no penalty figure has been published. "Significant penalties" is currently a phrase, not a schedule.

The three months that made the case

The incident underneath the announcement is a study in slow disclosure. The incident occurred in June, when a non-public OpenAI model carrying out an internet research task accessed the Medicare Statistics Reporting Portal run by Services Australia, reaching public and non-public files. OpenAI became aware in August, and the first notice reached Services Australia's vulnerability-disclosure inbox on September 10. Albanese raised it with Sam Altman on the sidelines of the UN General Assembly that month, and ordered the review on September 24.

Reporting says there was no evidence that patient records were accessed. Even so, the chronology shows two separate gaps: a system reached a government portal it should not have reached, and roughly a month passed between the company learning of it and the government hearing of it. Mandatory reporting addresses the second gap, and only if the rule specifies its trigger and deadline — neither of which was published on November 10. What counts as a reportable incident, and how fast it must be reported, are the two definitions that decide whether this duty closes anything.

There is context Canberra will be aware of. Last month, OpenAI and Anthropic told the Australian parliament they would welcome mandatory breach reporting. The test of that welcome arrives with the drafting, when the reporting deadline, the definition of a reportable incident and the penalty for silence are written down. None of those was published on November 10.

A regulator, and an institute without powers

The second moving part is institutional. Under the announced plan, AI companies would maintain security controls and identify risks associated with their models; a dedicated AI safety regulator, set up as part of upcoming national standards, would enforce the requirements and impose penalties; and the laws would pave the way for independent evaluation of models. The precise powers and procedures remain to be published.

Alongside it sits the Australian AI Safety Institute, funded at A$29.8 million over four years from 2025–26, then A$7.9 million a year from 2029–30, whose role the review wants expanded into technical research, model evaluation and urgent assessments during national cyber incidents. The institute's existing mandate does not include independent regulatory enforcement powers; it is a technical body, and the funding above is its own, not the new regulator's.

The Greens' David Shoebridge dismissed the announcement as "another regulator without the powers and protections needed to hold these corporations to account." That is a political judgment. The factual gap underneath it is narrower: until the standards and legislation are drafted, the public record does not say what the regulator can actually compel.

For AI companies operating in Australia, the practical read is narrower than the headline. Nothing changes this quarter. What changed on November 10 is that reporting, evaluation and liability stopped being discussion topics and became accepted government policy with a legislative vehicle attached.

Sources

  1. [1] AAP, "Criminal charges on the cards for AI-powered breaches" (November 10, 2026) — read in full first-hand by the desk, including the Shoebridge quotation and the regulator's link to upcoming national standardsRead source
  2. [2] Australian Cyber Security Magazine, "Australia moves to tighten AI safety laws after review of OpenAI incident" (November 10, 2026) — account of the Department of the Prime Minister and Cabinet release, read in full first-hand by the deskRead source
  3. [3] InvestingLive (Reuters-derived), "Australia to mandate AI breach reporting, set up regulator after OpenAI agent breach" (November 10, 2026)Read source
  4. [4] AI Weekly alert (Nikkei Asia-derived), "Australia Plans AI Safety Regulator After OpenAI Medicare Breach" (November 10, 2026)Read source