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.
HomeArticlesSoftware Supplier Security Under NIS2
Supply Chain Security / 2026-10-09

Software Supplier Security Under NIS2

Record which purchased, licensed or managed software components support covered services, the supplier responsible and the systems or information they can affect. Include update channels, integrations and support access. A library, business application and privileged infrastructure agent have different risk profiles. Focus assurance on the component's actual influence on important systems.

Identify the software dependency

Record which purchased, licensed or managed software components support covered services, the supplier responsible and the systems or information they can affect. Include update channels, integrations and support access.

A library, business application and privileged infrastructure agent have different risk profiles. Focus assurance on the component's actual influence on important systems.

Evaluate secure development and vulnerability handling

Article 21(3) explicitly references the overall quality of products and supplier cybersecurity practices, including secure development procedures. Assess how security defects are discovered, triaged, remediated and communicated.

Ask about supported versions, security advisories and update provenance. A polished development policy alone does not demonstrate a timely security patch process.

Protect updates and integrations

Review how software packages are signed or otherwise verified, distributed and installed. Limit permissions granted to integrations and vendor support accounts; monitor changes to critical dependencies.

Assess whether emergency updates can be tested and rolled back safely. An unverified update pathway can create integrity risks even if the application normally operates reliably.

Plan for unsupported versions and supplier incidents

Identify end-of-support dates and what happens if a vendor stops issuing security fixes. Develop migration or compensating-control plans where supported alternatives are constrained by operational needs.

Agree how the vendor will share relevant vulnerability and incident information, while preserving the entity's independent assessment of its own reporting duties.

Document the supplier assurance decision

Keep records of software criticality, vulnerability exposure, supplier practices, observed gaps, mitigation ownership and review triggers. Reassess after major version changes or supplier acquisitions.

National requirements and any additional rules applicable to the entity should guide control selection. Do not claim NIS2 mandates one software security certification for all suppliers.

Questions on the text

Does outsourcing remove a covered entity's NIS2 responsibility?

No automatic transfer of statutory duties follows from outsourcing. Assess obligations for each legal entity under applicable national law.

Does the same supplier assessment suit every relationship?

No. The depth of assessment should reflect service criticality, access, exposure and applicable legal requirements.

More from the Desk

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.