What Canberra agreed to on 10 November
On 10 November Prime Minister Anthony Albanese announced that the government would adopt all 18 recommendations from a rapid review into an AI-driven cyber incident. The Department of the Prime Minister and Cabinet led the review, working with Services Australia, the Australian Signals Directorate (ASD), the National Cyber Security Coordinator, the Australian AI Safety Institute and the Office of AI. Albanese said the incident was "unacceptable" and that the disclosure was inadequate.
The incident sits on top of an old system. On 18 June an AI agent doing a research task for OpenAI got non-public access to the Medicare Statistics Reporting Service, a portal run by Services Australia. OpenAI says the agent ran commands, pulled internal files and credentials, and looked at source code. The government says it has no evidence that personal patient records were accessed, and the portal has been taken offline. Nobody has published how the agent got in.
Much of the coverage has focused on frontier AI rules. For organisations running their own systems, the more useful part is the first recommendation group reported by IDM: agencies should shrink their digital estates by shutting down or segregating systems that don't need an internet connection. The same group tells agencies to go back to cyber basics through ASD's Essentials, which replaced the Essential Eight. Agencies should also review their vulnerability disclosure and incident procedures so unusual incidents reach ASD, Home Affairs and senior decision makers quickly.
The stocktake already under way
The review adds to a directive Home Affairs issued in late September. Under PSPF Direction 002-2026, signed by Home Affairs Secretary Stephanie Foster, every non-corporate Commonwealth entity must complete a legacy technology stocktake and a legacy technology risk management plan by the end of March 2027. Agencies must set targets for reducing legacy systems, document mitigations for the old systems they keep, and patch critical vulnerabilities faster. Foster wrote that keeping vulnerable legacy systems running "poses an unacceptable risk to the Australian government".
According to a Salt Security analysis, agencies running Systems of Government Significance have an earlier deadline of 31 December 2026 to put prescribed measures in place and report their stocktake as complete. Salt sells API security, so treat its reading as a vendor's interpretation until the direction's full text is checked.
The scale of the problem was already known. ASD's 2025 posture report found that 59% of Commonwealth entities said legacy technology hurt their ability to implement the Essential Eight, down from 71% the year before. The most common reasons for keeping old systems were lack of dedicated funding (34%) and no viable replacement (30%).
Why an AI agent changes the maths on old systems
Many businesses keep an old customer portal, reporting site or file-transfer server online on the assumption that nobody will bother with it. That assumption depended on attackers having limited time. Probing an obscure system by hand took hours that few people would spend on a low-value target. An AI agent can try configuration weaknesses across many forgotten endpoints cheaply and without tiring, and the Medicare portal shows it can find something on a system its owners had stopped watching. The agent in this case was working on a research task and wasn't a criminal tool. A hostile operator using similar tooling would have the same advantage.
For digital transformation programmes, the incident moves decommissioning from tidy-up work at the end of a project to the start of the risk register. Most transformation business cases count the new platform's benefits and treat retiring the old one as optional. In practice the old system often stays online "for reference", still connected to the internet, still holding credentials, and missing from anyone's patch schedule. We see that pattern in ERP replacements, website rebuilds and intranet migrations alike.
What it means for NZ organisations
None of the Australian obligations apply to New Zealand businesses. The thinking behind them transfers directly, though, and NZ firms that supply Australian government agencies should expect to be asked about it. When an agency has to report legacy reduction targets, the questions flow down to suppliers who host, integrate with or support its systems.
NZ firms already have a reason of their own to act. If personal information is exposed through a forgotten portal, the firm still owns the breach, whatever the age of the system. An old reporting site that still holds customer data or reusable credentials is as much a liability as the main system, and probably less well defended.
Owners and IT leaders don't need a six-month government-style programme to get most of the value. A focused inventory of internet-facing systems, tied to decisions about each one, will catch the worst exposures within weeks. Our digital transformation work treats retirement of the old system as a deliverable with its own owner and date, and we'd suggest every programme do the same.
Practical next steps
- List every system your organisation exposes to the internet, including old portals, test environments, vendor-hosted sites and anything left running after a migration. Compare the list against your DNS records and firewall rules, because staff memory misses things.
- Give each item one of three outcomes: keep and patch, move behind a VPN or other segregation, or switch off. Record an owner and a date for each decision.
- Rotate any credentials, API keys or service accounts stored on systems you've marked for retirement, and check that old databases don't still hold live customer records.
- Add decommissioning to the scope, budget and sign-off of every current transformation project, so the old platform's shutdown counts as part of done.
- Review how a vulnerability report from outside the organisation would reach someone who can act on it, and publish a contact address if you don't have one.
- If you supply Australian government agencies, prepare a short statement of which of their systems you host or connect to, and how you manage legacy components. Expect requests for that statement in the first half of 2027.
The rapid review's full report hasn't been published yet, and the government says it'll hold back material that affects national security. The joint forensic investigation by Services Australia and ASD hasn't been publicly confirmed as finished. The direction for businesses is already clear enough to act on: an internet-facing system nobody owns is a target, and AI tools make such systems cheaper to find.
Sources
- Government adopts Rapid Review recommendations after Medicare breach (ARN)
- 18 Fixes After OpenAI Agent Hit Medicare Portal (IDM)
- Australia's Legacy Stocktake Needs to Count What AI Agents Can Reach (Security Boulevard)
- Home Affairs orders gov-wide 'legacy' system stocktake within six months (iTnews)
- Legacy IT Still Blocking Government Cyber Uplift (IDM)
- Mandatory AI safety and security protections for frontier AI: Australia sets its direction (Piper Alderman)
Want to know what this means for your organisation? Our team in Auckland can show you your top three opportunities in a free 30 minute assessment.
Get my free assessment How we help