Skip to main content

New: the AI Shortlist. Describe your company and get matched products with the review evidence behind each one. Try it free

Procurement VMSProcurement software, honestly rated.

HomeVendor managementVendor risk management

Risk

Vendor risk management: the complete guide

Every supplier you add is a door into your business. Vendor risk management is how you decide which doors to open, how wide, and how often to check them.

By Procurement VMS Editorial TeamReviewed by Michael, Procurement Advisor ExpertUpdated 7 minute read

On this page
  1. What vendor risk management is
  2. The risks that suppliers bring
  3. Step 1: Know who your vendors are
  4. Step 2: Tier your vendors
  5. Step 3: Assess before you sign
  6. Step 4: Put protections in the contract
  7. Step 5: Monitor continuously
  8. Step 6: Respond and exit
  9. Who owns vendor risk
  10. Responding when something goes wrong
  11. Common mistakes
  12. When tools help
  13. Questions to ask a critical vendor
  14. Jargon, decoded
  15. What to do this month
  16. Frequently asked questions

Key takeaways

  • Vendor risk management identifies, assesses and monitors the risks that third parties bring to your organization.
  • Main risk types are financial, operational, security, compliance, reputational and concentration risk.
  • Tier vendors by impact so the deepest checks go to the few suppliers that could really hurt you.
  • Risk is not a one-time check. Monitor continuously and reassess when something changes.
  • You can start with a short questionnaire and a tiering list. Tools help once the vendor count grows.

Your company can have flawless internal controls and still be hurt badly by a supplier it barely thinks about. A payroll provider has a breach. A key component maker loses its factory to a fire. A marketing agency posts something that makes the news and your logo is next to it.

In each case the problem began outside your walls and landed inside them. Vendor risk management exists to see those problems coming.

What vendor risk management is

Vendor risk management, also called third-party risk management, is the process of identifying, assessing, controlling and monitoring the risks that arise from using outside suppliers. It runs before you sign, while the relationship lasts and as it ends.

Quick definition

Vendor risk management is the structured practice of evaluating what could go wrong with each supplier, how badly, and what you will do to prevent or recover from it.

The risks that suppliers bring

Risk typeWhat it meansExample
FinancialThe supplier cannot pay its bills or stay in businessA small supplier goes insolvent mid-project
OperationalThe supplier cannot deliver as promisedA single factory outage halts your supply
Information securityThe supplier exposes your data or systemsA breach at a cloud provider leaks customer records
Compliance and legalThe supplier breaks a law or regulation that applies to youUse of sanctioned parties or forced labor in the chain
ReputationalThe supplier's conduct damages your brandPublic scandal at a visible partner
ConcentrationYou depend too heavily on one supplier or regionMost of a critical input comes from one place
Fourth partyYour supplier relies on another supplier that failsYour software vendor's hosting provider goes down

Step 1: Know who your vendors are

You cannot manage risk for suppliers you cannot list. Build a single inventory of every vendor with annual spend, internal owner, what they provide and what data or systems they touch. Expect surprises: departments buy things without telling anyone.

Step 2: Tier your vendors

Not every vendor needs the same scrutiny. Sort them by the damage they could cause.

TierCriteriaDepth of review
CriticalFailure stops revenue, exposes sensitive data or breaks complianceFull due diligence, security review, financial check, annual reassessment, exit plan
HighHard to replace or handles internal dataQuestionnaire, evidence review, reassessment every year or two
MediumReplaceable with limited impactShort questionnaire and document check at onboarding
LowMinimal spend, no data, easy to switchBasic onboarding only

A useful tiering question is: what happens to us if this vendor disappears for a week?

Step 3: Assess before you sign

For higher tiers, collect evidence, not just answers. A questionnaire tells you what a vendor says. Documents show what they have.

  • Financial health. Recent accounts, credit reports or funding status.
  • Security evidence. Independent audit reports, penetration test summaries and policies. Ask what they cover and when they were issued.
  • Compliance. Licenses, certifications, sanctions screening and data protection commitments.
  • Insurance. Certificates showing cover for liability, cyber and professional indemnity where relevant.
  • Business continuity. How they handle outages and how quickly they recover.
  • References. Call two customers of similar size to you.

Our vendor due diligence checklist lists the checks in order, and the vendor risk assessment template gives you a scoring sheet to start from.

Step 4: Put protections in the contract

  • Security and data protection requirements, with the right to audit.
  • Breach notification within a set number of hours.
  • Service levels with remedies if they are missed.
  • Subcontractor approval or notice.
  • Business continuity obligations.
  • Termination rights, data return and deletion.
  • Insurance requirements.

See what is contract management for keeping track of these obligations once they are signed.

Step 5: Monitor continuously

A clean assessment on day one says little about year three. Monitor for change.

  • Refresh evidence on a schedule that matches the tier.
  • Watch for news about financial trouble, breaches, ownership changes and regulatory action.
  • Track performance and incident data from your own teams.
  • Re-assess whenever the scope of work changes, especially if data access grows.

Get the next guide in your inbox

We publish plain-language guides for people who buy and run procurement software. Leave your email and we send you new ones as they go live.

One click to leave any time. See our privacy policy.

Step 6: Respond and exit

