Containment is the point at which the blue team stops watching an intrusion and starts changing the estate, and it is where the series' rule on autonomy meets its hardest test. This chapter describes B4 Respond as transformed: containment, eradication, recovery coordination, communication and reporting, where the response is increasingly codified as playbooks and parts of it run at machine speed. It sets out which response actions an AI system may take and at which level, what a playbook manifest contains, how Level 3 Bounded is enforced in practice, how a stop path is built so that it works when it is needed, and what the reporting clocks ask of the case record. It builds on the autonomy levels and the Level 3 definition of AI Red Team, Chapter 6, and on the containment design of AI Platform and Security, Chapter 19. The decision rights that surround these actions are the subject of Chapter 18, and the regulatory map is the subject of Chapter 19. Incident management, reporting and communication as a whole are treated in AI Red Team, Chapters 20 and 21.
Every containment action trades one harm against another. Isolating a host stops an intruder from moving, and it also stops the person or the process that used the host. Revoking a session removes the intruder's foothold and interrupts legitimate work that shared the session. Taking a service offline protects the data behind it and denies the service to everyone who depended on it. The first harm grows with every minute the action is delayed, and the second falls on people who did nothing wrong. A response is therefore a decision under uncertainty, made on evidence that is incomplete, and the architecture of the response is the architecture of that decision: who may take it, on what evidence, within what limits and with what means of undoing it.
Before AI entered the SOC, this decision was taken by a person, usually under time pressure, with a runbook as a guide. The runbook described the steps, and the analyst or the incident commander supplied the judgement about whether to take them. Two things have changed. The first is speed. AI Platform and Security, Chapter 18, recorded the collapse of the exploitation window when adversaries use AI, and the consequence for the defender is that the interval between the first sign and the point where containment is still cheap has shortened (63, Nordqvist, 2026). The second is delegation. A SOC agent that holds an identity of its own can execute a playbook step in seconds, so the question of whether a machine may take a containment action is no longer hypothetical for a team that runs a Mode 5 agent.
Primary topics explored
- Response is a decision
- Action classes
- The playbook manifest
- Level 3 in practice
- The stop path
- Break-glass and the incident commander
About AI Blue
AI Blue is Book 8 of The Transformed Architecture. It examines how the blue team, the people and functions that defend an organisation, is transformed when artificial intelligence takes part in their work: anticipating, detecting, investigating, responding and learning, the team's own AI and how to verify and protect it, operating models, roles, decision rights, regulation and measurement, and the careers and wellbeing of the people involved, for European enterprises and public authorities.
It builds on the conclusions of Architecture as Code, AI Governance, AI Platform and Security, AI Red Team, AI Threat, The Transformed Security Architect and AI Boss.
Chief information security officers, heads of security operations, SOC managers, analysts, detection engineers and incident commanders, security and AI architects, boards and management bodies, procurement leads, works councils and unions, data protection and audit functions, and public-sector leaders.
Continue with the full chapter
Chapter 10: Respond: Playbooks, Bounded Containment and the Stop Path in AI Blue gives the detailed explanations, practical examples and implementation patterns behind this summary.
This whitepaper belongs to “The Craft” and is one of 32 drawn from the manuscript.