Framework overlap

Does GDPR cover NIST SP 800-145?

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

63% of NIST SP 800-145 you already have

GDPR already covers about 63% of NIST SP 800-145, 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 GDPR reaches these. This is the list to scope.

NISTSP145-2
Resource Pooling and Multi-Tenancy Characteristic
NISTSP145-4
Measured Service Characteristic and Billing Transparency
NISTSP145-5
Service Model Classification (SaaS, PaaS, IaaS)
Show the 5 you already have
NISTSP145-3
Rapid Elasticity Characteristic and Capacity Management
NISTSP145-7
Cloud Procurement Standards Aligned to NIST SP 800-145 Definition
NISTSP145-8
Governance, Reporting, and Stakeholder Education on Cloud Definition
NISTSP145-1
On-Demand Self-Service and Broad Network Access Characteristics
NISTSP145-6
Deployment Model Classification (Private, Community, Public, Hybrid)

How this is calculated

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