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 worksRelated terms
- Third-party risk management (TPRM)Third-party risk management (TPRM) is the discipline of identifying, assessing, monitoring and controlling the risks an organisation takes on through any outside party it relies on, including vendors, partners, outsourcers and their own suppliers.
- Vendor due diligenceVendor due diligence is the assessment an organisation carries out before contracting with a vendor, and again at renewal, to confirm the vendor can deliver the service safely and meet the legal, security, financial and operational requirements that apply.
- Vendor tieringVendor tiering is the practice of sorting vendors into risk tiers, based on factors such as the data they handle, the functions they support and how hard they are to replace, so that review depth, evidence and monitoring match the risk.
- Remediation planA remediation plan is an agreed set of actions, owners and deadlines for closing the gaps found in a vendor assessment, such as missing controls, contract terms or evidence, tracked until each item is closed or formally accepted.
- Evidence-based assessmentAn evidence-based assessment is a vendor review in which every conclusion is tied to a specific source, such as a clause, page or test result in the vendor's documents, rather than to unverified questionnaire answers or reviewer judgement alone.
Sources
- 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
- 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.