Skip to content
NewCybercrime Report 2026 · Eight Chapters · A Post Is Not An Incident → Explore The ChaptersCybercrime Report 2026 → Explore

Third-Party Risk Management (TPRM)

Third-party risk management (TPRM) is the program a company uses to find, assess, reduce and monitor the risks that come from vendors, suppliers, service providers and other outside parties. It covers the whole relationship, from due diligence before you sign and security terms in the contract to monitoring and a safe exit.

Reviewed by
Brandefense Analyst Team
Published
Updated
Reading Time
13 min read
Dark glass glass chain of links with one red glowing link held outside a glass box with red neon lines, cover art for: Third-party risk management (TPRM)
Product track
External Attack Surface Management

What Is Third-Party Risk Management?

Third-party risk management, or TPRM, is how a company keeps the risk that outside parties bring at a level it accepts. A third party is any outside organization that holds your data, connects to your systems or runs a service you depend on. That includes software and cloud providers, managed service providers, contractors, consultants, payment processors and partners.

The circle is wider than the companies you pay. US banking regulators describe a third-party relationship as any business arrangement with another entity, "by contract or otherwise". Their interagency guidance of June 2023 adds that such a relationship can exist without a contract or payment.

NIST calls the same work cybersecurity supply chain risk management (C-SCRM). It defines it as "a systematic process for managing exposure to cybersecurity risks throughout the supply chain and developing appropriate response strategies, policies, processes, and procedures". The exposure itself, meaning what can go wrong through a vendor, has its own entry: third-party risk.

What Types of Third-Party Risk Does TPRM Cover?

One vendor can bring several kinds of risk at once. The table lists the main types, a real case for each from our coverage and the first question to ask.

Risk typeReal caseFirst question
Data and cloud access. The vendor holds your data or can act inside your accounts.Wiz says credentials from an AWS account associated with Qubole were used to reach several customers' AWS accounts, read secrets and take S3 data (Qubole AWS access breach).Which vendor roles and API keys can act inside our cloud?
Supplier staff access. A person at the vendor becomes your way in.Bybit says a Safe developer's compromised credentials let the attacker reach Safe{Wallet} infrastructure before the February 2025 theft (Bybit theft and supplier access).Who at the vendor can change what our staff approve?
Software supply chain. Code or updates from the vendor carry the attack.Attackers put a backdoor into Orion updates released between March and June 2020. SolarWinds believed fewer than 18,000 customers had an affected installation (SolarWinds Orion compromise).Which vendor software runs with admin rights, and do we have its SBOM?
Security vendor. The company that protects you is breached.F5 said a nation-state actor took some BIG-IP source code and details of undisclosed BIG-IP flaws. F5 learned of the access on 9 August 2025 (F5 breach).Who can reach the admin pages of our vendor-run edge devices?
Operational. A vendor outage stops your own service.Ransomware hit Synnovis, the pathology provider for several London NHS hospitals, on 3 June 2024. Thousands of appointments and operations were postponed (Synnovis attack).Which of our services stop if this vendor stops?
Concentration. Many organizations depend on one provider.The February 2024 attack on Change Healthcare disrupted pharmacies, claims and payments. The US government opened emergency Medicare payment programs (Change Healthcare attack).Where do many of our processes rely on one provider?
Fourth party. Your vendor's own supplier fails.Polymarket halted trading on 29 October 2026 after a provider was compromised. The provider said its DNS records were compromised through its own domain registrar (Polymarket hack).Which suppliers do our critical vendors depend on?
Compliance. A vendor gap becomes your regulatory finding.Under DORA Article 28, EU financial entities that use ICT providers "remain fully responsible" for their own obligations.Can we show a regulator our vendor register?

The head term covers more than security. Financial risk is a key vendor's insolvency or a sudden price change that stops a service you rely on. Reputational risk is a vendor's breach, fraud or labor practice being reported under your name.

Some programs add strategic and ESG risk, and geopolitical risk such as sanctions or the country a vendor operates from. This page goes deepest on the cyber, operational and compliance types, because a security team can test those.

How Does the TPRM Lifecycle Work?

TPRM runs as a cycle around each vendor, not as a yearly event. The US banking agencies' guidance names five stages: planning, due diligence and third-party selection, contract negotiation, ongoing monitoring, and termination. The diagram splits the same cycle into eight working steps.

1 Plan
   |
   v
2 Tier <---- re-tier -----+
   |                      |
   v                      |
3 Due diligence           |
   |                      |
   v                      |
4 Contract                |
   |                      |
   v                      |
5 Onboard                 |
   |                      |
   v                      |
6 Monitor -- signal --> 7 Fix and respond
   |    ^                 |
   |    +----- fixed -----+
   |
   v  contract ends
8 Exit

