What the existing frameworks don't see.
The Agent Threat Matrix sits alongside OWASP Top 10 for LLM and MITRE ATLAS. This page measures the overlap, and the agent-layer threats that neither framework was built to address.
How much falls through the cracks
23 of 61 techniques (38%) in the matrix are covered by neither OWASP Top 10 for LLM nor MITRE ATLAS. These are the threats that live in the agent layer: governance, protocols, memory, identity, skills, and infrastructure.
Not covered by OWASP or ATLAS · 23
Every technique below is unaddressed by both external frameworks. They are the reason the matrix exists.
Where each framework draws the line
The three efforts are complementary. Each owns a layer; together they span model, agent, and exposure.
OWASP Top 10 for LLM
Prompt injection, output handling, supply chain, info disclosure, excessive agency, overreliance.
Agent protocols (MCP, A2A), governance file manipulation, memory persistence, cross-agent lateral movement, sandbox escape, heartbeat attacks, identity attacks.
MITRE ATLAS
Reconnaissance, initial access (adversarial ML), credential access, model extraction, data poisoning.
Agent infrastructure, skill supply chain, MCP/A2A exploitation, governance files, memory poisoning, heartbeat persistence, webhook exfiltration.
Agent Threat Matrix
The agent layer between the model and the user: governance, protocols, memory, identity, skills, and infrastructure.
Model-level attacks (adversarial examples, training poisoning), enterprise network attacks.
Uncovered by each, individually
Looked at one framework at a time, before intersecting them, the blind spots are wider still.
Not in OWASP LLM
31of 61techniques fall outside OWASP's LLM Top 10.
Not in MITRE ATLAS
42of 61 techniques fall outside MITRE ATLAS.