ISO 27001:2022 and NIS2: mapping Article 21
If you already run ISO 27001, most of NIS2 is covered. The table below shows which control covers which point, and what still has to be built on its own.
Article 21(2) of the NIS2 Directive, transposed in Romania by OUG 155/2024, lists ten categories of measures, a) to j). Nearly all of them have a direct counterpart in Annex A of ISO 27001:2022. DNSC has not issued an official mapping, so the table below is a working one: the mapping we use in the platform, which you can check against your own Statement of Applicability.
The table
| Point | What NIS2 requires | ISO 27001:2022 controls |
|---|---|---|
| a) | Policies on risk analysis and information system security | A.5.1 Policies for information security; A.5.2 Information security roles and responsibilities; A.5.36 Compliance with policies, rules and standards |
| b) | Incident handling | A.5.24 Incident management planning and preparation; A.5.25 Assessment and decision on information security events; A.5.26 Response to incidents; A.5.27 Learning from incidents; A.5.28 Collection of evidence |
| c) | Business continuity: backup, disaster recovery, crisis management | A.5.29 Information security during disruption; A.5.30 ICT readiness for business continuity; A.8.13 Information backup; A.8.14 Redundancy of information processing facilities |
| d) | Supply chain security | A.5.19 Information security in supplier relationships; A.5.20 Security within supplier agreements; A.5.21 ICT supply chain; A.5.22 Monitoring and change of supplier services |
| e) | Security in acquisition, development and maintenance, including vulnerability handling | A.8.25 Secure development life cycle; A.8.26 Application security requirements; A.8.27 Secure architecture and engineering principles; A.8.28 Secure coding; A.8.29 Security testing; A.8.8 Management of technical vulnerabilities |
| f) | Assessing the effectiveness of measures | A.5.35 Independent review; A.5.36 Compliance with policies; A.5.37 Documented operating procedures |
| g) | Basic cyber hygiene and training | A.6.3 Awareness, education and training; A.6.8 Information security event reporting; A.8.7 Protection against malware |
| h) | Cryptography and, where appropriate, encryption | A.8.24 Use of cryptography |
| i) | Human resources security, access control, asset management | A.5.9 Inventory of assets; A.5.10 Acceptable use; A.5.11 Return of assets; A.5.14 Information transfer; A.5.15 Access control; A.5.16 Identity management; A.5.17 Authentication information; A.5.18 Access rights; A.6.1 Screening; A.6.2 Terms and conditions of employment; A.8.2 Privileged access rights; A.8.3 Information access restriction; A.8.5 Secure authentication |
| j) | Multi factor or continuous authentication, secured communications | A.8.5 Secure authentication; A.8.20 Networks security; A.8.21 Security of network services; A.8.22 Segregation of networks |
What ISO 27001 does not give you
Three things have to be built separately, certificate or not.
Reporting deadlines. ISO 27001 requires an incident management process but sets no deadlines. NIS2 requires an early warning within 24 hours, a notification within 72 hours and a final report within a month, to the national CSIRT, which in Romania is DNSC.
Obligations towards DNSC. Registration, the risk level evaluation under the ENIRE@RO methodology, the maturity self assessment and the remediation plan each have their own deadline under OUG 155/2024 and the DNSC orders. ISO does not know about them.
Management accountability. The ordinance requires the management body to approve the measures and to take part in training. Clause 5 of ISO 27001 comes close, but NIS2 wants a recorded, dated approval.
The table covers Article 21. The tiered catalogue of measures in DNSC Order 1/2026 is a separate exercise.
How Phalanx uses the table
In Phalanx, NIS2 is a view over the ISO controls you already have: when every applicable control of a point is implemented and documented, the point shows as covered, and until then you see exactly which control is missing. Automated checks carry references to the controls and requirements they support, for example ISO 27001 A.8.24 and NIS2 Art. 21(2)(h). Reporting deadlines start when a NIS2 incident is recorded, using its detection date, rather than on every open case.