eProcurement Toolkit

You are here: risk, stop 5/6

The lineSupplier management

What is third-party vendor risk management, and how do you assess a vendor’s security?

Short answer

Third-party vendor risk management checks that vendors holding your data or reaching your systems are secure and compliant, before you sign and for as long as they serve you.

Cite this answereProcurement Toolkit, “What is third-party vendor risk management, and how do you assess a vendor’s security?”, updated 13 Nov 2026, eprocurementtoolkit.org/supplier-management/third-party-vendor-risk-management

Key takeaways

  • Third-party vendor risk management, often called TPRM, is the security, data and compliance side of working with outside companies: what they can see, what they can reach and what happens if they are breached.
  • Breaches involving third parties are growing. Verizon’s breach reports found a third party involved in 30% of breaches in the 2025 edition and 48% in the 2026 edition.
  • Set the depth of the assessment by what the vendor will touch: no data, business data, personal or sensitive data, a connection to your network, or a critical service.
  • Ask for evidence, not only answers: a certificate with the right scope, an audit report with its exceptions, a data processing agreement with the list of sub-processors.
  • Every gap ends in a decision with a name and a date: fixed before go-live, fixed by a deadline, covered by your own control, accepted by the business owner, or a refusal.

What is third-party vendor risk management?

Third-party vendor risk management checks that outside companies that hold your data, connect to your systems or run a service for you are secure and compliant enough for that work. It covers the check before signing, security and data terms in the contract, monitoring, and removing access at the end.

A common case: the marketing team signs up for an online email tool and uploads the customer list. Nobody in procurement saw a purchase order, because the first months were free. The tool now holds personal data on every customer. Third-party vendor risk management is what asks, before the upload, where that data is stored, who at the vendor can see it, what happens if the vendor is hacked, and how the data is deleted when the team stops using the tool.

Three neighbouring pages cover the rest of the subject. Vendor risk management covers every type of vendor risk, financial, delivery, fraud and compliance, with tiers and due diligence. Third-party vendor management covers the inventory of all outside parties, their owners, their subcontractors and the exit. Supplier risk management covers continuity of supply. This page stays on security, data and the rules that ask for them, the part usually run with the information security and compliance teams.

Why do third parties matter for security?

Because attackers use them. Verizon’s Data Breach Investigations Report found that the share of breaches involving a third party doubled to 30% in its 2025 edition, which analysed 12,195 confirmed breaches. The 2026 edition, based on 2025 data, puts it at 48% of all breaches. A vendor’s stolen password, an unpatched product you bought or a hosting provider’s weak setting can open your data to someone you never dealt with.

The responsibility stays with you. The US interagency guidance on third-party relationships says that using a third party does not reduce a bank’s responsibility to operate safely and comply with the law. Under the GDPR, an organisation may use only processors that give sufficient guarantees of appropriate security measures. DORA says the same for EU financial entities and their technology providers.

Security frameworks now treat this as a core part of security, not an extra. The NIST Cybersecurity Framework 2.0, published on 26 February 2024, has a category of its own for it, cybersecurity supply chain risk management (GV.SC), under the Govern function.

What are the steps of third-party vendor risk management?

The steps follow the life of the relationship. The NIST framework’s outcomes under GV.SC give a useful checklist; the steps below put them in the order a buyer meets them.

  1. Know your vendors and rank them by criticality. NIST GV.SC-04: suppliers are known and prioritised by criticality. In practice, a list of vendors with the data and systems each one touches; third-party vendor management explains how to build it.
  2. Assess before signing. GV.SC-06: planning and due diligence are performed to reduce risks before entering into formal supplier or other third-party relationships. The depth depends on what the vendor will touch.
  3. Write the requirements into the contract. GV.SC-05: requirements to address cybersecurity risks are integrated into contracts and other agreements with suppliers and other relevant third parties.
  4. Monitor during the relationship. GV.SC-07: the risks posed by a supplier, its products and services are understood, recorded, prioritised, assessed, responded to and monitored over the course of the relationship.
  5. Include vendors in incident plans. GV.SC-08: relevant suppliers are included in incident planning, response and recovery. You need to know whom to call at the vendor at 2 a.m., and they need to know whom to call at yours.
  6. Close the relationship safely. GV.SC-10: plans include activities after a partnership or service agreement ends, for example removing access and getting data returned or deleted.

The US banking guidance describes the same life cycle in five stages: planning, due diligence and third-party selection, contract negotiation, ongoing monitoring and termination. Both say the effort at each step depends on the risk.

How deep should the assessment of each vendor go?

Set the depth by what the vendor will touch. The US guidance states that not all third-party relationships present the same level of risk, and that due diligence should match the level of risk and complexity. For security, five questions do most of the sorting: will the vendor hold our data, which kind, will it connect to our network, will it have administrator access, and would its failure stop a critical service?

