# CBEST: the Bank of England's threat intelligence-led assessment

Framework, read 16 November 2026

**The short answer.** CBEST is a regulator-led, intelligence-led security testing framework run by the Bank of England with the Prudential Regulation Authority and the Financial Conduct Authority. It has been in use since 2014, and the implementation guide read here is the 2024 edition. Projects run about 9 to 12 months. Read 16 November 2026.

## What is CBEST?

CBEST is an intelligence-led penetration testing approach that mimics the actions of attackers intent on compromising a firm's important business services. The Bank of England says it has been part of the regulators' supervisory toolkit since 2014.

The implementation guide calls CBEST a guiding framework rather than a detailed prescriptive method, and describes a "golden thread" linking the testing to the threats to the firm's activities.

## Who has to do a CBEST assessment?

A CBEST should be carried out when one of three conditions holds. The regulator requests it as part of the supervisory cycle, the firm asks to do one within its own program with the regulator's agreement, or an incident has led the regulator to request one for remediation and validation.

It applies to firms and financial market infrastructures.

## What are the CBEST phases?

Four: initiation, threat intelligence, penetration testing and closure. Indicative durations are about 6, 10, 14 and 4 weeks, and the average project runs 9 to 12 months. Initiation scopes the assessment and procures providers. Threat intelligence produces the profiles and scenarios. Penetration testing runs the scenarios and assesses detection and response. Closure finalizes the remediation plan and debriefs the providers.

## Who does the work, and what rules apply to providers?

The firm's control group, a threat intelligence service provider and a penetration testing service provider, with the regulator overseeing. The providers must be independent companies accredited for CBEST through a Bank of England process, and must also be members of CREST. The threat intelligence provider needs a CREST Certified Threat Intelligence Manager and the testing provider a CREST Certified Red Team Manager or a Cyber Scheme Red Team Manager.

The control group is a select number of senior people, and its coordinator must obtain the regulator's approval for changes to the list.

## Related pages

- [Red team frameworks by regulator: TIBER-EU, DORA, CBEST, iCAST, AASE and CORIE](/frameworks/)
- [TIBER-EU: the European Central Bank's red team framework](/frameworks/tiber-eu/)
- [White team or white cell: who they are and what they do](/engagement/white-team/)
- [Red team for financial services: what regulators ask of a red team](/services/red-team-for-financial-services/)
- [What to ask a red team provider: twelve questions and why](/services/what-to-ask-a-red-team-provider/)
- [Red team process: the phases of an engagement](/engagement/red-team-process/)
- [DORA threat-led penetration testing: who must do it and how](/frameworks/dora-tlpt/)
- [AASE: adversarial attack simulation exercises in Singapore](/frameworks/aase/)

## Sources

- Bank of England, CBEST Implementation Guide, 2024 edition: https://www.bankofengland.co.uk/financial-stability/operational-resilience-of-the-financial-sector/cbest-threat-intelligence-led-assessments-implementation-guide (read 16 November 2026)

Last reviewed 16 November 2026. Canonical: https://redteamvsblueteam.com/frameworks/cbest/
