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.
HomeArticlesWhat Article 21 of NIS2 Requires
Article 21 Risk Management / 2026-10-09

What Article 21 of NIS2 Requires

Article 21 requires covered essential and important entities to manage cybersecurity risks using proportionate technical, operational and organisational measures. Those measures must protect the security of network and information systems used in operations or services, follow an all-hazards approach, and address the ten areas identified in Article 21(2).

Start with the relevant entity and services

An Article 21 review should begin with the legal entity that may be covered and the services it delivers. The organisation should map the systems supporting those services, including outsourced infrastructure and systems shared with a corporate group.

A single corporate group may have entities with different sector classifications or national obligations. The review should record which entity owns each decision and which Member State's requirements apply.

Assess risk before selecting controls

A risk assessment should connect plausible threat scenarios to affected assets, service consequences and existing safeguards. It should address accidental events and physical disruptions as well as malicious cyber activity. This is necessary because Article 21 uses an all-hazards approach.

For example, a service operator may consider both ransomware affecting its production environment and loss of power affecting a data centre. The two scenarios may need different preventive measures, recovery procedures and dependencies.

Meet the minimum areas without treating them as isolated tasks

The ten areas in Article 21(2) cover risk and security policies, incident handling, continuity, supply chains, secure acquisition and maintenance, effectiveness assessment, cyber hygiene and training, cryptography, workforce and access security, and appropriate authentication and communication safeguards.

An organisation should identify its current controls under each area and record gaps. Requirements cannot be dismissed merely because another control framework uses different headings. Mapping ISO or another standard may help, but the legal requirement remains the reference point.

Show measures operate and are reviewed

An approved policy is one form of evidence, not the completed security outcome. Testing a backup restoration, reviewing privileged access, validating supplier escalation contacts and tracking incident lessons demonstrate whether controls function as intended.

Assign owners and review dates to high-priority weaknesses. Escalate decisions about unresolved risks using the organisation's governance process; Article 20 places obligations on management bodies to approve and oversee implementation of cybersecurity risk-management measures.

Keep the legal boundary clear

Article 21 states the EU framework, while national implementing law and, where applicable, detailed implementing rules determine how it operates for a covered entity. Record the legal provisions consulted and avoid using an EU-wide checklist as a substitute for a jurisdiction-specific review.

Points of clarification

Is Article 21 limited to technical IT controls?

No. The provision addresses technical, operational and organisational measures, including governance, supply-chain security, training and continuity.

What should be retained as evidence?

Retain the risk assessment, control ownership, implementation records, test outcomes and decisions about remediation.

Further entries on this subject

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.