23% of ISO 31000 you already have
PCI SSF already covers about 23% of ISO 31000, leaving
33 of 43 controls as genuinely new work.
Already covered 3
Likely covered 7
New work 33
What is genuinely new work
Nothing in PCI SSF reaches these. This is the list to scope.
ISO31000-02Risk governance structure
ISO31000-03Risk culture and communication
ISO31000-04Stakeholder requirements for risk
ISO31000-06Risk identification methods
ISO31000-08Risk criteria and thresholds
ISO31000-11Risk treatment options and selection
ISO31000-12Risk treatment plan development
ISO31000-13Residual risk acceptance
ISO31000-14Risk transfer and insurance
ISO31000-15Control implementation and monitoring
ISO31000-16Risk monitoring procedures
ISO31000-17Risk reporting and communication
ISO31000-20Management review of risk program
ISO31000-4.1Risk management principles overview
ISO31000-4.2Integrated principle
ISO31000-4.3Structured and comprehensive principle
ISO31000-4.4Customised principle
ISO31000-4.5Inclusive principle
ISO31000-4.6Dynamic principle
ISO31000-4.7Best available information principle
ISO31000-4.8Human and cultural factors principle
ISO31000-4.9Continual improvement principle
ISO31000-5.3Integration into the organisation
ISO31000-5.4Design of framework
ISO31000-5.5Implementation
ISO31000-6.4.1Risk identification
ISO31000-6.4.2Risk analysis
ISO31000-6.4.3Risk evaluation
ISO31000-6.5Risk treatment
ISO31000-6.6Monitoring and review
ISO31000-6.7Recording and reporting
Show the 10 you already have
ISO31000-01Risk management policy and scope
ISO31000-05Risk management integration
ISO31000-18Risk register maintenance
ISO31000-07Risk analysis and evaluation
ISO31000-09Risk scenario development
ISO31000-10Risk interdependency analysis
ISO31000-19Continuous improvement of risk processes
ISO31000-5.2Leadership and commitment
ISO31000-6.2Communication and consultation
ISO31000-6.3Scope, context and criteria
How this is calculated
Already covered means a mapping runs from a control in PCI SSF 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