Third-Party Operational Risk Management (1)
  • Third-Party Risk
  • Risk Management
  • 9th Nov 2026
  • 1 min read

Third-Party Operational Risk Management

Gabriel Few-Wiegratz
  • Written by
Gabriel Few-Wiegratz
Product Marketing Manager
View my profile on
In Short...
  • Third-party risk is now a legal obligation, with DORA, NIS2, and FCA rules making suppliers part of your regulated risk exposure.
  • Regulators expect continuous oversight, including live monitoring, due diligence, concentration risk management, and tested exit plans.
  • Most programmes fall short due to manual, fragmented processes, with spreadsheets and periodic assessments no longer defensible.
  • TPRM must be integrated into your wider GRC model, connecting supplier risk to operational resilience, compliance, and board reporting.

Third-party operational risk used to sit near the bottom of most GRC agendas. A questionnaire sent annually. A box ticked. A spreadsheet updated when someone remembered.

That era is over.

Under DORA, NIS2, and FCA operational resilience rules, the risk your suppliers carry is now legally your risk. Boards are personally liable. Enforcement is active. And the gap between what most organisations have in place and what regulators now expect is significant.

This guide explains what third-party operational risk management actually requires, why the regulatory floor has risen, and what a programme fit for 2026 looks like in practice.

 

Updated: November 2026 

What Is Third-Party Operational Risk Management?

Third-party operational risk management (TPRM) is the discipline of identifying, assessing, monitoring, and controlling the risks that arise from an organisation's reliance on external parties — including suppliers, vendors, outsourced service providers, and technology partners — to deliver critical operations.

It differs from general vendor management in scope and intent. TPRM focuses specifically on operational exposure: what happens to your business continuity, regulatory compliance, data integrity, and service delivery if a third party fails, is compromised, or exits the relationship unexpectedly.

The full lifecycle, not just onboarding

A mature TPRM programme covers the complete lifecycle of third-party relationships:

  1. Pre-engagement: due diligence, risk assessment, and contractual alignment before a supplier is onboarded
  2. Active relationship: continuous monitoring of risk posture, performance, and regulatory standing
  3. Exit and transition: managed offboarding with documented exit plans, data portability, and alternative provider identification

Most organisations have reasonable controls at the onboarding stage. The gaps almost always appear in the middle and end of that lifecycle — where continuous monitoring gives way to periodic snapshots, and exit planning is treated as a theoretical exercise rather than a tested capability.

The regulatory shift: what regulators now require maps directly to this full lifecycle. DORA, NIS2, and FCA rules do not just ask whether you assessed a supplier before engaging them. They ask whether you can evidence continuous oversight, concentration risk management, and a credible exit strategy for every critical relationship.

Why Third-Party Risk Is Now a Regulatory Obligation

The regulatory landscape for third-party risk has shifted materially since 2024. Three frameworks now create binding obligations for organisations operating in the UK and EU — and all three are in active enforcement.

DORA: ICT third-party risk in financial services

The Digital Operational Resilience Act (DORA) came into force across EU financial services in January 2025. It places binding obligations on firms to manage ICT third-party risk, not as a best practice but as a legal requirement.

Under DORA, financial entities must maintain a complete Register of Information (ROI) documenting all ICT third-party service providers. ROI submissions to National Competent Authorities were due in March 2026, and NCAs are now deploying automated tools to cross-reference submissions. Inconsistencies trigger enforcement automatically.

DORA also introduces concentration risk obligations: firms must understand and actively manage situations where multiple critical functions depend on a single third party or a small number of providers. Exit plans are mandatory, not optional. The European Supervisory Authorities (ESAs) have published oversight frameworks for Critical Third-Party Providers (CTPPs), with on-site inspections now underway for the most systemically important ICT suppliers.

Senior management is personally accountable. DORA is not a compliance exercise that can be delegated and forgotten.

NIS2: supply chain risk across critical infrastructure

The Network and Information Security Directive 2 (NIS2) extends cybersecurity obligations across a significantly wider range of sectors, including energy, transport, health, digital infrastructure, and manufacturing. The transposition deadline was October 2024.

