# Assumed breach red team: starting from inside

Explainer, read 16 November 2026

**The short answer.** An assumed breach red team test starts with the attacker already inside, usually with a workstation or account, and spends its time on movement, privileges and detection. TIBER-EU calls such help leg-ups and the Singapore guidelines call it concessions. Read 16 November 2026.

## What is an assumed breach red team?

It is a design in which the attacker starts with internal access already granted. Bishop Fox describes it as focusing on lateral movement, privilege escalation and detection. NetSPI describes it as assuming an attacker has already breached the environment and then outlining the potential scope of a compromise.

The Singapore guidelines give the example of providing a laptop up front on the assumption that an endpoint compromise would succeed.

## How is it different from leg-ups and concessions?

An assumed breach start is planned from day one; a leg-up is help given when testers stall. TIBER-EU defines a leg-up as assistance or information from the control team that lets the testers continue an attack path they cannot advance on their own, and requires them to be logged.

The Singapore guidelines call planned help a concession and give examples: an administrator told to issue accounts on demand, an IT person issuing laptops, information about assets, bypass of a physical access control, or a trusted agent opening a file that gives the first foothold.

## When does an assumed breach start make sense?

It makes sense when the entry stage is not the question. The Bank of England says CBEST results show the value of simulating highly privileged internal attackers, such as malicious insiders and supply chain attacks, because these test the controls inside the network rather than at the perimeter.

TIBER-EU explains the pressure behind leg-ups: real attackers have more time and fewer legal and ethical limits than a test, so a granted foothold lets the test go on within the legal and ethical limits.

## What should be written down?

Every start position and every concession. The TIBER-EU report guidance asks that leg-ups be listed in the report, and the Singapore guidelines say that when concessions run out the organization may let the attacker continue while the blue team watches passively.

## Related pages

- [Assumed breach, defined](/glossary/assumed-breach/)
- [Leg-up, defined](/glossary/leg-up/)
- [Concession, defined](/glossary/concession/)
- [Red team rules of engagement: what they cover and a template](/engagement/red-team-rules-of-engagement/)
- [Red team services: kinds, what is included and who delivers](/services/red-team-services/)
- [Red team engagement scoping sheet: 50 questions to answer before testing](/scoping-sheet/)
- [Red team legal authorization: the letter and the law](/engagement/red-team-legal-authorization/)
- [Red team report: what it must contain, with a template](/engagement/red-team-report/)

## Sources

- Bishop Fox, Red Team Services page (the firm's own page): https://bishopfox.com/services/red-team (read 16 November 2026)
- NetSPI, Red Team Operations page (the firm's own page): https://www.netspi.com/netspi-ptaas/red-team-operations/ (read 16 November 2026)
- European Central Bank, TIBER-EU Red Team Test Report Guidance, 2025: https://www.ecb.europa.eu/pub/pdf/annex/ecb.tiber_red_team_test_report_guidance_2025.en.pdf (read 16 November 2026)
- European Central Bank, TIBER-EU Framework, January 2025: https://www.ecb.europa.eu/pub/pdf/other/ecb.tiber_eu_framework_2025~b32eff9a10.en.pdf (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)
- 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/engagement/assumed-breach-red-team/
