Framework overlap

Does API 1164 cover NIST SP 800-146?

You hold API 1164 and have been told to do NIST SP 800-146. Here is how much overlaps, control by control.

50% of NIST SP 800-146 you already have

API 1164 already covers about 50% of NIST SP 800-146, leaving 4 of 8 controls as genuinely new work.

Already covered 4 Likely covered 0 New work 4

What is genuinely new work

Nothing in API 1164 reaches these. This is the list to scope.

NISTSP146-2
SaaS Operational Recommendations and Provider Assurance
NISTSP146-3
PaaS Operational Recommendations and Application Portability
NISTSP146-5
Deployment Model Recommendations (Public, Private, Community, Hybrid)
NISTSP146-8
Cloud Auditing, Accountability, Cost Management, and Lessons Learned
Show the 4 you already have
NISTSP146-1
Cloud Adoption Strategy, Workload Suitability, and Decision Framework
NISTSP146-4
IaaS Operational Recommendations and Workload Hardening
NISTSP146-6
Cloud Security and Privacy Recommendations
NISTSP146-7
Service Level, Performance, Reliability, Interoperability, and Portability

How this is calculated

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