When the playbook is the outage: automated response becomes an underwriting question

The mechanism in Aon's first pattern is not that the machine judged wrong. It is that the alert was resolved. Automation bought in to cure alert fatigue can create a blind spot instead, which Aon links to repeat incidents and longer business interruption even where the control stack looks advanced ^[4]. Its illustration is a rental operation: customers turned up for vehicles at businesses that no longer had access to the software managing reservations and vehicle assignments ^[5]. From the counter, containment and an outage are the same event.

The privilege problem is more specific than "AI is a target". An attacker who compromises orchestration, or who can feed it false signals, inherits the ability to lock and unlock access, to choose which systems get isolated and which stay exposed, and to influence what is logged ^[6]. Aon's phrasing is that they do not need to bypass every control, they can redirect yours ^[7]. The logging half is what will hurt twice, because the same piece recommends capturing logs, model versions and approval paths in a form that satisfies auditors, regulators and claims handlers months after the event ^[11]. Evidence that your own automation can suppress is evidence a claims handler will not accept.

Then there is the scoring gap. Most of these systems still rank incidents by technical severity rather than financial impact ^[8], and without a mapping to crown-jewel systems, key customers, service levels and regulatory constraints, the automation over-remediates where it costs revenue and under-remediates where it matters ^[9]. Aon's summary of that state is that cyber operations quietly become earnings volatility ^[10].

Worth noting what the piece does not contain. None of the three failure patterns carries a figure, and neither the database-deletion story nor the rental example is attributed to a named organisation ^[14]. Aon also says its portfolio analysis shows well-governed AI tooling correlating with shorter dwell times and better containment ^[12], with no number attached, while pointing at its own Cyber Risk Analyzer and AI risk diagnostic ^[13]. Treat the correlation as a sales claim and the questionnaire as the load-bearing part.

The questionnaire is answerable in writing this quarter: how orchestration is authenticated and permissioned, whether the people who design playbooks are separate from those who approve them, and how fast an automated action can be reversed with an audit trail ^[3]. The three-tier version Aon says leading firms adopt is blunter still, sorting actions into fully automated, one-click approval, and multi-party signoff ^[15]. Most security teams already know which of their playbooks would fail that sort, and know that reconstructing the answer after an incident costs more than writing it down before one.