A signal sends the vendor to step 7. A real change, such as new data, new access or an incident, sends it back to step 2.

StepWhat you doWho leads
1. PlanDecide what the vendor will do, what data and access it needs and how you would leave. Keep: data and access list.Business owner.
2. TierRank the vendor by the damage a failure on its side could do. Keep: tier and reason.Security and risk.
3. Due diligenceQuestionnaire, evidence (a SOC 2 Type II report or ISO/IEC 27001 certificate with its scope, a recent penetration test summary, insurance and business-continuity evidence), and an outside-in check before you sign. Keep: review record.Security, privacy and procurement.
4. ContractSecurity duties, breach notice, audit rights, subcontractor rules and exit terms. Keep: signed terms.Legal and procurement.
5. OnboardOnly the access the service needs, through named accounts with MFA. Keep: access list with owners.IT and security.
6. MonitorWatch exposure, leaked credentials, breach notices and leak-site claims between reviews. Keep: signal log.Security operations.
7. Fix and respondAgree fixes with the vendor, track them to a date and act fast on a vendor incident. Keep: action tracker.Vendor owner and security.
8. ExitRemove access, get your data back or proof of deletion, and move the service. Keep: offboarding checklist.Business owner and IT.

The steps line up with NIST's Cybersecurity Framework 2.0. Its supply chain category, GV.SC, has ten subcategories. GV.SC-04 says suppliers are known and prioritized by criticality. GV.SC-06 asks for due diligence before a formal relationship, and GV.SC-10 for plans that cover the time after an agreement ends.

Which Vendors Need the Closest Look?

Tiering sorts vendors by the damage a failure on their side could do to you. Five questions do most of the work.

  • Data: do they hold personal, regulated or secret data of yours?
  • Access: do they have network, admin or cloud access to your systems? The FASCSA order on Acronis backup tools cites this kind of access as its reason.
  • Impact: which of your services stop if they stop?
  • Replacement: could you switch in weeks, or not within a year?
  • Fourth parties: which suppliers do they depend on, and do your other vendors share them?
Tier and typical vendorReview
Tier 1, critical. Privileged access to production, regulated data, or a service you cannot run without.All questions, with evidence for every critical and high item, before signing and then yearly. Outside-in check: monthly or continuous.
Tier 2, important. Limited access or internal data.The critical and high questions. Outside-in check: quarterly.
Tier 3, standard. No sensitive data and no access.The critical questions only. Outside-in check: at renewal.

Our third-party risk questionnaire template has the scoring method behind these tiers and 41 questions with the evidence to ask for. Re-tier a vendor whenever its service changes.

What Does a TPRM Finding Look Like?

A finding is a dated record of something wrong at a vendor, with evidence, an owner and a due date. Without those parts it is only a worry. Below is an illustrative example: the vendor is a placeholder, and the days count from the first alert.

FieldExample entry
Vendor and tierPayroll provider, vendor.example. Tier 1: it holds staff bank details and has single sign-on into the HR system.
SignalTwo vendor staff logins for its admin portal appear in stealer logs. The portal is on the internet with a password-only login.
Source and dateDark web monitoring alert on day 0. Portal checked from outside on day 1.
Why it mattersA working admin login could expose staff bank details or change where salaries are paid.
Asked of the vendorConfirm the accounts, reset them, end active sessions, put the portal behind MFA and reply in writing.
Our own actionReview the single sign-on trust and check payroll runs for changed bank details.
Owner and due dateHR vendor owner with the security lead. Vendor reply due on day 5.
StatusOpen. If the vendor cannot confirm the fix, raise the review level and tell the business owner.

Treat every signal as a lead until the vendor confirms it. Our steps for a supplier's new exposure signal say who does what.

Three Checks You Can Run on a Vendor Domain

Some evidence needs no questionnaire. These checks read public DNS, one public file and the TLS certificate. We ran them on public domains on 10 November 2026; replace vendor.example with the vendor's domain.

# 1. Email spoofing protection: look for p=quarantine or p=reject
dig +short TXT _dmarc.vendor.example

# 2. A published security contact
curl -s https://vendor.example/.well-known/security.txt

# 3. Certificate expiry date and issuer
echo | openssl s_client -connect vendor.example:443 -servername vendor.example 2>/dev/null | openssl x509 -noout -enddate -issuer

Under RFC 7489, a DMARC policy of p=none asks mail servers to take no specific action on mail that fails the check. Fake invoices sent from the vendor's exact domain are then less likely to be stopped.

RFC 9116 places security.txt under the /.well-known/ path and requires a Contact and an Expires field. A missing file is not a failure, but it tells you to put a named security contact into the contract. Do not scan a vendor's systems beyond what your contract and the law allow.

