Vendor 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.
What Vendor due diligence means
Due diligence gathers and reviews evidence: security reports and certifications, policies, contracts, financial statements, continuity plans and, where relevant, references and adverse media. The depth follows the vendor's tier. For a critical vendor it can also include ownership checks, sanctions screening and a review of past incidents.
Several rules require it. GDPR Article 28(1) allows only processors that provide sufficient guarantees. DORA Article 28(4) requires financial entities to assess providers before entering ICT contracts, including concentration risk and conflicts of interest. The US Interagency Guidance lists due diligence factors from strategy and financial condition to information security and subcontractors. NIST CSF 2.0 covers it in GV.SC-06.
Good due diligence ends in a decision with reasons. A pile of collected documents with no recorded conclusion is evidence that the review did not finish. Record the decision, the conditions attached to it and the date of the next review, so that renewal does not start from scratch.
What to check in vendor documents
- The documents requested for the tier are present and in date.
- The scope of each report or certificate matches the service.
- Financial statements or other evidence of viability for critical vendors.
- Contract terms required by your policies and regulations.
- Findings recorded with a source and a decision.
In ProcureCortex
ProcureCortex reads the documents a vendor sends, checks them against the frameworks and policies selected for its tier, and records each finding with its rule, excerpt and page.
How an assessment worksRelated terms
- 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.
- Vendor questionnaireA vendor questionnaire is a structured set of questions sent to a vendor about its security, privacy, resilience and compliance practices, used to gather information for a risk assessment, often alongside or instead of documents.
- 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.
- 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.
- Digital Operational Resilience Act (DORA)The Digital Operational Resilience Act (DORA) is the EU regulation, applying since 17 January 2025, that sets ICT risk management, incident reporting, resilience testing and ICT third-party risk rules for financial entities, including mandatory contract terms for ICT service providers.
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
- Regulation (EU) 2022/2554 (DORA)eur-lex.europa.eu/eli/reg/2022/2554/oj
- Regulation (EU) 2016/679 (GDPR)eur-lex.europa.eu/eli/reg/2016/679/oj
Summarised for practitioners, not legal advice. Check the source text for your own obligations.