Explore our new Cybersecurity Terms Glossary, explained by our experts.

View the Glossary View the Glossary
PRIVIA

Cybersecurity Terms Glossary

What Is Third-Party Risk Management?

Third-party risk management is the discipline of identifying, assessing, and monitoring the risk suppliers introduce, from onboarding through contract renewal to offboarding.

Illustration for the cybersecurity term Third-Party Risk Management
Home / Blog / Cybersecurity Terms / What Is Third-Party Risk Management?
17 November 2026

What Is Third-Party Risk Management?

What Is Third-Party Risk Management?

Third-party risk management is the programme that governs the risk other organisations create for yours: suppliers, processors, resellers, contractors, and the software you embed. It runs across the whole relationship, from selection and contracting through monitoring and renewal to the day you disconnect them.

It has become one of the hardest problems in security for an unsentimental reason: the average organisation’s attack surface now includes several hundred companies it does not control, and attackers have noticed. Compromising one supplier reaches many victims at once.

Why the Discipline Grew Up

Two UK-visible incidents make the case. In May and June 2023, the Cl0p group exploited a zero-day in MOVEit Transfer, a managed file transfer product. Organisations that had never heard of MOVEit found their employee data exposed because a payroll provider used it, with the BBC, British Airways, and Boots among those affected through a single supplier. In March 2023, an intrusion at outsourcing provider Capita exposed personal data belonging to millions of people, much of it held on behalf of pension schemes and public bodies, and resulted in ICO enforcement action in 2025.

In both cases the organisations suffering the harm had chosen a reputable supplier and signed a reasonable contract. That is the lesson: due diligence at onboarding is necessary and nowhere near sufficient.

The Lifecycle

  1. Inventory. You cannot manage what you have not listed. Build the register from accounts payable, single sign-on application lists, and cloud spend rather than from memory, and expect the real number to be several times what the business assumed.
  2. Tiering. Rank suppliers by the harm they could cause, not by what you pay them. A free monitoring tool with API access to production outranks an expensive stationery contract.
  3. Due diligence. Proportionate to tier, from a short questionnaire to a full supplier security assessment with evidence review and technical validation.
  4. Contracting. Security requirements, audit rights, incident notification duties, subprocessor approval, data location, and exit provisions.
  5. Monitoring. Reassessment on a cadence set by tier, plus event-driven review when the supplier is breached, acquired, or changes its subprocessors.
  6. Offboarding. Data returned or destroyed with evidence, access revoked, API keys rotated, and the entry closed in the register. Dormant supplier accounts are a recurring finding in penetration tests.

Tiering in Practice

TierCharacteristicsDue diligenceReassessment
CriticalProcesses personal or regulated data, or an outage halts a core serviceFull assessment, evidence review, right to audit, testing resultsAnnual, plus on material change
ImportantSystem access or moderate data volumesQuestionnaire plus certification evidenceEvery 18–24 months
LowNo data access, easily replacedBasic checks at onboardingOn renewal

Fourth Parties and Concentration

Your supplier’s suppliers matter, because the contract you hold does not reach them. Processors under UK GDPR must obtain authorisation before appointing subprocessors and must pass equivalent obligations down the chain, so the practical control is a subprocessor list you receive notice of, plus the right to object. Ask critical suppliers who they depend on for hosting, authentication, and payment processing.

Concentration risk is the related problem. Twenty suppliers running on the same cloud region, or three critical services authenticating through one identity provider, means a single failure takes out more than the register suggests. Mapping dependencies is tedious and is the thing most programmes skip.

What UK Regulators Expect

Under UK GDPR, Article 28 requires controllers to use only processors providing sufficient guarantees and to write specified terms into the contract, and accountability for the choice stays with the controller. The ICO’s enforcement history shows that “our supplier did it” has never been a defence. In financial services, PRA Supervisory Statement SS2/21 sets expectations on outsourcing and third-party risk, while DORA requires EU entities to maintain a register of information on all ICT third-party arrangements and imposes contractual content requirements. For operators in scope of the NIS Regulations, supply chain security is an explicit objective of the NCSC Cyber Assessment Framework, and the NCSC publishes a twelve-principle supply chain security guidance set that maps well onto the lifecycle above.

Making It Less Painful

Programmes collapse under their own weight when every supplier gets the same 300-question form. Tier ruthlessly, accept existing attestations such as a current SOC 2 Type 2 or ISO 27001 certificate instead of re-asking the questions they answer, and spend the saved effort on the dozen suppliers that could actually hurt you. Then test the assumption occasionally: external attack surface checks on critical suppliers find more than questionnaires do.

If you need an evidence-based view of supplier exposure, our cyber risk analysis services assess third-party risk alongside your own.

FAQ – Frequently Asked Questions

What Is the Difference Between TPRM and Supply Chain Security?

TPRM is the governance discipline covering commercial relationships: inventory, assessment, contracts, and monitoring of the organisations you buy from. Supply chain security is broader and more technical, covering the integrity of software and hardware you consume, including dependencies, build pipelines, and firmware. They overlap heavily in practice, and most mature programmes run them as one function with two sets of techniques.

How Many Suppliers Should Be in Scope?

All of them in the register, but only a small proportion in deep assessment. Typically 5% to 15% of suppliers account for nearly all the risk, being those with access to personal data, production systems, or a service whose failure stops operations. Trying to assess every supplier equally exhausts the team and delays the assessments that matter.

Who Is Liable When a Supplier Causes a Data Breach?

Under UK GDPR, the controller remains accountable to the ICO for choosing and instructing the processor, while the processor has direct obligations of its own and can be fined independently. Contracts allocate financial liability between the parties, but they do not transfer regulatory accountability. Affected individuals may pursue either party, which is why indemnities and insurance terms deserve legal review.

What Should We Monitor Between Assessments?

Breach disclosures and regulatory actions involving the supplier, changes to their subprocessor list, ownership or location changes, certification lapses, and their external attack surface where you can observe it. Set a trigger for event-driven reassessment so that a supplier breach or acquisition prompts review immediately rather than waiting for the next scheduled cycle.

Related Terms

You May Be Interested In These

What Is Looney Tunables?

Cybersecurity Terms

17 November 2026

What Is Looney Tunables?

Read More
What Is NetExec?

Cybersecurity Terms

17 November 2026

What Is NetExec?

Read More