Skip to content

Template, read 16 November 2026

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

Open the scoping sheetSee the frameworks table

The attack, red side

Step 5: Actions on target

Actions on target: gain further access and reach the objective.

From What does a red team do?

Download the templates

Free to reuse under CC BY 4.0. Open the scoping sheet to print it.

What should a red team report contain?

It should contain the attack story and the findings. TIBER-EU requires: the targeted functions and systems; a summary of each scenario; flags reached and not reached; attack paths followed successfully and unsuccessfully; techniques used successfully and unsuccessfully; deviations from the plan; and leg-ups granted.

It also needs the blue team actions the testers are aware of, stealth techniques used and whether detection was adequate, findings categorized by NIST function, criticality and complexity, a provisional root cause analysis, and recommendations for remediation.

Is a red team test a pass or fail?

No. 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. The report is written to feed the replay, the purple session and the remediation plan.

A reader who wants a score should note that the sources read do not define one.

Who is the report for?

Several readers, so it has layers. TIBER-EU asks for a short narrative in lay terms for senior management and governance bodies, covering what was tested, a high-level timeline, the main findings, categories of recommendations and any significant exceptions. A storyline per scenario, in line with MITRE ATT&CK, is for the staff of the tested entity.

What does a red team report template look like?

Use the outline below, based on the TIBER-EU required content. Fields can be adjusted to your scheme.

Table for: What does a red team report template look like
SectionFields
1. Management summaryFunctions and systems tested; timeline; scenarios; main findings; recommendation categories; exceptions.
2. Scope and planFunctions, systems, flags, deviations from the plan, leg-ups with date and reason.
3. Storyline per scenarioSimulated actor; in, through and out phases; techniques mapped to MITRE ATT&CK; flags reached and not reached.
4. Attack paths and detectionSuccessful and unsuccessful paths with techniques; stealth techniques used; whether the entity's detection capability was adequate and, if not, what to improve; the threat actor sophistication actually needed.
5. Blue team actionsDefender actions the testers are aware of, with a timeline and logs the blue team can use for its own report.
6. FindingsFor each: category by NIST function (Identify, Protect, Detect, Respond, Recover), criticality and complexity, how the entity was compromised and the impact.
7. Provisional root causesRoot causes across people, process and technology, rated by criticality, and what further attack was possible with more time.
8. RecommendationsConcrete remediations tied to findings, with a priority.

How soon is the report due?

Under the EU technical standards the testers deliver the red team test report to the control team within 4 weeks of the end of active testing. CBEST says a draft penetration test report should be issued within a period agreed with the regulator, generally no later than two weeks after testing.

Sources

  1. European Central Bank, TIBER-EU Red Team Test Report Guidance, 2025, read 16 November 2026
  2. European Central Bank, What is TIBER-EU?, read 16 November 2026
  3. EUR-Lex, Commission Delegated Regulation (EU) 2025/1190 (TLPT technical standards), read 16 November 2026
  4. Bank of England, CBEST Implementation Guide, 2024 edition, read 16 November 2026
  5. Association of Banks in Singapore, Red Team: Adversarial Attack Simulation Exercise Guidelines, September 2024, read 16 November 2026

Last reviewed 16 November 2026.