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.
HomeArticlesPatch Management Requirements Under NIS2
Secure Acquisition Development Vulnerabilities / 2026-10-10

Patch Management Requirements Under NIS2

Patch management implements part of secure system maintenance and vulnerability handling under NIS2 Article 21(2)(e). NIS2 does not set one universal number of days for every security patch; timing and safeguards should be selected according to risk and any more specific applicable rules.

Inventory systems and update responsibility

Identify operating systems, applications, network devices, firmware and dependencies supporting covered services. Record suppliers, supported versions, responsible teams and maintenance constraints.

Patch plans cannot protect unmanaged assets. Distinguish systems patched automatically by vendors from those requiring internal testing or specialist service windows.

Prioritise with business and threat context

Assess severity, exploitation evidence, exposure, privilege and the consequences of compromise. Flag emergency changes for critical externally reachable weaknesses while considering service availability.

Static categories alone can mislead. A supplier's critical advisory needs to be mapped to the version and configuration actually in use.

Test and deploy safely

Use controlled testing where possible, verify authenticity of updates and maintain rollback or recovery arrangements appropriate to service criticality. Coordinate operational technology and other fragile environments with responsible owners.

A rushed update can interrupt covered services. Document necessary exceptions, temporary restrictions and the reason for the chosen deployment window.

Manage suppliers and unsupported components

Agree who tracks advisories and applies updates in managed or hosted systems. Escalate when a supplier cannot deliver a fix and consider compensating controls, isolation or replacement.

Procurement should account for security support lifecycles, because unsupported products can create persistent risks that routine patching cannot resolve.

Verify installation and exception closure

Compare deployed versions or other technical evidence against the target, confirm required services still function and track failed installations. Keep accepted deferrals visible to accountable risk owners.

An installed package does not always prove that the vulnerable function has been mitigated; investigate configuration, restart and environmental requirements where relevant.

Measure outcomes and check applicable rules

Maintain evidence of scope, update decisions, deployment outcomes and unresolved risks. Review repeat failures and time taken to resolve exposed critical weaknesses.

Article 21 sets the general framework. Specific providers within the scope of Regulation (EU) 2024/2690 have more detailed obligations; check that scope and national law rather than inventing an across-the-board NIS2 patch deadline.

Questions arising

Does NIS2 prescribe one universal technical process for every entity?

No. The Directive requires appropriate and proportionate measures; additional rules may apply depending on the entity and jurisdiction.

How should exceptions be handled?

Document the exposure, mitigation, accountable approver, review triggers and an actionable route to resolution.

Related entries

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.