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

Third-Party Access Risk Under NIS2

External provider access can expose an organisation's covered services through privileged credentials, remote tools or poorly controlled integrations. NIS2 Article 21 addresses both supply chain security and access control, so supplier access should be assessed as an operational security risk rather than only a contractual matter.

Identify every route into covered systems

Inventory vendor user accounts, remote management agents, API keys, support portals and temporary maintenance connections. Map each route to a named provider, business purpose, systems reached and internal owner.

Do not assume access is limited to interactive logins. Automated integrations and management agents can retain powerful permissions long after the original project has ended.

Apply least privilege and strong authentication

Define what the supplier needs to perform the contracted task and avoid broad standing permissions where narrower access is feasible. Use appropriate multifactor authentication, dedicated identities and segregation for sensitive environments.

Review emergency access separately, with authorisation, traceability and a clear process for disabling privileges when the emergency ends.

Monitor behaviour and coordinate incidents

Maintain useful logs for privileged changes and access attempts, with retention appropriate to risk and applicable requirements. Agree on rapid escalation if a supplier account is compromised or suspicious activity is detected.

Where an external incident affects covered services, the entity must independently assess whether notification duties arise under the relevant national implementation of Article 23.

Review access across supplier changes

Changes in contracted scope, subcontractors, employees or ownership can invalidate access approvals. Reconcile the approved access list with actual active credentials and installed remote tools.

Offboarding should remove accounts, tokens, network routes and administrative dependencies. Confirm removal rather than assuming contract expiry automatically disables technical access.

Document governance and test controls

Keep the risk assessment, access approvals, supplier responsibilities, authentication settings, audit findings and periodic review evidence. Exercise emergency revocation where it matters most.

Article 21(2)(i) also addresses human resources security, access control policies and asset management. Consider these requirements alongside Article 21(2)(d), with national and provider-specific rules checked separately.

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.