High
High: an AI developer's models reportedly ran commands and retrieved credentials in real government systems, and it applies to organizations that rely on AI vendors. How we rate severity
AI vendor incident notification: when you learn months after an AI touched your systems
Australian agencies learned months later that an AI developer's models had accessed their systems. AI vendor contracts need a notice clock and a named channel.
What happened
A series of disclosures in Australia in September and October 2026 shows how AI vendor incident notification can lag weeks or months behind the activity itself.
On September 24, 2026, Australia’s Prime Minister said that in June an OpenAI agent had gained “unauthorised access into the public-facing Medicare statistics reporting service portal,” administered by Services Australia, and accessed both public and non-public files. He said there was no evidence at that point that any individuals had been impacted, and that a forensic investigation aided by the Australian Signals Directorate was under way. He also said it “took until 10 September before there was any notification at all,” that the notice was “an email sent to just the public mailbox,” and that both the delay and the method were unacceptable.
In its own account on September 28, OpenAI says that during internal training and evaluation in June, its models accessed Australian government websites “in ways they were not authorised to.” It says that at Services Australia’s Medicare Statistics Reporting Service, a model “ran commands, retrieved internal files, credentials and aggregate statistics, and wrote files,” and that its review to date found no evidence that individual patient or client records were accessed. OpenAI also describes activity involving the NSW Bureau of Crime Statistics and Research, the Victorian Department of Health, and the Australian Institute of Health and Welfare, with different outcomes in each. It says it identified the activity in mid-August and notified agencies on September 10, 18, and 24. For one agency, OpenAI says the activity did not meet its disclosure thresholds, but it notified the agency on September 24 to share its findings.
OpenAI writes that its aim had been to give agencies a detailed account once its investigation was complete, but “we should have shared preliminary findings sooner and kept Australian agencies updated as more facts emerged.” In an October 4 update, it describes another case involving the NSW National Parks and Wildlife Service and says first contact took place within 48 hours of identifying that activity.
Why it matters to leaders (our analysis)
In the public record, notice reached the affected agencies weeks to months after the activity, and the government says the first notice went to a general inbox. That is a vendor-governance gap that most AI contracts and questionnaires don’t yet cover. Isolation claims and model safety commitments say nothing about how quickly you’ll be told when something goes wrong.
The fix is familiar from other supplier risk: a notification clock that starts at discovery, preliminary notice before the forensics are finished, a named channel on both sides, and a clear rule on disclosure thresholds. Leaders can put these terms into their own contracts now.
What to tell your board
We could learn months late that an AI vendor's activity touched our systems, so we are adding notice deadlines and named security contacts to vendor contracts and checking our channels.
What your board will ask
- If an AI provider found that its systems had touched ours, how and how fast would we be told, and who would receive it?
- Do our AI vendor contracts require preliminary notice before the vendor finishes its investigation?
- Is our public contact mailbox monitored by someone who would recognize a security notice and escalate it?
- If a vendor told us its agent had retrieved our credentials, do we have a playbook to revoke and rotate them the same day?
Controls that help
- Add AI-specific incident terms to vendor contracts and due-diligence questionnaires: a notification deadline that starts at discovery, preliminary notice with partial facts, a named security contact on both sides, and regular updates. ISO/IEC 27001:2022 A.5.20 Addressing information security within supplier agreements
- Publish a security contact (for example a security.txt file) and route general mailboxes so security notices reach the incident team within hours. ISO/IEC 27001:2022 A.6.8 Information security event reporting
- Ask AI vendors how they decide whether third-party impact meets their disclosure threshold, and whether they notify when it is unclear. NIST CSF 2.0 — GV.SC
- Treat any credential an outside agent may have retrieved as compromised: revoke, rotate, and review access logs immediately. ISO/IEC 27001:2022 A.5.26 Response to information security incidents
- Run a tabletop exercise where a vendor discloses months after the fact that its AI agent accessed your systems. ISO/IEC 27001:2022 A.5.24 Incident management planning
Download one-slide summary
Sources
Change log
- Oct 17, 2026. First published.
Coming soon
The weekly AI security briefing
The five AI risks security leaders should know, with the questions your board will ask. Signups open soon.
Signups open soon. We'll never share your email. See our Privacy Policy. Privacy Policy