Example of assessment depth by what the vendor touches (to adapt in your own policy)
What the vendor touchesExampleAssessment depth
No data, no accessOffice furniture, cateringNo security assessment; identity and sanctions screening only
Business data, not personalA translation agency receiving product manualsShort questionnaire, confidentiality terms
Personal or sensitive dataAn online HR or email marketing toolFull questionnaire, certificate or audit report, data processing agreement, list of sub-processors
Connection to your network or administrator accessAn IT support provider with remote accessFull assessment, access controls reviewed, named accounts, logging, right to audit
Critical serviceA payment processor, a core cloud platformFull assessment, continuity and exit plan, incident contacts tested, yearly review

A low-risk vendor that receives a 300-question form is a cost with no benefit; a critical vendor that receives a one-page form is a risk you did not see.

The full tiering method, with the other risk types and review cycles, is in the vendor risk management guide. For security, the rule of thumb is that data and access set the tier, not the price: a free tool can hold your most sensitive data.

What evidence shows that a vendor is secure?

A questionnaire gives the vendor’s answers; evidence shows whether they hold. Ask for both, and read the evidence with three questions in mind: does it cover the service you are buying, is it recent, and what did it find?

Common security evidence from vendors: what it shows and what to check
EvidenceWhat it showsWhat to check
Security questionnaireThe vendor’s own description of its controlsAnswers that are vague or all “yes”; ask for proof of the important ones. For cloud services, the Cloud Security Alliance’s CAIQ is a common standard set of yes/no questions
ISO/IEC 27001 certificateA certification body found that the vendor’s information security management system meets the standardThe scope on the certificate: does it cover the service and sites you use? The expiry date and the certification body
SOC 2 reportAn examination by a certified public accountant of controls relevant to security, availability, processing integrity, confidentiality or privacyThe date or period covered, the exceptions found, and whether the report covers the service you buy
Data processing agreement and sub-processor listHow the vendor processes personal data for you, and which other companies help itThe GDPR Article 28 terms, where the data is stored, and how you are told of new sub-processors
Penetration test summaryThe result of an attempt to break into the product or serviceThe date, who ran it, and whether serious findings were fixed
Outside security ratingsWhat can be seen of the vendor from the internet, such as exposed servicesTreat as a signal to ask questions, not as an assessment

The most common mistake is to accept a certificate or report that covers another part of the vendor’s business.

ISO/IEC 27001 itself includes controls on information security in supplier relationships (Annex A 5.19 to 5.22), so a certified vendor should be able to show how it checks its own suppliers. Ask for that answer for critical vendors.

What happens when the assessment finds gaps?

Each gap ends in one of five decisions, recorded with a name and a date: the vendor fixes it before go-live; the vendor fixes it by a deadline; you add a control on your side that covers it; the business owner accepts the risk in writing; or you do not sign. Security assesses, but the business owner who wants the vendor decides whether a remaining risk is acceptable.

Worked example (fictional): findings from the assessment of an online HR tool and the decision on each
FindingWhy it mattersDecisionOwner and date
No multi-factor login for customer administratorsA stolen password opens every employee recordTurn on single sign-on with your own multi-factor login before go-live (your control)IT, before go-live
ISO/IEC 27001 certificate covers the parent company’s data centre, not the HR productThe evidence does not cover what you buyVendor sends its SOC 2 report for the HR product; review before signingSecurity, before signature
Two sub-processors outside the EU, not listed in the draft agreementPersonal data leaves the EU without terms you agreedList them in the agreement with transfer safeguards and a notice duty for changesLegal, before signature
Backups are tested only once a yearRestoring data after an attack may failAccepted by the HR director for year one; vendor commits to tests every quarterHR director, review in 12 months

Without a decision and an owner, findings stay in a report that nobody reads, and the vendor goes live with the same gaps.

Which contract terms matter for security and data?

The contract turns the assessment into duties. The general clauses that control vendor risk, audit, service levels, subcontracting and exit, are described in the vendor risk management guide. For security and data, these terms do most of the work:

  • Breach notice. Under the GDPR, a processor must notify the controller “without undue delay” after becoming aware of a personal data breach (Article 33(2)). Many contracts set a number of hours so that you can meet your own duty to inform the supervisory authority.
  • Data processing terms. GDPR Article 28 lists what the contract must say: processing only on your documented instructions, confidentiality, security, no new sub-processor without your authorisation, help with your duties, deletion or return of data at the end, and audits.
  • Flow-down to subcontractors. The same duties apply to the vendor’s own suppliers. In US health care, the HIPAA Security Rule requires a business associate contract in which the vendor agrees to comply with the rule, to make its subcontractors that handle electronic protected health information agree to the same, and to report security incidents.
  • Security requirements and right to assess. The controls the vendor must keep, the evidence it must send each year, and your right to assess or audit when something changes.
  • Access and data at the end. Removal of all accounts and keys, and return or deletion of data, with written confirmation.

