Policy Register

Vendor security assessment procedure

How a supplier is assessed before contract and on a cycle after it: the questionnaire, the evidence asked for, the scoring and who signs it off.

How the register reads it

Also calledsupplier due diligence, vendor questionnaire
FamilySuppliers and third parties
Document typeProcedure. 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 security assessment policy.

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

3 requiring clauses, 2 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.19 Information security in supplier relationships

Define 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.

Evidence an auditor accepts: The supplier security process, covering identification, risk assessment, selection, onboarding and exit; the supplier register with risk tiering, showing what drives the tier such as data access, criticality or connectivity; risk assessments performed for suppliers in the period, at the depth their tier requires
Common gap: Treating all suppliers as low risk
Source: ISO/IEC 27001:2022; guidance ISO/IEC 27002:2022
ISO 27001 5.22 Monitoring, review and change management of supplier services

Regularly 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.

Evidence an auditor accepts: The schedule of supplier reviews, showing frequency by tier and evidence the schedule was met; service reports and security metrics received from suppliers, and the review of them; records of issues raised with suppliers, and their resolution or escalation
Common gap: relying on informal verbal updates
Source: ISO/IEC 27001:2022; guidance ISO/IEC 27002:2022

DORA (Regulation (EU) 2022/2554)

DORA Art. 28 ICT third-party risk: general principles

Financial 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.

Evidence an auditor accepts: Register of information on all ICT service arrangements at entity and consolidated level, flagging critical or important functions; yearly report to the competent authority on new arrangements, provider categories, contract types and services, with submission confirmation; pre-contract assessment files covering criticality, supervisory conditions, risk and concentration, due diligence and conflicts of interest
Common gap: Register omits intra-group or low-value ICT arrangements
Source: DORA (Regulation (EU) 2022/2554)

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. Information security in supplier relationships ISO 27001 A.5.19
  5. Monitoring, review and change management of supplier services ISO 27001 A.5.22
  6. ICT third-party risk: general principles DORA Art. 28
  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

Vendor contract security requirements · Business continuity plan