Skip to content

Buyer guide, read 16 November 2026

Scoping a red team engagement: ten decisions to make before the start

Open the scoping sheetSee the frameworks table

Download the templates

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

How do you scope a red team engagement?

You answer ten groups of questions in writing, with the white cell and sponsor, before the provider starts. The groups are objectives, crown jewels, threat profile, scope and exclusions, rules of engagement, emergency stop, legal authorization, timing, white cell contacts, and reporting and retest.

The scoping sheet holds the 50 questions in full, each with why it matters and its source. It prints on a page and downloads as Word, CSV and JSON.

What decides the objective?

The objective is a question your team wants answered about itself. TIBER-EU says the outcome is learning, not pass or fail. The Singapore guidelines say goals should be based on what real-world adversaries want, such as a large unauthorized funds transfer, and need not change every time unless intelligence or controls change.

What should the scope exclude?

Write down what is off limits and why. NIST SP 800-115 calls the list of systems not authorized for testing the exclude list. The Singapore guidelines give no-fly zones for functions where the risk of testing is excessive, and say that parts of the exercise not run live must be documented with reasons.

TIBER-EU requires the scope document to explain the reason each critical function is left out.

How long should the engagement run?

Time follows scope. TIBER-EU and the EU rules set 12 weeks as the minimum for active testing in regulated tests; CBEST allows about 14 weeks for its testing phase. The Singapore guidelines say complex scenarios at large firms often need four to six months in all.

Check planned system changes with change management before fixing dates.

Who should be in the room when you scope?

The sponsor, the white cell lead and subject experts for the in-scope systems, and legal. CBEST says the control group usually includes one person per system being tested and must be kept as small as possible. The Singapore guidelines list senior management, risk, business continuity, incident management, information security, system owners, legal and compliance for the working group.

Sources

  1. European Central Bank, What is TIBER-EU?, read 16 November 2026
  2. Association of Banks in Singapore, Red Team: Adversarial Attack Simulation Exercise Guidelines, September 2024, read 16 November 2026
  3. NIST SP 800-115, Technical Guide to Information Security Testing and Assessment, September 2008, read 16 November 2026
  4. European Central Bank, TIBER-EU Scope Specification Document Guidance, January 2025, read 16 November 2026
  5. EUR-Lex, Commission Delegated Regulation (EU) 2025/1190 (TLPT technical standards), read 16 November 2026
  6. Bank of England, CBEST Implementation Guide, 2024 edition, read 16 November 2026

Last reviewed 16 November 2026.