Safeguard
AI Security•

OWASP LLM Top 10 or Agentic Top 10: which should you map tools to?

Map tools to the OWASP LLM Top 10 for model-centred apps and to the Agentic Top 10 when software plans and acts. Many teams need both, so check design.

Safeguard Security Team
4 min read

Use the OWASP Top 10 for LLM Applications when your risk centres on a model inside an application, and the OWASP Top 10 for Agentic Applications when software plans, remembers and acts through tools. Many teams need both. Pick by architecture, then ask each tool to show coverage for the risks that apply to you.

What each list is

The OWASP GenAI Security Project publishes both. The LLM Top 10 2025 has ten entries, from LLM01 Prompt Injection through LLM10 Unbounded Consumption. They include sensitive information disclosure, supply chain, improper output handling, excessive agency, system prompt leakage and misinformation.

The Top 10 for Agentic Applications for 2026 was published on 9 December 2025, and OWASP describes it as a peer-reviewed framework for the most critical risks to autonomous and agentic AI systems, developed with more than 100 experts. Read the official document for its exact categories before you quote them.

Choosing by architecture

Your systemStart withWhy
Chat feature that answers questions from a modelLLM Top 10Risks sit in prompts, outputs and data
Retrieval over your documentsLLM Top 10Vector and data risks matter
Assistant with tools that actBothModel risks plus the risks of acting
Several agents coordinatingAgentic Top 10 first, then LLMDelegation and autonomy dominate
Coding assistant in the developer workflowBothTool access and supply chain together

Excessive agency appears in the LLM list already. OWASP defines it as a system taking damaging actions in response to unexpected, ambiguous or manipulated output, with excessive functionality, permissions and autonomy as root causes. That entry is the bridge between the two lists.

How to use a list when buying

Do not accept "covers the OWASP Top 10" as an answer. Ask for a table: each entry, what the tool does about it, and how you can verify. Mark the entries as detect, prevent, or not covered. An honest vendor will have not covered rows. A page that claims all ten should lead you to ask for the test.

Keep in mind that a list is a prioritised awareness document. It does not tell you which of your own systems are affected, and it does not measure a product.

A simple method

  1. Draw your architecture and mark where a model decides something.
  2. Mark where it can call a tool or change data.
  3. Choose the list or lists that match.
  4. For each entry, write a one line statement of your exposure.
  5. Compare candidate tools against your highest exposures first.

See also what a tool claim should mean.

Try it yourself

Click through it at your own pace, or open it full screen.

See how one control maps to several frameworks, then imagine doing the same for each OWASP entry.

Quick check

Are the OWASP lists a standard I can certify against?

No. They are awareness and guidance documents, not certifications.

Which list changes more often?

Check the publication dates on both pages. The LLM list carries a 2025 edition and the agentic list a 2026 edition.

Safeguard offers policies and guardrails, an MCP Guardrail and dependency scanning that relate to supply chain and agency risks, and a free scan.

Sources

Last reviewed: 19 October 2026.

Never miss an update

Weekly insights on software supply chain security, delivered to your inbox.

Self-healing security runs on Safeguard.

Your first fix PR is minutes away.

No sales call required, even your agent can complete the purchase over MCP.