Overview

The first two crosswalks in this chapter answered a threat model and a requirements framework. This one answers the checklist. When a security team reviews an agent deployment, the framing on the table is usually OWASP’s: the Agentic AI Threats and Mitigations taxonomy from the GenAI Security Project (first published in February 2025 with fifteen threats, revised to version 1.1 in December 2025 with seventeen, and distilled the same month into the Top 10 for Agentic Applications for 2026, mapped below), seventeen threats spanning single agents, multi-agent systems, their protocols and supply chains, and the humans around them, alongside the Top 10 for LLM Applications, now in its 2026 edition. If the handbook cannot state its position against that list, threat by threat, the reviewer is right to treat it as unevaluated.

A crosswalk that claims everything has been fitted to its framing, so this one sorts every threat into three verdicts, each stated as what an attacker can still do:

VerdictWhat it means
ContainedThe attacker cannot exceed the authority the Mission committed or keep it past the Mission’s end, and machinery built for the threat, with a draft behind it, enforces that. Inside the committed authority, the attacker can still act
BoundedThe cause is out of authorization’s reach: the attacker can still poison, steer, or deceive, and the action gate caps what any resulting action can do
DelegatedNot an authorization problem: a named complement owns it, and the handbook composes with it

Most rows turn on a distinction the trifecta post established. The authorization layer does not make the model resistant to anything. It makes the model’s compromise survivable, because authority was fixed at approval and every consequential action is checked against it fresh. A verdict follows what the threat attacks. Threats that attack authority are contained. Threats that attack the agent, its memory, its goals, its inputs, or the humans around it are bounded, even where the gate also stops the resulting action from exceeding the committed authority, because the cause is untouched. Threats that attack layers the handbook never claimed are delegated, by name. Neither contained nor bounded means prevented at the cause. A manipulated goal, a misused tool, or a rogue instance can still act inside the committed authority, which is why scope stays tight. Throughout the chapter, the gate checks a committed boundary and never an inferred intent.

The agentic threats, all seventeen

ThreatThe attackThe handbook’s answerVerdict
T1 Memory PoisoningPersistent memory is seeded with malicious data that steers future behaviorPoisoned memory can steer proposals, not authority. Shaping fails closed on ambiguity, and every consequential action still needs a fresh parameter-bound permit against the approved MissionBounded
T2 Tool MisuseDeceptive prompts or misdirection drive the agent to abuse tools it is authorized to use, staying within its granted permissionsThe manipulation itself is untouched, and a misuse that stays within the committed authority still executes. Per-action PEP/PDP enforcement with parameters bound into the permit, applied at the tool boundary by the MCP application post, refuses any invocation outside the approved Mission’s entries and constraints, so the misuse reaches only what the Mission committedBounded
T3 Privilege CompromisePermissions escalate beyond what the task requiresNarrowing: every derivation is a strict subset of the Mission’s Authority Set, Child Missions only narrow, and there is no ambient inheritance to escalate into. This holds for all authority derived from the Mission. A standing credential the agent holds outside the Mission is not narrowed, and an Authority Set approved broader than the task stays as broad as approvedContained
T4 Resource OverloadUnbounded agent activity exhausts compute, API, or financial budgetsexpires_at on every Mission, fan-out bounded by count and depth, and Consumption Metering (experimental) for spendBounded
T5 Cascading Hallucination AttacksFalse content propagates through memory, messages, and downstream systemsAuthorization does not verify truth. Hallucinated content can reach the world only through consequential actions, and each needs its own permitBounded
T6 Intent Breaking and Goal ManipulationInjection or instruction manipulation redirects the agent’s objectivesThe manipulation itself is untouched, and the agent’s goal can be rewritten. The rewritten goal cannot widen the committed one, because the PDP checks actions against the approved Mission, not against the agent’s current intentBounded
T7 Misaligned and Deceptive BehaviorsThe agent acts against its intended purpose or conceals what it doesThe gate does not detect deception. Only approved action classes execute, and Decision and Execution Evidence come from the gate, not from the agent’s self-reportBounded
T8 Repudiation and UntraceabilityActions cannot be reliably attributed or auditedOn mediated paths, attribution end to end: the act chain on every hop and the evidence family joined on mission_id. Tamper evidence rests on optional SCITT registration (Audit Transparency). Without it the records are signed, and a holder of the signing key can still backdate, drop, or reorder them. With it, a registered record verifies as unaltered, but registration proves inclusion, not that every record was registered or that a reported effect occurred. An unmediated path produces no evidenceContained
T9 Identity Spoofing and ImpersonationAttackers assume an agent’s identity or abuse non-human authenticationAttested instance identity and sender-constrained tokens bind each credential to one instance’s key. The verdict rests on mediated custody (High-Assurance Agent), which keeps the credential and its key out of the agent for the mediated classes. That isolation rests in turn on the deployment’s attested Enforcement Scope Statement, a self-declared artifact. Outside mediated custody, an attacker who takes the agent’s key acts as that instance, within its Mission-bound authority, until revocationContained
T10 Overwhelming the Human in the LoopApproval volume is weaponized until humans rubber-stampHuman decisions stay rare and consequential by design. The PDP decides individual actions, a deterministic policy can adjudicate activation within a ceiling a human consented to, and humans stay accountable for the ceilings and keep the class-guard classes by default, with deferred approval and the batched discovery loop absorbing the volumeBounded
T11 Unexpected RCE and Code AttacksTool invocations achieve code executionSandboxing owns execution. The handbook gates what executed code can reach. Consequential effects still need permits, and capabilities are bound to source digests with drift failing closedBounded
T12 Agent Communication PoisoningMalicious instructions ride inter-agent messagesInfluence carries no authority between agents, because delegation only narrows and every hop is enforced against its own narrowed authority (a subset token under the act chain, or its Child Mission)Bounded
T13 Rogue AgentsA compromised agent inside the system acts maliciouslyThe compromise itself is untouched. A rogue instance holds only mission-bound, instance-bound, revocable authority, and Termination cascades through the delegation tree to issuance, permits, and the harness on the paths the deployment governsBounded
T14 Human Attacks on Multi-Agent SystemsOperators are manipulated into enabling harmSocial engineering is out of authorization’s reach. A manipulated operator can still approve only what shaping renders, and the approval is attributed to themBounded
T15 Human ManipulationThe agent deceives its own human into approving or enabling harmConsent Evidence commits the disclosure as rendered, so the record shows what the trusted approval surface committed, never what the human perceived or understood. An accurately disclosed bad idea remains the human’s decision, and the record says soBounded
T16 Insecure Inter-Agent Protocol AbuseProtocol weaknesses let attackers manipulate coordination messages, memory, or protocol logic to bypass safeguards, including skipped consent checksA skipped protocol step cannot mint authority: approval is an event at the Mission Issuer, every hop authenticates with a sender-constrained credential, and each consequential action is checked against that hop’s own narrowed authority (a subset token under the act chain, or its Child Mission). The protocol weakness itself is untouched, and protocol security is the delegated layerBounded
T17 Supply Chain CompromisePoisoned prompts, fake agent identities, tampered tool metadata, or malicious updates corrupt the agent’s logicModel, dependency, and tool provenance belong to the software supply chain. On the authorization-shaped edge, capabilities bound to source digests fail closed on drift, an entry pinned to a resource contract fails closed when the resource changes what the action means, and a discovered tool still binds under encounter adjudication (Open-World Discovery, experimental)Delegated