How do you monitor vendors after onboarding?

Monitoring has three parts. Scheduled reviews, set by the tier: a critical vendor sends new evidence every year (a new audit report, a renewed certificate) and you check that its scope still matches. Events: a breach at the vendor, a new sub-processor, a change of owner, or new access requested by your own team trigger a new assessment. Outside signals: news of an attack or a weakness in a product you use.

Keep the vendor in your own incident plan. When a vendor is breached, the first hours are lost finding the contract, the contact and the list of data it holds. Record all three in the vendor record before you need them. Your vendors’ own subcontractors, often called fourth parties, are covered in third-party vendor management.

Offboarding is where many gaps appear. A project ends, the invoices stop, but the vendor’s accounts still work and its copy of your data still exists. Close each relationship with a short checklist: accounts and keys removed, data returned or deleted with written confirmation, and the vendor record closed.

Which rules ask for third-party vendor risk management?

Several rules ask for this work, each for a different group of organisations. The table lists the main ones and what each asks about vendors.

Rules and frameworks that ask for third-party vendor risk management (checked November 2026)
Rule or frameworkWho it applies toWhat it asks about vendors
US interagency guidance on third-party relationships (2023)US banks supervised by the Federal Reserve, the FDIC and the OCCRisk management across the life cycle, due diligence matched to risk, more oversight for critical activities
DORA, Regulation (EU) 2022/2554EU financial entities, from 17 January 2025A register of all ICT third-party arrangements, those supporting critical or important functions marked, reported to supervisors
NIS2, Directive (EU) 2022/2555Essential and important entities in the EU, from 18 October 2024Supply chain security in cybersecurity measures, taking into account each direct supplier’s weaknesses and practices
GDPR Articles 28 and 33Any organisation that uses a processor for personal data of people in the EUProcessors with sufficient guarantees, a processing contract, and breach notice from the processor
HIPAA Security Rule, 45 CFR 164.314US health care covered entities and their business associatesBusiness associate contracts, flow-down to subcontractors, reporting of security incidents
NIST Cybersecurity Framework 2.0Voluntary, any organisationThe GV.SC outcomes: vendors known and ranked, due diligence, contract requirements, monitoring, incident planning, end of relationship
ISO/IEC 27001:2022Organisations certified, or seeking certificationControls on information security in supplier relationships and their monitoring (Annex A 5.19 to 5.22)

Even where no rule applies, customers and auditors increasingly ask the same questions; a vendor risk process answers them once.

Which tools support third-party vendor risk management?

A small organisation can run the vendor list, the questionnaires, the evidence and the decisions in a shared register with a calendar of expiry dates. As the number of vendors grows, dedicated software sends questionnaires, stores evidence and expiry dates, tracks findings to closure and receives outside signals.

Before choosing a tool, test it on three real cases: a new vendor that will hold personal data, a vendor that reports a breach, and an expired certificate. How to compare tools, and the difference with supplier risk platforms, is explained in vendor risk management software.

Questions

Is third-party risk management the same as vendor risk management?

They overlap. Third-party risk management covers every outside party, including partners, agents and affiliates, and is often led by security or compliance teams. Vendor risk management covers suppliers, and is often led by procurement. The general method for vendors is explained in the vendor risk management guide.

What is a third-party risk assessment?

It is the review of one vendor before signing, or at a set review, against the risks of what it will do for you. For security, it usually combines a questionnaire, evidence such as a certificate or audit report, a review of the data processing terms, and a list of findings with a decision on each.

Is an ISO/IEC 27001 certificate or a SOC 2 report enough?

It is strong evidence, but only for what it covers. Check that the certificate’s scope or the report’s description includes the service and sites you use, that it is recent, and, for a SOC 2 report, which exceptions the auditor found. Then ask the questions the evidence does not answer, such as where your data is stored.

Who should run third-party vendor risk management, procurement or security?

Both, with clear roles. Procurement or the vendor owner runs the intake and makes sure no vendor starts without it. Information security assesses technical risk, privacy or legal reviews data terms, and the business owner accepts or rejects the remaining risk. A vendor that bypasses procurement, such as a free online tool, still needs the same check.

Do small vendors need a full security assessment?

Only if they touch something that matters. A small vendor with administrator access to your systems, or holding personal data, can be riskier than a large one with none. Set the depth by data and access, not by the size of the vendor or the contract.

New guides on the supplier management line

One short email when a guide on this line is added or revised. Nothing else.

Coming soon: sign-up opens with the first email.

Seb Troz

Source-to-pay consultant · written and maintained this guide

Seb Troz is a source-to-pay consultant who implements Ivalua for buying organisations. He writes the guides on eProcurement Toolkit from that hands-on work.

Disclosure: the author works as an Ivalua consultant. Pages that compare software say so next to the comparison.