Timedora

Vendor Assessment and Due Diligence

A practical lesson on assessing vendor relationships, verifying relevant evidence, evaluating security and privacy, and making documented risk decisions.

Set the Scope and Criticality

Set the Scope and Criticality

Before sending a questionnaire, establish what the vendor will do and what could go wrong. Record the service it provides and any dependencies, such as subcontractors or cloud platforms. Identify the information the vendor will collect, access, store, transmit, or delete, and note whether it is personal, confidential, regulated, or otherwise sensitive. Clarify whether the vendor can connect to internal systems, administer accounts, or handle credentials. Finally, consider whether an incident, outage, or data loss could interrupt essential operations or harm customers.

Use these factors to classify the relationship—for example, as low, moderate, or high criticality—and match the review to that classification. A vendor handling public information without system access may warrant a lighter assessment than one processing sensitive personal data or supporting a critical service. Criticality is therefore about the vendor’s actual role and the consequences of failure, not simply the size or familiarity of the supplier.

Verify Evidence, Security, and Privacy

Verify Evidence, Security, and Privacy

A questionnaire is a starting point, not proof that controls work. Request evidence that matches the vendor’s service and the risks identified during scoping. Depending on the relationship, this might include security policies and technical-control descriptions; independent audit or certification reports; vulnerability-management or penetration-test summaries; incident-response, continuity, and disaster-recovery documentation; or data-flow diagrams, hosting locations, subprocessor lists, and privacy, retention, or deletion practices.

Then check whether the evidence actually applies. Review its scope, date, coverage, and exceptions: a report might cover a different service, omit a relevant location, or identify unresolved findings. Confirm that a certificate is current and names the organization providing the service. Where practical, corroborate important claims with more than one source. The right evidence depends on the service and its risks; collecting documents without checking their relevance is not meaningful verification.

Assess security controls in light of the vendor’s actual role rather than applying a generic checklist mechanically. Relevant areas include identity and access management, encryption, secure development and change management, vulnerability remediation, logging, incident response, resilience, and protection of customer data. Also consider product and supply-chain risks, such as dependencies on subcontractors or components whose origin and integrity are unclear.

For privacy, trace what personal data is handled, why it is used, where it goes, how long it is retained, and how it is deleted or returned. Compare this map with the proposed data flows and intended use; stated practices should fit what the vendor will actually do. Legal requirements depend on jurisdiction and relationship. For example, the GDPR requires controllers to use processors that provide sufficient guarantees and sets requirements for processing agreements and appropriate security measures.

Score and Disposition the Risk

Score and Disposition the Risk

Separate inherent risk—risk before considering controls—from residual risk—risk remaining after controls and planned mitigations. One practical approach is to rate likelihood and impact on defined scales and multiply the ratings. In an illustrative method, scores from 1 to 5 are used for each factor, with example score bands of 1–4 (low), 5–9 (moderate), 10–16 (high), and 17–25 (critical). These bands are examples, not universal thresholds; an organization should define them to fit its risk tolerance.

For example, a vendor storing sensitive customer records might receive a likelihood score of 3 and an impact score of 5, giving an inherent risk score of 15 (high). Record the reasoning and evidence behind each rating. If verified controls reduce the likelihood score to 2 while impact remains 5, the residual score is 10 (high). The impact remains high, so the relationship may still call for stronger safeguards or approval by a designated risk owner.

A score helps structure a decision, but cannot replace judgment. Record the assessment scope, evidence reviewed, gaps and exceptions, assumptions, risk owner, required mitigations, and approval or rejection decision. Escalate critical gaps or uncertain evidence; missing information is not proof that a vendor is safe. The decision should make clear whether to proceed, reject, or proceed only under specified conditions.