14% of ISO 22317 you already have
ISO 37301:2021 already covers about 14% of ISO 22317, leaving
31 of 36 controls as genuinely new work.
Already covered 1
Likely covered 4
New work 31
What is genuinely new work
Nothing in ISO 37301:2021 reaches these. This is the list to scope.
ISO22317-01Business continuity policy
ISO22317-02BCM program scope and objectives
ISO22317-03Resource allocation for BCM
ISO22317-04BCM roles and responsibilities
ISO22317-05Management commitment to BCM
ISO22317-06Business impact analysis methodology
ISO22317-07Critical activity identification
ISO22317-09Resource requirements assessment
ISO22317-10Interdependency mapping
ISO22317-13Alternate site and resource planning
ISO22317-16Exercise program development
ISO22317-17Tabletop and simulation exercises
ISO22317-18Full-scale testing procedures
ISO22317-19Post-exercise review and improvement
ISO22317-20Plan maintenance and update
ISO22317-4.1BIA Programme Establishment
ISO22317-4.2BIA Methodology and Approach
ISO22317-5.1Prioritized Activities Identification
ISO22317-5.2Impact Categories and Tolerances
ISO22317-5.3Maximum Tolerable Period of Disruption (MTPD)
ISO22317-5.4Recovery Time Objective (RTO)
ISO22317-5.5Recovery Point Objective (RPO)
ISO22317-5.6Minimum Business Continuity Objective (MBCO)
ISO22317-5.7Resource Requirements Analysis
ISO22317-5.8Interdependencies and Single Points of Failure
ISO22317-6.1BIA Data Collection
ISO22317-6.2BIA Validation and Sign Off
ISO22317-7.1BIA Outputs Reporting
ISO22317-7.2Linking BIA to Continuity Strategy
ISO22317-8.1BIA Maintenance and Refresh
ISO22317-8.2BIA Programme Assurance
Show the 5 you already have
ISO22317-15Communication strategy during disruption
ISO22317-08Recovery time and point objectives
ISO22317-11Continuity strategy development
ISO22317-12Recovery strategy for critical activities
ISO22317-14Supply chain continuity
How this is calculated
Already covered means a mapping runs from a control in ISO 37301:2021 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