Framework overlap

Does GDPR cover OWASP SAMM?

You hold GDPR and have been told to do OWASP SAMM. Here is how much overlaps, control by control.

80% of OWASP SAMM you already have

GDPR already covers about 80% of OWASP SAMM, leaving 1 of 5 controls as genuinely new work.

Already covered 0 Likely covered 4 New work 1

No control in GDPR maps directly to one in OWASP SAMM. Everything counted as covered is covered because both map to the same third standard, which is what a crosswalk is, but it is an inference rather than a lookup.

What is genuinely new work

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

OWASPSAMM-3
Implementation: Secure Build, Secure Deployment, Defect Management
Show the 4 you already have
OWASPSAMM-1
Governance: Strategy, Policy, Compliance, Education, Champions
OWASPSAMM-2
Design: Threat Assessment, Security Requirements, Security Architecture
OWASPSAMM-4
Verification: Architecture Assessment, Requirements-Driven Testing, Security Testing
OWASPSAMM-5
Operations: Incident Management, Environment Management, Operational Management

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