75% of OpenSSF Scorecard you already have
GDPR already covers about 75% of OpenSSF Scorecard, leaving
2 of 8 controls as genuinely new work.
Already covered 0
Likely covered 6
New work 2
No control in GDPR
maps directly to one in OpenSSF Scorecard. 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.
OSSFSC-4Security Policy, Vulnerability Disclosure, Responsible Reporting
OSSFSC-5Static Analysis, Fuzzing, Testing Coverage
Show the 6 you already have
OSSFSC-1Branch Protection, Code Review, and Repository Governance
OSSFSC-2Dependency Management, Pinning, Updates, Vulnerability Tracking
OSSFSC-3Build, CI/CD Security, Workflow Permissions, Dangerous Patterns
OSSFSC-6Signed Releases, Provenance, Trusted Publishing, Binary Artifacts
OSSFSC-7Webhook Authentication, Contributors Diversity, Aggregate Score
OSSFSC-8Project Maintenance, Sustainability, Integration with Supply Chain Security
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