Three contained, thirteen bounded, and one delegated. The threats that attack authority itself (privilege, attribution, identity) land on machinery built for them. The threats that attack the agent, its tool use, its memory, its goals, its protocols, or the humans around it are capped at the action gate. A misused tool, an injected goal, or a rogue instance still cannot exceed the committed authority, but the cause is untouched, so the chapter’s own rule grades those rows bounded. The supply chain is another layer’s job.

The 2026 Agentic Top 10, mapped

In December 2025 the same OWASP project distilled its agentic work into the Top 10 for Agentic Applications for 2026 (ASI01 through ASI10), and that list is now the checklist most reviews open with. It compresses cleanly onto the seventeen-threat crosswalk above, so the verdicts carry over rather than multiply:

Agentic Top 10 (2026)Lands onVerdict
ASI01 Agent Goal HijackT6 intent breaking: the goal can still be hijacked, and the PDP checks actions against the approved Mission, not the agent’s current goalBounded
ASI02 Tool Misuse and ExploitationT2: the misuse inside granted permissions is untouched, and per-action PEP/PDP with parameter binding at the tool boundary caps it at the committed authorityBounded
ASI03 Identity and Privilege AbuseT3 and T9: strict-subset derivation, attested instances, sender constraintContained
ASI04 Agentic Supply Chain VulnerabilitiesT17: the supply chain is another layer’s job, and discovered tools still bind under encounter adjudication (Open-World Discovery, experimental)Delegated
ASI05 Unexpected Code ExecutionT11: sandboxing owns execution, and consequential effects still need permitsBounded
ASI06 Memory and Context PoisoningT1: poisoned context steers proposals, never authority, and least exposure shrinks what can poisonBounded
ASI07 Insecure Inter-Agent CommunicationT12 and T16: influence carries no authority, since delegation only narrows and every hop re-authenticates, with transport the delegated layerBounded
ASI08 Cascading FailuresT4 and T5: expiry, fan-out bounds, metering, and cascade revocation cap the blast radiusBounded
ASI09 Human-Agent Trust ExploitationT14 and T15: disclosure integrity and the fatigue budget raise the bar, and a deceived human is still the residualBounded
ASI10 Rogue AgentsT13: the compromise is untouched, and instance-bound, mission-bound, revocable authority with cascade termination caps itBounded

The tally keeps the same shape. The authority-shaped risks land on machinery built for them, and the risks that live in the agent, the model, the supply chain, or the human stay bounded or delegated.

The LLM Top 10, split by layer

The Top 10 for LLM Applications, now in its 2026 edition, mixes layers, which makes it the better test of the delegated verdict. Half of it is not an authorization problem, and the table delegates that half by name:

Entry (2026 edition)The handbook’s answerVerdict
LLM01:2026 Prompt InjectionThe trifecta post carries this end to end: the injected instruction cannot widen committed authority, and the external leg needs a fresh parameter-bound permit. The mechanism is T6’s, but the threat here is the injected input itself, which the gate does not preventBounded
LLM02:2026 Sensitive Information DisclosureExposure discipline: bound what the agent may see as deliberately as what it may do, and mediated custody keeps credentials out of the leakable setBounded
LLM03:2026 Excessive AgencyThe handbook’s subject: authority derived from an approved task, narrowed for each delegate, and checked at each consequential action, with the class guard and, where adopted, action-bound approval on the high-consequence classes. On the paths the deployment governs, that prevents an action beyond the committed authority. OWASP’s risk also covers excessive functionality, permissions, and autonomy inside what was approved. An Authority Set approved broader than the task stays as broad as approved, and inside it a manipulated output can still trigger a damaging actionBounded
LLM04:2026 Supply ChainModel and dependency provenance, owned by the software supply chain. One authorization-shaped edge: capabilities bound to source digests fail closed on driftDelegated
LLM05:2026 Data and Model PoisoningTraining and embedding pipeline security, upstream of any authorization decisionDelegated
LLM06:2026 Unbounded ConsumptionExpiry on every Mission and metering (experimental) on spendBounded
LLM07:2026 MisinformationContent truth is semantic, and the gate is structuralDelegated
LLM08:2026 Hidden Context ExposurePrompt and context hardening belongs to the model layer. Authority lives in the Mission and its tokens, not in hidden context, and mediated custody keeps credentials out of the context, so exposed context discloses instructions and tool schemas, not powerDelegated
LLM09:2026 Vector and Embedding WeaknessesRetrieval pipeline security. What retrieval returns is untrusted content, and the taint response treats it that wayDelegated
LLM10:2026 Improper Output HandlingOutput causes harm when a downstream system acts on it, and no consequential action crosses the PEP without a permitBounded

OWASP’s mitigations for Excessive Agency are to minimize the extensions and their permissions, avoid open-ended functions, require human approval for high-impact actions, enforce authorization in downstream systems rather than trusting the model, and log everything. The handbook names a mechanism for each: authority derived from an approved task, the class guard and action-bound approval, PEP enforcement at the downstream boundary, and evidence joined on the Mission.

Three threats worth a closer look

Intent breaking is the taxonomy’s center, and the handbook’s enemy. T6 is prompt injection grown up. The attacker does not need to breach anything, only to change what the agent is trying to do. Every mitigation that asks the model to notice the manipulation is probabilistic. The handbook gives the same answer it gives the trifecta. The injection changed the agent’s mind, and the agent’s mind was never the source of authority. The Mission was committed at approval, the permit is checked at execution, and between those two points there is nothing the injected goal can rewrite. T6 is bounded rather than contained because the gate does not stop the manipulation, only what the manipulation can reach.

Overwhelming the human in the loop is an argument about grain. T10 is the taxonomy’s sharpest design question, because both naive answers lose. If humans approve every action, fatigue turns them into rubber stamps. If they approve nothing, governance is gone. The handbook’s grain is the Mission. A human, or a policy a human consented to, approves the envelope once, against a committed disclosure, and the per-action volume goes to the PDP, which does not tire. When the work outgrows the envelope, the discovery loop batches the overflow into a governed expansion request instead of a stream of interrupts. At Mission grain, approval fatigue remains a governance discipline rather than a solved problem, disclosure quality is what stands between an approver and a reflex, and the fatigue budget collects the controls that spend against it.

A rogue agent is an insider, and every agent here is treated as one. T13 assumes the attacker is already inside the system, wearing a legitimate agent. The handbook never trusted that agent more than its paperwork: its authority is a strict subset of its parent’s, its tokens are bound to its attested instance so they do not travel, its consequential actions need permits like everyone else’s, and when it is caught, revocation cascades through the delegation tree it belongs to. The multi-agent threats (T12 through T14) all get the same structural reply. Cooperation happens in messages, and messages carry no authority. T13 is bounded for the same reason as T6, because the compromise itself is untouched.

What the crosswalk does not claim

Three of this crosswalk’s ceilings are the trifecta post’s residuals, inherited unchanged. The verdicts are only as strong as PEP coverage, and an unmediated path is a threat with no verdict at all. The enforcement is structural, not semantic. Inside the approved scope, a compromised agent can still use the authority the Mission grants. Two ceilings are this crosswalk’s own.

  • Bounded is not prevented. For every bounded row the cause is untouched: the memory is still poisoned, the model is still fooled, the human is still tired. A bounded verdict claims only that the gate caps what the compromise can reach.
  • The delegated rows are real dependencies. Supply chain, poisoning, retrieval security, and sandboxing are layers the handbook composes with and cannot replace. A deployment that skips them leaves those threats open, whatever its authorization layer enforces.

The taxonomy’s own mitigation columns keep naming least privilege, human approval, complete mediation, and audit trails. The crosswalk above shows which of those the handbook turns into verifiable artifacts, and where the gate only caps what an attack can reach. The vendor test carries its six questions from here.