BCBS 239
Basel Committee Principles for Effective Risk Data Aggregation
Framework summaries on this platform are AI-assisted interpretations for educational and compliance planning purposes. They do not reproduce or replace the official standards. Refer to the authoritative source for the definitive text. Framework names and trademarks belong to their respective organisations.
Framework Domains (9)
BCBS 239: Cybersecurity Controls
Technical cybersecurity measures (BCBS 239)
| Code | Title |
|---|---|
| BCBS239-06 | Network security and segmentation |
| BCBS239-07 | Endpoint protection and detection |
| BCBS239-08 | Application security controls |
| BCBS239-09 | Encryption and key management |
| BCBS239-10 | Secure configuration standards |
BCBS 239: Incident Management & Reporting
Incident handling for financial services (BCBS 239)
| Code | Title |
|---|---|
| BCBS239-21 | Incident detection and classification |
| BCBS239-22 | Incident response and containment |
| BCBS239-23 | Regulatory reporting requirements |
| BCBS239-24 | Customer notification procedures |
| BCBS239-25 | Post-incident review and improvement |
BCBS 239: Information Security Governance
IT governance for financial institutions (BCBS 239)
| Code | Title |
|---|---|
| BCBS239-01 | Information security program management |
| BCBS239-02 | Board and management oversight |
| BCBS239-03 | Risk appetite and tolerance for IT risk |
| BCBS239-04 | Security policy framework |
| BCBS239-05 | Roles and responsibilities definition |
BCBS 239: Operational Resilience
Business continuity and resilience (BCBS 239)
| Code | Title |
|---|---|
| BCBS239-11 | Business continuity planning and testing |
| BCBS239-12 | Disaster recovery procedures |
| BCBS239-13 | Third-party dependency management |
| BCBS239-14 | Critical service identification |
| BCBS239-15 | Communication and escalation procedures |
BCBS 239: Third-Party Risk Management
Managing vendor and supplier risks (BCBS 239)
| Code | Title |
|---|---|
| BCBS239-16 | Due diligence and onboarding |
| BCBS239-17 | Contractual security requirements |
| BCBS239-18 | Ongoing monitoring and assessment |
| BCBS239-19 | Concentration risk management |
| BCBS239-20 | Exit strategy and transition planning |
Governance and Infrastructure
| Code | Title |
|---|---|
| Principle 1 | Governance |
| Principle 1.A | Chief Data Officer and data governance roles |
| Principle 2 | Data architecture and IT infrastructure |
| Principle 2.A | Data lineage and metadata management |
Risk Data Aggregation Capabilities
| Code | Title |
|---|---|
| Principle 3 | Accuracy and Integrity |
| Principle 3.A | End user computing and manual adjustments |
| Principle 4 | Completeness |
| Principle 5 | Timeliness |
| Principle 5.A | Stress and crisis reporting timeliness |
| Principle 6 | Adaptability |
Risk Reporting Practices
| Code | Title |
|---|---|
| Principle 10 | Frequency |
| Principle 11 | Distribution |
| Principle 7 | Accuracy (Reporting) |
| Principle 8 | Comprehensiveness |
| Principle 9 | Clarity and Usefulness |
Supervisory Review Tools
| Code | Title |
|---|---|
| Principle 12 | Review |
| Principle 13 | Remedial actions and supervisory measures |
| Principle 14 | Home/host cooperation |
Your Compliance Coverage
If you comply with BCBS 239, you already cover:
MAS TRM
44%
19 controls mapped
Compare →PCI P2PE
44%
19 controls mapped
Compare →DORA
44%
19 controls mapped
Compare →+ 624 more: PCI SSF (44%), FFIEC IT Examination Handbook (44%)
See all 627 mapped frameworks ↓Maps to 627 other frameworks
Frequently Asked Questions
What is BCBS 239?
BCBS 239 is a compliance framework from International with 9 domains and 43 controls. Basel Committee Principles for Effective Risk Data Aggregation It is used by organisations to establish and maintain compliance with industry standards and regulatory requirements.
How many controls does BCBS 239 have?
BCBS 239 has 43 controls organised across 9 domains. The largest domains are Risk Data Aggregation Capabilities (6 controls), BCBS 239: Cybersecurity Controls (5 controls), BCBS 239: Incident Management & Reporting (5 controls). Each control defines specific requirements that organisations must implement to achieve compliance.
What frameworks does BCBS 239 map to?
BCBS 239 maps to 627 other compliance frameworks. The top mapping partners are MAS TRM (44% coverage), PCI P2PE (44% coverage), DORA (44% coverage). Use our comparison tool to explore control-level mappings between frameworks.
How do I get started with BCBS 239 compliance?
Start your BCBS 239 compliance journey by running a self-assessment on our platform to identify your current compliance posture. Our AI advisory can answer specific questions about BCBS 239 requirements, and cross-framework mapping helps you leverage existing controls from other frameworks you may already comply with. Create a free account to access all 43 controls and track your progress.
Start Your Compliance Journey
Create a free account to run self-assessments, get AI advisory, and track your compliance progress across 700 frameworks.
Get Started Free →Free forever — no credit card required