Framework overlap

Does APRA CPS 234 cover Open Banking Security?

You hold APRA CPS 234 and have been told to do Open Banking Security. Here is how much overlaps, control by control.

63% of Open Banking Security you already have

APRA CPS 234 already covers about 63% of Open Banking Security, leaving 3 of 8 controls as genuinely new work.

Already covered 5 Likely covered 0 New work 3

What is genuinely new work

Nothing in APRA CPS 234 reaches these. This is the list to scope.

OPENBANK-1
FAPI 2.0 Security Profile and OpenID Foundation Conformance
OPENBANK-5
Data Minimisation, Scope Enforcement, Localisation, Cross-Border Transfers
OPENBANK-6
Fraud Detection, Transaction Risk Analysis, Rate Limiting, Sandbox
Show the 5 you already have
OPENBANK-2
Strong Customer Authentication (SCA), Consent Lifecycle, and Customer UX
OPENBANK-3
Mutual TLS, Token Binding, Request Signing (JWS), Key Management
OPENBANK-4
Third Party Provider (TPP) Onboarding, Directory Integration, Due Diligence
OPENBANK-7
Logging, Monitoring, Regulatory Reporting, SLA, Availability
OPENBANK-8
Incident Detection, Response, Customer Notification, Post-Incident Review, BCM

How this is calculated

Already covered means a mapping runs from a control in APRA CPS 234 to that control. Likely covered means no direct mapping exists but both frameworks map to the same control in a third standard. New work means neither. We keep those separate rather than adding them into one friendlier number, because blending them would present a two-hop inference as a verified fact.

Coverage is not symmetric. Run it the other way and you will get a different number; both are correct.

From 332,959 cross-framework control mappings across 723 frameworks, 531 of them verified against their source documents. It does not tell you that you are compliant: a mapped control means the two standards ask for the same thing, not that you have done it.

Try another pair ยท Today's edition