Key takeaways
- Effective third-party risk management focuses on understanding and mitigating vendor risk, not just completing compliance checklists.
- Tier vendors by risk and business impact so higher-risk relationships receive greater scrutiny.
- Prioritize evidence and ongoing monitoring over self-reported questionnaires and point-in-time assessments.
- Coordinate security, legal, compliance and operations to build a complete picture of third-party risk.
When your business agrees to work with a third party, it needs to be able to answer two questions: What exposure does this vendor introduce, and how will we address it?
Answering those questions is much easier if your organization has implemented an effective third-party risk management (TPRM) program. But the problem with many TPRM programs is that they’ve drifted from understanding risk to simply documenting that a review took place. If you don’t understand the cybersecurity risk a vendor presents, you’re exposing your business to a higher risk of breaches.
Research from Verizon found that 62% of system intrusion incidents originated with a partner. That number should put TPRM at the center of every cybersecurity strategy. Instead, it often sits at the edges as an afterthought managed by a single team with just a checklist or questionnaire.
Keep reading to learn how your organization can design and implement a robust third-party risk management program.
Why TPRM matters more than most organizations realize
Every vendor relationship extends your attack surface. Any third party that touches your network or holds your data, such as cloud service providers, managed service providers, payroll platforms or healthcare billing systems, is part of your risk profile.
This includes downstream vendors you may not even know about. Think of it this way: a healthcare organization may hand off patient data to a clearinghouse for claims processing. That clearinghouse may use its own subcontractors. If any link in that chain is breached, the exposed data remains your responsibility. Regulators, partners, customers and patients don’t distinguish between who held the data when it was compromised.
What TPRM should be
A mature vendor risk management program is a risk-informed process. It weighs each vendor against three factors: the data it handles, the access it holds and how critical it is to business operations. From there, leadership can decide how to mitigate or transfer the risk, accept it or walk away from the vendor.
Why many third-party risk management programs fall short
For many organizations, TPRM has turned into a compliance exercise. A questionnaire goes out. Answers come back that are self-reported, unverified and only reflect that moment in time. A SOC 2 report gets filed. A checkbox gets checked. And the organization moves on, under the assumption that due diligence has been performed. But the reality is, it hasn’t.
Questionnaires have been the industry default for years. They often include hundreds of questions, but neither the vendor completing them nor the team reviewing them finds them particularly valuable. They capture a point in time, not a current state. And they speak to what a vendor says about itself, not what it can actually demonstrate.
A SOC 2 report has the same limitation. If the service your organization is using was launched after the SOC 2 audit period ended, that report has little or no value to you. Without someone who knows what to look for, that distinction gets missed, and the organization logs the report and keeps moving.
Organizations that treat vendor risk management as a check-the-box exercise instead of a meaningful review aren’t eliminating risks. In fact, they may not ever see them until it’s too late.
Vendor risk management goes beyond security
Vendor risk is more than a security issue that can be handled by a CISO or a director of information security.
There are legal and compliance implications, especially in healthcare and financial services, where PHI and payment card data flow downstream. There are also operational dependencies and financial considerations, including the costs associated with a vendor failure or replacement.
All impacted departments should play a role in assessing a vendor’s risk, and communication between teams is key. A compliance team might confirm that a vendor signed the right agreements but has no idea which specific application or service is being used and what that means from a data-handling standpoint. A legal team might draft contract protections for a service they don’t fully understand.
Information must flow throughout the organization. Without deliberate orchestration across security, privacy, compliance, legal and operations, each team checks what applies to them — and nobody gets the full picture.
The keys to third-party risk management
Here are some actions your organization can take to effectively assess your vendor’s cybersecurity posture:
Scope deliberately
Before any review begins, the organization needs to define exactly what data will be shared with the vendor, how access will be granted, how long the engagement will last and what services or applications are actually being used. An open-ended request to “approve Claude for the organization” is very different from a privacy and security standpoint than a request to use a specific Claude deployment for a defined workflow.
Prioritize evidence over assertions
Don’t accept attestations at face value. Look for policy documentation, audit evidence and third-party validation. Be sure to verify that what you’re reviewing actually covers the product or service you’re evaluating.
Monitoring platforms can provide ongoing signals about a vendor’s external security posture. These tools help shift risk assessment from a point-in-time snapshot to more continuous monitoring. But someone still needs to review that data and connect it to the specific services the vendor provides.
To get a jump-start on your vetting, check whether the vendor maintains a trust center. Many larger vendors now maintain a dedicated section of their website — often password-protected or requiring an NDA — where they publish pre-answered questionnaires, SOC 2 reports, security policies and compliance certifications.
Tier vendors by risk and business impact
Not every vendor deserves the same level of scrutiny. Categorize vendors using risk tiers such as low, medium and high or business-impact tiers such as critical and non-critical. Tiering focuses attention on high-risk and high-impact third parties.
The criteria for tiering should include:
- The sensitivity of data the vendor accesses
- The financial commitment
- How operationally dependent the organization is on the vendor’s services
- How difficult it would be to replace the vendor
Take a hospital system using a third-party revenue cycle management platform. That vendor handles billing data for thousands of patients, integrates directly with electronic health records and is operationally essential. It belongs in a critical or high-risk tier, with proportional oversight.
A vendor stocking the breakroom with coffee and snacks is low-risk or non-critical and doesn’t warrant as much attention.
Reassess on triggers, not just calendars
Reassessments of vendor risk shouldn’t be driven by arbitrary dates. They should be driven by:
- Changes to a vendor’s security posture
- Changes in the scope of services they provide
- Contract amendments
- Significant infrastructure changes
- A known incident
These are the moments that actually signal new or elevated exposure — not dates on the calendar.
Plan for vendor failure
Mature TPRM programs don’t hope vendors will be secure. They assume something will go wrong and plan accordingly.
Establish notification requirements in your contracts. If a vendor experiences a breach involving your data or network, how quickly must they notify you? That timeline needs to be in the service-level agreement. For public companies, the SEC requires disclosure of material cybersecurity incidents within four business days of discovery. Your vendors need to tell you before that clock runs out.
Internally, this means extending your incident response plan to vendor scenarios. Critical vendors should be included in tabletop exercises. When you receive a notification from a vendor, who gets looped in? Who makes the call on response? You can’t outsource accountability; you can only prepare for it.
Orchestrate the functions, not just the roles
Even in smaller organizations where one person handles compliance, security and legal, those reviews need to stay functionally separate. A legal review should be distinct from a compliance review. An IT review should not be conflated with a security assessment. The sequencing matters, and the context from each review must inform the next one.
Think of it like a symphony. Somebody has to decide when each section plays and how all the parts come together. Without that coordination, you get noise. Independent, disconnected reviews that don’t add up to a real understanding of risk.
The executive team needs oversight of this process. Someone at the top has to understand what each function reviewed, what risk was identified and what the collective picture looks like before an approval decision is made.
Read more
Wipfli’s cybersecurity team works with organizations to design and implement TPRM programs that actually function as risk management: building the policy framework, standing up vendor management workflows, configuring monitoring and performing the security portion of the vendor review. For organizations that don’t have the internal bandwidth or specialized knowledge to run this well, Wipfli can do the heavy lifting — from program design to ongoing monitoring. Improve your third-party risk management.
