Cross-Framework Mapping

BCBS 239vsAPRA CPS 230 Operational Risk Management

See exactly how BCBS 239 controls map to APRA CPS 230 Operational Risk Management. Pre-computed mappings, identified gaps, and coverage analysis.

17
Controls Mapped
8
Gaps Found
32%
Coverage

According to the TheArtOfService Compliance Knowledge Graph:

BCBS 239 maps to APRA CPS 230 Operational Risk Management with 32% coverage across 8 directly mapped controls. Analysis of 25 BCBS 239 controls identifies 17 compliance gaps — primarily concentrated in BCBS 239: Cybersecurity Controls.

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

Control Mappings

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

BCBS 239: Information Security Governance(3 mappings)

BCBS239-03Risk appetite and tolerance for IT risk3 targets
CPS230-16Internal Audit Review
CPS230-37Service Provider Management Policy
CPS230-46Ongoing Risk Management

BCBS 239: Operational Resilience(5 mappings)

BCBS239-11Business continuity planning and testing2 targets
CPS230-25Business Continuity Policy
CPS230-26Business Continuity Plans
BCBS239-12Disaster recovery procedures3 targets
CPS230-25Business Continuity Policy
CPS230-26Business Continuity Plans
CPS230-28Recovery Objectives

BCBS 239: Third-Party Risk Management(6 mappings)

BCBS239-18Ongoing monitoring and assessment3 targets
CPS230-16Internal Audit Review
CPS230-37Service Provider Management Policy
CPS230-46Ongoing Risk Management
BCBS239-19Concentration risk management3 targets
CPS230-16Internal Audit Review
CPS230-37Service Provider Management Policy
CPS230-46Ongoing Risk Management

BCBS 239: Incident Management & Reporting(3 mappings)

BCBS239-22Incident response and containment
CPS230-13Incident Management
BCBS239-24Customer notification procedures
CPS230-13Incident Management
BCBS239-25Post-incident review and improvement
CPS230-13Incident 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 APRA CPS 230 Operational Risk Management?

BCBS 239 has 25 controls across its framework, while APRA CPS 230 Operational Risk Management covers 43 controls. Direct mapping analysis identifies 8 overlapping controls (32% coverage). The frameworks diverge most significantly in BCBS 239: Cybersecurity Controls, where 5 BCBS 239 controls have no direct APRA CPS 230 Operational Risk Management equivalent.

How many controls map between BCBS 239 and APRA CPS 230 Operational Risk Management?

Of 25 total BCBS 239 controls, 8 map directly to APRA CPS 230 Operational Risk Management controls — representing 32% coverage. The remaining 17 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 APRA CPS 230 Operational Risk Management?

17 BCBS 239 controls have no direct equivalent in APRA CPS 230 Operational Risk Management. The highest concentration of gaps is in BCBS 239: Cybersecurity Controls 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 APRA CPS 230 Operational Risk Management?

The domain with the highest gap count is BCBS 239: Cybersecurity Controls (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.