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.
HomeArticlesEnd-of-Life Systems and NIS2 Cybersecurity Risk
Secure Acquisition Development Vulnerabilities / 2026-10-10

End-of-Life Systems and NIS2 Cybersecurity Risk

End-of-life systems can create persistent security risk when vendors stop providing fixes, support or replacement parts. Under NIS2 Article 21(2)(e), secure system maintenance and vulnerability handling make lifecycle decisions relevant to covered entities, but no universal rule requires every legacy system to be replaced on the same date.

Identify unsupported and soon-to-expire assets

Link hardware, software, firmware and platform dependencies to supplier support dates and covered services. Track versions and ownership so end-of-support announcements can be assessed against the actual environment.

Support status may differ for individual editions or extended contracts. Verify the relevant supplier terms rather than assuming all installations of a product share the same deadline.

Assess exposure and operational constraints

Evaluate external reachability, privileged connections, exploitable weaknesses, data handled and consequences of failure or compromise. Determine why the legacy technology remains necessary and whether replacement is technically feasible.

Some industrial or specialist systems cannot be replaced immediately without threatening service continuity. A risk-based decision should acknowledge that constraint while addressing the exposure.

Choose compensating measures where needed

Consider segmentation, restricted access, monitoring, application controls or removal of unnecessary services when reliable security fixes are unavailable. Validate whether the chosen measures can realistically limit relevant attack paths.

Compensating controls are not permanent evidence of safety. Revisit them after new vulnerabilities, network changes or supplier developments.

Plan migration and test dependencies

Establish a realistic replacement plan with responsible owners, funding, compatibility testing, data export and recovery arrangements. Identify interfaces or licences that could block a safe migration.

A rushed replacement can itself interrupt covered services. Test critical functions and rollback options before removing a long-lived system.

Record exceptions and management decisions

Maintain the asset's support position, identified risk, mitigation effectiveness, replacement milestones and documented approval for continued operation. Escalate especially material exposure to accountable leaders.

Make clear when a plan is delayed and how the interim risk will be managed. A historical exception should not silently authorise indefinite use.

Link lifecycle planning to procurement

Require suitable support lifetime and update commitments for new ICT acquisitions, reducing the chance that today's purchasing decisions create tomorrow's unsupported estate.

Check relevant national law and applicable provider-specific EU provisions when selecting measures; Article 21 does not establish a single fixed retirement deadline for every type of system.

Questions arising

Does NIS2 prescribe one identical technical configuration for every system?

No. The Directive requires appropriate and proportionate measures; detailed obligations may depend on entity type and national law.

What should happen when a required control cannot be applied?

Document the exposure, accountable approval, compensating measures, review triggers and a credible remediation plan.

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.