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.
HomeArticlesSecure System Maintenance Under NIS2
Secure Acquisition Development Vulnerabilities / 2026-10-10

Secure System Maintenance Under NIS2

Secure system maintenance keeps critical technology supported, correctly configured and recoverable after deployment. Article 21(2)(e) explicitly covers maintenance security and vulnerability handling, so a programme should address both routine updates and the operational consequences of change.

Identify what requires maintenance

Maintain an inventory of relevant systems, versions, dependencies, support arrangements and owners. Highlight components supporting covered services, including appliances and operational technology that cannot always be maintained on an ordinary IT schedule.

Record maintenance constraints before a security issue creates urgency. An unsupported device with no viable replacement path can become a recurring source of avoidable risk.

Plan secure updates and repairs

Use supplier advisories, service criticality, exploit evidence and operational impact to prioritise work. Protect the integrity of update packages and define authorisation for important changes.

Where an update may interrupt an essential service, coordinate maintenance windows, backout procedures and recovery arrangements with the service owner.

Maintain secure settings and access

Review privileged accounts, remote support, certificates, exposed interfaces, logging and baseline compliance during maintenance. Ensure temporary supplier access is removed or constrained after work.

An equipment repair can reintroduce insecure defaults or old firmware. Verify relevant security properties after replacing hardware or restoring configurations.

Manage support and supplier dependencies

Track vendor end-of-support schedules, third-party maintenance commitments and availability of security fixes. When fixes are unavailable, consider isolation, access restrictions, monitoring or replacement according to risk.

Supplier responsibilities should be explicit. A contract requiring updates is ineffective if no one monitors advisories or confirms deployment.

Test changes and document exceptions

Keep implementation logs, relevant verification results, incidents caused by updates and outstanding risks. Differentiate completed maintenance from changes deferred with documented reasons and accountable approval.

For critical systems, test whether the change preserves recovery and continuity capabilities. A technically successful patch can still disrupt a dependent service.

Review the effectiveness of maintenance

Monitor persistent unsupported assets, repeated change failures, late remediation and loss of approved configurations. Feed findings into procurement and architecture decisions to reduce recurring operational risk.

The Directive sets proportionate obligations, while some entities must also follow national or provider-specific requirements. Avoid inventing universal patch deadlines or maintenance intervals.

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.