Skip to main content
How secure are your AI vendors? We assessed 18,160 of them. Read the 2026 AI Supply Chain Report.Read the Report
BlackKite: Home
Menu
blog

From Observational to Actionable TPCRM: Why Finding Vendor Risk Isn’t Enough

Published

Nov 12, 2026

Introduction

Third-party risk programs have gotten very, very good at seeing things. Fixing things? Not so much.

For years, third-party risk management, vendor risk management and supply chain risk management have all run on the same engine: observability. We discovered this, we learned about that, we asked these questions and got those answers. Then we hand the findings off, and the risk profile of the organization stays right where it was.

The results speak for themselves. Third-party and supply chain breaches keep climbing, and AI is about to make everything move faster. (You can't write anything these days without mentioning AI. I think it might actually be illegal.) If the goal of third-party cyber risk management (TPCRM) is to reduce risk, observation alone isn't getting us there.

Why Observational Third-Party Risk Management Keeps Failing

The typical workflow goes like this: gather information, package it up, throw it over the wall to the vendor, move on. No ongoing maintenance, no follow-up, no risk treatment plan, other than, “they'll fix it sooner or later, I think.”

A few years ago, I was at an event for a data governance product, where a big tech vendor had three very impressive CISOs on stage. I asked what I thought was a simple question: Do you go back afterward and validate that you made the right decisions, that your data was accurate, that your analysis held up?

Two of the three said, more or less, "Why would we do that?"

That answer is the whole problem in five words. We treat discovery as the finish line.

What Actionable TPCRM Looks Like

Actionable TPCRM (I'm not really a fan of the term "actionable," please send alternatives) is a collaborative back and forth dance. It focuses on what we do with the information, not just the fact that we have it.

That starts with speaking the language of the person on the receiving end. Business stakeholders care about three things: money coming in, money going out and, if something goes sideways, who gets in trouble. When you dump a list of doubtful, dubious, and unverified alerts in their lap, you're just handing them more work. They won't respond, because they're busy managing those three things inside their own organizations.

So reframe it. "We found 3,000 open vulnerabilities in your environment" lands with a thud. "If you fix these 25, or 40, or 58, we're in good shape, and we'll keep working on the rest together" is a conversation people can leverage to drive action.

The data backs this up. Black Kite's 2026 Supply Chain Vulnerability Report found that of more than 48,000 CVEs published in 2025, only 58 posed a genuine threat to enterprise supply chains. The bottleneck has always been prioritization, not awareness. And when the volume of CVEs keeps increasing - we are on target for more than 100,000 CVEs in 2026 - it gets even harder.

Shift the Mindset From "Your Problem" to "Our Problem"

The biggest change actionable TPCRM requires is a change in mindset. Observational programs run on "this is your problem." Actionable programs run on "this is our problem." We're all in this together. It's the same reason policing vendors, finger wagging, and empty threats, backfire and partnering works.

The logic is simple. If Vendor XYZ gets safer for us, it gets safer for every customer it serves, and everyone downstream benefits from the same improvement. If we're safer, everybody's safer. That's the ecosystem effect finally working in our favor.

Collaboration also has to reach the technical stakeholders on the vendor side. That's where The Bridge® comes in, moving the relationship from "here's what we found" to structured, evidence-based remediation both sides can work through together.

Four Moves That Turn Observation Into Action

Getting to actionability takes more than good intentions. Here's where I'd focus first.

1. Communicate business impact, not findings

Help business stakeholders answer one question: If this critical vendor goes down and can't ship products or deliver services, what happens to us? Framed that way, the reaction tends to be, "That sounds significant. Maybe we should talk to them."

2. Validate before you reach out

When I covered this market as an industry analyst, one of the biggest complaints I heard was false positives. A company would tell a vendor it had an open vulnerability, and the vendor would reply that it didn't even run that software. Credibility, gone. Data efficacy, accuracy and defensibility determine whether vendors take your outreach seriously.

3. Put accountability where it belongs

Managing third-party risk can't be the CISO's job alone, or even the CRO's. Accountability belongs with the business owner of the relationship. For significant exposures, it may sit with a risk committee. For a major provider, it may belong with the audit committee or the board. Vendor risk is a security problem, but deciding what to do about it is a business decision.

4. Prioritize by situation, not just by vendor

How risky the vendor is matters. How risky the situation is matters more. Data loss is one thing. An operational outage is another, and it usually deserves a higher place in the queue. Tier your vendors, tier the exposures within each vendor's environment, then build multi-layered escalation paths on top of that.

Continuous Monitoring Closes the Loop

Asking a vendor to fix something is half the job. Confirming they fixed it is the other half.

Most organizations still assess vendors once a year. Some do it once every couple of years. If you ask a vendor to remediate a critical issue and won't see a completed questionnaire for another 11 and a half months, that's not an acceptable way to understand or manage risk.

Risk profiles change overnight. A piece of software that looked harmless yesterday becomes a priority the moment a new zero-day drops, and frontier AI models are speeding up how quickly those discoveries happen. We can't wait for the next discovery cycle to say, "Oh, look what we found."

Continuous monitoring lets you validate that vendors did what they committed to do. It also supports an iterative approach. Nobody goes from all the risk to none of the risk. We can make steady, incremental improvements in how we communicate, how we react and how we respond.

Accountability, Risk Focus and Collaboration Drive Actionable TPCRM

Moving from observational to actionable TPCRM comes down to three things. 

  1. Accountability. 
  2. A relentless focus on risk. 
  3. And collaboration, working together instead of pointing fingers or kicking the blame down the road.

Until security and risk teams make that shift, they'll keep struggling and keep getting exposed through the same third-party doors. The intelligence already exists. The harder work is walking it over, agreeing on what matters and seeing it through together.

Ready to move from spotting vendor risk to resolving it? See how Black Kite helps teams prioritize the exposures that matter and work them through to the fix.

About the author

Jeffrey Wheatman · SVP Cyber Risk Strategist

Jeffrey Wheatman is SVP Cyber Risk Strategist at Black Kite. A former Gartner VP of 15 years, he advises Fortune 500 and public sector leaders on cyber risk strategy and board communication.