Cross-Framework Mapping

BCBS 239vsProposal for a Regulation on Cyber Resilience Act (CRA)

See exactly how BCBS 239 controls map to Proposal for a Regulation on Cyber Resilience Act (CRA). Pre-computed mappings, identified gaps, and coverage analysis.

16
Controls Mapped
9
Gaps Found
28%
Coverage

According to the TheArtOfService Compliance Knowledge Graph:

BCBS 239 maps to Proposal for a Regulation on Cyber Resilience Act (CRA) with 28% coverage across 7 directly mapped controls. Analysis of 25 BCBS 239 controls identifies 18 compliance gaps — primarily concentrated in BCBS 239: Incident Management & Reporting.

Source: TheArtOfService Knowledge Graph | 25 controls analysed | 693 frameworks | 819K+ cross-framework mappings

Control Mappings

Showing 16 of 16 mapped controls across 3 domains. Sign up to explore all 819K+ mappings across 693 frameworks.

BCBS 239: Information Security Governance(1 mappings)

BCBS239-05Roles and responsibilities definition
EU-CRA-04Roles and responsibilities definition

BCBS 239: Cybersecurity Controls(5 mappings)

BCBS239-06Network security and segmentation
EU-CRA-27Network security management
BCBS239-09Encryption and key management4 targets
EU-CRA-17Encryption of data at rest
EU-CRA-18Encryption of data in transit
EU-CRA-19Certificate management
EU-CRA-20Key lifecycle management

BCBS 239: Operational Resilience(10 mappings)

BCBS239-12Disaster recovery procedures
EU-CRA-23Backup and recovery procedures
BCBS239-13Third-party dependency management3 targets
EU-CRA-21Operational procedures and responsibilities
EU-CRA-22Protection from malware
EU-CRA-25Technical vulnerability management
BCBS239-14Critical service identification3 targets
EU-CRA-21Operational procedures and responsibilities
EU-CRA-22Protection from malware
EU-CRA-25Technical vulnerability management
BCBS239-15Communication and escalation procedures3 targets
EU-CRA-21Operational procedures and responsibilities
EU-CRA-22Protection from malware
EU-CRA-25Technical vulnerability management

Stop Paying Consultants to Read Spreadsheets

AI-powered compliance intelligence across 693 frameworks — at a fraction of consulting costs.

$0/forever

Free

  • 693 framework browser
  • Cross-framework mappings (819K+)
  • 824 compliance assessments
  • 3 AI queries & searches per day
Get Started Free
Recommended
$49/month

Professional

  • Unlimited AI Compliance Advisory
  • Unlimited full-text search
  • Framework self-assessment
  • PDF, Excel & CSV exports
Start 7-Day Free Trial →

What are the key differences between BCBS 239 and Proposal for a Regulation on Cyber Resilience Act (CRA)?

BCBS 239 has 25 controls across its framework, while Proposal for a Regulation on Cyber Resilience Act (CRA) covers 31 controls. Direct mapping analysis identifies 7 overlapping controls (28% coverage). The frameworks diverge most significantly in BCBS 239: Incident Management & Reporting, where 5 BCBS 239 controls have no direct Proposal for a Regulation on Cyber Resilience Act (CRA) equivalent.

How many controls map between BCBS 239 and Proposal for a Regulation on Cyber Resilience Act (CRA)?

Of 25 total BCBS 239 controls, 7 map directly to Proposal for a Regulation on Cyber Resilience Act (CRA) controls — representing 28% coverage. The remaining 18 controls represent compliance gaps requiring additional documentation or compensating controls to satisfy both frameworks simultaneously.

What are the compliance gaps when mapping BCBS 239 to Proposal for a Regulation on Cyber Resilience Act (CRA)?

18 BCBS 239 controls have no direct equivalent in Proposal for a Regulation on Cyber Resilience Act (CRA). The highest concentration of gaps is in BCBS 239: Incident Management & Reporting with 5 unmapped controls. These gaps represent areas where additional controls, policies, or documentation must be created to achieve compliance with both frameworks.

Which control domains have the most gaps between BCBS 239 and Proposal for a Regulation on Cyber Resilience Act (CRA)?

The domain with the highest gap count is BCBS 239: Incident Management & Reporting (5 gaps). Export the full domain-by-domain gap breakdown via the Professional tier to generate a prioritised remediation roadmap.

This platform provides educational compliance tools, not legal, regulatory, or professional compliance advice. Cross-framework mappings are AI-assisted interpretations and do not reproduce or replace official standards. Framework names and trademarks belong to their respective owners. Consult qualified professionals for your specific compliance requirements. See our Terms of Service.