Supplier and third-party security policy
How suppliers are selected, what security terms they are held to, how they are monitored and reviewed, and how the relationship ends.
How the register reads it
| Also called | third-party risk management policy, vendor risk policy, TPRM |
|---|---|
| Family | Suppliers and third parties |
| Document type | Policy. 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. |
| Expected owner | Procurement or the vendor manager, with the information security lead. |
| Review cadence | Annual (the register's default: the clauses say planned intervals and on significant change, and do not fix a period). |
| On the gap list when | ISO 27001 or DORA or NIS2 or ISO 42001 is ticked and no line resolves to it (ISO 27701 requires it too, inside a parent document, so it does not list it separately). |
| Template | Third party risk management policy. |
Which standards require it, and what each expects it to contain
8 requiring clauses, 5 regimesShown 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.19 Information security in supplier relationshipsDefine and apply processes to manage the security risk suppliers introduce.
What the ISO 27002 guidance expects the document to say: Requires processes and procedures to be defined and implemented for managing the information security risks that arise from using suppliers' products or services.
Common gap: Treating all suppliers as low risk
Source: ISO/IEC 27001:2022; guidance ISO/IEC 27002:2022
ISO 27001 5.20 Addressing information security within supplier agreementsEstablish 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.
Common gap: missing explicit security clauses
Source: ISO/IEC 27001:2022; guidance ISO/IEC 27002:2022
ISO 27001 5.21 Managing information security in the ICT supply chainExtend security requirements down the ICT products and services supply chain.
What the ISO 27002 guidance expects the document to say: Requires processes and procedures to be defined and implemented to manage information security risk arising along the supply chain for ICT products and services.
Common gap: Treating supplier security as one-off check
Source: ISO/IEC 27001:2022; guidance ISO/IEC 27002:2022
ISO 27001 5.22 Monitoring, review and change management of supplier servicesRegularly monitor, review and manage change in supplier security practice and service delivery.
What the ISO 27002 guidance expects the document to say: Requires supplier information security practice and service delivery to be monitored, reviewed and evaluated on a regular basis, and requires change within them to be managed.
Common gap: relying on informal verbal updates
Source: ISO/IEC 27001:2022; guidance ISO/IEC 27002:2022
ISO/IEC 27701:2025
ISO 27701 A.3.10 Addressing information security within supplier agreementsAgreements with suppliers shall specify whether PII is processed and the minimum technical and organizational measures the supplier must meet for the organization to meet its information security and PII protection obligations, shall clearly allocate responsibilities between the organization, its partners, suppliers and applicable third parties taking account of the type of PII processed, shall provide a mechanism for ensuring the organization supports and manages compliance with applicable legislation and regulation, and shall call for independently audited compliance acceptable to the customer. When the organization is a PII processor, its contracts with suppliers shall specify that PII is processed only on its instructions.
Common gap: Supplier contracts silent on PII while the supplier processes it
Source: ISO/IEC 27701:2025
ISO/IEC 42001:2023
ISO 42001 A.10.3 SuppliersEstablish a process ensuring that the organization's use of services, products or materials provided by suppliers aligns with its approach to the responsible development and use of AI systems.
Common gap: standard security due diligence used with nothing AI specific
Source: ISO/IEC 42001:2023
DORA (Regulation (EU) 2022/2554)
DORA Art. 28 ICT third-party risk: general principlesFinancial entities manage ICT third-party risk as part of ICT risk inside the ICT risk management framework, remain fully responsible for their obligations when they use ICT services, and apply proportionality according to the nature and importance of ICT dependencies and the criticality of each service. They keep a register of information on all ICT service arrangements at entity, sub-consolidated and consolidated level, distinguishing those supporting critical or important functions; report at least yearly to the authority on new arrangements, provider categories, contract types and services; provide the full register or sections of it on request; and inform the authority in time of planned arrangements for critical or important functions. Before contracting they assess criticality, supervisory conditions, risks including concentration, due diligence and conflicts of interest; they use only providers meeting appropriate security standards, set risk-based audit frequencies, ensure contracts can be terminated in the listed cases, and keep tested exit strategies for services supporting critical or important functions. The ICT third-party risk strategy with its policy on critical or important functions (Art. 28(2)) is required only of entities other than Article 16(1) entities and microenterprises.
Common gap: Register omits intra-group or low-value ICT arrangements
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 providerThe 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.
Common gap: Inventory built from the procurement system, so shadow and free-tier services are missing
Source: NIS2 Directive
Customizable template
14 sections, 8 cited to requiring clausesWith 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.
- Purpose
- Scope
- Roles and responsibilities
- Information security in supplier relationships ISO 27001 A.5.19
- Addressing information security within supplier agreements ISO 27001 A.5.20
- Managing information security in the ICT supply chain ISO 27001 A.5.21
- Monitoring, review and change management of supplier services ISO 27001 A.5.22
- Addressing information security within supplier agreements ISO 27701 A.3.10
- Suppliers ISO 42001 A.10.3
- ICT third-party risk: general principles DORA Art. 28
- Supply chain security, covering the relationship with each direct supplier and service provider NIS2 Art. 21(2)(d)
- Exceptions
- Related documents
- 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 registerService level management policy · Supply chain security policy