Policy Register

Outsourcing policy

The conditions for handing a function or a development to an external party: the approval, the oversight, the access and the return.

How the register reads it

Also calledoutsourced development, managed services policy
FamilySuppliers and third parties
Document typePolicy. 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).
TemplateOutsourcing policy.

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

2 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 8.30 Outsourced development

Direct, monitor and review outsourced system development.

What the ISO 27002 guidance expects the document to say: Requires the organisation to direct, monitor and review the activities involved in outsourced system development. Secondary commentary notes that explicit direction and review were added in the 2022 revision in response to third party risk.

Evidence an auditor accepts: Contractual security requirements imposed on the development supplier, covering secure development practice, testing, code ownership and the right to review; evidence of direction given, such as agreed standards, architecture constraints and acceptance criteria; evidence of monitoring during delivery, including progress and security reviews rather than acceptance testing alone
Common gap: contracts lack specific security obligations
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

8 sections, 2 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. Outsourced development ISO 27001 A.8.30
  5. ICT third-party risk: general principles DORA Art. 28
  6. Exceptions
  7. Related documents
  8. 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

Cloud vendor management policy · Service level management policy