88% of OWASP MASVS you already have
NIST Cybersecurity Framework 2.0 already covers about 88% of OWASP MASVS, leaving
1 of 8 controls as genuinely new work.
Already covered 0
Likely covered 7
New work 1
No control in NIST Cybersecurity Framework 2.0
maps directly to one in OWASP MASVS. 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 NIST Cybersecurity Framework 2.0 reaches these. This is the list to scope.
OWASPMASVS-5MASVS-PLATFORM: Platform Interaction
Show the 7 you already have
OWASPMASVS-1MASVS-STORAGE: Storage of Sensitive Data
OWASPMASVS-2MASVS-CRYPTO: Cryptography Usage
OWASPMASVS-3MASVS-AUTH: Authentication and Authorization
OWASPMASVS-4MASVS-NETWORK: Network Communication
OWASPMASVS-6MASVS-CODE: Code Quality, Build Settings, and Updates
OWASPMASVS-7MASVS-RESILIENCE: Resilience Against Reverse Engineering
OWASPMASVS-8MASVS-PRIVACY: Privacy and Data Protection
How this is calculated
Already covered means a mapping runs from a control in NIST Cybersecurity Framework 2.0 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