{
 "name": "Red Team Frameworks by Regulator",
 "edition": "2026-11-16",
 "read_date": "2026-11-16",
 "source": "https://redteamvsblueteam.com/datasets/",
 "license": "CC BY 4.0",
 "cite": "Red Team vs Blue Team, \"Red Team Frameworks by Regulator\", edition 16 November 2026, https://redteamvsblueteam.com/frameworks/",
 "description": "Threat-led penetration testing and red team frameworks as published by regulators and central banks, with who must do them, provider rules, phases, timing and the source and read date. Fields that were not read say so.",
 "rows": [
  {
   "framework": "TIBER-EU",
   "owner_or_regulator": "European Central Bank, with the national central banks of the EU",
   "region": "European Union",
   "sector": "Financial entities providing core financial infrastructure; usable in all critical sectors",
   "year": "Published May 2018; updated 2024; current framework document dated January 2025",
   "status": "Adoption by authorities is voluntary; the framework can also serve as operational guidance for DORA threat-led penetration testing",
   "who_must_do_it": "Entities invited by the national or European TIBER authority, taking voluntary interest into account",
   "threat_intelligence_provider_rules": "At least one threat intelligence manager (5 years of experience) and one more team member (2 years); 3 references; indemnity insurance; no conflict of interest; separate from the red team staff",
   "red_team_provider_rules": "A red team test manager (5 years of experience) and at least two testers (2 years each); 5 references; indemnity insurance; combined participation in at least 5 prior assignments",
   "phases": "Preparation, testing (threat intelligence, then red team testing) and closure",
   "timing_and_frequency": "Active red team testing at least 12 weeks; closure in parts of up to 10 and 8 weeks plus the authority's assessment time; three-year intervals are the norm",
   "source_url": "https://www.ecb.europa.eu/paym/cyber-resilience/tiber-eu/html/index.en.html",
   "other_sources": "https://www.ecb.europa.eu/paym/cyber-resilience/tiber-eu/html/index.en.html https://www.ecb.europa.eu/pub/pdf/other/ecb.tiber_eu_framework_2025~b32eff9a10.en.pdf https://www.ecb.europa.eu/pub/pdf/annex/ecb.tiber_eu_service_provider_procurement_2025.en.pdf",
   "read_date": "2026-11-16"
  },
  {
   "framework": "DORA threat-led penetration testing (TLPT)",
   "owner_or_regulator": "European Union: Regulation (EU) 2022/2554 and Commission Delegated Regulation (EU) 2025/1190",
   "region": "European Union",
   "sector": "Financial entities identified by the authorities, other than microenterprises",
   "year": "Regulation of 14 December 2022; technical standards of 13 February 2025",
   "status": "Mandatory for identified entities",
   "who_must_do_it": "Financial entities identified by the TLPT authority using size, interconnection, criticality and ICT risk criteria; significant credit institutions must use external testers",
   "threat_intelligence_provider_rules": "Manager with 5 years in threat intelligence and one more member with 2 years; 3 references; CVs and certifications; indemnity insurance; no blue team or conflicting work",
   "red_team_provider_rules": "External testers: manager with 5 years and two testers with 2 years each; 5 references; indemnity insurance; internal testers allowed under set conditions, with external testers every third test",
   "phases": "Preparation, testing (threat intelligence, then red team test), closure, remediation plan and attestation",
   "timing_and_frequency": "At least every 3 years (the authority may raise or lower it); active red team testing at least 12 weeks; red team report within 4 weeks; blue team report and replay within 10 weeks",
   "source_url": "https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX:32025R1190",
   "other_sources": "https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX:32022R2554 https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX:32025R1190",
   "read_date": "2026-11-16"
  },
  {
   "framework": "CBEST",
   "owner_or_regulator": "Bank of England, with the Prudential Regulation Authority and the Financial Conduct Authority",
   "region": "United Kingdom",
   "sector": "Firms and financial market infrastructures",
   "year": "In use since 2014; implementation guide 2024 edition",
   "status": "Regulator-led; run when requested in the supervisory cycle, when a firm asks, or after an incident",
   "who_must_do_it": "Firms and market infrastructures selected by the PRA and FCA, or those that ask with the regulator's agreement",
   "threat_intelligence_provider_rules": "Independent company accredited for CBEST; manager holding CREST Certified Threat Intelligence Manager",
   "red_team_provider_rules": "Independent company accredited for CBEST; manager holding CREST Certified Red Team Manager or Cyber Scheme Red Team Manager",
   "phases": "Initiation, threat intelligence, penetration testing, closure",
   "timing_and_frequency": "About 9 to 12 months in all; indicative phases of 6, 10, 14 and 4 weeks",
   "source_url": "https://www.bankofengland.co.uk/financial-stability/operational-resilience-of-the-financial-sector/cbest-threat-intelligence-led-assessments-implementation-guide",
   "other_sources": "https://www.bankofengland.co.uk/financial-stability/operational-resilience-of-the-financial-sector/cbest-threat-intelligence-led-assessments-implementation-guide",
   "read_date": "2026-11-16"
  },
  {
   "framework": "iCAST (Intelligence-led Cyber Attack Simulation Testing), part of C-RAF 2.0",
   "owner_or_regulator": "Hong Kong Monetary Authority",
   "region": "Hong Kong",
   "sector": "Authorized institutions (banks)",
   "year": "Cybersecurity Fortification Initiative launched 2016; version 2.0 effective 1 January 2021",
   "status": "Set out in a circular to all authorized institutions with an implementation timeline",
   "who_must_do_it": "Authorized institutions whose inherent risk level is assessed as medium or high",
   "threat_intelligence_provider_rules": "Not stated in the pages read",
   "red_team_provider_rules": "Not stated in the pages read",
   "phases": "Not stated in the pages read",
   "timing_and_frequency": "iCAST completion deadlines by group: end-June 2022 (Group 1), end-March 2023 (Group 2), end-December 2023 (Group 3)",
   "source_url": "https://brdr.hkma.gov.hk/eng/doc-ldg/docId/getPdf/20201103-1-EN/20201103-1-EN.pdf",
   "other_sources": "https://brdr.hkma.gov.hk/eng/doc-ldg/docId/getPdf/20201103-1-EN/20201103-1-EN.pdf https://www.hkma.gov.hk/eng/news-and-media/press-releases/2020/11/20201103-4/",
   "read_date": "2026-11-16"
  },
  {
   "framework": "AASE (Adversarial Attack Simulation Exercises)",
   "owner_or_regulator": "Association of Banks in Singapore (industry guidelines); referred to by the Monetary Authority of Singapore in its Technology Risk Management Guidelines",
   "region": "Singapore",
   "sector": "Financial institutions",
   "year": "Industry guidelines version 1 November 2018; current edition September 2024; MAS guidelines January 2021",
   "status": "MAS guidelines say a financial institution should perform an adversarial attack simulation exercise; the detailed method is an industry guideline",
   "who_must_do_it": "Financial institutions, who choose the frequency by risk",
   "threat_intelligence_provider_rules": "Not stated in the pages read",
   "red_team_provider_rules": "Seek assurance on methodology, data handling, criminal background checks, insurance and indemnity; consider reputation, references and recognized accreditations",
   "phases": "Planning, attack preparation, attack execution, exercise closure, post-exercise actions",
   "timing_and_frequency": "Recommended at least every 24 months; large firms may run a 4 to 6 month cycle for complex scenarios",
   "source_url": "https://abs.org.sg/docs/library/abs-red-team-adversarial-attack-simulation-exercises-guidelines----september-2024.pdf",
   "other_sources": "https://abs.org.sg/docs/library/abs-red-team-adversarial-attack-simulation-exercises-guidelines----september-2024.pdf https://www.mas.gov.sg/-/media/mas/regulations-and-financial-stability/regulatory-and-supervisory-framework/risk-management/trm-guidelines-18-january-2021.pdf",
   "read_date": "2026-11-16"
  },
  {
   "framework": "CORIE (Cyber Operational Resilience Intelligence-led Exercises)",
   "owner_or_regulator": "Council of Financial Regulators (APRA, ASIC, Reserve Bank of Australia, Treasury)",
   "region": "Australia",
   "sector": "Financial institutions, including financial market infrastructure",
   "year": "Launched December 2020; version 2.0 July 2022",
   "status": "Program run in rounds; participants invited by the regulators",
   "who_must_do_it": "Financial institutions invited by the Council of Financial Regulators in each round, chosen on a risk basis",
   "threat_intelligence_provider_rules": "Lead with CREST CCTIM or GIAC GCTI and 3 years of experience; analyst with 1 year; legal and ethical intelligence gathering, including from the dark web",
   "red_team_provider_rules": "Red team lead with 7 years of red teaming or penetration testing and set certifications; team of at least a lead, a specialist and an exploit development specialist",
   "phases": "Preparation, test and closure (six stages), then a replay (purple) exercise",
   "timing_and_frequency": "Closure phase typically 5 weeks; overall length depends on the number of scenarios",
   "source_url": "https://www.cfr.gov.au/publications/policy-statements-and-other-reports/2022/revised-corie-framework-rollout/pdf/corie-framework.pdf",
   "other_sources": "https://www.cfr.gov.au/publications/policy-statements-and-other-reports/2022/revised-corie-framework-rollout/pdf/corie-framework.pdf https://www.cfr.gov.au/publications/policy-statements-and-other-reports/2022/revised-corie-framework-rollout/pdf/corie-guide-providers.pdf https://www.cfr.gov.au/news/2022/mr-22-03.html",
   "read_date": "2026-11-16"
  },
  {
   "framework": "United States: no single regulator-published equivalent found in the sources read",
   "owner_or_regulator": "Not applicable",
   "region": "United States",
   "sector": "Not applicable",
   "year": "NIST SP 800-53 Rev. 5 (control CA-8(2)); CISA advisory of 28 February 2023",
   "status": "The sources read describe a federal security control and an agency service, not a sector-wide program",
   "who_must_do_it": "NIST SP 800-53 lets the organization define its red team exercises. CISA says it ran its red team assessment at the request of a critical infrastructure organization",
   "threat_intelligence_provider_rules": "Not stated in the pages read",
   "red_team_provider_rules": "Not stated in the pages read",
   "phases": "CISA describes Phase I (gain and keep persistent access while avoiding detection) and Phase II (try to trigger a security response)",
   "timing_and_frequency": "Not stated in the pages read",
   "source_url": "https://www.cisa.gov/news-events/cybersecurity-advisories/aa23-059a",
   "other_sources": "https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r5.pdf https://www.cisa.gov/news-events/cybersecurity-advisories/aa23-059a",
   "read_date": "2026-11-16"
  }
 ]
}