Skip to main content

What this is

One row per shipped probe in src/agent_guardian/probes/. Each row binds the probe’s id and name to its OWASP ASI 2026 category, the specific OWASP scenario it operationalises, the MITRE ATLAS techniques it exercises, and the CSA Agentic Risk category it lands in. This is what scan.json writes into every findings[].asi / findings[].mitre_atlas / findings[].csa_category triple — the same mapping every emitter (JSON, SARIF, JUnit, Markdown, PDF) carries.

When to use this

  • You opened a finding and want to know exactly which OWASP / MITRE / CSA buckets it touches.
  • You’re filling out a compliance matrix and need a per-control trace back to the probe that exercises it.
  • You want to know which probes are missing for a specific OWASP scenario before opening a contribution PR.
  • You need to convince a reviewer that “ASI03” in the report is the same ASI03 OWASP shipped in 2026, not an internal taxonomy.

How the mapping is generated

The rows below are extracted from the asi, owasp_scenario, mitre_atlas, and csa_category keys on every *.yaml under src/agent_guardian/probes/. The loader at src/agent_guardian/probes/loader.py is the same code path that populates the canonical scan.json — there is no second table, no human-curated rewrite. Source-of-truth = the YAML files.

ASI category totals

96 probes ship in this release, distributed across the ten OWASP ASI 2026 categories. Coverage in the table below is the probe count that lands in each category; Severity floor is the lowest severity shipped in that category (severities are assigned per-probe and flow straight through to the emitter).

Canonical probe → OWASP mapping

ASI01 — Prompt Injection / Goal Hijack

ASI02 — Tool Misuse

ASI03 — Privilege Compromise

ASI04 — Resource Overload / Supply Chain

ASI05 — Cascading Hallucination → Code Execution

ASI06 — Memory Poisoning

ASI07 — Misalignment / A2A Trust

ASI08 — Cascading Failure

ASI09 — Identity Spoofing / Output Handling

ASI10 — Untraceability / Goal Drift

OWASP LLM Top 10 (2025) crosswalk

The OWASP LLM Top 10 is a separate (model-centric) list from ASI 2026 (agent-centric). Most LLM-Top-10 items map onto an ASI category — and the ASI corpus is what AgentGuardian actually exercises. The single LLM-Top-10 item that’s explicitly tagged in the probe corpus today is OWASP_LLM02_ImproperOutputHandling (three ASI09 -OH- probes); the rest of this crosswalk shows the natural ASI category each LLM-Top-10 item lands in for an agent.
Only LLM02 — Improper Output Handling is asserted as a first-class owasp_scenario in the probe YAML today (three ASI09 -OH- probes). Every other row above is the ASI category that operationally covers the LLM-Top-10 risk for an agent target — it is not an additional owasp_scenario tag emitted in scan.json. If you need LLM-Top-10 trace IDs in your report, post-process findings[].asi / findings[].probe_id using this table.

How to interpret a finding’s mapping

A scan.json finding carries the OWASP / MITRE / CSA triple directly:
Read it in this order:
  1. probe_id — the row in the per-ASI table above. That row is the ground truth for everything else.
  2. asi — the OWASP ASI 2026 category. Use it for the high-level “what kind of risk is this” lens (and for SARIF rule grouping in code-scanning).
  3. mitre_atlas — the techniques the probe exercises. Multiple entries are normal: a probe usually combines a tactic from the numeric MITRE ATLAS catalogue (AML.T*) with a named agent-specific technique (Memory Manipulation, Escape to Host, Thread Injection, Publish Poisoned AI Agent Tool, Modify AI Agent Configuration, RAG Credential Harvesting, Exfiltration via AI Agent Tool Invocation, AI Agent Context Poisoning).
  4. csa_category — the CSA Agentic Risk taxonomy bucket. Use it when reporting into a CSA-aligned risk register.

Next step

Reports overview

See the five emitters that carry this mapping into JSON, SARIF, JUnit, Markdown, and PDF.

Signatures & trust

The mapping rides inside the Ed25519-signed envelope — verify it end-to-end with agent-guardian verify.

Attack library

Browse the same probe corpus organised by attack technique, with payload seeds and detection logic.

Contributing a probe

Add a probe and its OWASP / MITRE / CSA triple — the YAML schema that drives this table.