Vendor & Third-Party Risk Management: The Complete Guide
Third-party risk management (TPRM) is the program an organization uses to identify, assess, monitor and reduce the risks created by vendors, suppliers, partners and service providers across the whole relationship, from planning to exit. It matters more every year: third parties were involved in 30% of breaches in Verizon’s 2025 Data Breach Investigations Report, double the year before, and regulators from US banking agencies to NYDFS and the EU now expect full life-cycle oversight.
- TPRM covers the whole life cycle: planning, due diligence, contracting, ongoing monitoring and termination, not just an onboarding questionnaire.
- Tiering is the foundation. Match review depth and frequency to each vendor’s inherent risk so critical vendors get scrutiny and low-risk vendors move fast.
- Third-party involvement in breaches doubled to 30% in the 2025 Verizon DBIR.
- Regulators expect it: the 2023 interagency guidance for US banks, NYDFS‘s October 2025 guidance that Part 500 responsibility cannot be delegated to vendors, and DORA‘s register of ICT third-party arrangements.
- Vendor findings belong in the enterprise risk register, next to the internal risks and controls they affect.
What is third-party risk management?
A third party is any outside organization you rely on: software and cloud vendors, outsourced IT and security providers, payment processors, data processors, contractors, consultants, distributors and business partners. Third-party risk is the chance that one of them causes a security incident, a compliance failure, an operational outage, financial loss or reputational harm for you.
TPRM is broader than vendor security reviews. A mature program covers several risk domains:
| Risk domain | Example |
|---|---|
| Cybersecurity | A vendor with access to your data or network is breached |
| Operational and resilience | A critical provider has an outage you cannot work around |
| Compliance and regulatory | A processor mishandles personal data or PHI |
| Financial | A key supplier becomes insolvent |
| Concentration | Many critical services depend on one provider |
| Reputational and ESG | A partner’s conduct becomes a headline about you |
| Fourth-party | Your vendor’s own vendor fails |
Why does third-party risk matter more in 2026?
- Breaches. Verizon’s 2025 DBIR found third-party involvement in 30% of breaches, up from 15% (Security Magazine). In healthcare, about 30% of 2024’s large breaches occurred at business associates (HIPAA Journal).
- Banking regulation. The Federal Reserve, FDIC and OCC’s June 2023 interagency guidance replaced each agency’s earlier guidance and applies risk-based oversight across the life cycle, including fintech relationships (Hunton).
- NYDFS. In October 2025 NYDFS issued third-party service provider guidance stating that covered entities may not delegate responsibility for Part 500 compliance to vendors (Bright Defense).
- EU DORA. Since January 17, 2025, EU financial entities must manage ICT third-party risk and maintain a register of information on ICT contractual arrangements (Roschier).
- AI vendors. Embedded AI features change what vendors do with your data, which most legacy questionnaires never asked about.
What are the stages of the third-party risk life cycle?
| Stage | Key activities | Output |
|---|---|---|
| 1. Planning and intake | Business owner requests the vendor; define the service, data and access involved | Intake record with owner and purpose |
| 2. Inherent risk tiering | Score data sensitivity, access, criticality, regulatory impact and replaceability | Risk tier that sets review depth |
| 3. Due diligence | Questionnaires, SOC reports, certifications, financials, references, sanctions screening | Assessment with findings and residual risk |
| 4. Contracting | Security, privacy, audit, breach notice, subcontractor and exit terms | Signed agreement with risk controls |
| 5. Ongoing monitoring | Continuous signals, periodic reassessment, performance and SLA tracking | Current risk rating; triggered reviews |
| 6. Issue management | Track vendor findings to remediation or formal risk acceptance | Findings closed or accepted with expiry |
| 7. Termination | Revoke access, return or destroy data, transition services | Documented offboarding |
How should you tier vendors?
Score inherent risk on a handful of factors, then map the score to a tier that decides how deep and how often you review.
| Tier | Typical vendors | Due diligence | Reassessment |
|---|---|---|---|
| Critical | Core hosting, payment, data processors handling sensitive data at scale, services supporting critical activities | Full questionnaire (SIG or CAIQ), document review, SOC 2 or ISO review, financial review, possibly audit rights | Annually plus continuous monitoring |
| High | Access to sensitive data or important processes | Standard questionnaire and SOC report review | Annually |
| Moderate | Limited data, replaceable services | Short questionnaire or published evidence | Every one to two years |
| Low | No sensitive data, low business impact | Intake review only | At renewal or on material change |
Use the same factors for every vendor so tiers are defensible to auditors and examiners. See how to assign vendor risk ratings.
What should vendor due diligence include?
- Security posture. SOC 2 Type 2 or ISO 27001 certificate, penetration test summary, security questionnaire. Read the SOC report’s exceptions and complementary user entity controls, not just the opinion. See how to review a vendor SOC 2 report.
- Data handling. What data, where it is stored and processed, encryption, retention and deletion, subprocessors.
- Resilience. Business continuity and disaster recovery plans, recovery objectives, recent outages.
- Privacy and regulatory. DPA terms, HIPAA BAA, PCI responsibility matrix, regulatory history.
- AI use. Whether the vendor uses AI on your data, trains models on it, and how it governs AI. See our AI vendor risk assessment guide.
- Financial and corporate. Financial stability for critical vendors, ownership, sanctions and adverse media.
Choosing a questionnaire format matters less than right-sizing it. See SIG vs CAIQ.
What contract terms reduce third-party risk?
| Clause | Why it matters |
|---|---|
| Security requirements | Sets minimum controls such as MFA and encryption, which NYDFS guidance recommends contracting for |
| Breach notification | A defined window, often 24–72 hours, so your own regulatory clocks can be met |
| Right to audit and evidence | Annual SOC reports or assessment rights |
| Subcontractors | Notice of and approval rights over fourth parties handling your data |
| Data location, return and deletion | Control over where data lives and proof it is destroyed at exit |
| Business continuity | Recovery commitments aligned to your own |
| Termination and transition | An orderly exit, especially for critical services |
How do you monitor vendors continuously?
An annual questionnaire is a snapshot. Between reviews, watch for signals that change a vendor’s risk:
- Security rating changes and exposed services
- Breach disclosures and adverse media
- Expired SOC reports, certificates and insurance
- Ownership changes, layoffs or financial distress
- New subprocessors or data locations
- Missed SLAs and incidents affecting you
Define which signals trigger an immediate reassessment and which simply update the risk rating. See how to manage vendor risk at scale and AI in vendor risk management.
How do you manage fourth-party and concentration risk?
Ask critical vendors to disclose the subprocessors and infrastructure providers that support your service, and record them. Where many critical vendors rely on the same cloud provider or service, you have concentration risk even if every vendor looks healthy on its own. Map these dependencies for your most important business services and plan for the failure of a shared provider. See fourth-party risk management.
Which TPRM metrics should you report?
| Metric | What it tells you |
|---|---|
| Vendors without a tier or owner | Coverage gaps in the inventory |
| Critical vendors past reassessment date | Whether the program keeps pace |
| Open vendor findings by age and severity | Remediation discipline |
| Intake-to-approval cycle time | Whether the program slows the business |
| Share of critical vendors with current evidence | Evidence freshness |
| Concentration on shared providers | Systemic dependency |
Frequently asked questions
What is the difference between vendor risk management and third-party risk management?
What are the stages of third-party risk management?
How often should vendors be reassessed?
What percentage of breaches involve third parties?
Do banks have to follow the interagency third-party guidance?
Can you outsource responsibility for vendor compliance?
What is fourth-party risk?
- Security Magazine, Verizon 2025 Data Breach Investigations Report
- Hunton, Interagency guidance for bank risk management of third-party relationships
- Morrison Foerster, Banking agencies issue joint third-party risk management guidance
- Bright Defense, NYDFS cyber rules enter stricter enforcement phase
- Roschier, Digital Operational Resilience Act (DORA)
- HIPAA Journal, 2024 Healthcare Data Breach Report
- Compyl, How to manage vendor risk at scale
- Compyl, AI vendor risk assessment guide
Manage Third-Party Risk Inside Your GRC Program With Compyl
Compyl runs vendor intake, tiering, automated questionnaires, evidence tracking and reassessment on configurable workflows. Third Party Insights delivers vendor intelligence without waiting on questionnaires, and every finding rolls into the enterprise risk register with FAIR quantification for critical relationships.
About this guide. By Compyl Research. Last updated November 9, 2026. This is general information, not legal advice — consult counsel for your specific obligations. Compyl is an AI-powered, agentic GRC platform built by CISOs.