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

Third-Party Risk and the Alphabet Soup Problem

Third Party Podcast: Why EASM, CTEM and TPCRM Labels Won't Tell You What to Buy

YouTube video thumbnail

In this article

Check out our podcast, Third-Party. This is the podcast built for the people behind the dashboards. The ones managing 5,000 vendors with a team of three.

WATCH ON YOUTUBE

Acronyms Don't Solve Problems

Security has an acronym problem, and it is getting worse. Analyst firms define markets, draw category lines and invent new labels so they can own a space. Buyers end up holding a bowl of alphabet soup that doesn't map to anything they actually need to fix.

In the latest episode of the Third Party podcast, Jeffrey Wheatman, Bob Maley, and Ferhat Dikbiyik sort through the labels piling up around third-party cyber risk management (TPCRM) and ask a more useful question: what are you actually trying to solve?

The answer matters, because markets should form around customer demand. Too often, they form around a chart.

Decoding the Alphabet Soup

Quick glossary, then we get to the good part. Most of these categories started as first-party security operations tools. Here is what each one describes:

  • EASM (external attack surface management): An attacker's outside-in view of your digital footprint. Websites, exposed assets, anything reachable from the internet.
  • CTI (cyber threat intelligence): Context on top of that footprint. What threat actors say about you, and what threats target your industry.
  • DRPS (digital risk protection services): Action. Taking down the phishing domain that impersonates your brand, for example.
  • CTEM (continuous threat exposure management): A program model for continuously finding, prioritizing and fixing exposures.
  • TPCRM: Managing the cyber risk that flows in from vendors, suppliers and the rest of your ecosystem.

A first-party program needs EASM, CTI and DRPS working together. Yet the categories got split apart, so startups launched to fill a single box. Most were acquired. A standalone point solution rarely has enough market to survive on its own, and the steady consolidation proves it.

Labels Fit the Buyer and Miss the User

Here is the quiet flaw in every category map. Talk to a thousand organizations, average out their needs, and you blend all the lumps out of the mashed potatoes. The result fits most people a little and nobody well. Small business? Not quite. Financial services? Not quite. Public sector? Definitely not.

Add your vendor ecosystem, and the lines blur further, because two different teams touch the same work:

  • Risk operations buys the tool and sees a third-party risk product.
  • Security operations, often on the vendor's side, uses the output and sees an attack surface tool.

Categories get drawn from the buyer's perspective, not the user's. So the same capability lands in two boxes depending on who is looking. Meanwhile, prospects ignore the labels entirely and ask the only question that helps them: who do you compete with?

That collaboration gap is exactly where third-party and attack surface tools are converging. Risk teams can share cyber risk intelligence with vendors, telling them what their exposure looks like. Smaller vendors that could never afford a full EASM stack benefit first. Expect more attachment between these worlds, not a tidy merger.

How to Build a Stack When Tools Keep Shapeshifting

Start with this uncomfortable truth: nobody is secure. Some organizations are more secure than others, and attackers know exactly which ones to hit. So the job isn't buying coverage for everything. It's understanding what drives your business and mapping the attack surface around whatever could hit the bottom line.

A few rules hold up no matter how the categories shift:

  • Name the problem first. "Do we need a ratings tool?" is the wrong question. "What problem should this solve?" is the right one.
  • Treat governance as a process, not a product. Technical teams move fast and route around controls. Governance keeps everyone from building their own island.
  • Be wary of long contracts. A three-year deal looks cheaper until the vendor gets acquired or a better technology arrives fifteen months in.
  • Audit for overlap. Tools that did different jobs at purchase often do the same job today. You may be paying twice.

Even the right question has limits. Ask TPRM teams fifteen years ago what they needed, and they wanted better questionnaire management. They got it, and it made a bad process easier to run. Still a bad process. Nobody asked for continuous, standards-based risk intelligence back then, the same way nobody asked for chunky pasta sauce until someone put it on the shelf.

Executives, meanwhile, care about three things: money coming in, money going out, and who gets in trouble when something breaks. Every tool in the stack should connect to one of those. A cool acronym and a steak dinner don't count.

Find Your AI Before You Try to Secure It

The next acronym is already loading. Inboxes are full of four-person startups promising to "secure your AI." That's a bold claim, considering most organizations can't say where their AI lives.

AI doesn't sit in one place. It hides in browser plugins, free trials and SaaS tools that quietly switched on new features. Securing it starts with finding it, which suddenly calls for another tool. Then another for machine learning, another for LLMs and another for agents. Call it AI attack surface management, or AIASM, and watch the turtle stack grow.

Agents deserve the most attention. LLMs generate text. Agents take action. "My people will call your people" has become "my agent will connect to your agent," and to every other agent it can reach. Without a human in the loop, that connectivity spreads across vendors and their Nth-party ecosystem faster than any category chart can track.

So push back. Buyers, practitioners and vendors should all tell the analysts the same thing: skip the new market definition and help solve the problem. That's the standard Black Kite holds itself to: intelligence tied to the business outcomes that actually matter.

Don't Miss an Episode!

Subscribe to Third Party on YouTube, the podcast for people who don't need to ask ChatGPT what TPCRM means. New episodes every other week.

Next time on Third Party:

Next time we tackle the question every risk team eventually asks — when we say a program is ‘actionable,’ what does that actually mean? We get specific about what comes after “here’s what we found.”

Subscribe below.

Real Talk on Third-Party Risk.

Check out our new podcast, Third Party, where we unpack what actually works (and what doesn't) in TPRM.

Apple Podcasts
Follow Third Party on Apple Podcasts
Follow
Spotify
Follow Third Party on Spotify
Follow

Ready to get started?

Integrate risk intelligence into every part of your workflow so you can make more informed decisions with confidence.