# 15 questions about red teams, answered

FAQ, read 10 November 2026

**In short.** 15 short answers on what red, blue and purple teams do, how a red team differs from a penetration test, rules of engagement, the white team, frequency and what to ask a provider. Each is drawn from NIST, the ECB, the EU rules, the Singapore guidelines or CISA, with the read date on the pages it links to.

## What are the most common questions about red teams?

The questions below come from what people search for: the difference between the teams, between a red team and a penetration test, what a red team does, rules of engagement, the white team, how long and how often, and what to ask a provider.

**What is the difference between a red team and a blue team?**

A red team plays the attacker and a blue team defends. NIST describes the red team as a group authorized to emulate an adversary's attack against an enterprise, and the blue team as the group defending its systems against mock attackers. A white team referees. See the [red team vs blue team page](/compare/red-team-vs-blue-team/).

**What is a purple team?**

A purple team is not a separate staff. It is a collaborative exercise in which red and blue work together so that detections are tested and improved as techniques run. The Singapore guidelines describe it as a structured assessment that brings both sides together. See the [purple team page](/purple-team/).

**What is the difference between a red team and a penetration test?**

A penetration test looks for as many weaknesses as possible in a limited scope, usually with staff aware. A red team test pursues a goal across people, process and technology, covertly. The Singapore guidelines set out the contrast in a table. See [red team vs penetration testing](/compare/red-team-vs-penetration-testing/).

**What does a red team do?**

A red team plans and runs a simulated attack on an organization to reach agreed objectives, then reports what worked, what was detected and what to fix. CISA describes its red team as emulating cyber threat actors to assess detection and response. See [what a red team does](/red-team/what-does-a-red-team-do/).

**Is adversary simulation the same as adversary emulation?**

Not always. Emulation copies the known behavior of a named threat actor from public reports. The CORIE framework uses adversary simulation as another name for a red team exercise driven by threat intelligence. See [adversary simulation vs emulation](/compare/adversary-simulation-vs-emulation/).

**What is a red team assessment?**

It is the buyer's name for a purchased red team engagement: an agreed objective, a covert attack by a provider, and a report. Mandiant, for example, describes a no-holds-barred attack scenario using non-destructive methods against jointly agreed objectives. See [the red team assessment page](/services/red-team-assessment/).

**What are rules of engagement in a red team test?**

They are the written limits and permissions for the test: scope, exclusions, allowed methods, contacts, halt criteria and signatures. NIST SP 800-115 supplies a template. See [rules of engagement](/engagement/red-team-rules-of-engagement/).

**What is the white team or white cell?**

It is the small group on the tested side that knows about the covert test and referees it. NIST calls it the white team. TIBER-EU calls it the control team, CBEST and CORIE call it the control group, and the Singapore guidelines use exercise working group. See [the white team page](/engagement/white-team/).

**How long does a red team engagement take?**

It depends on the framework and scope. The EU technical standards require at least 12 weeks of active testing. CBEST gives about 14 weeks for its testing phase and 9 to 12 months overall. See [the red team process](/engagement/red-team-process/).

**How often should a red team exercise be run?**

TIBER-EU says three-year intervals are the norm. DORA requires threat-led testing at least every three years for identified entities. The Singapore guidelines recommend at least every 24 months, with a risk-based choice. See [the frameworks table](/frameworks/).

**Is a red team test pass or fail?**

Under TIBER-EU it is not. The ECB says the outcome is not a pass or fail but a view of strengths and weaknesses, with a focus on learning. See [what to expect from the report](/engagement/red-team-report/).

**What should a red team report contain?**

TIBER-EU requires the flags reached and not reached, attack paths, techniques used, deviations from the plan, leg-ups granted, known blue team actions, findings with root causes and a remediation priority. See [the red team report page](/engagement/red-team-report/).

**Is a red team test legal?**

It is lawful only with authorization. The Singapore guidelines describe a letter of engagement signed by senior management, and TIBER-EU says a legal analysis should be done because some activities, such as gathering employee account data, need care. See [legal authorization](/engagement/red-team-legal-authorization/).

**Do financial firms have to do red team testing?**

In the EU, identified financial entities must carry out threat-led penetration testing at least every three years under DORA. Other regimes, such as CBEST and CORIE, select firms by regulator. See [red team for financial services](/services/red-team-for-financial-services/).

**What should I ask a red team provider?**

Ask for references, team experience, insurance, conflicts of interest, how high-risk actions are approved and what the report contains. TIBER-EU and the Singapore guidelines list such checks. See [what to ask a provider](/services/what-to-ask-a-red-team-provider/).

## Related pages

- [Home: red team vs blue team](/)
- [8 dated items on red team frameworks and guidance](/news/)
- [Red team: what a red team is and what it delivers](/red-team/)
- [Red team vs blue team: roles, goals and how they meet](/compare/red-team-vs-blue-team/)
- [Red team services: kinds, what is included and who delivers](/services/red-team-services/)
- [25 red team terms, each with a sourced example](/glossary/)
- [Red team frameworks by regulator: TIBER-EU, DORA, CBEST, iCAST, AASE and CORIE](/frameworks/)

## Sources

- NIST CSRC Glossary, red team: https://csrc.nist.gov/glossary/term/red_team (read 16 November 2026)
- NIST CSRC Glossary, blue team: https://csrc.nist.gov/glossary/term/blue_team (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)
- NCSC (UK), Penetration testing: https://www.ncsc.gov.uk/guidance/penetration-testing (read 16 November 2026)
- CISA, advisory AA23-059A, CISA Red Team Shares Key Findings to Improve Monitoring and Hardening of Networks, 28 February 2023: https://www.cisa.gov/news-events/cybersecurity-advisories/aa23-059a (read 16 November 2026)
- MITRE Center for Threat-Informed Defense, Adversary Emulation Library: https://ctid.mitre.org/resources/adversary-emulation-library/ (read 16 November 2026)
- Council of Financial Regulators, CORIE Framework version 2.0, July 2022: https://www.cfr.gov.au/publications/policy-statements-and-other-reports/2022/revised-corie-framework-rollout/pdf/corie-framework.pdf (read 16 November 2026)
- Mandiant, Red Team Assessment datasheet (the firm's own document): https://services.google.com/fh/files/misc/ds-red-team-operations-en.pdf (read 16 November 2026)
- NIST SP 800-115, Technical Guide to Information Security Testing and Assessment, September 2008: https://nvlpubs.nist.gov/nistpubs/Legacy/SP/nistspecialpublication800-115.pdf (read 16 November 2026)
- NIST CSRC Glossary, rules of engagement: https://csrc.nist.gov/glossary/term/rules_of_engagement (read 16 November 2026)
- NIST CSRC Glossary, white team: https://csrc.nist.gov/glossary/term/white_team (read 16 November 2026)
- European Central Bank, What is TIBER-EU?: https://www.ecb.europa.eu/paym/cyber-resilience/tiber-eu/html/index.en.html (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)
- EUR-Lex, Commission Delegated Regulation (EU) 2025/1190 (TLPT technical standards): https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX:32025R1190 (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)
- EUR-Lex, Regulation (EU) 2022/2554 (DORA): https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX:32022R2554 (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 Guidance for Service Provider Procurement, 2025: https://www.ecb.europa.eu/pub/pdf/annex/ecb.tiber_eu_service_provider_procurement_2025.en.pdf (read 16 November 2026)

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