RS Glossary
Red Teaming
Red teaming is an authorized, structured exercise in which participants act like adversaries, harmful users, or failure-seeking evaluators to expose vulnerabilities, unsafe behavior, and weaknesses in a system or its safeguards.
- Review state
- Reviewed in POC
- Freshness
- Current
- Version
- 1
- red-teaming
Remember it this wayThink like the threat, within rules.
In plain language
A red team tests the system from the side of the threat. It uses agreed scenarios, boundaries, and evidence collection to discover how the system can fail before a real attacker or harmful situation does.
Why it matters
Normal testing often checks whether expected behavior works. Red teaming explores misuse, manipulation, edge cases, and interactions that ordinary test plans may miss. Its findings can improve safeguards and reveal residual risk.
Example
Before deploying an internal AI assistant, an authorized team tries prompt injection, attempts to obtain restricted data, supplies misleading context, and tests whether the system's refusal behavior survives multi-turn pressure. The team records methods and outcomes for remediation.
Common misconception
Red teaming is not random abuse, permission to cause harm, or a complete guarantee of safety. It requires scope, authorization, controls, and documented results. Adversarial review is broader and can challenge a single claim, plan, or artifact without simulating a threat actor.
Related terms
Sources
- NIST, “Artificial Intelligence Risk Management Framework: Generative Artificial Intelligence Profile”AI red-teaming, independent evaluation, role separation, and structured risk measurement.
- NIST, “Assessing Risks and Impacts of AI: Pilot Evaluation Report”documented model testing, red teaming, and field testing in an AI evaluation program.
Learn more
Public history
24 recorded events · 24 public summaries
Candidate vocabulary was imported from the Learning Lab discovery queue.
The captured candidate received a complete initial draft and entered section-level human review.
Radar reviewed the initial definition draft for human consideration.
Radar reviewed the initial plain-language-explanation draft for human consideration.
Radar reviewed the initial why-it-matters draft for human consideration.
Radar reviewed the initial example draft for human consideration.
Radar reviewed the initial common-misconception draft for human consideration.
Radar reviewed the initial remember-it-this-way draft for human consideration.
Radar reviewed the initial related-terms draft for human consideration.
Radar reviewed the initial sources draft for human consideration.
Radar reviewed the initial learn-more draft for human consideration.
A proposal was opened for section-level human review while preserving the current version.
A human reviewer opened a proposed revision while preserving the current approved or captured version.
definition approved by a human reviewer.
plain-language-explanation approved by a human reviewer.
why-it-matters approved by a human reviewer.
example approved by a human reviewer.
common-misconception approved by a human reviewer.
Radar issue red-teaming-merge-boundary was accepted-as-is by the human section decision.
remember-it-this-way approved by a human reviewer.
sources approved by a human reviewer.
learn-more approved by a human reviewer.
related-terms approved by a human reviewer.
All section gates are approved; content version 1 is now a fully approved term.
Source: vault/Glossary/terms/red-teaming/term.md · sha256:b8e3a0604fe1a4cca26601fabc2d6b5b12a4fb3651fda3e9362137ab915e2da8 · Release: rs-glossary-glossary-team-poc-0.5.5-2026-09-02