# Assumed breach, defined

Glossary term, read 16 November 2026

**The short answer.** A red team design that starts with the attacker already inside, usually with a workstation or account. It skips the entry stage to spend the time on movement, privileges and detection. Bishop Fox describes it on its red team page as "Starts with internal access already granted. Focuses on lateral movement, privilege escalation, and detection." Read on 16 November 2026.

## What is assumed breach?

A red team design that starts with the attacker already inside, usually with a workstation or account. It skips the entry stage to spend the time on movement, privileges and detection.

## A sourced example

Bishop Fox describes it on its red team page as "Starts with internal access already granted. Focuses on lateral movement, privilege escalation, and detection."

## Related terms

- [Adversary emulation](/glossary/adversary-emulation/)
- [Adversary simulation](/glossary/adversary-simulation/)
- [Attestation](/glossary/attestation/)
- [Blue team](/glossary/blue-team/)

## Related pages

- [All red team terms](/glossary/)
- [Red team](/red-team/)
- [The red team process](/engagement/red-team-process/)
- [FAQ](/faq/)

## Sources

- bishopfox.com: https://bishopfox.com/services/red-team (read 16 November 2026)

Last reviewed 16 November 2026. Canonical: https://redteamvsblueteam.com/glossary/assumed-breach/
