Template, read 16 November 2026
Blue team report template and what it must contain
Open the scoping sheetSee the frameworks table
The attack, red side
They deactivate command and control, set scope and date kill switches, remove backdoors and malware, and securely delete compromised credentials.
Recommendations, in the red team reportConcrete remediations tied to findings, with a priority.
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
Free to reuse under CC BY 4.0. Open the scoping sheet to print it.
What goes in a blue team report?
A blue team report answers one question: what did the defenders see, and when? TIBER-EU requires, for each attack step described by the red team, a list of detected actions, threat hunting activity and configuration changes, log entries, and a timeline mapped to both teams' actions.
It also requires the red team artifacts the blue team found, an assessment of the red team findings, the evidence collected, a root cause analysis of successful attacks, lessons learned and topics for the purple teaming exercise.
When is the blue team report written?
The blue team report is written after the test, once the blue team has at least a draft of the red team report and before the replay and purple teaming sessions. Under the EU rules it is due within 10 weeks of the end of active testing.
The guidance recommends an executive summary suitable for senior management and a board.
Template: fields to fill in
Copy the fields below into your own document. Fields follow the TIBER-EU required content and the context items the guidance suggests.
| Section | Fields to fill in |
|---|---|
| 1. Executive summary | What was tested, headline result, main lessons, for senior management. |
| 2. Blue team context | Structure and size of the blue team, levels of responsibility (for example level 1, 2, 3), outsourced duties and providers, sources of information such as log types. |
| 3. Timeline of events | One timeline mapping red team actions (from the red team report) to blue team actions. |
| 4. Detections per attack step | For each red team step: detected or not, time, alert or log entry, who acted. |
| 5. Threat hunting and changes | Hunting performed and configuration changes (firewall rules, detection rules, hardening) during or after active testing. |
| 6. Artifacts found | Remaining red team artifacts, where and when found, whether the red team told the blue team. |
| 7. Assessment of red team findings | Agree or dispute each finding and recommendation, with evidence. |
| 8. Root cause analysis | Why each successful attack worked. |
| 9. Lessons learned | Strengths, gaps and potential for improvement. |
| 10. Purple session topics | Topics to examine together with the red team in the replay and purple session. |
Related pages
- Blue team: what a blue team does and how it is tested
- Red team report: what it must contain, with a template
- Red team debrief: how to turn findings into fixes
- Purple team exercise: how it runs, step by step
- Replay exercise, defined
- Red team vs blue team: roles, goals and how they meet
- Purple team: what it is and who is in the room
Sources
- European Central Bank, TIBER-EU Blue Team Test Report Guidance, 2025, read 16 November 2026
- EUR-Lex, Commission Delegated Regulation (EU) 2025/1190 (TLPT technical standards), read 16 November 2026
Last reviewed 16 November 2026.