Explainer, read 16 November 2026
Blue team: what a blue team does and how it is tested
Open the scoping sheetSee the frameworks table
The attack, red side
Reconnaissance: collect as much information as possible on the target.
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. |
What is a blue team in cyber security?
A blue team is the group responsible for defending an enterprise's use of information systems by maintaining its security posture. The NIST glossary, citing CNSSI 4009-2022, adds that it defends against real or simulated attacks over a significant period, in a representative operational context.
The Singapore guidelines describe it as made up of resources from the security operations center, the incident response teams and other supporting teams, employed or contracted to detect or prevent an attack and respond to it.
What does a blue team do?
A blue team prevents, detects and responds. The Singapore guidelines list baseline activities: establish a security operations center, internal or external, an incident response plan and an incident response team. Additional activities are threat hunting, incident response and digital forensics.
Because the exercise tests incident and crisis response, the blue team needs an incident response playbook to respond to attacks and remediate incidents.
How is a blue team tested?
A blue team is tested by an attack it does not know about. In a TIBER-EU test the blue team's prevention, detection and response are tested without foreknowledge, and only the control team knows. Afterward the blue team writes its own report.
The blue team report lists the detected attack actions for each red team step, the log entries, a timeline, the artifacts it found, its root cause analysis and lessons learned. See the blue team report template.
What do outside providers offer to a blue team?
Several firms sell blue team coaching and joint exercises. Mandiant lists a Purple Team Assessment, Cisco Talos describes its own blue team sitting beside the customer's defenders, and Sygnia describes guided investigation training during live attack scenarios. The services directory lists each firm's own wording.
Related pages
- Blue team report template and what it must contain
- Red team: what a red team is and what it delivers
- Purple team: what it is and who is in the room
- Red team vs blue team: roles, goals and how they meet
- Who offers red team services?
- Red team debrief: how to turn findings into fixes
- Who are red teamers, and how do you become one?
Sources
- 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
- European Central Bank, TIBER-EU Blue Team Test Report Guidance, 2025, read 16 November 2026
- Mandiant, Red Team Assessment datasheet (the firm's own document), read 16 November 2026
- Cisco Talos Incident Response, Purple Team page (the firm's own page), read 16 November 2026
- Sygnia, Purple Teaming page (the firm's own page), read 16 November 2026
Last reviewed 16 November 2026.