Write down what happens if a critical vendor fails. Who is called, what is switched on, how long you can operate without them. Exit plans need testing, at least on paper, for your top vendors. When a relationship ends, revoke access, retrieve data, confirm deletion and close the record. See vendor offboarding workflow.

Illustration: tiering and response in practice

A company reviews 240 vendors. It places 12 in the critical tier, including its payment processor, cloud host and a sole-source component maker. Each of the 12 gets a named owner, an annual assessment and a written exit plan. The remaining 228 get lighter checks. When the cloud host announces a security incident, the owner opens the exit plan, checks what data is held, contacts the vendor under the breach notice clause and informs the security team within the same day. These details are invented to show how tiering shapes the response.

Who owns vendor risk

Risk is shared. Procurement runs the process and keeps the inventory. Information security reviews technical controls. Legal reviews contract terms. Finance checks financial health. The business owner for each vendor owns the day to day relationship and raises concerns. Someone must coordinate, or each group assumes another is watching.

Responding when something goes wrong

Even good programs face incidents. The difference is how fast you can act.

  1. Confirm what happened. Ask the vendor for facts: what, when, which of your data or services are affected.
  2. Contain. Cut access, rotate credentials, switch to a backup process if one exists.
  3. Notify. Inform your security team, legal and leadership. Check whether you have regulatory or customer notification duties and the deadlines that come with them.
  4. Record. Keep a dated log of actions and communications.
  5. Recover. Restore service and verify.
  6. Review. Ask what the contract allows: remedies, audits, termination. Update the vendor's risk rating.
  7. Learn. Change the onboarding or monitoring step that would have caught it.

A one-page response plan for each critical vendor, written before an incident, saves hours when it counts.

Common mistakes

  1. One questionnaire for everyone. Low risk vendors get overwhelmed and critical vendors get under-checked.
  2. Accepting answers without evidence. Self-reported compliance is not proof.
  3. Checking once. Risk changes with the vendor and the work.
  4. Ignoring fourth parties. Ask your critical vendors who they depend on.
  5. No exit plan. Leaving a vendor in a hurry is far harder than planning ahead.

When tools help

A spreadsheet handles a few dozen vendors. Beyond that, you want reminders, evidence storage, scoring and workflow in one place. See the third-party risk management software page and supplier risk management software page.

A minimum viable vendor risk program
  • One list of all vendors with owners.
  • Tiers defined, with the critical tier named.
  • A standard onboarding questionnaire per tier.
  • Evidence collected and stored for critical vendors.
  • Security and breach clauses in contracts.
  • A yearly reassessment for critical and high tiers.
  • An exit plan for every critical vendor.

Questions to ask a critical vendor

  1. What data of ours will you hold or access, where is it stored and who can see it?
  2. When was your last independent security assessment, and can we see the summary?
  3. What happens to our service if your main site or cloud region fails, and how fast do you recover?
  4. Which third parties do you rely on for the service you provide to us?
  5. How soon will you tell us about a security incident that affects us?
  6. Do you carry cyber and professional liability insurance, and at what limits?
  7. Have you had any regulatory action or major legal dispute in the last three years?
  8. What would the exit look like: how do we get our data back and in what format?

Jargon, decoded

  • Inherent risk. The risk a vendor carries before controls are considered.
  • Residual risk. The risk left after controls and protections.
  • Attestation. A signed statement or independent report about a vendor's controls.
  • SOC 2 report. An independent audit report on a service provider's controls over security and related areas.
  • Concentration risk. Over-reliance on a single vendor or location.
  • Fourth party. A supplier of your supplier.

What to do this month

List your vendors with access to customer or employee data. That list is your starting tier. Send those vendors the eight questions above and read what comes back. The answers, and the vendors who do not answer, will tell you where to look first.

Frequently asked questions

What is vendor risk management?

It is the process of identifying, assessing, controlling and monitoring the risks that outside suppliers bring to an organization, from before signing until the relationship ends.

What is the difference between vendor risk management and third-party risk management?

They mean nearly the same. Third-party risk management is the broader name and may include partners, resellers and contractors as well as suppliers.

How do you assess vendor risk?

Tier vendors by impact, then collect evidence proportional to the tier: financial data, security reports, compliance documents, insurance and references.

How often should vendors be reassessed?

Critical vendors yearly, high tier every year or two, and others at renewal. Reassess immediately after a security incident or a change in scope.

What is a fourth party?

A fourth party is a supplier that your supplier depends on, such as the hosting provider behind a software vendor. Its failure can still reach you.

Where to read next

Ready to look at software?

Tell us your company size and region. We use AI to match you to products, and a person checks the list before it reaches you, with the reason behind each pick.

Disclosure: Zapro AI appears on some comparison pages as an editor's pick, and the people behind this site have a professional connection to Zapro AI.

We reply by email, usually within one business day. No spam, and no vendor calls unless you ask. See our privacy policy.

Written by

Procurement VMS Editorial Team

Our editors research each guide from vendor documentation, public pricing pages and buyer feedback, and name the sources on the page. Learn who the team is.

Reviewed by

Michael, Procurement Advisor Expert

Michael checks our guides for practical accuracy against how procurement teams buy and run software. Read his profile.

Editorial guide

How we write and check pages

Read our editorial policy, how we handle corrections and what we do when a source changes.

Explore this topic with AI

Open this page in your assistant of choice, get the key takeaways and carry on the conversation.