The Dependency Trap: one hidden connection can make separate systems part of the same incident

The Dependency Trap. Wk21

Your next incident may start in a component nobody remembered to own. This week: Australia's national warning and the local work it demands, PHP2Shell and the CMS dashboard that is not a runtime inventory, OT support stacks, a LiteLLM key marked for revocation that an attacker checked first, identity resets, the 28 October certificate deadline, and five decisions to make before the next status meeting.

The recovery gap. Wk20

What happens when the tools that watch, administer and restore the business become part of the incident
Australian Cyber Threat Brief: The authority problem, week 19 feature image

Australian Cyber Threat Brief: The authority problem. Wk19

An attacker can borrow a trusted account. An agent can stretch a legitimate task. A quantum service can place exceptional power behind an ordinary interface. Who controls the authority between a request and its consequence?

Australian Cyber Threat Brief: The capability shock. Wk18

Your oldest employee might be an API key. It has survived three restructures. Nobody knows its manager. The capability shock, from benchmark to boundary.

Australian Cyber Threat Brief: Hype, harm, hardening. Wk17

An OpenAI agent breached a Medicare statistics portal. A hijacked coding assistant seeded 100 repositories. Not every AI headline is the same incident. Hype, harm and the hardening that separates them.
Security Control Validation

Australian Cyber Threat Brief: The control test. Wk16

An attacker rewrote a live website at the edge while the origin stayed clean. A CVSS 10 flaw under active exploitation. AI agents crossing boundaries to finish tasks. Trust is not a setting. It is a result you can demonstrate.