What must Australian agencies change after the new AI-enabled cyber direction?
A binding direction requires non-corporate Commonwealth entities to inventory and plan down legacy-technology risks. It sets deadlines and a reporting route, but leaves agencies to define the depth of their own stocktakes.
The short version
- What happened
- The direction applies to non-corporate Commonwealth entities under Australia's Protective Security Policy Framework.
- Who it affects
- Residents depend on secure, continuously available public services and may be harmed by either exploitation or poorly managed replacement work.
- What remains unproven
- The direction is a policy instrument and provides no denominator for systems, agencies, vulnerabilities or AI-enabled incidents.
Keep in mind
The direction is a policy instrument and provides no denominator for systems, agencies, vulnerabilities or AI-enabled incidents.
Agencies determine the depth and scope of their own stocktakes, which may reduce comparability.
Additional measures for critical government systems depend on an explanatory note due after publication.
Source analysis · 2 linked sources. Primary analysed source date: 29 September 2026. Earliest linked supporting source: 27 May 2026.
Read the full report · 4 min The evidence, methods, implications and limitations
What is mandatory—and for whom
Australia's Department of Home Affairs published PSPF Direction 002-2026 on 29 September. Under the Protective Security Policy Framework, accountable authorities of non-corporate Commonwealth entities must comply with a direction issued by the department's secretary. The instrument says frontier-AI capabilities have targeted the Commonwealth technology estate and that unsupported systems plus accumulated vulnerabilities now pose an unacceptable risk.
The scope is specific: non-corporate Commonwealth entities covered by the PSPF, not every Australian business, state government or public body. The document defines legacy technology through existing PSPF criteria covering end-of-life or out-of-support products combined with factors such as impractical maintenance, unacceptable risk, poor value or obstruction of technology strategy. It does not publish the number of affected systems or agencies and should not be read as a measured prevalence study.[1]
The deadlines turn advice into accountable work
By 31 March 2027, every covered entity must conduct a stocktake of legacy systems it manages or has managed on its behalf. It must develop and maintain a risk-management plan inside its cyber strategy and uplift plan, including a reduction target, priorities, mitigations for systems that remain and procedures to rationalise the technology estate. Completion and a copy of the plan must be reported to Home Affairs' Commonwealth Security Policy Branch.
Entities operating Systems of Government Significance face an additional 31 December 2026 deadline to incorporate risk-reduction measures that will be detailed in an explanatory note due by 13 October. The direction tells agencies to prioritise public-facing services and critical government systems, while recognising the shorter interval between vulnerability discovery and exploitation. National-security functions may seek a reporting exemption for a legitimate business reason, but the document does not create a general opt-out.[1][2]
Why AI changes the timing, not the basics
The required actions are familiar security fundamentals: know the estate, remove unsupported technology, patch rapidly, reduce exposure and plan for continued operation. The AI element is the threat tempo. More capable systems can help attackers discover, combine and exploit weaknesses faster, shrinking the time available for defenders. That does not mean an autonomous model can compromise every legacy system, and the direction supplies no incident count or comparative exploitation rate.
For agency leaders, a useful stocktake should record ownership, support status, public exposure, data sensitivity, dependencies, patchability, compensating controls and the consequence of failure. A list without service relationships can miss a supported front end that depends on an unsupported back end. Suppliers should be included where they operate systems on an agency's behalf, but accountability remains with the entity. Risk reduction may mean replacement, isolation, tighter access, virtual patching or a tested continuity plan rather than immediate removal in every case.[1][2]
Effects on people and the evidence still missing
People rely on government systems for payments, health, identity, taxation and other essential services. Faster patching can reduce exposure, but rushed changes can also interrupt access, especially where an old system supports a public-facing service with few alternatives. The direction explicitly tells entities to balance availability with security. Agencies should test accessible fallbacks, publish service notices and include continuity for people who cannot switch channels easily.
The assessment would become stronger if the October explanatory note defines measurable risk-reduction standards and later reporting shows how many systems were found, retired, isolated or remediated, with incident and outage trends. It would weaken if agencies choose shallow stocktakes, set non-comparable targets or treat plan submission as the outcome. The present document is important because it creates mandatory governance and dates; it is not evidence that Australia's legacy-system risk has already fallen.[1]