Policy Register

Vendor contract security requirements

The standard security terms written into every supplier agreement: access, incident notice, audit rights, sub-contracting, exit.

How the register reads it

Also calledsecurity schedule, security addendum
FamilySuppliers and third parties
Document typeStandard. The regimes ask for the content, not the label; a line pasted as a standard, procedure, plan or schedule is placed here with the label noted.
Folds intoThe regimes accept it folded into the supplier and third-party security policy; when neither is listed, the gap is counted once, under the parent.
Expected ownerProcurement or the vendor manager, with the information security lead.
Review cadenceAnnual (the register's default: the clauses say planned intervals and on significant change, and do not fix a period).
On the gap list whennever on its own: the register recognises it and names the clauses, but no ticked regime lists it as a separate document (its parent, supplier and third-party security policy, is).
TemplateVendor contract security requirements.

Which standards require it, and what each expects it to contain

3 requiring clauses, 3 regimes

Shown on a register for the regimes you tick; with none ticked, ISO 27001 is applied. Requirement text is our own statement of each clause, read from the published text and cited so you can check it against the official text; it is not the instrument verbatim.

ISO/IEC 27001:2022

ISO 27001 5.20 Addressing information security within supplier agreements

Establish and agree the relevant security requirements in each supplier contract.

What the ISO 27002 guidance expects the document to say: Requires the relevant information security requirements to be established and agreed with each supplier, scaled to the type of supplier relationship involved.

Evidence an auditor accepts: Executed agreements containing the agreed information security requirements, sampled across supplier tiers; the clause set used, covering confidentiality, information handling, incident notification with a timeframe, subcontracting, personnel screening, return or deletion at exit and right to audit; evidence requirements were scaled to the relationship type rather than applied as one template regardless
Common gap: missing explicit security clauses
Source: ISO/IEC 27001:2022; guidance ISO/IEC 27002:2022

DORA (Regulation (EU) 2022/2554)

DORA Art. 30 Key contractual provisions

Contracts set out the rights and obligations of both parties in one written document, available on paper or another durable, downloadable format, including the service levels. Every ICT services contract covers at least: the functions and services and whether and how subcontracting is permitted; service and data processing locations, with advance notice of changes; data protection provisions; access, recovery and return of data on insolvency, resolution, discontinuation or termination; service level descriptions; incident assistance at no cost or a cost fixed in advance; cooperation with competent and resolution authorities; termination rights and minimum notice periods; and participation in security awareness training. Contracts for services supporting critical or important functions add: full service levels with quantitative and qualitative targets, notice and reporting duties, provider contingency testing and security measures, participation in the entity's TLPT, unrestricted access, inspection and audit rights for the entity and the authority, and exit strategies with a mandatory transition period (Art. 30(3)). A microenterprise may agree with the provider that its access, inspection and audit rights are handed to an independent party that the provider appoints, from which it can request information and assurance at any time (Art. 30(3), final subparagraph). Standard contractual clauses from public authorities should be considered.

Evidence an auditor accepts: ICT service contracts held as a single written document that includes the service level agreement; contract clause checklist per contract mapped to the Article 30(2) minimum elements; for critical or important functions: clauses on quantitative service targets, TLPT participation, unrestricted audit and access rights and exit transition periods
Common gap: Contract silent on data location changes or data return on termination
Source: DORA (Regulation (EU) 2022/2554)

The NIS2 Directive

NIS2 Art. 21(2)(d) Supply chain security, covering the relationship with each direct supplier and service provider

The Directive scopes this deliberately at direct suppliers and service providers, which makes the first artefact an inventory of who those parties are and which of them touch the network and information systems behind the service. From there the entity has to manage the security-related aspects of each relationship: what the supplier may access, what security obligations bind it, what happens on incident, and what happens at exit. Contract terms are the enforcement mechanism, so contracts that predate NIS2 and carry no security clauses are a live gap rather than a legacy inconvenience. Managed service providers and managed security service providers deserve separate attention because they hold privileged access into the estate, which makes their compromise the entity's incident.

Evidence an auditor accepts: Inventory of direct suppliers and service providers, flagged for access to in-scope systems; risk assessment per supplier proportionate to the access and criticality involved; contractual security clauses, including incident notification obligations and audit or assurance rights
Common gap: Inventory built from the procurement system, so shadow and free-tier services are missing
Source: NIS2 Directive

Customizable template

9 sections, 3 cited to requiring clauses

With every regime ticked. Each clause section carries our statement of the clause, guidance beside it and starter wording to adapt; enter your organisation once, edit any section, export to Word, print or text. Every template is a draft to adapt and approve.

  1. Purpose
  2. Scope
  3. Roles and responsibilities
  4. Addressing information security within supplier agreements ISO 27001 A.5.20
  5. Key contractual provisions DORA Art. 30
  6. Supply chain security, covering the relationship with each direct supplier and service provider NIS2 Art. 21(2)(d)
  7. Exceptions
  8. Related documents
  9. Review and approval

Customise this template The template document on the compliance platform

Do this for every document on your list

Paste the list and get this reading for every document at once, with the owner and cadence against each, the clauses quoted, and the documents the regimes expect that the list does not carry. Eight documents free, no account.

Build a register

Supply chain security policy · Vendor security assessment procedure