For a quick outside view of one domain, use our free domain scanner. It builds a risk score from breach data, infostealer logs, dark web mentions and phishing domains in about 30 seconds.

Why Does TPRM Matter?

More breaches now involve a third party. The Verizon 2026 Data Breach Investigations Report says breaches with third-party involvement rose by 60% from the previous year's dataset. They reached 48% of all breaches.

The share differs by region and sector. These are the third-party figures in Verizon's 2026 executive summary.

Region or sectorBreaches with third-party involvement
Latin America and the Caribbean74%
Asia and the Pacific69%
Europe, Middle East and Africa54%
North America43%
Retail68%
Manufacturing61%
Small and medium-sized businesses55%
Educational services40%
Public administration36%
Financial34%
Healthcare32%

Vendor gaps also close slowly. In third-party cloud exposures, Verizon found that only 23% of third-party organizations fully fixed missing or improperly secured MFA on their cloud accounts. Half of those findings were closed within a month. For weak passwords and permission misconfigurations, closing half of the findings took almost eight months.

What Brandefense Blackhole Data Adds

Ransomware leak sites are one place where a vendor's incident can become public. For the ransomware chapter of our Cybercrime Report 2026, we counted 9,203 leak-site claims from 177 groups between 1 January and 27 October 2026. Each claim is a distinct pair of group and victim, taken from Brandefense Blackhole data.

A claim is the group's statement, not proof of a breach. Still, any supplier on your list can appear among them. The report's response table covers this case. When a supplier or software vendor is claimed, ask for written confirmation, rotate shared credentials and API keys, and review inbound connections.

Our playbook for a supplier on a ransomware leak site turns that into steps by role.

Which Rules Require Third-Party Risk Management?

Regulators in the EU, Australia and the US now write vendor oversight into law or supervisory guidance. The table lists the main rules.

Rule and dateWho it coversWhat it asks about vendors
DORA, Regulation (EU) 2022/2554. Applies from 17 January 2025.EU financial entities.A register of all ICT third-party contracts, due diligence before signing, key contract terms (Article 30) and exit strategies for critical or important functions.
NIS2, Directive (EU) 2022/2555. National rules apply from 18 October 2024.Essential and important entities in the EU.Supply chain security, including relationships with direct suppliers and service providers (Article 21(2)(d)), and the vulnerabilities specific to each direct supplier (Article 21(3)).
APRA CPS 230. In force since 1 July 2025. An amended version applies from 1 July 2026.APRA-regulated entities in Australia.Manage the risks from service providers, with material service providers listed on a register sent to APRA.
23 NYCRR 500.11, New York. In force.Covered entities under New York's cybersecurity regulation.Written policies on service providers: risk assessment, minimum practices, due diligence and periodic assessment, plus MFA, encryption and incident notice.
Interagency Guidance on Third-Party Relationships. Final as of 6 June 2023.US banking organizations supervised by the Federal Reserve, FDIC and OCC.Risk management across the five life-cycle stages, scaled to how critical each relationship is.
GDPR, Regulation (EU) 2016/679, Article 28. Applies since 25 May 2018.Any controller that uses a processor of personal data.Use only processors with sufficient guarantees, set the terms in a written contract, and give prior authorization for any sub-processor.
NIST CSF 2.0, category GV.SC. Published 26 February 2024.Any organization, whatever its size or sector.Ten supply chain outcomes, from knowing suppliers by criticality to plans for after an agreement ends.

For the EU rules in more depth, read our NIS2 and DORA vendor requirements and the glossary entries for DORA and NIS2.

These names overlap, and vendors use them loosely. The table shows where each one stops.

PracticeScopeQuestion it answers
TPRMEvery outside party, over the whole relationship.How do we manage vendor risk from selection to exit?
Third-party riskThe exposure itself.What can go wrong through a vendor?
Vendor risk managementUsually the companies you buy from; often another name for TPRM.Are the vendors we pay safe enough?
Vendor risk assessmentOne review at one point in time.Is this vendor safe enough today?
Supply chain risk managementProducts, parts and services, including your suppliers' own sources.Where can the chain break?
Continuous vendor monitoringOutside signals about vendors between reviews.What changed since the last review?
Fourth-party riskYour vendors' own suppliers.Who do our critical vendors depend on?
Security ratingAn outside-in score of one company.How does this vendor look from the internet?

A questionnaire tells you what the vendor says, and outside signals show what anyone can see. Our comparison of continuous vendor monitoring and the annual audit explains the gap a yearly review leaves. For the wider chain, see supply chain risk management and our entry on the supply chain attack.

Where Do TPRM Programs Go Wrong?

  • A yearly questionnaire that nobody checks against evidence.
  • No tiering, so the critical vendors get the same short review as the rest.
  • Vendors that never went through procurement, such as cloud tools signed up with a work email. Compare the vendor list with your single sign-on apps and card payments.
  • No named owner and no due date, so findings stay open for months.
  • No exit plan, so access and data stay with a vendor after the contract ends.

