Framework overlap

Does GDPR cover NIST SP 800-30?

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

75% of NIST SP 800-30 you already have

GDPR already covers about 75% of NIST SP 800-30, leaving 2 of 8 controls as genuinely new work.

Already covered 3 Likely covered 3 New work 2

What is genuinely new work

Nothing in GDPR reaches these. This is the list to scope.

NISTSP30-5
Likelihood and Impact Determination
NISTSP30-7
Risk Communication and Sharing
Show the 6 you already have
NISTSP30-3
Threat Source and Threat Event Identification
NISTSP30-4
Vulnerability and Predisposing Condition Identification
NISTSP30-6
Risk Determination, Uncertainty, and Sensitivity Analysis
NISTSP30-1
Risk Management Strategy and Risk Assessment Programme Establishment
NISTSP30-2
Three-Tier Risk Assessment Scoping (Organisation, Mission/Business, Information System)
NISTSP30-8
Risk Assessment Maintenance, Continuous Monitoring, and Integration with the RMF

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