# 25 red team terms, each with a sourced example

Glossary, read 10 November 2026

**In short.** 25 terms from red, blue and purple teaming, from rules of engagement and the white team to leg-ups, flags and attestations. Each has a plain definition and an example quoted from NIST, the ECB, the EU rules, the Singapore guidelines, MITRE or the Australian framework, with the read date.

## What do red team terms mean?

These 25 terms are the words a red team engagement uses. Each entry defines the term in plain language and quotes a source. Start with red team, blue team, purple team and white team, then the terms for the rules and reports.

- [Adversary emulation](/glossary/adversary-emulation/): Testing that copies the known behavior of a named threat actor, step by step, so defenders can see whether the
- [Adversary simulation](/glossary/adversary-simulation/): Testing in which a team models and carries out an attack from threat intelligence about the adversaries likely
- [Assumed breach](/glossary/assumed-breach/): A red team design that starts with the attacker already inside, usually with a workstation or account
- [Attestation](/glossary/attestation/): A formal statement from the authority that a threat-led test followed the rules
- [Blue team](/glossary/blue-team/): The people who defend an organization's systems day to day, such as the security operations center and inciden
- [Catch-and-release](/glossary/catch-and-release/): A limited collaborative step in a live test: testers continue a scenario, are detected, and then resume
- [Concession](/glossary/concession/): Planned help given to the attackers during an exercise, such as a laptop, an account or information about an a
- [Control team](/glossary/control-team/): The tested organization's own small team that runs a threat-led test from its side: it approves changes, manag
- [Critical or important function](/glossary/critical-or-important-function/): A business function whose failure would seriously harm the organization or its customers
- [Flag](/glossary/flag/): A target the testers must reach to show an attack succeeded, such as access to a data set or the ability to al
- [Kill switch](/glossary/kill-switch/): A built-in way to make testing tools stop working outside the agreed scope or date
- [Leg-up](/glossary/leg-up/): Help from the tested organization that lets testers continue when they cannot advance on their own, such as an
- [Letter of engagement](/glossary/letter-of-engagement/): A short signed document from senior management that authorizes the exercise and says how testers can prove the
- [MITRE ATT&CK](/glossary/mitre-attack/): A public catalog of attacker tactics and techniques drawn from real-world observation
- [No-fly zone](/glossary/no-fly-zone/): A system, area or function that testers must not touch because the risk of damage is too high
- [Penetration test](/glossary/penetration-test/): A scoped security test in which assessors try to breach a system with an attacker's tools to learn which weakn
- [Purple team](/glossary/purple-team/): A collaborative exercise, not a separate staff, in which attackers and defenders work together in the open so 
- [Red team](/glossary/red-team/): A group authorized to act as an attacker against an organization, using the methods a real adversary would use
- [Remediation plan](/glossary/remediation-plan/): The tested organization's written plan to fix what the test found
- [Replay exercise](/glossary/replay-exercise/): A session after the test in which testers and defenders walk through what each side did, step by step, using b
- [Rules of engagement](/glossary/rules-of-engagement/): The written limits and permissions for a test: what may be touched, which methods are allowed, who to call, wh
- [Tactics, techniques and procedures (TTPs)](/glossary/ttps/): The way an attacker works: the goals they pursue (tactics), the methods used (techniques) and the exact steps 
- [Threat intelligence provider](/glossary/threat-intelligence-provider/): A firm that studies who is likely to attack the organization and how, and hands the red team realistic scenari
- [Threat-led penetration testing (TLPT)](/glossary/threat-led-penetration-testing/): The EU term for a red team style test on live systems that follows threat intelligence about the entity
- [White team](/glossary/white-team/): The small group on the tested side that knows about a covert test and referees it

## Related pages

- [15 questions about red teams, answered](/faq/)
- [Red team: what a red team is and what it delivers](/red-team/)
- [Red team process: the phases of an engagement](/engagement/red-team-process/)
- [Red team frameworks by regulator: TIBER-EU, DORA, CBEST, iCAST, AASE and CORIE](/frameworks/)

Last reviewed 16 November 2026. Canonical: https://redteamvsblueteam.com/glossary/