A vendor can change a lot between two reviews. In October 2026 DreamHost reset email and FTP/SFTP passwords for some accounts after an incident it reported on its status page. The affected users could not sign in until the account owner set new ones. Our DreamHost incident guide lists what hosting customers should check.

What Should a TPRM Tool Do?

A spreadsheet can hold a short vendor list. As the list grows, check any tool against these points.

  • It finds a vendor's internet-facing assets itself and shows why each one is linked to that vendor.
  • It records the evidence and the date behind every score.
  • It watches tier 1 vendors between reviews and tracks each finding to an owner and a due date.
  • It keeps an audit trail and sends findings to the tools your team already uses, such as a GRC system.

Our TPRM software buyer's guide turns these points into a weighted scorecard and a proof-of-concept plan. For tender wording, use our RFP questions for threat intelligence, DRP, EASM and third-party risk.

Brandefense runs third-party risk management as a module of External Attack Surface Management. It discovers supplier assets automatically, refreshes them daily and scores vendors on an A to F scale, with GRC integration, webhooks and an audit trail. For ongoing vendor checks that go beyond a yearly questionnaire, see our third-party risk management platform.

How Do You Start a TPRM Program?

  1. Build the list. Pull vendors from accounts payable, the contract system and your single sign-on apps. Add every managed service provider with admin access.
  2. Tier the riskiest first. Score the vendors that hold sensitive data or have access before the rest.
  3. Check tier 1 from outside. Run the domain checks above, and look for leaked credentials and leak-site claims.
  4. Fix contracts at renewal. Add breach notice, audit rights, subcontractor rules and exit terms.
  5. Start monitoring. Watch tier 1 vendors all the time and review tier 2 vendors on a schedule.

Report a few numbers each month. Useful ones are the share of vendors with a tier, the share of tier 1 vendors under monitoring, overdue vendor findings and the median days to close one.

Barracuda's November 2026 XDR notice illustrates how a third party's exposed cloud key can become an access path into a provider environment. Read the Barracuda XDR credential incident analysis for the vendor's confirmed timeline and customer guidance.

Also Called

  • TPRM
  • vendor risk management
  • supplier risk management

Frequently Asked Questions

What does TPRM stand for?

TPRM stands for third-party risk management. It is the program a company uses to find, assess and monitor the risks that vendors, suppliers and other outside parties bring.

What is the main purpose of third-party risk management?

It keeps the risks that come with vendors and suppliers at a level you accept. It does this through checks before you sign, clear contract terms, monitoring afterwards and a planned exit.

What is a TPRM framework?

It is a documented way of working: how you list vendors, tier them, assess them, set contract terms, monitor them and end the relationship. You can map it to NIST CSF 2.0, category GV.SC, or to the five life-cycle stages in the US banking agencies' guidance.

What are the stages of the TPRM lifecycle?

The US banking agencies' guidance names five: planning, due diligence and third-party selection, contract negotiation, ongoing monitoring, and termination. This page also treats tiering, onboarding and fixing findings as steps of their own.

Is TPRM the same as vendor risk management?

The terms are often used for the same thing. TPRM is a little wider because it also covers contractors, partners and service providers.

What is fourth-party risk?

It is the risk from your vendors' own suppliers, such as the cloud host, registrar or software provider a vendor relies on. You rarely have a contract with them, so ask critical vendors to name their key subcontractors and to tell you when those change.

How often should vendors be assessed?

It depends on the tier. Critical vendors need monitoring all year and a full review at least once a year, while low-risk vendors can wait until renewal. New York's 23 NYCRR 500.11 asks for periodic assessment based on the risk each provider presents.

Sources

  1. Cybersecurity Supply Chain Risk Management (glossary), NIST CSRC1
  2. The NIST Cybersecurity Framework (CSF) 2.0, CSWP 29, NIST2
  3. Interagency Guidance on Third-Party Relationships: Risk Management (Bulletin 2023-17), OCC3
  4. 2026 Data Breach Investigations Report, Verizon4
  5. Regulation (EU) 2022/2554 on digital operational resilience (DORA), EUR-Lex5
  6. Directive (EU) 2022/2555 (NIS2 Directive), EUR-Lex6
  7. Prudential Standard CPS 230 Operational Risk Management, APRA7
  8. 23 NYCRR 500.11: Third-party service provider security policy, Cornell LII8
ShareLinkedInX
Brandefense logo

Stay Ahead of Digital Threats.

Take control of your digital security with an exclusive demo of our AI-driven threat intelligence platform.

Open The Full Demo Form →