Explainer, read 16 November 2026
Red team vs blue team: what each does and how an engagement runs
One attack, ten steps, told from both sides
-
Red team attacks
Reconnaissance: collect as much information as possible on the target.
Purple what both learn
The frameworks use covert tests to measure and open exercises to teach.
From Red team vs blue team vs purple team: a three-way table
Blue team defends
A blue team is tested by an attack it does not know about.
-
Red team attacks
The team gained initial access to two workstations at separate sites through spearphishing after open-source research on targets.
Purple what both learn
One of CISA's actions to takeEnforce phishing-resistant MFA to the greatest extent possible.
Blue team defends
The organization did not detect the activity at any point.
-
Red team attacks
Used directory data to find standard user accounts with administrative access and ran a second phishing campaign against them.
Purple what both learn
Run the chosen techniques while the blue team watches, tunes and responds.
Blue team defends
Host and network monitoring was insufficient.
-
Red team attacks
The team gained persistent access, moved laterally across sites and reached systems adjacent to sensitive business systems.
Purple what both learn
One of CISA's actions to takeEstablish a baseline of normal network activity and tune tools to detect anomalies.
Blue team defends
The organization failed to detect lateral movement, persistence and command and control.
There was little monitoring of endpoint management systems, which the team used to gain root access across the network.
-
Red team attacks
Actions on target: gain further access and reach the objective.
Purple what both learn
The ECB says a TIBER-EU test does not produce a pass or fail but an insight into strengths and weaknesses and a focus on learning.
Blue team defends
MFA prompts stopped the team from reaching one sensitive system, and it could not finish its plan for a second within the assessment period.
-
Red team attacks
In Phase II it tried to trigger a security response from the organization's people, processes or technology.
Purple what both learn
One method of limited purple teamingCatch-and-release, where testers continue, get detected and then resume.
Blue team defends
Most Phase II actions drew no response.
-
Red team attacks
They deactivate command and control, set scope and date kill switches, remove backdoors and malware, and securely delete compromised credentials.
Purple what both learn
Purple session topicsTopics to examine together with the red team in the replay and purple session.
Blue team defends
Artifacts found, in the blue team reportRemaining red team artifacts, where and when found, whether the red team told the blue team.
-
Red team attacks
Red team test report: flags reached, attack paths, techniques, leg-ups, findings, within 4 weeks of testing (EU rules).
Purple what both learn
Both reports are shared in advance so each side can prepare.
Blue team defends
Blue team test report: detections per step, timeline, artifacts found, lessons, within 10 weeks (EU rules).
-
Red team attacks
The red side runs attacker techniques.
Purple what both learn
Replay the engagement using the red team and blue team reports, so each side explains what it did and saw.
Blue team defends
The blue side focuses on detecting them and improving its response.
-
Red team attacks
Recommendations, in the red team reportConcrete remediations tied to findings, with a priority.
Purple what both learn
Record detections added, gaps found and open items, and feed them into the remediation plan.
Blue team defends
Root cause analysis, in the blue team reportWhy each successful attack worked.
Set any two side by side
| Point | Red team | Blue team |
|---|---|---|
| Purpose in a test | Emulate an adversary to show impact and what works for defenders (NIST). | Defend against real or simulated attacks over a significant period (NIST). |
| Who they are | Internal or hired testers, often a provider's team with a manager, testers and sometimes an exploit developer. | The organization's security operations center, incident response and support teams (Singapore guidelines). |
| Knowledge of the test | Know the plan and the scope. | Tested without foreknowledge in a covert test; only the control team knows (ECB). |
| Main report | Red team test report: flags reached, attack paths, techniques, leg-ups, findings, within 4 weeks of testing (EU rules). | Blue team test report: detections per step, timeline, artifacts found, lessons, within 10 weeks (EU rules). |
| What is measured | Whether objectives were reached and by which path. | Whether the attack was prevented, detected and handled. |
Download the templates
- DOCXScoping sheet, Word50 questions, blank answer column, landscape, 10 KB
- CSVScoping sheet, CSV50 rows with why each matters and its source
- JSONScoping sheet, JSON50 rows, edition and license in the file
- CSVFrameworks by regulator, CSV7 rows with provider rules, phases and timing
- JSONFrameworks by regulator, JSON7 rows with the source and read date
Free to reuse under CC BY 4.0. Open the scoping sheet to print it.
Frameworks by region and sector
Filter the regulator frameworks from the frameworks table by where a firm is and what it does. Rows stay in the table's order.
All 7 rows shown.
| Framework | Region | Sector, as the regulator words it | Year |
|---|---|---|---|
| TIBER-EU | European Union | Financial entities providing core financial infrastructure; usable in all critical sectors | Published May 2018; updated 2024; current framework document dated January 2025 |
| DORA threat-led penetration testing | European Union | Financial entities identified by the authorities, other than microenterprises | Regulation of 14 December 2022; technical standards of 13 February 2025 |
| CBEST | United Kingdom | Firms and financial market infrastructures | In use since 2014; implementation guide 2024 edition |
| iCAST | Hong Kong | Authorized institutions (banks) | Cybersecurity Fortification Initiative launched 2016; version 2.0 effective 1 January 2021 |
| AASE | Singapore | Financial institutions | Industry guidelines version 1 November 2018; current edition September 2024; MAS guidelines January 2021 |
| CORIE | Australia | Financial institutions, including financial market infrastructure | Launched December 2020; version 2.0 July 2022 |
| United States | United States | Not applicable | NIST SP 800-53 Rev. 5 (control CA-8(2)); CISA advisory of 28 February 2023 |
What is the difference between a red team, a blue team and a purple team?
A red team is a group authorized to emulate an attacker against an organization. A blue team is the group that defends it, and a purple team exercise brings the two together so detections are tested and improved as the techniques run. NIST, the ECB and the Singapore bank guidelines are the sources for the definitions.
The three-way comparison sets them side by side, and the red team vs penetration testing page explains why a red team test is not a longer penetration test.
Where should you start?
Start with the question you have. To commission a test, fill in the scoping sheet and read what to ask a provider. If a regulator is involved, read the frameworks table. To understand the roles, read the red team page first.
Sources
- NIST CSRC Glossary, red team, read 16 November 2026
- NIST CSRC Glossary, blue team, read 16 November 2026
- Association of Banks in Singapore, Red Team: Adversarial Attack Simulation Exercise Guidelines, September 2024, read 16 November 2026
- European Central Bank, What is TIBER-EU?, read 16 November 2026
Last reviewed 16 November 2026.