vendorapp logo

Docs

NIS2 vs ISO 27001: does certification make you compliant?


Short answer. No. ISO 27001 is a voluntary management-system standard; NIS2 is law. A certified ISMS is strong evidence toward several Article 21 measures and the fastest route to a defensible programme, but it does not cover the statutory reporting deadlines, registration, management liability, or anything outside your certification scope.

Last reviewed: 31 July 2026.

Does ISO make you NIS compliant

The confusion is understandable. Both concern information security management; both expect risk assessment, controls and continual improvement; a well-run ISMS covers most of what Article 21(2) lists.

But NIS2 imposes obligations that no certification body assesses, and it applies to your whole in-scope activity rather than to a scope statement you chose. Article 21(2) is a legal floor. ISO 27001 is a framework for deciding, and documenting, which controls you apply.

There is one place where certification carries formal weight: Article 24 allows member states to require the use of ICT products, services and processes certified under EU cybersecurity certification schemes, and Article 32(7) lists adherence to approved certification schemes as a factor when authorities decide on enforcement. Useful, but not a safe harbour.

Where the two align

An ISO 27001:2022 ISMS gives you, largely out of the box:

  • A risk assessment methodology and risk treatment process — Article 21(2)(a).
  • Incident management processes — Article 21(2)(b).
  • Continuity and backup controls — Article 21(2)(c).
  • Supplier relationship controls — Article 21(2)(d), via Annex A 5.19–5.23.
  • Secure development and vulnerability management — Article 21(2)(e).
  • Internal audit, monitoring, measurement and management review — Article 21(2)(f).
  • Awareness and training — Article 21(2)(g).
  • Cryptography — Article 21(2)(h).
  • HR security, access control and asset management — Article 21(2)(i).
  • Authentication controls — Article 21(2)(j).

That is a near-complete mapping to the ten measures, which is why "we have an ISMS" is a genuinely good starting position.

The gaps certification does not close

Four gaps recur:

1. Statutory incident reporting. ISO 27001 requires incident management; it says nothing about a 24-hour early warning to a national CSIRT, a 72-hour notification or a one-month final report. Your ISMS incident procedure must be extended with the regulatory clock, the reporting channels, and the significance criteria. See NIS2 incident reporting timelines.

2. Scope. Certification covers a declared boundary. NIS2 covers your in-scope services, entities and member states. If your certificate covers one product line and one data centre, the rest of the organisation is uncertified and unevidenced.

3. Governance and liability. Article 20's specific duties — management-body approval of the measures, oversight, mandatory training, personal liability — go beyond ISO's "top management commitment". You need a dated approval record. See What NIS2 requires of directors.

4. Registration and supervision. Registering with the competent authority, responding to supervisory requests, submitting to audits and inspections. No certification body substitutes for the regulator.

A fifth, softer gap: risk acceptance. ISO 27001 lets you exclude a control with justification via the statement of applicability. Article 21(2) does not permit you to exclude a measure — proportionality changes depth, not existence.

Mapping Annex A to the ten measures

For supply chain specifically, the ISO 27001:2022 Annex A controls that carry the load:

ControlCoverage
5.19 Information security in supplier relationshipsThe programme itself — processes and procedures to manage supplier-related risk
5.20 Addressing information security within supplier agreementsThe contractual layer — the clause set NIS2 needs
5.21 Managing information security in the ICT supply chainICT products and services specifically, including sub-suppliers and components
5.22 Monitoring, review and change management of supplier servicesThe ongoing part — reassessment cadence and change handling
5.23 Information security for use of cloud servicesCloud acquisition, use and exit

Implemented properly, 5.19–5.23 satisfy most of Article 21(2)(d). What they do not automatically produce is the per-supplier evidence trail in the form supervisors ask for — see What supply chain evidence do regulators expect?

Using your ISMS as the backbone

If you are certified, do not start a parallel NIS2 programme. Extend:

  1. Reconcile scope. Compare the ISMS scope statement against your in-scope NIS2 entities and services. Document the delta and plan to close it.
  2. Map controls to the ten measures in a single traceability table. It becomes your supervisory response document.
  3. Add the regulatory clock to the incident procedure — significance criteria, deadlines, channels, named filers, and a timestamp log.
  4. Add the governance layer — management-body approval record, board reporting, training records.
  5. Extend supplier controls to per-supplier evidence — register, tiering criteria, dated assessments, remediation log.
  6. Register with each relevant competent authority and record the registrations.
  7. Reuse internal audit as your Article 21(2)(f) effectiveness evidence, extending its scope to cover the added items.

Organisations that do this typically find the work is weeks, not quarters — the ISMS carries most of it.

What about suppliers with certificates

When a supplier offers ISO 27001 as assurance, three checks before you accept it:

  • Scope statement. Does it cover the service you buy, delivered from the sites and by the entity you contract with? Certificates covering "corporate IT" are common and useless for a SaaS assessment.
  • Statement of applicability. Which controls were excluded and why. Exclusions around supplier management or secure development matter to you directly.
  • Currency and body. Is it in date, and issued by an accredited certification body? Check the certificate number against the registry.

Certification should shorten your questionnaire, not replace your assessment. SOC 2 Type II reports work similarly — read the scope, the trust services criteria covered, the period, and the exceptions section, which is where the useful information lives. See ISO 27001 and SOC 2 for a fuller comparison, and NIS2 supplier questionnaire for what to ask on top.