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

Security Change Management Under NIS2

Secure change management helps organisations avoid introducing vulnerabilities or service outages when systems are updated, reconfigured or integrated. It supports NIS2 Article 21(2)(e) on secure acquisition, development and maintenance, alongside risk-based continuity and effectiveness measures.

Classify changes by cyber and service impact

Determine what system is changing, which covered services rely on it, what privileges or interfaces will change and whether the change could affect availability, integrity or confidentiality. Link change records to assets and accountable service owners.

An emergency security patch, a configuration change to shared identity and a minor cosmetic update require different scrutiny. Make the classification reflect actual exposure, not simply the number of code lines modified.

Establish approval and separation of duties

Specify who proposes, assesses, tests and approves a consequential change. Where feasible, avoid allowing a single privileged account to bypass review, deployment safeguards and logging.

Emergency procedures may use expedited approvals but should retain traceability and retrospective review. An approval process that cannot operate during an urgent vulnerability response may itself increase risk.

Verify before deployment

Define meaningful acceptance tests for access controls, integrations, recovery capability and relevant security properties. Protect development pipelines and deployment secrets, and ensure that proposed software or configuration originates from trusted sources.

Testing should consider operational dependencies. A patch that closes one weakness but prevents critical services from restarting requires a managed decision and recovery route.

Plan rollback and communication

Document deployment windows, affected stakeholders, go or no-go criteria and restoration options. For high-impact systems, verify that reliable configuration backups and recovery permissions are available before implementing the change.

A rollback is not always safe for database schema or security-sensitive changes. Record viable alternatives and the limits of recovery.

Confirm results and investigate failures

After implementation, verify the intended control is present and services behave as expected. Review logs or monitoring signals where appropriate. Investigate unsuccessful or unauthorised changes and feed findings into vulnerability handling.

A closed ticket without validation is weak evidence. Capture the version, result, reviewer, and outstanding issues.

Maintain usable records and legal distinctions

Retain change rationale, impact assessment, approvals, test evidence, implementation timing and exceptions. Analyse recurring emergency changes and failures to improve controls.

NIS2 does not require every entity to adopt an identical change advisory board or workflow. More specific rules may apply under national law or Regulation 2024/2690 for the specified provider categories.

Questions arising

Does NIS2 mandate a formal change advisory board for every entity?

No. Its general requirements are proportionate and do not prescribe a single board structure for all organisations.

Can emergency patches skip all security records?

Urgency may justify streamlined approval, but accountability, testing where feasible and retrospective review remain important.

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.