14% of ISO 22318 you already have
ISO 27018 already covers about 14% of ISO 22318, leaving
31 of 36 controls as genuinely new work.
Already covered 2
Likely covered 3
New work 31
What is genuinely new work
Nothing in ISO 27018 reaches these. This is the list to scope.
ISO22318-01Business continuity policy
ISO22318-02BCM program scope and objectives
ISO22318-03Resource allocation for BCM
ISO22318-04BCM roles and responsibilities
ISO22318-05Management commitment to BCM
ISO22318-06Business impact analysis methodology
ISO22318-07Critical activity identification
ISO22318-09Resource requirements assessment
ISO22318-10Interdependency mapping
ISO22318-11Continuity strategy development
ISO22318-16Exercise program development
ISO22318-17Tabletop and simulation exercises
ISO22318-18Full-scale testing procedures
ISO22318-19Post-exercise review and improvement
ISO22318-20Plan maintenance and update
ISO22318-4.1Supply Chain Continuity Programme
ISO22318-4.2Supply Chain Risk Appetite
ISO22318-5.1Supplier Identification and Mapping
ISO22318-5.2Supplier Criticality Assessment
ISO22318-5.3Supplier Dependency Analysis
ISO22318-5.4Supplier Continuity Requirements
ISO22318-5.5Supplier Due Diligence
ISO22318-6.1Supply Chain Continuity Strategies
ISO22318-6.2Alternative Supplier Arrangements
ISO22318-6.3Inventory and Buffer Stock Strategy
ISO22318-7.1Supplier Continuity Plans
ISO22318-7.2Communication and Coordination
ISO22318-8.1Supplier Continuity Exercising
ISO22318-8.2Supplier Performance Monitoring
ISO22318-9.1Concentration and Systemic Risk Review
ISO22318-9.2Continual Improvement of Supply Chain Continuity
Show the 5 you already have
ISO22318-08Recovery time and point objectives
ISO22318-12Recovery strategy for critical activities
ISO22318-13Alternate site and resource planning
ISO22318-14Supply chain continuity
ISO22318-15Communication strategy during disruption
How this is calculated
Already covered means a mapping runs from a control in ISO 27018 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