What Should a Third-Party Risk Management Program Measure?
What Should a Third-Party Risk Management Program Measure?
A third-party risk management (TPRM) program should measure more than how many vendors have been assessed or how many reviews have been completed. It should help an organization understand where third-party risk exists, how much risk remains, and whether that risk is within established tolerance.
That requires looking beyond traditional activity metrics.
Vendor inventories, questionnaires, assessments, certifications, audit reports, and cyber scores all provide useful information. But an effective measurement model connects those inputs to the actual exposure created by third-party relationships.
A TPRM program should focus on measures beyond work volumetrics, such as:
Why Traditional TPRM Metrics Don't Tell the Whole Story
Many TPRM programs are good at measuring activity.
They can report how many vendors have completed assessments, how many findings remain open, how long reviews take, and how many vendors fall into different risk tiers.
Those metrics are useful for managing a program, but they do not necessarily tell leadership how much third-party risk the organization is carrying.
The goal is to shift the question from "Did we assess our vendors?" to "What risk do those vendors create for the organization?"
Measuring Vendor Risk Starts with Exposure and Assurance
Not every third party creates the same level of risk.
Organizations first need to understand which vendors support critical operations, handle sensitive information, connect to important systems, or create other material dependencies. They can then evaluate whether the controls relevant to those risks are operating effectively.
But control effectiveness alone does not tell the whole story.
Organizations also need to consider the quality of the assurance supporting that conclusion. Evidence can differ in scope, testing methods, treatment of exceptions, and reporting formats, making assurance difficult to compare across vendors. HITRUST's TPRM guidance recommends establishing consistent criteria for evaluating assurance and increasing reliance on standardized, independently validated evidence. This gives organizations a more comparable and trustworthy foundation for evaluating vendor risk.
Together, criticality, control effectiveness, and assurance of confidence provide a stronger foundation for understanding how much risk remains.
Residual Risk Has to Connect to Risk Tolerance
Once an organization understands the risk a vendor creates and the controls that are in place to address it, the next question is whether the remaining risk is acceptable.
That is where residual risk and risk tolerance become particularly important.
A consistent measurement approach allows organizations to identify vendors that fall outside established tolerance and determine how those risks should be treated. Depending on the situation, the organization may choose to mitigate, accept, avoid, or transfer the risk.
This helps make TPRM decisions more consistent and defensible rather than relying primarily on individual reviewer judgment or whether a vendor passed a particular assessment.
TPRM Programs Also Need a Portfolio-Level View
Looking at vendors individually can hide risk that becomes significant across the organization.
Multiple vendors may depend on the same cloud provider, support the same critical business process, handle similar sensitive information, or share common control weaknesses.
Measuring concentration helps organizations identify those patterns.
TPRM programs should also monitor how the portfolio changes over time. Remediation efforts may reduce exposure, while new dependencies, changing services, outdated assurance evidence, or deteriorating controls may increase it.
Adding financial exposure gives leadership another way to understand the potential business impact associated with those risks.
Together, these measures provide a more complete picture of third-party risk than individual vendor ratings alone.
How HITRUST Modernizes Third-Party Risk Management
HITRUST's approach to third-party risk management focuses on moving beyond disconnected assessments and vendor-review activity toward a more standardized approach to understand risk and exposure.
Standardizing TPRM using HITRUST can reduce the time and effort required for vendor reviews while giving organizations greater confidence in their understanding of vendor risk. CHIME research commissioned by HITRUST found that 92% of respondents estimated that relying on a single validated certification could save at least eight hours per vendor assessment. By using standardized, independently validated assurance that can be reused across vendor relationships, TPRM teams can reduce repetitive review work and establish a more consistent foundation for evaluating risk.
That matters because security and risk leaders need more than metrics that their TPRM program is processing vendor reviews. They need to understand which third parties create significant risk, how reliable the supporting assurance is, whether the remaining exposure is acceptable, and where action is needed.
Instead of measuring success by the number of assessments completed, organizations can measure what ultimately matters: how effectively they understand and manage the risk created by their third-party ecosystem.
Ready to move beyond counting vendor assessments and really understanding your third-party risk exposure? Explore the TPRM Top 10 for insights into today’s most pressing third-party risk challenges.