Framework overlap

Does ISO 27019 cover NIST SP 800-137?

You hold ISO 27019 and have been told to do NIST SP 800-137. Here is how much overlaps, control by control.

63% of NIST SP 800-137 you already have

ISO 27019 already covers about 63% of NIST SP 800-137, leaving 3 of 8 controls as genuinely new work.

Already covered 3 Likely covered 2 New work 3

What is genuinely new work

Nothing in ISO 27019 reaches these. This is the list to scope.

NISTSP137-2
Monitoring Metrics, Measures, and Frequencies
NISTSP137-3
ISCM Technical Architecture and Automation
NISTSP137-8
Programme Review, Training, and Third-Party ISCM
Show the 5 you already have
NISTSP137-1
ISCM Strategy, Governance, and Volatility Assessment
NISTSP137-6
Malware, Identity Access, and Network Boundary Monitoring
NISTSP137-7
Incident Response Integration and Ongoing Authorization
NISTSP137-4
Security Status Reporting and Risk Score Aggregation
NISTSP137-5
Vulnerability + Patch + Configuration Status Monitoring

How this is calculated

Already covered means a mapping runs from a control in ISO 27019 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