Red teaming

Spec sheet // Glossary // RED TEAMING
Glossary / R / Red teaming
Glossary · AI and model risk

Red teaming

Also called AI red teaming, adversarial testing

Definition

AI red teaming is structured adversarial testing in which experts try to make an AI system fail, misbehave or cause harm before and after it goes live. Testers probe for jailbreaks, prompt injection, data leakage, biased or harmful outputs and unsafe actions, so weaknesses can be fixed and controls tested.

SCOPEATTACKLOGFIXRETEST
Fig. 1 · Red teaming
EU AI Act, Article 55 · NIST AI 600-1
Key rulesEU AI Act, Article 55 · NIST AI 600-1
Applies toProviders of general-purpose AI models with systemic risk
RegionsGlobal · EU · US
01

How it works

A red team agrees the scope, the harms that matter for the use case and the success criteria, then attacks the model or application. Manual testers write creative prompts and multi-step attacks, while automated tools generate large numbers of variations and score the outputs. For a bank chatbot, testers might try to extract other customers' data, get the model to give regulated advice or bypass its guardrails with role-play.

Findings are logged with severity, reproduced and passed to developers, who change prompts, filters, training data or system permissions, after which the red team retests. Results feed model validation, the model inventory and go-live decisions. Firms repeat red teaming when the model, data or connected tools change, because agentic systems that can take actions widen the range of possible failures.

Step 1ScopeDefine the system, use case and harms to test.
Step 2AttackRun manual and automated adversarial prompts and scenarios.
Step 3Log findingsRecord each failure with severity and steps to reproduce.
Step 4FixChange prompts, filters, data or permissions.
Step 5RetestConfirm fixes and repeat after material changes.
02

The rules

EU · 2 August 2025EU AI Act, Article 55Regulation (EU) 2024/1689 (Artificial Intelligence Act), Article 55, Obligations for providers of general-purpose AI models with systemic risk

Requires providers to evaluate their models using state-of-the-art protocols, including conducting and documenting adversarial testing, and to assess and mitigate systemic risks.

Providers of general-purpose AI models with systemic risk
US · 26 July 2024NIST AI 600-1NIST AI 600-1, Artificial Intelligence Risk Management Framework: Generative Artificial Intelligence Profile

Lists generative AI risks and recommends actions including AI red teaming to test for harmful outputs, information security weaknesses and misuse.

Voluntary for organisations developing or using generative AI
03

Common questions

How is AI red teaming different from penetration testing?

Penetration testing looks for security weaknesses in networks and applications. AI red teaming also tests model behaviour, such as harmful or biased outputs, hallucinations and whether guardrails can be bypassed with crafted prompts.

Who should carry out AI red teaming?

A mix of internal testers independent of the build team, domain experts such as compliance staff, and external specialists. Automated tools add scale but do not replace human creativity.

Is AI red teaming required by law?

The EU AI Act requires adversarial testing for general-purpose AI models with systemic risk. For other systems, it is expected practice under model risk and AI governance frameworks.