As of November 2026, 24 out of 27 EU Member States have transposed NIS2 into national law, with enforcement now active across the majority of jurisdictions. The European Commission referred Ireland, Spain, France and the Netherlands to the Court of Justice in July 2026 for failing to complete transposition. The Commission has also proposed targeted amendments to NIS2 (January 2026) to increase legal clarity and simplify compliance for smaller entities.

Critically, NIS2 puts supply chain security explicitly in scope. Regulated entities must assess the cybersecurity practices of their suppliers and take appropriate risk management measures where weaknesses are identified. This is not a one-time exercise. NIS2 expects continuous oversight, not annual questionnaires.

Fines under NIS2 reach up to €10 million or 2% of global annual turnover. Management are personally liable for non-compliance.

FCA operational resilience: third parties and critical services

UK financial services firms face a parallel set of obligations under FCA operational resilience rules. Firms must identify important business services, set impact tolerances, and demonstrate they can remain within those tolerances even when a third party fails.

The FCA issued £15.7 million in fines in Q1 2026. Critical Third Party designations, applying enhanced oversight to the most systemically important service providers, are being progressed during 2026. Firms are now expected to evidence operational resilience, not just document it. Telling your regulator you have a plan is not sufficient if you cannot demonstrate it holds under realistic stress scenarios.

The common thread across all three frameworks: regulators are not asking whether you have a TPRM policy. They are asking whether you can prove it works — with audit trails, continuous monitoring data, and tested exit plans to back it up.

The GRC brief
New frameworks and control changes, monthly.

What a Third-Party Operational Risk Management Programme Must Include

Most TPRM programmes were built for a lower-stakes environment. The following components reflect what regulators now expect from any organisation subject to DORA, NIS2, or FCA operational resilience rules.

Risk-tiered supplier classification

Not all third parties carry equal exposure. A critical ICT provider processing customer data under DORA is materially different from an office supplies vendor. Tier your suppliers based on their criticality, replaceability, data access, and regulatory relevance — and apply proportionate oversight to each tier.

Without tiering, teams either over-assess low-risk suppliers (wasting capacity) or under-assess high-risk ones (creating gaps). Regulators expect evidence that your oversight intensity is proportionate to actual exposure.

Due diligence before onboarding

Risk assessment must happen before a supplier is engaged, not after the contract is signed. This includes financial stability, security posture, regulatory standing, and sub-contractor exposure (fourth-party risk). For regulated services, the assessment must be documented and retained.

Contractual obligations aligned to regulatory requirements

DORA mandates specific contractual clauses with ICT third-party providers, covering audit rights, exit assistance, security standards, incident notification, and business continuity obligations. Firms that have not reviewed legacy contracts against DORA requirements have an urgent gap to close. The DORA regulation text published via EUR-Lex sets out the minimum contractual provisions in detail.

Ongoing monitoring, not point-in-time assessment

Annual questionnaires do not meet the standard regulators now expect. Effective TPRM requires continuous monitoring of supplier risk: tracking changes in security posture, financial health, regulatory status, and incident history between formal review cycles.

The practical implication: a supplier that passed your annual review in January may have suffered a significant security incident, a change of ownership, or a regulatory sanction by March. Point-in-time programmes miss this entirely.

Concentration risk management

Regulators are specifically focused on scenarios where a single failure could cascade across multiple firms or critical services. Mapping your dependencies — including where the same provider underpins multiple business services — is now a core TPRM requirement under DORA and a key concern for the FCA's Critical Third Party regime.

Exit planning

Every critical third-party relationship should have a documented exit strategy before it is needed. This includes data portability, transition timelines, interim service arrangements, and identification of alternative providers. DORA makes this explicit. Regulators treat an untested exit plan with similar scepticism to an untested business continuity plan.

Audit-ready records

Documentation, evidence of assessments, board-level reporting, and response records must be retained and accessible. When a regulator asks for evidence of your TPRM programme, "we have a spreadsheet" is not a defensible answer.

Programme component

Minimum standard

Common gap

Supplier classification

Risk-tiered, documented

Flat lists with no exposure weighting

Due diligence

Pre-engagement, retained

Post-contract or not retained

Contractual alignment

DORA clauses included

Legacy contracts not reviewed

Monitoring

Continuous, not annual

Periodic snapshots only

Concentration risk

Mapped and managed

Not systematically tracked

