Skip to content

Category 9 of 12 · Controls: Testing before and after deployment

Red teaming and evaluation

Automated and managed adversarial testing of models and agents for injection, jailbreaks, data leakage, and unsafe tool use, before release and continuously after.

Mitigates: ASI01 Agent Goal Hijack, ASI02 Tool Misuse and Exploitation, ASI05 Unexpected Code Execution, LLM01 Prompt Injection · MITRE ATLAS AML.T0051, AML.T0054

Vendors, by signal score

Ranked within this category only. How the score works.

Also covers this category

Questions to ask a vendor

  1. Does it test multi-step agent behaviour and tool use, not only single prompts?
  2. Can tests run in CI on every model or prompt change?
  3. Are findings mapped to OWASP and MITRE ATLAS IDs?

Go deeper

FAQ

Is open source red teaming enough?
Open source harnesses such as garak, PyRIT, and promptfoo cover a lot of ground and are a good start. Commercial tools add managed attack libraries, agent-level scenarios, and reporting.
How often should agents be red teamed?
On every material change to the model, prompts, tools, or permissions, which in practice means continuously in CI.