TPRM & Vendors
What is TPRM (Third-Party Risk Management) and how to structure it
8 min read · Updated
Most security incidents and compliance findings today pass through a supplier. Third-party risk management (TPRM) is the discipline of knowing who your third parties are, how much risk each one carries, and what you do about it, from the first contract to the day you part ways. This guide covers the six-step lifecycle, the KPIs worth reporting and the regulations that make it mandatory.
What TPRM is, and what it is not
TPRM is the continuous process of identifying, assessing, treating and monitoring the risks introduced by external parties: software vendors, cloud and hosting providers, outsourcers, consultants and partners that access your data, systems or customers. It differs from basic vendor management, which is about price, delivery and performance. TPRM asks a different question: what could this relationship do to our security, privacy, continuity and compliance?
It also reaches beyond direct suppliers. A fourth party is a subcontractor of your supplier, such as the cloud platform behind a SaaS tool. You rarely contract with them, but their failure can still become your incident.
Why it is now a compliance requirement
- NIS2 requires in-scope entities to manage supply chain security as part of their cybersecurity risk-management measures (Article 21).
- ISO/IEC 27001:2022 dedicates controls in Annex A to supplier relationships, including supplier agreements, monitoring and the ICT supply chain (A.5.19 to A.5.23).
- GDPR (Article 28) and LGPD (Article 39) require controllers to bind processors by contract and instructions, which makes due diligence and DPAs part of everyday vendor work.
- DORA adds specific ICT third-party risk requirements for financial entities in the European Union.
The 6-step TPRM lifecycle
1. Centralised inventory
Build a single register of every third party, with the service they provide, the data and systems they touch, the business owner and the contract. You cannot assess what you have not listed, and shadow IT is where the surprises hide.
2. Classification and tiering
Rate each party by criticality, based on data sensitivity, access level and business dependency. Tiering decides how deep every later step goes, so effort follows risk instead of being spread evenly.
3. Proportionate due diligence
Assess before signing, with depth matched to the tier: questionnaires, evidence such as an ISO 27001 certificate or a SOC 2 report, and a score. See our vendor due diligence questionnaire template.
4. Contract clauses and DPA
Turn findings into obligations: a data processing agreement, security requirements, incident notification timing, sub-processor approval, audit rights, and data return or deletion at exit. Notification timing matters because your own regulatory clocks, such as the 24-hour and 72-hour windows under NIS2, start when the incident reaches you.
5. Continuous monitoring
A point-in-time assessment goes stale. Track expiring certificates and reports, remediation actions with due dates, changes in sub-processors, incidents and the cadence of reassessments by tier.
6. Secure offboarding
When the relationship ends, revoke access, retrieve or securely delete data with written confirmation, close integrations and keep the evidence for audit. Offboarding is the step most programs forget, and it is where orphaned access accumulates.
TPRM KPIs to bring to the board
| KPI | What it tells the board |
|---|---|
| Suppliers inventoried and tiered (%) | How much of the supply chain is actually under management |
| Critical suppliers with a current assessment (%) | Whether the highest risks are reviewed on schedule |
| Average onboarding time by tier | Whether risk reviews slow the business down |
| Open and overdue remediation actions | Whether findings turn into closure |
| Contracts with DPA and incident-notification clause (%) | Whether privacy and incident obligations are enforceable |
| Evidence expiring in 90 days | Upcoming lapses before they become findings |
| Incidents involving third parties | Whether the program is reducing real exposure |
Where spreadsheets fall short in TPRM
Supplier risk is where spreadsheets fail first: dozens of files, answers in email, evidence with no expiry date and no history of who accepted which risk. We cover the broader picture in spreadsheets vs. GRC software.
TPRM in KORAGRC
The third-party risk module covers inventory, risk-based onboarding, questionnaires and monitoring in one place. Suppliers respond through the vendor portal, obligations and expiries are tracked in compliance obligations, and the KPIs above feed executive dashboards and reports.
Frequently asked questions
What is the difference between TPRM and vendor management?
Vendor management focuses on commercial performance such as price and delivery. TPRM focuses on the risk the relationship creates for security, privacy, continuity and compliance.
Who should own third-party risk?
Typically a shared model: the business owner of each supplier is accountable for the relationship, while security, privacy, procurement and legal define the requirements, and a GRC function coordinates the process and reporting.
How many suppliers do I need before TPRM makes sense?
There is no threshold. Even with a handful of critical suppliers, you need an inventory, tiering and a repeatable review. The volume only changes how much you need to automate.
What is a fourth party?
A subcontractor or provider used by your supplier, such as the cloud platform behind a SaaS product. Ask your suppliers to list the ones that matter and to flow your requirements down to them.