vendorapp logo

Docs

What contract clauses does NIS2 require with suppliers?


Short answer. NIS2 prescribes no clause list. But Article 21(2)(d) covers "security-related aspects concerning the relationships" with suppliers, and a relationship is governed by its contract — so in practice you need clauses covering security requirements, incident notification, access and personnel controls, subcontracting, audit or evidence rights, and secure exit.

Last reviewed: 31 July 2026.

What clauses does NIS require

There is no NIS2 equivalent of DORA's Article 30 list. The directive states the outcome; you choose the instrument. Every serious implementation reaches the same conclusion — the contract is the only mechanism that binds a third party you do not control.

Commission Implementing Regulation (EU) 2024/2690 makes this explicit for the digital entities it covers, requiring security requirements to be set in agreements with direct suppliers and service providers. Even outside its scope, it is the closest thing to an official clause template.

Why contracts are the control

A supplier assessment tells you what is true today. A contract determines what you can require tomorrow: notification when things go wrong, evidence on demand, the right to inspect, and an orderly exit.

Three consequences follow:

  • Assessment findings that are not reflected in the contract have no enforcement path.
  • A supplier that will not accept a 24-hour notification obligation is telling you something about their incident capability.
  • Contract terms are durable evidence. They are dated, signed and easy for a supervisor to inspect — which is exactly why supervisors ask for them.

The core clause set

ClauseWhat it should do
Security requirementsBind the supplier to a defined security standard or schedule — not "industry best practice". Reference a named framework or an annexed control set
Incident notificationRequire notification of security incidents affecting your data or services within a fixed window, with defined content and a named contact channel
Cooperation during incidentsRequire assistance with investigation, forensics, evidence preservation and any regulatory reporting you must make
Access control and personnelLeast privilege, joiner/mover/leaver handling, background screening proportionate to access, named individuals for privileged access
Data handling and locationCategories, permitted processing, storage locations, encryption in transit and at rest, deletion standards
SubcontractingPrior notice or consent for material subcontractors, flow-down of equivalent obligations, right to object
Assurance and auditRight to request evidence — certifications with scope, audit reports, test summaries — and a proportionate audit or inspection right
Vulnerability and patchingRemediation timeframes by severity; coordinated vulnerability disclosure; for software, a disclosure policy and patch commitments
Business continuityRecovery objectives aligned to your own, tested, with results shared
Change notificationNotice of material changes to the service, its architecture, its hosting location or its ownership
Termination and exitData return in an agreed format, verified deletion, access revocation timelines, transition assistance
Compliance and cooperationCooperation with your regulatory obligations and with your competent authority where relevant

Not every clause belongs in every contract. Tier the requirement set the same way you tier assessments — see Does NIS2 require vendor risk assessments?

Incident notification is the clause to get right

Your own obligation is an early warning to the authority within 24 hours of becoming aware of a significant incident. If a supplier's contract says "without undue delay", you have no defensible position when they take three days.

Draft for the clock:

  • Window. For critical suppliers, "without undue delay and in any event within 24 hours of becoming aware". Some organisations require 12 hours for suppliers supporting in-scope services.
  • Trigger. Not just confirmed breaches. Include suspected incidents affecting your data or services, and incidents at the supplier's own subcontractors.
  • Content. What happened, what is affected, what is known about cause, what the supplier is doing, and a named contact.
  • Channel. A monitored address or portal, not an account manager's mobile. Test it annually.
  • Updates. Ongoing updates at defined intervals until closure, plus a post-incident report.

See NIS2 incident reporting timelines for how the supplier window feeds your regulatory one.

Clauses for software and cloud suppliers

Article 21(3) singles out secure development procedures, so software suppliers need additional terms:

  • Secure SDLC commitments, including code review and security testing before release.
  • A published coordinated vulnerability disclosure policy and a security contact.
  • Patch and remediation SLAs by severity, with defined maximum times for critical vulnerabilities.
  • SBOM provision or, at minimum, disclosure of third-party components on request.
  • Notification of vulnerabilities affecting the version you run, whether or not exploited.
  • For cloud: shared-responsibility clarity, region and sub-processor commitments, log availability and retention, and support for your own investigation needs.

What DORA requires by comparison

Financial entities under DORA get a prescriptive list in Article 30 — service description and locations, data processing locations, availability and integrity commitments, assistance during incidents, notification obligations, access, inspection and audit rights, exit strategies and termination rights, and more for services supporting critical or important functions.

If you are subject to both regimes, draft to DORA and reuse for NIS2; the DORA set is a superset in practice. See NIS2 vs DORA.

Remediating an existing contract estate

Nobody renegotiates a thousand contracts at once. A defensible sequence:

  1. Inventory. Get every in-force supplier contract into one place with the counterparty, service, term, renewal date and owner.
  2. Extract the terms that matter. Determine which contracts already contain security, notification, audit, subcontracting and exit provisions — and what the notification window actually says.
  3. Tier and prioritise. Critical suppliers with weak or missing terms come first; low-risk suppliers wait for renewal.
  4. Standardise. One security schedule with tiered annexes beats bespoke drafting per supplier.
  5. Remediate. Addendum for critical suppliers now; renewal-triggered updates for everyone else. Track each as a dated action with an owner.
  6. Prove it. Maintain a report showing clause coverage across the estate and the trend over time — that is the artefact a supervisor wants, not a folder of PDFs.

Steps 1 and 2 are the bottleneck in most organisations, because the answers sit inside unstructured documents. Vendorapp's contract handling and AI-assisted term extraction target exactly that problem — see How Vendorapp supports NIS2 supply chain requirements and the product guide to adding and managing contracts.