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.
HomeArticlesFourth-Party Cybersecurity Risk Under NIS2
Supply Chain Security / 2026-10-10

Fourth-Party Cybersecurity Risk Under NIS2

Fourth-party cybersecurity risk arises when a direct supplier depends on another provider whose failure or compromise could affect the covered entity. NIS2 explicitly addresses direct supplier and service-provider relationships; indirect dependencies should be examined where they materially affect the organisation's overall risk.

Understand the indirect dependency

A managed service provider may host its platform with a separate cloud operator, rely on a specialist identity service or outsource security monitoring. The covered entity contracts with the first provider, but an incident at the subprovider may still interrupt its services.

Map significant dependencies through the direct supplier, prioritising those whose failure could impact critical operations. The term fourth party is a risk management description, not a distinct entity category established by NIS2.

Identify concentration and common causes

Different direct suppliers may share one hosting region, telecommunications network or security technology. This can make apparently diversified supply chains vulnerable to the same incident.

Review concentration at the service level. A supplier inventory that lists only contractual counterparties may miss dependencies that determine continuity.

Obtain proportionate visibility

Discuss material subproviders and changes to critical subcontracting arrangements with direct suppliers. Seek assurance about their oversight, resilience and incident escalation without presuming access to every subprovider's confidential information.

Contractual disclosure and audit rights need to be feasible, risk-based and consistent with applicable law. Where visibility is limited, record the uncertainty and possible mitigations.

Plan for a fourth-party disruption

Assess whether the direct supplier can recover, switch services or provide an alternate operating mode if a critical subprovider becomes unavailable. Consider technical lock-in, data portability and the realism of stated recovery targets.

Exercises that include shared infrastructure outages can expose dependencies that ordinary supplier assurance reports do not reveal.

Keep legal scope and accountability clear

Article 21(2)(d) refers to direct suppliers and service providers, and Article 21(3) sets related considerations. Mapping indirect risk does not mean that the Directive automatically imposes an identical direct-assessment obligation on every fourth party.

Record material dependencies, supplier responses, continuity options and review triggers. Check national implementation and any additional obligations applicable to the entity's sector.

Questions on the text

Are the same measures mandatory for every supplier?

No. Control selection should be proportionate to the supplier's role, exposure, risks and applicable law.

Should the assessment change after a significant supplier incident?

Yes. Material incidents, changed services or new dependencies can require reassessment and corrective action.

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.