Skip to content

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

Step 7: Leaving the systems

They deactivate command and control, set scope and date kill switches, remove backdoors and malware, and securely delete compromised credentials.

From What does a red team do?

Step 10: Remediation

Recommendations, in the red team reportConcrete remediations tied to findings, with a priority.

From Red team report: what it must contain, with a template

Download the templates

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.

Blue team report template and what it must contain
SectionFields to fill in
1. Executive summaryWhat was tested, headline result, main lessons, for senior management.
2. Blue team contextStructure 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 eventsOne timeline mapping red team actions (from the red team report) to blue team actions.
4. Detections per attack stepFor each red team step: detected or not, time, alert or log entry, who acted.
5. Threat hunting and changesHunting performed and configuration changes (firewall rules, detection rules, hardening) during or after active testing.
6. Artifacts foundRemaining red team artifacts, where and when found, whether the red team told the blue team.
7. Assessment of red team findingsAgree or dispute each finding and recommendation, with evidence.
8. Root cause analysisWhy each successful attack worked.
9. Lessons learnedStrengths, gaps and potential for improvement.
10. Purple session topicsTopics to examine together with the red team in the replay and purple session.

Sources

  1. European Central Bank, TIBER-EU Blue Team Test Report Guidance, 2025, read 16 November 2026
  2. EUR-Lex, Commission Delegated Regulation (EU) 2025/1190 (TLPT technical standards), read 16 November 2026

Last reviewed 16 November 2026.