Exit planning

Documented and tested

Theoretical or absent

Audit records

Accessible and complete

Fragmented across systems

Where Most Third-Party Risk Programmes Fall Short

The gap between regulatory expectation and current practice is, for many organisations, substantial. The most common failures are structural, not superficial.

Spreadsheet-based tracking

Point-in-time data held in spreadsheets cannot support continuous monitoring, automated risk scoring, or audit-trail requirements. Manual processes introduce errors, create version control problems, and cannot scale as supply chains grow. More fundamentally, a spreadsheet cannot alert you when a supplier's risk profile changes between review cycles — which is precisely what regulators now expect your programme to catch.

Inconsistent assessment depth

Without a standardised framework and tooling, the depth and quality of third-party assessments depends on who conducted them. Regulators expect consistency. Firms that cannot demonstrate it cannot demonstrate control. The 2024 Standardised Information Gathering (SIG) questionnaire, including SCRM and AI risk domains, provides a recognised baseline — but only if it is applied consistently across your supplier population.

No fourth-party visibility

Your critical suppliers have their own suppliers. A breach or failure at a fourth party can disrupt your operations even if your direct supplier remains intact. Most TPRM programmes have no systematic view of this exposure. DORA's concentration risk provisions implicitly require firms to understand these dependencies, and the FCA's Critical Third Party framework is designed precisely to address systemic fourth-party risk at a sector level.

Reactive rather than continuous

Assessing a supplier at onboarding and then annually is not the same as monitoring them continuously. A supplier's risk profile can change materially between annual reviews — through a security incident, a change of ownership, a financial deterioration, or a regulatory sanction. Programmes built on periodic snapshots miss this.

The cost of missing it: when a supplier incident occurs, organisations running reactive programmes discover the exposure after the fact. Regulators, and increasingly courts, are treating that as a governance failure, not bad luck.

Disconnected from the wider GRC estate

Third-party risk exists in isolation in many organisations: managed by procurement or a separate vendor team, disconnected from the risk register, compliance programmes, and operational resilience planning. Regulators view TPRM as integral to the GRC estate, not adjacent to it. A supplier risk that is not visible in your risk register is a risk that is not being managed — it is being ignored.

For a deeper look at the structural challenges, see The Top 5 Challenges of Third-Party Risk Management and the TPRM maturity framework guide.

How Technology Supports Third-Party Operational Risk Management

Manual TPRM processes cannot meet the scale, consistency, and auditability that regulators now require. Purpose-built GRC technology closes the gap between what organisations need to evidence and what spreadsheet-based programmes can realistically deliver.

What the platform needs to do

Effective TPRM technology is not a questionnaire tool with a dashboard bolted on. It needs to:

  1. Centralise all third-party data in a single connected record, updated in real time and visible across risk, compliance, and operational resilience workstreams
  2. Automate assessment workflows with standardised questionnaires (including SIG 2024), scoring, and remediation tracking
  3. Monitor continuously, not just at onboarding and annual review
  4. Generate audit-ready outputs with a complete, immutable trail of every assessment, finding, and decision
  5. Connect supplier risk to the wider GRC estate, so a supplier risk automatically surfaces in the risk register and feeds into board reporting

SureCloud TPRM: built for the regulatory environment

SureCloud's TPRM product delivers 50% faster third-party risk assessments, 40% faster third-party onboarding, and 35% greater consistency across assessments, with a complete audit trail available at every stage.

Gracie AI Agents with Personas and Skills brings a Vendor Risk Manager Persona to the TPRM programme: an AI agent with a defined role, running codified expertise across supplier assessment, risk scoring, and continuous monitoring. Gracie monitors the programme continuously, flags changes in supplier risk profiles, surfaces emerging exposures, and generates audit-ready outputs without analyst overhead. Every action Gracie performs is logged in an immutable reasoning record and can be reviewed, redirected, or rolled back at any point.

For organisations facing DORA, NIS2, or FCA scrutiny, this is the difference between a programme that evidences control and one that documents intent.

Independent analyst recognition

