An independent information publicationDirective (EU) 2022/2555 · The NIS2 DirectiveNot an official publication
The Independent NIS2 Desk
NIS2 Compliance
Independent information on the NIS2 Directive, for the organisations it covers.
HomeArticlesNIS2 Article 21 Gap Assessment: Controls, Evidence and Priorities
Readiness Templates Software Automation / 2026-10-11

NIS2 Article 21 Gap Assessment: Controls, Evidence and Priorities

An Article 21 gap assessment compares the cybersecurity risk-management measures actually operating in an organisation with the Directive's required measure areas and applicable national law. It should document coverage, effectiveness, evidence and remediation rather than simply award a checklist score.

Define the assessment boundary

Identify the covered legal entity, regulated services, critical systems, providers and responsible owners. Confirm its Member State implementing law before describing a gap as a legal noncompliance.

Article 21(1) sets an appropriate and proportionate, all-hazards approach. A gap assessment must therefore reflect exposure, service criticality, incident likelihood and severity, and the organisation's circumstances.

Map the ten Article 21 measure areas

Review policies on risk analysis and information security; incident handling; business continuity, backup, disaster recovery and crisis management; supply-chain security; secure acquisition, development, maintenance and vulnerability handling; effectiveness assessment; basic cyber hygiene and training; cryptography and encryption where appropriate; human resources security, access control and asset management; and suitable authentication and secure communications.

Use the actual wording and structure of Article 21(2) rather than treating a commercial control catalogue as law. For specific digital and ICT providers, consider the additional detail in Implementing Regulation (EU) 2024/2690 when applicable.

Distinguish documented, implemented and tested

A published policy is different from an operating safeguard. Record for each requirement the intended control, owner, systems in scope, evidence source, last test and any limitation.

A backup procedure may appear complete but fail restoration. A supplier questionnaire may exist while significant exceptions go unreviewed. Assessment status should reflect such outcomes rather than counting documents.

Prioritise the resulting gaps

Connect every finding to affected services, risk impact, potentially relevant legal provisions and an accountable remediation owner. Consider immediate safeguards for exposed critical assets and set realistic deadlines for permanent correction.

Keep unresolved national-law interpretation separate from verified operational failures. Escalate issues involving risk acceptance or resources to the appropriate management body.

Verify corrective action and update the baseline

Recheck controls after changes, preserving the initial finding and the evidence of verified closure. Update the assessment following material incidents, outsourcing changes, acquisitions or relevant legal amendments.

Report the residual exposure and areas lacking reliable evidence. An overall percentage can help track work, but cannot alone demonstrate regulatory compliance.

Questions on the text

Does this template provide a binding NIS2 compliance finding?

No. It structures a documented preliminary assessment that requires review against applicable legislation and relevant facts.

Does NIS2 prescribe one scoring methodology?

The Directive requires appropriate and proportionate risk-management measures; the assessment approach must suit the circumstances and applicable rules.

When should the assessment be revisited?

Review it after material changes to services, risks, corporate structure or the legal framework.

More from the Desk

The texts relied on

General editorial guidance only: it does not determine your organisation's legal obligations. See our editorial policy for how this site works and corrects errors.