<what>

What is third-party risk management?

Third-party risk management (TPRM) is the ongoing work of finding and managing the risks your organisation takes on when it relies on external suppliers. A third party is any outside company or person you depend on for IT, data, services or operations.

For most suppliers, the risk you take on is minimal. But some are critical enough to threaten your security and ability to operate. A hosting partner outage takes your systems offline. Your cleaning company has keys to every room and empties every bin - along with confidential documents nobody shredded.

The purpose of TPRM is to spot your critical suppliers and to keep your organisation running when something goes wrong.

Build a TPRM programme that holds when a supplier fails

Eight chapters covering all stages of the work, with practical starting points and an incident response template for your organisation.

Free PDF, no sign-up.

<why>

Why does third-party risk management go wrong?

Third-party risk management is hard because you’re accountable for risks that your suppliers manage. Also, there’s no single function that owns the work, and it competes with projects in your organisation that pay off sooner.

So most teams build their programme one regulatory requirement at a time, never as a system. Because of that, they make the same three mistakes.

Illustration: a large ball and a small ball with a long shadow

Suppliers are ranked by spend, not business impact

It’s easy to find out what you spend on a supplier, but that doesn’t tell you how much you depend on it. A low-spend supplier can run a critical process; a high-spend one can be easy to replace. Ranking suppliers by spend instead of dependency means you’ll vet and monitor the wrong companies most closely.

Illustration: a fence that is solid at the gate and falls apart further along

Onboarding gets the rigour - the rest is neglected

Vetting a new supplier has a deadline and ends with sign-off, so that work gets done. Monitoring, reassessment and exit planning come second, if at all. But services change and dependencies grow long after you sign the contract, without anyone noticing.

Illustration: coloured pipe sections that do not line up

Decisions don’t travel between teams, so nothing connects

Tasks are split by team: procurement picks the supplier, legal runs contracts, IT sets up monitoring. Each delivers its part, but no one carries decisions from one stage to the next. So the contract doesn’t target the risk, and monitoring tracks what’s easiest to collect.

<lifecycle>

How do you manage
third-party risk?

The best way to manage third-party risk is through the TPRM lifecycle: eight stages, run in a fixed order. Each stage produces the input the next one needs.

Foundation

Onboarding

Ongoing

Offboarding

Offline for

About a month

Plan covered

A couple of days

Reach

Every store

Business impact

Operations and compliance hit

<TPRM gone wrong>

A real case of mismanaged risk: a month offline at Christmas

Store employee folding green knitwear at a retail counter

A large Nordic retail chain ran on cost discipline. So when the chain set up a third-party risk management programme, it ranked supplier criticality by spend. The five most expensive suppliers were watched closely. The rest could wait.

If we’re paying a lot of money for it, it must be important.

But among the rest was the scheduling and time-registration system every store employee used.

In December 2021, that supplier suffered a major breach and went offline for about a month. The chain’s continuity plans were built to hold only for a couple of days.

So through the busiest season of the year, store managers logged hours on paper and part-time staff couldn’t see their schedules. And the chain ended up in breach of its collective agreement for part-time staff, a consequence no one had mapped.

<cyber risk>

When a supplier is hacked: third-party cyber risk

Third-party cyber risk means a supplier’s weak information security could turn into a breach or outage for your organisation.

Your exposure depends on whether the supplier holds your data, can reach your systems, runs software in your environment or delivers a service you can’t work without.

Usually, you assess a supplier with a security questionnaire, an ISO 27001 certificate or a SOC 2 or ISAE audit report. But the supplier fills in the questionnaire itself, and sets the scope of the certificate and report. That scope may leave out the service you buy.

So make sure to request evidence that matches your exposure, and update it every year as part of your Oversight.

<DORA and NIS2>

Third-party risk management compliance under DORA and NIS2

DORA and NIS2 both hold you responsible for the risk your suppliers bring. But they differ in how much they spell out.

DORA is detailed, so the work is in the upkeep. Keeping the DORA register of information accurate means updating it whenever you add a supplier or change a contract. Supply chain security under NIS2 is far less defined. You decide how to tier suppliers and what evidence to ask for, even from those the directive doesn’t cover. And you need to justify those choices.

Prescriptive

DORA

Who it’s for

Organisations in finance

In force

Applies since January 2025

Approach

Tells you what to have in place

Supplier requirements

Register of all IT and digital (ICT) supplier arrangements

Suppliers assessed before signing

Mandatory clauses in ICT contracts

Tested exit plans for critical or important functions

Enforced in Denmark by

Danish FSA

Risk-based

NIS2

Who it’s for

Energy, health, manufacturing and other critical sectors

In force

Danish law since July 2025

Approach

Tells you what to achieve and leaves the method to you

Supplier requirements

Supply chain security in proportion to the risk

Each direct supplier’s security and weak spots assessed

Enforced in Denmark by

Each sector’s own authority

What your regulator checks.

Policies on paper aren’t enough. Your regulator wants to see that you know your critical suppliers, follow up on them and could leave one if you had to.

<our approach>

How Kopenhagen Konsulting approaches TPRM

If the problems on this page look familiar, this is the work we do.

We help Nordic organisations design third-party risk management programmes and put them into practice: governance models, supplier inventories, criticality assessments, contract requirements, oversight and exit plans. Much of our work focuses on regulated industries: finance, life sciences and critical infrastructure.

TPRM works when people know what to do and the routines are light enough to keep. So our third-party risk consulting builds your programme with the teams who will run it, rather than for them.

<experts>

Meet our experts

André Duus

André Duus

Associate Partner

Has designed DORA and third-party risk programmes for large financial institutions, after 15 years of running IT, security and strategic suppliers as CIO and head of IT.

Get in touch
Laura Marie Birkegaard

Laura Marie Birkegaard

Management Consultant

Background in IT audit and assurance, from large-scale and PCAOB-regulated audits to ISAE 3402 and ISAE 3000 reporting in regulated industries.

Get in touch
Martin Modvig Stausbøll

Martin Modvig Stausbøll

Partner

Former CISO at COWI, Topsoe and Semco Maritime, with 15 years of setting supplier criticality, contract requirements and third-party security from the buyer's side.

Get in touch

<FAQ>

Questions we often get