Headnote
Article 21 requires covered entities to take appropriate and proportionate technical, operational and organisational measures to manage risks to the security of network and information systems used for their operations or services. The measures must address an all-hazards approach and at least ten specified areas, from risk analysis and incident handling to supply-chain security, access control and multifactor authentication where appropriate. The applicable national law and any sector-specific EU rules still need checking.
Who must apply Article 21
Article 21 concerns essential and important entities within the NIS2 framework. Determining whether a legal entity falls within scope comes first: its activity, sector, size, specific inclusion rules and the Member State with jurisdiction can change the result.
The duty concerns network and information systems used for the entity's operations or provision of services. A documented asset and service inventory helps identify which systems and dependencies the risk assessment should cover.
The proportionality test
Article 21(1) calls for measures that are appropriate and proportionate. The assessment must take account of the entity's degree of exposure to risks, its size, the likelihood of incidents and their severity, including societal and economic impact. Article 21(2) also refers to state of the art, relevant European and international standards and the cost of implementation.
Cost does not create a general exemption. The organisation should explain why each selected safeguard matches its exposure and service criticality, and why any material gaps remain acceptable or require remediation. A small operator delivering a highly critical service may need stronger measures than headcount alone would suggest.
The ten minimum measure areas
Article 21(2) identifies ten areas that the risk-management measures must cover at least. Their application should form a connected programme rather than ten documents prepared independently.
- Policies on risk analysis and information system security
- Incident handling
- Business continuity, including backup management, disaster recovery and crisis management
- Supply-chain security, including relevant supplier relationships
- Security in network and information system acquisition, development and maintenance, including vulnerability handling and disclosure
- Policies and procedures to assess effectiveness of cybersecurity risk-management measures
- Basic cyber hygiene and cybersecurity training
- Policies and procedures on cryptography and, where appropriate, encryption
- Human resources security, access control policies and asset management
- Multifactor authentication or continuous authentication solutions, secured communications and secured emergency communication systems where appropriate
Translate legal duties into operating controls
A useful control map links each Article 21 area to the systems in scope, an accountable owner, the operating control and its evidence. For incident handling, that might mean an approved response procedure, on-call escalation, incident records and exercise results. For suppliers, it may include a critical-supplier inventory, security requirements in contracts and periodic reassessments.
Controls should be assessed for actual effectiveness. A policy that was approved but never used does not demonstrate that response teams can detect, contain or recover from an incident. Evidence can include testing results, training records, configuration reviews, management decisions and corrective-action tracking.
National law and sector-specific measures
NIS2 is a directive, so covered entities need to consider the applicable Member State's implementing legislation and competent-authority guidance. The Directive also provides for implementing acts establishing technical and methodological requirements for certain digital infrastructure and ICT-related entities. Do not assume those detailed rules apply automatically to every NIS2 sector.
The regulatory review should identify the exact legal entity, relevant national measures, applicable implementing rules, reporting authority and review date. Keep proposals for legal change separate from rules already in force.
Points of clarification
Does Article 21 prescribe a single checklist for every organisation?
No. It specifies minimum areas and a proportionality framework, while concrete controls depend on the entity's risks, services and applicable legal requirements.
Do important entities also have Article 21 duties?
Yes. Both essential and important entities are subject to Article 21 within the relevant NIS2 framework.
Is documenting policies enough?
No. Entities need appropriate measures in operation and should be able to demonstrate how those measures are implemented and evaluated.