Skip to content

Method, read 16 November 2026

How the red team scoping sheet was made

Open the scoping sheetDownload the data

Download the templates

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

How were the scoping questions chosen?

The questions were chosen from the documents that tell a tested organization what to decide before testing: the ECB's TIBER-EU scope, test plan and report guidance, the EU technical standards for threat-led penetration testing, the Bank of England's CBEST guide, the Singapore AASE guidelines, NIST SP 800-115 and its rules of engagement template, and the CORIE framework. A question was kept only if a page read names the decision.

The result is 50 questions in ten sections: Objectives (5), Crown jewels and critical functions (6), Threat profile (4), Scope and exclusions (8), Rules of engagement (4), Emergency stop (5), Legal authorization (5), Timing (3), White cell contacts (4), Reporting and retest (6).

How is each question sourced?

Each question has one main source, shown in the last column of the sheet with its address and read date. The "why it matters" text is our paraphrase of that source. Where the sources are for regulated tests, such as the 12-week minimum, the text says so, and the buyer outside those schemes may choose differently.

What is missing from the sheet?

The sheet asks how fixes will be checked later, but no source read sets a retest rule, so that field asks the buyer to decide and says why. The sheet does not cover tabletop exercises, cyber ranges or automated attack tools, which this site leaves to other sources.

How is the Word file made?

A small Python script, tools/make_docx.py, reads the same JSON as the page and writes an Office Open XML file with the Python zipfile module. It lays the sheet out in landscape, one table per section, with the answer column blank. The CSV and JSON files are written by the site build from the same rows.

Cite this

Red Team vs Blue Team, "Engagement Scoping Sheet", edition 16 November 2026. Data: CSV, JSON.

Sources

  1. European Central Bank, What is TIBER-EU?, read 16 November 2026
  2. European Central Bank, TIBER-EU Framework, January 2025, read 16 November 2026
  3. Association of Banks in Singapore, Red Team: Adversarial Attack Simulation Exercise Guidelines, September 2024, read 16 November 2026
  4. Mandiant, Red Team Assessment datasheet (the firm's own document), read 16 November 2026
  5. Bank of England, CBEST Implementation Guide, 2024 edition, read 16 November 2026
  6. European Central Bank, TIBER-EU Scope Specification Document Guidance, January 2025, read 16 November 2026
  7. EUR-Lex, Commission Delegated Regulation (EU) 2025/1190 (TLPT technical standards), read 16 November 2026
  8. NIST SP 800-115, Technical Guide to Information Security Testing and Assessment, September 2008, read 16 November 2026
  9. European Central Bank, TIBER-EU Red Team Test Plan Guidance, 2025, read 16 November 2026
  10. European Central Bank, TIBER-EU Control Team Guidance, 2025, read 16 November 2026
  11. European Central Bank, TIBER-EU Red Team Test Report Guidance, 2025, read 16 November 2026

Last reviewed 16 November 2026.