Resilience & third parties

Third Party Risk Management (TPRM)

Third Party Risk Management (TPRM) is the management of the risks that arise when an organisation obtains products or services from suppliers, outsourcing partners and their subcontractors, across the whole life cycle from selection and contracting to monitoring and exit. The organisation remains responsible for what it has third parties do. DORA (Regulation (EU) 2022/2554, Articles 28 to 30) governs it for ICT services at financial entities; the IIA has a Topical Requirement on it for internal audit.

Source: Regulation (EU) 2022/2554 (DORA) Articles 5, 28, 29 and 30; EBA/GL/2019/02; EBA/GL/2026/09; Delegated Regulation (EU) 2015/35 Article 274; Dutch Pensions Act (Pensioenwet) Article 34; BCBS Principles for the sound management of third-party risk (December 2025); Dutch Cybersecurity Act (Cyberbeveiligingswet) Article 21(3); Dutch Cybersecurity Decree (Cyberbeveiligingsbesluit) Article 10; IIA Topical Requirement Third-Party (2025); ESAs, report on major ICT-related incidents 2025 (JC 2026 16)

For financial entities, the rules come in layers. DORA treats ICT third-party risk, including subcontractors, as part of ICT risk: the entity remains fully responsible (Article 28(1)), adopts a strategy on ICT third-party risk, keeps a register of information on all ICT contracts (paragraph 3), assesses risks and concentration risk in advance (paragraph 4 and Article 29) and has tested exit plans (paragraph 8). For non-ICT outsourcing, banks and payment institutions follow guidelines EBA/GL/2019/02 until the new guidelines EBA/GL/2026/09 become applicable; insurers follow Article 274 of Delegated Regulation (EU) 2015/35 and pension funds Article 34 of the Dutch Pensions Act (Pensioenwet).

Outside the financial sector, the Dutch Cybersecurity Act (Cyberbeveiligingswet) has required supply chain security since 15 August 2026 (Article 21(3)(d)), and the Cybersecurity Decree (Cyberbeveiligingsbesluit) requires essential and important entities to verify that direct suppliers meet their security requirements and to check this periodically (Article 10(2)). The Basel Committee's third-party principles of 10 December 2025 place ultimate responsibility for oversight with the board. According to the first annual report of the European Supervisory Authorities, almost one third of major ICT-related incidents in 2025 originated at third parties, including providers not designated as critical.

For internal audit, the IIA's Topical Requirement Third-Party has applied since 15 September 2026 and is mandatory for assurance engagements on third parties. It covers governance including board oversight, risk assessment down the chain of subcontractors, and controls from due diligence to a complete and current listing of all third-party relationships. Third Party Risk Management differs from outsourcing of internal audit, where an organisation contracts out its own internal audit function.

Governance & Control Design at ONE Risk Advisory translates risks into a workable control structure, with an internal control framework aligned, where relevant, with DORA or NIS2, and clear decision-making, escalation and reporting lines.

Last updated: · Editor: ONE Risk Advisory

Related service Governance & Control Design

Frequently asked questions

What is the difference between Third Party Risk Management and outsourcing?

An outsourcing arrangement is one type of third-party relationship: an organisation has another party perform one of its own activities. Third Party Risk Management is broader and also covers suppliers, advisers, subcontractors and parties further down the chain. DORA applies to all ICT services from third-party providers, including through outsourcing, and the IIA's Topical Requirement Third-Party names vendors, suppliers, contractors, subcontractors, outsourced service providers and consultants.

Who is responsible for Third Party Risk Management?

The organisation itself remains responsible, even when a third party performs the activity. Under DORA, the management body approves and periodically reviews the policy on ICT services provided by third parties (Article 5(2)(h)), and entities other than microenterprises designate a role or a member of senior management to monitor the contracts (Article 5(3)). The Basel Committee places oversight with the board and implementation with senior management.

Must internal audit always apply the Topical Requirement Third-Party?

Application is mandatory only for assurance engagements on third parties; for advisory engagements it is recommended. The Topical Requirement does not oblige internal audit to audit third-party risk; the audit plan follows the risk assessment. For each requirement, applicability is documented and any exclusion is justified. Conformance is evaluated in quality assessments.

← All terms