ISO 27001: the shortcut to meeting NIS2, GDPR and DORA at once
ISO 27001 and NIS2 share almost the entire risk-management core. That is why a well-run management system is the best shortcut to the directive, and it also covers much of GDPR and DORA. However, it does not cover everything, and certification does not equal compliance.
In 30 seconds: ISO/IEC 27001:2022 gives you a management system, a risk assessment and 93 controls. Those controls match the directive’s measures, Article 32 of GDPR and the DORA ICT risk framework. Still, each regulation adds its own duties: reporting deadlines, data subject rights, an ICT third-party register and TLPT. In addition, ENISA published a table in June 2025 that links each technical requirement to the ISO standard.
Why ISO 27001 works as a foundation for NIS2
The standard sets out how to build and improve an information security management system (ISMS). First, you assess the risks. Then you choose Annex A controls and justify them in the Statement of Applicability. Finally, you audit and review the system every year.
That cycle matches what all three regulations ask for. Directive (EU) 2022/2555 requires measures with an all-hazards approach in Article 21. Regulation (EU) 2022/2554, known as DORA, demands a documented and reviewed ICT risk management framework. For its part, GDPR requires technical and organisational measures appropriate to the risk in Article 32.
Moreover, Article 25 of the directive encourages the use of European and international standards. So running ISO 27001 and NIS2 within one system is the most efficient way to work. To review the controls, see the 93 Annex A controls after the 2022 revision.
Coverage table by regulation
The table sums up what a mature ISMS brings when you handle ISO 27001 and NIS2 alongside GDPR and DORA. Coverage is indicative and depends on the real scope of your system.
| Obligation | What your ISMS brings | Coverage | What to add |
|---|---|---|---|
| Risk-management measures (directive, Art. 21) | Risk assessment, Annex A and Statement of Applicability | High | Emergency communications and full scope |
| Incident reporting (directive, Art. 23) | Controls A.5.24 to A.5.28 | Partial | Deadlines of 24 hours, 72 hours and one month |
| Management governance (directive, Art. 20) | Leadership and management review (clauses 5 and 9.3) | Partial | Formal approval and training for management bodies |
| Security of processing (GDPR, Art. 32) | Encryption, backups, access control and regular testing | High | Risk to individuals, not just to the business |
| Personal data breaches (GDPR, Arts. 33 and 34) | Incident management | Partial | Notice to the supervisory authority within 72 hours and, where needed, to data subjects |
| Rights, records of processing and DPIAs (GDPR) | Asset inventory and classification | Low | Privacy processes or ISO/IEC 27701 |
| ICT risk management framework (DORA, Arts. 5 to 16) | ISMS, continuity and change management | High | Requirements of Delegated Regulation (EU) 2024/1774 |
| Major incidents (DORA, Art. 19) | Incident management | Partial | Classification and reports at 4 hours, 72 hours and one month |
| Register of information on ICT third parties (DORA, Art. 28(3)) | Supplier controls A.5.19 to A.5.22 | Low | Templates from Implementing Regulation (EU) 2024/2956 |
| TLPT (DORA, Art. 26) | Management of technical vulnerabilities (A.8.8) | Low | Threat-led testing every three years, if designated |
ENISA: the official mapping between ISO 27001 and NIS2
On 26 June 2025, ENISA published its technical implementation guidance on Implementing Regulation (EU) 2024/2690. That regulation details the Article 21 measures for digital providers. They include cloud and data centre services, managed services and managed security services, DNS, online marketplaces and trust service providers.
The guidance offers practical advice and examples of evidence. It also includes a mapping table to standards such as ISO/IEC 27001:2022. Therefore, if you manage ISO 27001 and NIS2 together, that table gives you a starting map. Although it is not binding and targets those digital entities, its logic works for any organisation.
What your ISMS does not cover
Three areas sit outside any ISMS on its own.
Reporting deadlines the standard does not set
The standard asks you to manage incidents, but it sets no deadlines for authorities. By contrast, the directive requires an early warning within 24 hours, a notification within 72 hours and a final report within one month. DORA moves even faster. Under Delegated Regulation (EU) 2025/301, the initial notification is due 4 hours after you classify the incident as major. In addition, it can never come later than 24 hours after you detect it. If personal data is affected, you will also need to report the breach to the supervisory authority within 72 hours.
GDPR: beyond Article 32
Your ISMS covers the security of processing well. However, GDPR demands much more: a legal basis, records of processing, impact assessments, processor contracts and handling of rights. Article 32(3) also accepts approved certification mechanisms under Article 42 as evidence, and an ISO certificate is not one of them. To cover privacy, many organisations extend their system with ISO/IEC 27701.
DORA: third-party register and TLPT
Article 28(3) of DORA requires financial entities to keep a register of all their contracts with ICT providers. It must follow the templates in Implementing Regulation (EU) 2024/2956, and no Annex A control produces it as it stands. We explain it in how to prepare the register of information on ICT providers. In addition, entities that the supervisor identifies must run threat-led penetration testing at least every three years. Article 26 and Delegated Regulation (EU) 2025/1190 set this out. Remember, too, that for the financial sector DORA takes precedence over the directive on risk management and reporting.
ISO 27001 certification does not equal NIS2 compliance
An ISO 27001 certificate shows that your ISMS meets the standard within a set scope, but it does not prove NIS2 compliance. First, the scope can leave out services that the directive includes. Next, the Statement of Applicability can exclude controls that the regulator expects to see. Finally, the auditor checks conformity with the standard, not legal deadlines or management duties.
So treat certification as strong evidence, not as a free pass. In Spain, the draft transposing bill asks essential entities for a certificate of conformity, although the law has still not passed. We explain it in how Spain’s ENS relates to the directive.
How to combine ISO 27001 and NIS2 with GDPR and DORA
The efficient approach is to define each control once and link it to every regulation that requires it. That way, one piece of evidence serves several audits. These are the steps:
- Start from the ISMS risk assessment and add the risks to individuals that GDPR requires.
- Widen the scope to cover every service the directive affects.
- Bring the deadlines of all three regulations into a single incident clock.
- Turn your supplier inventory into the register of information if you are a financial entity.
- Record board approval and training.
With this method, ISO 27001 and NIS2 stop being two separate projects. In addition, GDPR and DORA become layers on the same base.
Frequently asked questions
Does ISO 27001 cover the NIS2 requirements?
Largely, yes. The ten areas of Article 21(2) have related controls in Annex A, so a mature ISO 27001 implementation covers much of NIS2. Even so, reporting deadlines, management accountability and often the full scope remain open.
Does a certified ISMS help with DORA?
It helps with the ICT risk management framework, but DORA adds its own requirements. Besides the register of information and TLPT, it requires you to classify incidents and report major ones within very short deadlines.
Does ISO 27001 cover Article 32 of GDPR?
It covers the security measures well. However, GDPR weighs the risk to individuals and asks for records, impact assessments and rights handling that the standard does not address.
Do I need ISO 27001 certification to comply with NIS2?
No. The directive does not require any specific certification, although it lets Member States impose European schemes for certain ICT products or services. Even so, a valid certificate against the 2022 version is strong evidence for the supervisor.
Reviewed on 14 October 2026. For information only, not legal advice.
How Atalaya GRC helps
Atalaya GRC manages ISO 27001 and NIS2 in the same system, alongside GDPR and DORA: one control, several regulations. Each Annex A control links to the articles it covers and to its evidence, service by service. In addition, the regulatory clock warns you before every reporting deadline. The third-party register forms the basis of your DORA register of information. See the ISO 27001 and 22301 page on Atalaya GRC or request a demo.

