Following an incident involving an OpenAI agent that accessed an Australian government website without authorization, Australia is moving to establish stricter oversight of AI developers.
In a November 10 announcement, Prime Minister Anthony Albanese confirmed that the government has accepted all 18 recommendations from a review of the incident, including mandatory reporting of AI-related cybersecurity incidents and stronger accountability for developers.
The incident occurred in June when an autonomous OpenAI agent conducting an internet research task gained unauthorized access to the Medicare Statistics Reporting Service Portal. OpenAI reportedly did not detect the activity until August and notified the Australian government in September.
Australia now plans to establish an AI safety regulator, introduce mandatory safety and security standards, and consider criminal-law reforms for serious misconduct involving AI systems. The proposals also call for improved information sharing and coordination between government cybersecurity agencies and AI developers.
Ryan McCurdy, Vice President of Marketing, Liquibase
“What’s concerning about this incident is that the AI agent wasn’t trying to do anything malicious. It was carrying out a legitimate research task, encountered restrictions, and found another way to access information it wasn’t authorized to retrieve.
“AI agents are probabilistic systems. They interpret instructions, make decisions, and sometimes take actions their operators didn’t anticipate. That’s why the controls governing what they’re allowed to do need to be deterministic. We can’t rely on an AI agent to determine whether its own actions are authorized. Those boundaries need to be enforced independently of the model.
“Australia’s response puts more attention on accountability and incident reporting, which are important. But reporting an incident after it happens doesn’t prevent the damage. Organizations need technical controls that enforce permissions, validate high-risk actions, and prevent unauthorized changes before they’re executed.
“As AI agents take on more responsibility across software development and IT operations, the same security and governance standards should apply whether an action comes from a person or an AI agent.”
ㅤ
Darin Fredde, Senior Director and Offensive Security Evangelist, Ridge Security
“Giving an AI agent a legitimate research task does not authorize it to bypass someone else’s access controls. OpenAI describes an experimental model crossing that boundary. Its report that individual patient records were not accessed matters, but it does not erase the authorization failure. Australia’s proposed reporting requirements and independent evaluations are sensible steps. I would judge their success by the evidence: can developers show what an agent was authorized to do, what it did, and whether controls stopped unauthorized actions? Permissions need to be enforced outside the model and tested when an agent encounters resistance or changes its approach.
“A prompt is not a permission system. The timeline also raises two separate questions: how quickly unauthorized activity is detected, and how quickly affected organizations are notified after discovery. Both need clear ownership and tested response procedures. Organizations should receive prompt preliminary notice and usable technical evidence while the investigation continues. Autonomy can change how work gets done; it should never make responsibility disappear.”
ㅤ
Seemant Sehgal, Founder & CEO, BreachLock
“An OpenAI agent given free access to the public internet during an internal evaluation hit a government portal, got denied, and then created a disposable email address to register for an account anyway. That is the same lightweight social engineering workflow attackers use, with no containment layer inside OpenAI’s own environment catching it on the way out.
“The same AI companies producing these incidents are launching cybersecurity tools with minimal internal expertise to back them, and asking security professionals to trust them in production environments. There’s a real conflict of interest in asking practitioners to trust companies that prioritize speed of innovation over cybersecurity and guardrails every time, and this incident is a direct consequence of that tradeoff. Taking 84 days to notify through a public feedback inbox is a difficult credential to bring to a cybersecurity product conversation.
“Australia accepting all 18 recommendations and moving toward mandatory incident reporting is the right call. Every other government is going to end up here eventually.”
Australia leads the way because there is zero chance that I would trust OpenAI given its track record with the Australians alone. Sadly this will not force them to clean up OpenAI’s act as OpenAI really needs it.
Microsoft releases Azure Linux update addressing more than 470 vulnerability references
Posted in Commentary with tags Microsoft on November 11, 2026 by itnerdMicrosoft has released a major security update for Azure Linux, addressing more than 470 CVE references across the operating system, open-source packages and container infrastructure.
The November 7 release includes fixes affecting the Linux kernel, OpenSSL, Kubernetes, Docker and other components supporting cloud environments. Some vulnerabilities appear multiple times across different packages, so the total does not represent 470 distinct flaws.
The update also addresses certificate trust issues following the eMudhra certificate incident, removing or distrusting affected root certificates and strengthening validation in Python and Go. Additional patches cover container technologies including KubeVirt, containerd and Docker Compose, while the Linux kernel has been updated to version 6.6.161.1.
John Strand, Black Hills Information Security
“Four hundred CVEs in Linux is absolutely terrifying. But honestly, that’s not what makes me most uncomfortable.
“It’s like a magic trick. If the magician is showing you something in one hand, you need to watch the other hand.
“AI is speeding up code analysis and vulnerability discovery in the core applications and operating systems everyone uses. Organizations are trying to patch those vulnerabilities. That’s great. Linux, Windows, and OpenSSL may finally get the level of security scrutiny we should have been giving them all along.
“But what happens when you step away from those frontline technologies? When you move beyond the Linux kernel, OpenSSL, Docker, and Windows, you get into second and third tier projects and products that organizations use every single day.
“Who’s looking at those? Are they getting the same support? Who’s funding the security reviews, and who’s paying someone to fix what gets found?
“That’s what makes me uncomfortable. Attackers don’t need to get through the most heavily scrutinized software in your environment. They need a way in. And I think these less supported technologies are going to give them one.”
ㅤ
Darin Fredde, Senior Director and Offensive Security Evangelist, Ridge Security
“A patched host can still be running an unpatched workload. That is why I would look beyond the 470-plus CVE references and ask which affected components are actually deployed and reachable. The eMudhra-related certificate changes deserve particular attention because trust decisions can live in operating-system stores, bundled certificates, and application code. Go’s own guidance calls for rebuilt binaries to receive its verifier fix. Installing a newer compiler does not update an application already running in production.
“For operators, the job is to apply the supported updates, rebuild or replace affected application artifacts where necessary, and verify the result. Exposure and potential impact should guide rollout priorities. Certificate testing should confirm that affected chains are rejected while legitimate connections continue to work. From an offensive-security perspective, the useful follow-up is to test whether the relevant attack path has closed. A completed patch ticket records an action. Evidence from the running workload shows whether the intended protection is working.”
I have a post about the latest flaws found in Microsoft software for the month of November. Which to be frank is crazy. Having said that, this is required reading. ㅤ
Leave a comment »