Publish date
November 18, 2026
{x} minute read
Written by
Reviewed by
Table of contents

AI coding tools have changed what's possible to build in-house. For organizations looking to improve their third-party cyber risk management (TPCRM) program, developing more of the technology themselves is becoming a realistic consideration. Teams can now build tools that read vendor SOC 2 reports, extract key findings, and draft follow-up questions in days.

The more useful question is which parts of your program genuinely benefit from being built in-house, and what are you sacrificing for the perceived flexibility of building it yourself.

Usually, the answer splits the program into two. Build the workflow that's specific to your team. Buy the market view that no single company can collect from its own vendor list. Then blend them, so your workflow runs on data you couldn't collect alone.

Three questions for each part of the program

A TPCRM program is several jobs bundled together. Before building any of them, ask three questions about each one:

  • Is it specific to how we work?
  • Does it depend on information gathered outside our organization, over years?
  • Will someone have to stand behind its output in front of an auditor, regulator or the board?

Put a typical program through those questions and the jobs sort themselves:

Part of the program Usually Why
Intake forms, approval routing, notifications, and reminders Build or configure They follow your process, and your team knows it best
Vendor tiering and risk appetite Configure They express your policy
A security rating for every vendor Buy A rating is only comparable when one method is applied to many companies
Emerging risk across your vendors Buy You need to have been watching before the news broke
Links to your vendors’ own suppliers Buy It takes visibility across many vendors at once
The assessment record Buy or blend Someone has to sign it, and auditors will ask how it was produced

The first two rows are where a build or a configuration pays off. Your intake process, approval chain, notification rules, and tiering criteria belong to you, and an engineer with an AI coding tool can fit them closely to how your team works. Most TPRM platforms, ours included, let you configure these workflows too, so check whether you need to build at all.

The remaining four rows of the table are where building runs into trouble. Three of them depend on data collected beyond your own vendor list, and the fourth needs a record someone will sign.

A security rating that supports a decision

You use a security rating to answer questions from the board and the business. Which vendors fall outside our risk appetite? Which are getting worse? Which are getting better? How does a new supplier compare with the one it replaces?

Each answer depends on comparison. A rating means something when the same scoring method covers your vendors, your own organization, their industry peers, and suppliers you haven’t signed yet. Daily scanning keeps it current, so a change in the rating tells you something happened, and you can find out what.

A rating built only from your own vendor list has nothing outside it to compare against. You’d see how your vendors rank against each other, with no way to tell whether a vendor’s letter grade is typical for its industry or an outlier.

UpGuard scans more than 15 million organizations daily, so each vendor’s security rating sits inside a market-wide picture. We publish our scoring method, so when a rating moves, your team can see which findings moved it and explain the change to the board without calling us.

Seeing emerging risk across your vendors

In the IBM Cost of a Data Breach Report 2026, supply chain compromise was the second most common initial attack vector, behind phishing. When a supplier is breached, or a new vulnerability turns up in software your vendors use, the board asks one question: are we exposed through our supply chain?

A team that was already watching can answer from what it knows. A team with a new prototype has to start collecting. Answering quickly depends on work done before the news broke: scanning every vendor’s internet-facing systems for software with known vulnerabilities, and following the security news and incident reports about each one.

The PHP2Shell vulnerabilities are an example. A security team that hadn’t been scanning for this vulnerability would’ve had to email every vendor, then wait while each one checked with its hosting provider.

That work runs every day, whether or not anything is in the news. UpGuard processes around 10 billion signals a day, tracking 13,435 Common Vulnerabilities and Exposures. When a vendor’s security rating drops or a new risk appears, UpGuard Vendor Risk alerts your team.

From third parties to fourth

Your vendors have suppliers too. When a widely used product or service has an incident, it can reach you through several vendors at once, including ones that never mentioned that supplier in a questionnaire.

The Fourth Parties view in Vendor Risk shows which of your vendors use the same technology products, so when one of those products has an incident, you can see which of your vendors rely on it. 

Building that view yourself means detecting the products each vendor uses across your whole portfolio, and keeping the picture current as vendors change suppliers. That’s data collection at scale, and it gets more useful the longer it runs.

An answer someone can sign

Every vendor decision ends with an owner. Months later, an auditor asks why a vendor passed, and the owner has to produce the record behind that decision.

That answer is only as strong as the system that produced it. Can you show the finding was right? Would it come out the same if you ran it again? Can you replay what the reviewer saw that day, even after the checks or the model behind them has changed? Can you show the vendor evidence that it held was protected the whole time?

Your team can build a tool that answers those questions. Then it has to keep answering them for as long as it runs, through every model update, framework revision, new regulation, and change of staff. 

Buying hands off that maintenance responsibility to a vendor whose business depends on getting it right. The vendor secures the product, keeps its findings defensible, controls how changes roll out, and absorbs each new framework and regulation for every customer at once.

Accountability for the decision stays with you either way. The question is how much of the proof you want to carry alone.

In Vendor Risk, Security Profile cites the evidence behind every check result, and check history shows how each result changed over time.

There’s a compliance angle too. A tool your team builds to store vendors’ SOC 2 reports and penetration test results is likely to fall inside your own ISO 27001 or SOC 2 audit scope, so you’ll need to show how it’s secured.

What blending looks like

In our experience, many programs end up with a blend. The platform runs the core third-party risk workflow, from vendor intake and assessment through continuous monitoring and remediation, with the data, ratings, alerts, and assessment record built in. 

Your team configures it to your policy, then builds or connects what sits on either side: the requests coming in from the business, and the reporting, ticketing, messaging, and AI tools that act on what comes out.

With UpGuard, a blend can look like this:

  • Your team’s AI tools and agents read vendor data through the UpGuard API, which gives programmatic access to vendors, risks, assessments, and questionnaires.
  • Rating changes and new findings flow into the systems your team already works in, including Jira, ServiceNow, and Slack.
  • Your own approval and follow-up workflows run on top, built in Risk Automations with more than 100 integrations, or in your own tools.

Questions to take to your AI council

If your organization reviews new software through an AI council, procurement, or a build-first policy, these questions keep the discussion on the whole program:

  • Which parts of the program get better because we built them?
  • Who approves the output, by name?
  • What does the tool know about a vendor before anyone has assessed it?
  • What can it see beyond our direct vendors?
  • Where does each vendor’s history start, and where does it go if the tool is retired?
  • Who finds out first when a data feed stops working?
  • Who maintains it once the engineers who built it move on?

If the answers favor a blend, the next decision is where your workflow ends and your data source begins. 

If you’re weighing which platform to blend with, IDC named UpGuard a Leader in its 2026 MarketScape for worldwide third-party risk management software, citing: “UpGuard’s TPRM AI differentiation centers on the company’s AI Global Risk Inference Domains (GRID) engine, which fuses billions of external signals with AI analysts and agents to produce a live, continuously updated security posture view across vendor ecosystems and attack surfaces simultaneously.”

Talk to us about a blended setup. Bring your AI council lead and their requirements, and we’ll work through which parts of your program to build yourself and which to run on UpGuard.

Source: IDC MarketScape: Worldwide Third-Party Risk Management Software 2026 Vendor Assessment, Doc #US53007725, September 2026.

Related posts

Learn more about the latest issues in cybersecurity.