Framework overlap

Does ISO/IEC 27003:2017 cover NIS2 Directive Implementing Acts?

You hold ISO/IEC 27003:2017 and have been told to do NIS2 Directive Implementing Acts. Here is how much overlaps, control by control.

63% of NIS2 Directive Implementing Acts you already have

ISO/IEC 27003:2017 already covers about 63% of NIS2 Directive Implementing Acts, leaving 3 of 8 controls as genuinely new work.

Already covered 1 Likely covered 4 New work 3

What is genuinely new work

Nothing in ISO/IEC 27003:2017 reaches these. This is the list to scope.

NIS2I-1
Implementing Regulation 2024/2690 Scope, Annex I Measures, and ENISA Technical Guidance
NIS2I-4
Supply Chain Security, Acquisition Development, and Effectiveness Assessment
NIS2I-8
Sector-Specific Requirements - Cloud Providers and Managed Service Providers (Articles 7, 10)
Show the 5 you already have
NIS2I-2
Policy, Risk Management, and Roles + Responsibilities
NIS2I-3
Incident Handling Policy, Reporting Significance Criteria, and Business Continuity
NIS2I-5
Cyber Hygiene, Training, Cryptography, and Human Resources Security
NIS2I-6
Access Control, Asset Management, and Physical Security
NIS2I-7
Network Security, Logging, Monitoring, and Vulnerability Handling

How this is calculated

Already covered means a mapping runs from a control in ISO/IEC 27003:2017 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