Platform OverviewOne evidence trail, from intake to Jira.See how it fits together
See it on your documentsA 30-minute call. Bring a vendor you are reviewing now.Book a demo
EU directiveDirective (EU) 2022/2555Checked

NIS2 supply chain security requirements

NIS2 Directive · Directive (EU) 2022/2555

In short

NIS2 requires essential and important entities in 18 sectors to manage cybersecurity risk, including the security of their supply chain and their relationships with direct suppliers, and to report significant incidents on fixed deadlines.

Who it applies to

Medium and large organisations in the sectors of Annexes I and II, such as energy, transport, banking, health, digital infrastructure, ICT service management, public administration, manufacturing of critical products and digital providers, plus some smaller entities named by member states. Each member state applies it through its own law.

Key dates

  1. 16 Jan 2023Entered into force
  2. 17 Oct 2024Deadline for member states to transpose it into national law
  3. 17 Oct 2024Implementing Regulation (EU) 2024/2690 sets technical measures for digital infrastructure and digital providers
  4. 18 Oct 2024National measures apply

What NIS2 asks of third-party risk management

Art. 20Management body accountability

The management body approves the cybersecurity risk measures, oversees them, can be held liable and must follow training.

Art. 21(2)(d)Supply chain security

Security-related aspects of the relationships between each entity and its direct suppliers or service providers.

Art. 21(3)Supplier-specific risk

Entities must take into account the vulnerabilities specific to each direct supplier, the overall quality of their products and cybersecurity practices, including secure development.

Art. 21(2)(e)Security in acquisition and development

Security in network and information systems acquisition, development and maintenance, including vulnerability handling and disclosure.

Art. 22Coordinated supply chain risk assessments

The EU can run coordinated risk assessments of critical ICT supply chains, and their results must be taken into account.

Art. 23Incident reporting

An early warning within 24 hours of becoming aware of a significant incident, a notification within 72 hours and a final report within one month.

Documents to request from vendors

  • Information security policy and risk management approach
  • SOC 2 Type II report or ISO/IEC 27001 certificate
  • Secure development and vulnerability handling policy
  • Incident notification commitment that supports your 24-hour early warning
  • List of the supplier's own critical suppliers
  • Business continuity and backup arrangements
  • Penetration test summary

In ProcureCortex

ProcureCortex checks supplier documents against the Article 21 measures you select, with your own notification deadlines as policy rules. A finding shows the clause, for example a 72-hour incident notice that leaves you no time for a 24-hour early warning.

How an assessment works

Sources

  1. Directive (EU) 2022/2555 (NIS2)eur-lex.europa.eu/eli/dir/2022/2555/oj
  2. Implementing Regulation (EU) 2024/2690eur-lex.europa.eu/eli/reg_impl/2024/2690/oj

Summarised for practitioners, not legal advice. Check the source text for your own obligations.

Vendor profilesby ProcureCortex

See it in the vendors you review

38 of 39 widely used SaaS vendors publish a subprocessor list. Read what each one publishes on its own pages, with the source behind every line.

Find each vendor’s subprocessor list

Check your vendors against NIS2.

Open a demo workspace with a sample vendor, its documents and its findings. Or bring your own vendor to a 30-minute call.

Procurement, compliance, security and auditOne workspace, one record of every decision

NIS2: questions

Short, direct answers.

Not directly unless the supplier is itself in scope. But in-scope entities must manage the security of their direct suppliers, so suppliers meet NIS2 requirements through contracts and assessments.

Managing the security aspects of relationships with direct suppliers and service providers, taking into account each supplier's vulnerabilities, product quality and cybersecurity practices.

An early warning within 24 hours of becoming aware of a significant incident, an incident notification within 72 hours, and a final report within one month of the notification.

No. It is a directive, so each member state passes its own law. Check the national law for scope, registration and penalties.