Why Agent Architectures Need a Distinct Kill Chain
Traditional network kill chains describe adversary behavior against static infrastructure: endpoints, servers, and credentials. AI agents introduce a different set of components: a prompt input layer, a planning loop that reasons over multi-step tasks, tool invocation interfaces, memory or context state, and an execution layer that carries out actions. Compromise can enter or persist through any of these, and generic security alerting was not built to observe them. A kill chain built for agents treats each of these components as a distinct stage with its own detection signals and containment options, rather than compressing the entire agent into a single monitored process.
Mapping Stages to Agent-Specific Telemetry
Detection at each stage depends on telemetry that is specific to how agents operate, not just standard application logs. Initial access is visible in prompt and input logs, including anomalies in upstream data sources feeding the agent. Planning deviation requires visibility into the reasoning trace itself: does the agent's stated plan diverge from the original task goal. Tool misuse is detected through logs of tool calls, including which permissions were invoked, whether scope escalated, and whether calls were chained in unexpected sequences. Persistence requires monitoring of memory and context stores across sessions, since poisoned state may not trigger any alert within a single session. Impact is confirmed through logs of executed actions, downstream system changes, and any outbound data transfer.
Containment Without Full Shutdown
A recurring failure mode in early agent security practice is treating "shut down the agent" as the only containment option. This disrupts legitimate multi-step tasks already in progress and creates pressure to under-report or delay response. A mature playbook defines containment actions scoped to the narrowest unit affected: suspending a single tool, isolating a single session, revoking a specific permission grant, or rolling back a poisoned memory state, while leaving unaffected agent functions operating. These containment options need to be defined and tested against legitimate workflows before an incident occurs, not designed reactively during one.
Governance and Responsibility Across the Kill Chain
Because agent incidents span reasoning, tool access, and data handling, responsibility for detection and response typically crosses security, platform engineering, and the teams that own individual tool integrations. Effective governance assigns clear ownership for monitoring each stage, defines escalation paths specific to agent incidents (rather than reusing generic application incident procedures), and requires audit logging sufficient to reconstruct what the agent reasoned, what it invoked, and what it executed at each stage of an incident.