SureCloud is recognised in the Gartner Market Guide for Third-Party Risk Management Technology Solutions (2025) and named in the GigaOm Third-Party Risk Management RADAR Report (2026). With 20 years of GRC expertise embedded in the platform, SureCloud's TPRM capability is built on the same connected architecture as its risk, compliance, audit, and operational resilience products — ensuring supplier risk is never siloed from the rest of your programme.

Verdantix, 14 Innovative Vendors Advancing GRC In 2026: "SureCloud's event-based architecture converts every user action into a discrete, traceable event. As regulatory scrutiny intensifies, this architecture will be particularly valuable for firms handling sensitive data in highly regulated sectors."

 

Key Takeaways

  1. Third-party operational risk management is a binding regulatory obligation under DORA, NIS2, and FCA operational resilience rules — not a best practice.
  2. Regulators expect continuous monitoring, documented due diligence, contractual alignment, concentration risk management, and tested exit plans.
  3. Annual questionnaires and spreadsheet-based tracking do not meet the current standard. Enforcement is active across all three frameworks.
  4. Fourth-party risk is in scope. Your suppliers' suppliers are a regulated concern under DORA's concentration risk provisions and must be systematically addressed.
  5. Management and boards are personally liable under DORA and NIS2 for failures in third-party risk oversight.
  6. A connected GRC platform — not a siloed TPRM tool — is the most defensible architecture against regulatory scrutiny. Supplier risk that is invisible to the risk register is risk that is not being managed.
See it in action

Build a Defensible Third-Party Risk Programme

See how SureCloud helps organisations move from fragmented vendor risk processes to continuous, regulator-ready oversight. Manage supplier risk, automate assessments, track remediation, and maintain a complete audit trail—all in one connected platform.Start by centralising your third-party data and proving oversight across one critical service—then scale to full DORA, NIS2, and FCA compliance.If your current programme relies on spreadsheets or periodic reviews, the gap to regulatory expectations is already widening.
Google preferred sources
Found this useful?

Choose SureCloud as a preferred source in Google and you will see more of our GRC guidance in Top Stories, AI Overviews and AI Mode. It takes one click and you can undo it at any time.

Your next step
PRICING

See what SureCloud costs

A short form, no sales call. Pricing built around your GRC estate.

Get Pricing
4.2 / 5 · 46 reviews on G2
ANALYST REPORT

IDC names SureCloud the industry's first cross-domain agentic GRC platform

Read the independent analyst view on how SureCloud is redefining risk and compliance.

Download for free

FAQ’s

What is third-party operational risk?

Third-party operational risk is the exposure an organisation faces as a result of its reliance on external suppliers, vendors, or service providers to deliver critical operations. It includes the risk of service disruption, data breach, regulatory non-compliance, and reputational damage caused by a third party's failure or compromise. Under DORA and NIS2, managing this risk is a legal obligation, not an optional best practice.

What does DORA require for third-party risk management?

DORA requires EU financial entities to maintain a complete Register of Information (ROI) covering all ICT third-party service providers, conduct due diligence before engagement, include specific contractual provisions covering audit rights, security standards, exit assistance and incident notification, manage concentration risk, and maintain documented exit strategies. Senior management is personally accountable for compliance. ROI submissions were due to National Competent Authorities by March 2026.

How does NIS2 affect supply chain risk management?

 NIS2 requires regulated organisations across critical infrastructure sectors to assess and manage the cybersecurity risks posed by their supply chain. This includes evaluating the security practices of direct suppliers and taking risk management measures where weaknesses are identified. Supply chain risk is not a peripheral concern under NIS2 — it is a primary compliance obligation, with fines up to €10 million or 2% of global turnover and personal management liability.

What is the difference between TPRM and vendor management?

Vendor management typically focuses on commercial performance — contract terms, SLAs, pricing, and relationship quality. Third-party operational risk management (TPRM) focuses on operational exposure — what happens to business continuity, regulatory compliance, and service delivery if a supplier fails or is compromised. TPRM includes security assessments, concentration risk analysis, exit planning, and continuous monitoring that vendor management programmes do not typically cover.

What is fourth-party risk?

Fourth-party risk refers to the exposure arising from your suppliers' own suppliers and service providers. Even if your direct supplier is sound, a failure at one of their critical dependencies can disrupt the service they provide to you. Regulators increasingly expect organisations to understand and account for fourth-party exposure, particularly in critical ICT supply chains.