Red-Teaming
Adversarial testing of AI systems to find failure modes before deployment.
Red-teaming (from military/security practice) is the process of deliberately attacking or stress-testing an AI system to surface failures โ before real users or adversaries do.
What red teams look for in AI:
- Jailbreaks โ prompts that bypass safety guidelines
- Harmful content โ can the model be induced to produce misinformation, malware, dangerous instructions?
- Bias and fairness failures โ differential treatment of demographic groups
- Prompt injection โ can adversarial content in external data control the agent?
- Capability elicitation โ can the model do things it shouldn't, even if not normally willing?
- Specification gaming โ does the model find unexpected ways to satisfy the letter but not spirit of instructions?
Methods:
- Manual red-teaming โ human experts crafting adversarial prompts (most creative, most expensive)
- Automated red-teaming โ use a separate LLM to generate adversarial prompts at scale
- Structured evaluation sets โ standardised benchmarks like HarmBench, StrongREJECT
Why it matters: All major AI labs run extensive red-teaming before releases. The US AI Safety Institute (AISI) and UK AISI conduct independent red-teaming of frontier models under safety commitments.
In plain terms
Hiring a security firm to break into your building before you open โ finding the unlocked back door before a real thief does.
Related concepts
AI Safety
The field working to ensure AI systems do what humans actually want โ now and as they become more capable.
Prompt Injection
A security attack where malicious instructions hidden in content hijack an AI agent.
Large Language Model
AI trained on vast text to understand and generate language.
AI Benchmark
Standardised tests that measure what a model can actually do.