Process, read 16 November 2026
Red team process: the phases of an engagement
What is the red team process?
The red team process is the sequence from agreeing scope to fixing findings. Every framework read has the same spine: prepare and scope, gather threat intelligence, attack, then report, replay and fix. They differ in how many phases they count and how long each takes.
The table lists each framework's phases and the time its text gives.
| Framework | Phases | Time given in the text |
|---|---|---|
| TIBER-EU (ECB) | Preparation (notification, initiation, procurement and scoping); testing (threat intelligence, then red team test plan and active testing); closure (reports, replay, purple teaming, feedback, attestation). | Active testing at least 12 weeks; closure reports and replay up to 10 weeks, then up to 8 weeks for summary and plan. |
| DORA TLPT (EU) | Preparation, testing (threat intelligence, red team test), closure, remediation plan, attestation. | Initiation information due within 3 months of notice; red team report within 4 weeks; blue team report and replay within 10 weeks. |
| CBEST (Bank of England) | Initiation; threat intelligence; penetration testing; closure. | About 6, 10, 14 and 4 weeks; 9 to 12 months overall. |
| AASE (Singapore) | Planning; attack preparation; attack execution; exercise closure; post-exercise actions. | Large firms may run a 4 to 6 month cycle for complex scenarios. |
| CORIE (Australia) | Preparation; test; closure, in six stages ending with a replay attack. | Closure phase typically 5 weeks. |
| NIST SP 800-115 (penetration test) | Planning; discovery; attack; reporting. | Not stated. |
What happens in each phase?
Preparation sets up the engagement. The tested entity forms its control team, appoints providers and writes the scope document with the functions, systems and flags. Under the EU technical standards the scope document goes to the authority for approval before threat intelligence starts.
The testing phase starts with a targeted threat intelligence report and ends with active testing, in which the red team works through scenarios on live systems. Closure covers the reports, the replay, the purple teaming exercise, feedback, the remediation plan and the attestation.
How long does a red team engagement take?
The shortest figure in the sources is the 12-week minimum for active testing under TIBER-EU and the EU technical standards. The whole engagement is longer: CBEST regulators find an average project duration of around 9 to 12 months.
The Singapore guidelines say large firms typically run a four to six month cycle for complex scenarios, including attack modeling. Duration scales with the number of scenarios and the scope.
Does a smaller engagement follow the same phases?
The phases are the same; the effort is not. The NIST penetration testing model of planning, discovery, attack and reporting is the smaller form. The frameworks above are written for large regulated firms. Buyers outside those regimes use them as a model and scale the effort.
See the step-by-step list and scoping a red team engagement.
Related pages
- Red team steps: ten steps with the output of each
- Red team frameworks by regulator: TIBER-EU, DORA, CBEST, iCAST, AASE and CORIE
- Scoping a red team engagement: ten decisions to make before the start
- Red team debrief: how to turn findings into fixes
- What does a red team do?
- Red team engagement scoping sheet: 50 questions to answer before testing
Sources
- European Central Bank, TIBER-EU Framework, January 2025, read 16 November 2026
- EUR-Lex, Commission Delegated Regulation (EU) 2025/1190 (TLPT technical standards), read 16 November 2026
- Bank of England, CBEST Implementation Guide, 2024 edition, read 16 November 2026
- Association of Banks in Singapore, Red Team: Adversarial Attack Simulation Exercise Guidelines, September 2024, read 16 November 2026
- Council of Financial Regulators, CORIE Framework version 2.0, July 2022, read 16 November 2026
- NIST SP 800-115, Technical Guide to Information Security Testing and Assessment, September 2008, read 16 November 2026
Last reviewed 16 November 2026.