Risk is assessed when a supplier is onboarded. The way the business uses that supplier keeps changing after it goes live.
Clive Besterwitch, Founder and Director · Part 2 of 5
A software supplier is onboarded as low risk. The intended use is a reporting tool for one team, with read-only access to a small data set. Due diligence is proportionate, the contract is standard and approval goes through without much debate.
Eighteen months later the tool feeds a customer-facing process. It has write access to a core platform, two more business units use it, and the supplier has moved its hosting to a different provider. The risk rating in the TPRM system still says low. Nothing in the onboarding was wrong. The record simply stopped at approval.
We see this drift in most programmes we review. TPRM is usually well structured at the start: intake, scoping, due diligence and contract. After go-live, the supplier record tends to stay frozen while the relationship keeps changing.
DORA expects firms to manage ICT third-party risk across the whole life of an arrangement. Article 28 requires a strategy and policy covering the full lifecycle, and the Register of Information has to stay current, including when a service starts to support a critical or important function.
The EBA Guidelines on outsourcing arrangements (EBA/GL/2019/02) set out ongoing monitoring of service providers, with reassessment when risks or the arrangement change. In the UK, PRA Supervisory Statement SS2/21 expects firms to monitor outsourcing and third-party arrangements on an ongoing basis and to reassess materiality when circumstances change.
The common thread is that criticality is a property of how the service is used today. A rating set at onboarding is a starting point.
Three patterns account for most of it:
Each of these is visible somewhere in the organisation: in change management, identity and access records, architecture reviews or the supplier’s own notifications. The problem is that none of those signals is wired to the supplier’s risk rating.
Scheduled reviews by tier are necessary, but they’re too slow on their own. Agree a short list of events that send a supplier back for reassessment straight away, and connect each one to the system where it shows up:
Give each trigger an owner and a response time. A trigger that nobody acts on is just another report.
Take twenty suppliers currently rated low or medium. For each, compare the onboarding record with how the service is used today, using access records, integration lists and the business owner’s own account. Count how many would score differently if assessed now. That number tells you how far your register has drifted, and the specific cases show which triggers you’re missing.
The supplier that matters is the one the business relies on today. A TPRM programme that keeps its records in step with real usage, through triggers connected to change and access processes, will rate its suppliers correctly when it counts.
Sources: EUR-Lex, Regulation (EU) 2022/2554 (DORA), Article 28; EBA, Guidelines on outsourcing arrangements (EBA/GL/2019/02); Bank of England, PRA Supervisory Statement SS2/21, Outsourcing and third party risk management.