Platform OverviewOne evidence trail, from intake to Jira.See how it fits together
See it on your documentsA 30-minute call. Bring a vendor you are reviewing now.Book a demo
Third-party risk conceptsPublished Updated

Vendor risk management (VRM)

Also called: Supplier risk management

Definition

Vendor risk management (VRM) is the part of third-party risk management that covers suppliers an organisation buys goods or services from: assessing them before contract, setting terms, monitoring them and managing exit.

What VRM means

VRM usually starts in procurement. A new purchase triggers intake, the answers decide the review depth, and the vendor sends evidence such as security reports, certifications, policies and contracts. Reviewers turn that evidence into findings and a decision. The decision, and the reasons for it, are then recorded.

The term is narrower than third-party risk management. A distributor or joint venture partner is a third party but not a vendor. Many organisations use the two terms interchangeably, but owners and triggers differ, so it helps to define which one your programme covers.

The hardest part for most teams is the reading. A single vendor can send a long SOC 2 report, a DPA, an MSA and a continuity plan. Consistency depends on written requirements by tier, so that two reviewers reach the same conclusion from the same documents.

What to check in vendor documents

  • The evidence requested for the vendor's tier was received and is current.
  • Each requirement for the tier has a documented result with a source.
  • Contract terms match the risks identified in review.
  • Open findings have an owner and a due date.
  • The vendor's next review date or trigger is set.

In ProcureCortex

Intake questions set the vendor's tier and the documents to request, and findings from those documents can go to Jira as tasks with the evidence attached.

How an assessment works

Related terms

Sources

  1. Interagency Guidance on Third-Party Relationships: Risk Management, 88 FR 37920 (June 2023)www.govinfo.gov/content/pkg/FR-2023-06-09/html/2023-12340.htm
  2. NIST CSWP 29, The NIST Cybersecurity Framework (CSF) 2.0doi.org/10.6028/NIST.CSWP.29

Summarised for practitioners, not legal advice. Check the source text for your own obligations.

VRM: questions

Short, direct answers.

It varies. Procurement often runs the process, with security, privacy, legal and the business owner each reviewing their part. Name one accountable owner per vendor.

See it on your own vendor documents.

Open a demo workspace with a sample vendor, its documents and its findings. Or bring your own vendor to a 30-minute call.

Procurement, compliance, security and auditOne workspace, one record of every decision