# Purple team exercise: how it runs, step by step

Process, read 16 November 2026

**The short answer.** A purple team exercise is a planned, open session in which red team testers and blue team defenders replay selected attacks together. In TIBER-EU and the EU rules the exercise follows the replay, must finish within 10 weeks of the end of testing, and covers topics both sides choose. Read 16 November 2026.

## How does a purple team exercise run?

A purple team exercise runs in an agreed sequence with both teams present. TIBER-EU requires the stakeholders to define the scope, goals, objectives, timing and rules of engagement for the purple activities, and to review risk controls, before any technique is run.

The steps below follow the TIBER-EU guidance and the EU technical standards.

1. Agree scope, goals and rules of engagement for the session.
2. Choose topics together: vulnerabilities found, issues the testers could not test during active testing, other steps the testers could have taken, alternative scenarios, proofs of concept, anticipated remediation and business continuity exercises.
3. Replay the engagement using the red team and blue team reports, so each side explains what it did and saw.
4. Run the chosen techniques while the blue team watches, tunes and responds.
5. Record detections added, gaps found and open items, and feed them into the remediation plan.

## How long does a purple team exercise take?

The sources fix the deadline, not the length. In a TIBER-EU test the purple teaming exercise in the closure phase must take place no later than 10 weeks after the end of active red team testing.

The sources read for this page do not set a number of days for the session itself; that is a scoping choice. The [scoping sheet](/scoping-sheet/) has a field for it.

## What is limited purple teaming?

Limited purple teaming is a narrow, collaborative step inside active testing. The EU technical standards allow it only as a last resort, in exceptional circumstances, when the test cannot otherwise continue and the control team lead has suspended the test.

They name three methods: catch-and-release, where testers continue, get detected and then resume; war gaming for strategic decisions; and collaborative proof of concept, where testers and blue team members validate a measure together.

## Related pages

- [Purple team: what it is and who is in the room](/purple-team/)
- [Red team debrief: how to turn findings into fixes](/engagement/red-team-debrief/)
- [Blue team report template and what it must contain](/blue-team/blue-team-report-template/)
- [Catch-and-release, defined](/glossary/catch-and-release/)
- [Replay exercise, defined](/glossary/replay-exercise/)
- [Red team vs blue team vs purple team: a three-way table](/compare/red-team-vs-blue-team-vs-purple-team/)
- [Red team: what a red team is and what it delivers](/red-team/)

## Sources

- European Central Bank, TIBER-EU Purple Teaming Guidance, 2025: https://www.ecb.europa.eu/pub/pdf/annex/ecb.tiber_eu_purple_best_practices_2025.en.pdf (read 16 November 2026)
- EUR-Lex, Commission Delegated Regulation (EU) 2025/1190 (TLPT technical standards): https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX:32025R1190 (read 16 November 2026)
- Association of Banks in Singapore, Red Team: Adversarial Attack Simulation Exercise Guidelines, September 2024: https://abs.org.sg/docs/library/abs-red-team-adversarial-attack-simulation-exercises-guidelines----september-2024.pdf (read 16 November 2026)
- Council of Financial Regulators, CORIE Framework version 2.0, July 2022: https://www.cfr.gov.au/publications/policy-statements-and-other-reports/2022/revised-corie-framework-rollout/pdf/corie-framework.pdf (read 16 November 2026)

Last reviewed 16 November 2026. Canonical: https://redteamvsblueteam.com/purple-team/purple-team-exercise/
