75% of NIS2 Directive you already have
NIST Cybersecurity Framework 2.0 already covers about 75% of NIS2 Directive, leaving
2 of 8 controls as genuinely new work.
Already covered 0
Likely covered 6
New work 2
No control in NIST Cybersecurity Framework 2.0
maps directly to one in NIS2 Directive. 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.
NIS2D-4Management Body Accountability and Training - Articles 20 and 26
NIS2D-7Penalties, Enforcement, and Article 32-34 Supervision
Show the 6 you already have
NIS2D-1NIS2 Scope, Essential and Important Entities, Sectoral Coverage
NIS2D-2Cybersecurity Risk Management Measures - Article 21
NIS2D-3Incident Reporting Obligations - Articles 23 and 30
NIS2D-5Supply Chain Security - Article 21(2)(d) and 22
NIS2D-6Vulnerability Disclosure and CVD Programme - Article 12 and 21
NIS2D-8Cross-Border Coordination, ENISA, CSIRTs Network, and CER Coordination
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