Framework overlap

Does APRA CPS 234 cover ISO 22320:2018?

You hold APRA CPS 234 and have been told to do ISO 22320:2018. Here is how much overlaps, control by control.

19% of ISO 22320:2018 you already have

APRA CPS 234 already covers about 19% of ISO 22320:2018, leaving 29 of 36 controls as genuinely new work.

Already covered 7 Likely covered 0 New work 29

What is genuinely new work

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

ISO-22320-4.2
Ethics
ISO-22320-4.4
Information sharing
ISO-22320-4.5
Safety
ISO-22320-4.6
Flexibility and adaptability
ISO-22320-4.7
Human and cultural factors
ISO-22320-4.8
Continual improvement
ISO-22320-5.5
Resource management
ISO-22320-6.1
General cooperation requirements
ISO-22320-6.2
Collaboration and coordination
ISO-22320-6.3
Communication protocols
ISO-22320-6.4
Joint direction
ISO-22320-A
Annex A: Collaboration and communication guidance
ISO22320-10.1
Post Incident Review and Lessons Learned
ISO22320-10.2
Continual Improvement of Incident Management
ISO22320-4.1
Incident Management Policy
ISO22320-4.2
Roles, Responsibilities, and Authorities
ISO22320-5.1
Command Function
ISO22320-5.2
Control Function
ISO22320-5.3
Coordination Function
ISO22320-6.1
Incident Command System Structure
ISO22320-6.2
Common Terminology and Plain Language
ISO22320-6.3
Incident Action Planning
ISO22320-7.1
Operational Information Management
ISO22320-7.2
Communication Systems and Interoperability
ISO22320-7.3
Situational Awareness and Common Operating Picture
ISO22320-8.1
Cooperation with External Agencies
ISO22320-8.2
Multi Agency Coordination
ISO22320-9.1
Human Factors and Welfare
ISO22320-9.2
Training, Exercising, and Competence
Show the 7 you already have
ISO-22320-4.3
Risk-based approach
ISO-22320-5.1
General process requirements
ISO-22320-5.2
Incident management process
ISO-22320-5.3
Incident management structure (command)
ISO-22320-5.4
Roles and responsibilities
ISO-22320-B
Annex B: Incident management plan structure
ISO-22320-C
Annex C: Incident management task examples

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