A consistent vendor risk assessment helps you decide which suppliers need deeper review, record why a vendor was approved, and show how open risks are being managed. This reusable checklist covers intake, tiering, evidence review, scoring, contract checks, remediation, and reassessment.
Overview
Third-party risk is easier to manage when every supplier follows the same basic workflow. The objective is not to give every vendor an identical questionnaire. It is to match the depth of review to the harm that could result from a failure, breach, outage, or contract dispute.
Start by creating a central vendor record. At minimum, capture the vendor name, service owner, business purpose, products used, data involved, systems or environments accessed, regions involved, contract status, renewal date, and internal risk owner. Record whether the vendor is a processor, subprocessor, service provider, or another type of supplier under the relationships relevant to your organization.
A practical assessment has five stages:
- Intake: identify the service, business need, and requested access.
- Tiering: classify the vendor according to data sensitivity, access, criticality, and operational dependency.
- Due diligence: request evidence and evaluate security, privacy, resilience, and contractual controls.
- Decision and remediation: approve, conditionally approve, reject, or defer the relationship while assigning actions and owners.
- Monitoring: track expiring evidence, incidents, changes, renewals, and reassessment dates.
Your vendor risk assessment template should preserve both the answers and the evidence behind them. A completed questionnaire without supporting documents may identify topics to discuss, but it does not necessarily demonstrate that a control is designed or operating effectively.
For broader control coverage, pair this process with a cybersecurity compliance checklist. If the supplier processes personal data, also connect the assessment to your DPA lifecycle and annual vendor review workflow.
Checklist by scenario
1. New vendor intake
Complete this short intake before sending a full supplier security questionnaire:
- What business process depends on the vendor?
- What data will the vendor collect, access, store, transmit, or generate?
- Does the service handle personal, confidential, regulated, payment, credential, or production data?
- Will the vendor connect to identity systems, endpoints, cloud environments, code repositories, or internal networks?
- Is the service business-critical, difficult to replace, or likely to affect customers if unavailable?
- Which internal team owns the relationship, and who can approve the risk?
- What contract, DPA, security addendum, or subprocessors list is required?
Do not allow a purchase request to bypass security or privacy review simply because the vendor is inexpensive, familiar, or already used by another team. The intake should create a traceable decision, even when the result is a low-risk classification.
2. Low-risk supplier
A low-risk vendor might have no access to sensitive data or internal systems and may support a noncritical business activity. The review can be proportionate, but it should still confirm:
- the service description and access scope;
- the vendor's contact for security or privacy matters;
- basic confidentiality and breach-notification terms;
- data retention and deletion expectations;
- account security and access management practices;
- contract owner, renewal date, and reassessment date.
Use a lightweight review only when the documented facts support the classification. A low invoice does not automatically mean low risk.
3. Medium-risk SaaS or service provider
For a vendor that handles business information, integrates with internal systems, or supports an important workflow, request evidence such as:
- a completed supplier security questionnaire;
- a current SOC 2 report or comparable independent assurance report, where available;
- an information security policy summary;
- penetration-test or vulnerability-management information, with sensitive technical details shared through an appropriate channel;
- access control, encryption, backup, and disaster-recovery descriptions;
- incident response and breach-notification procedures;
- subprocessor information and data-location details;
- cyber insurance or other insurance certificates where required by your risk policy.
Review the coverage period, report scope, exceptions, complementary user entity controls, and any limitations. A report's existence is not the same as evidence that every control you need is covered.
4. High-risk or business-critical vendor
Escalate the review when a supplier processes sensitive personal data, has privileged or production access, supports a critical process, or could create material operational or compliance exposure. Add:
- an architecture or data-flow review;
- clear requirements for privileged access, logging, authentication, and support access;
- recovery objectives, resilience testing, and continuity arrangements;
- an incident escalation path with named contacts;
- subprocessor approval or notification terms appropriate to your process;
- termination assistance, data return, deletion, and transition requirements;
- contractual audit, assurance, and remediation rights proportionate to the relationship;
- senior risk acceptance for unresolved high-impact findings.
Where personal data is involved, compare the proposed terms against your data protection requirements rather than treating a generic NDA as sufficient. A DPA versus NDA contract review can help separate confidentiality obligations from processor responsibilities.
5. Renewal, change, or incident review
Reassess a vendor when its contract is renewed, the service changes, a new data type or integration is introduced, ownership changes, a security report expires, or the vendor reports an incident. Confirm:
- whether the original risk tier is still accurate;
- whether data flows, subprocessors, hosting regions, or access permissions changed;
- whether new findings or control exceptions appeared;
- whether remediation items are closed with evidence;
- whether the contract and DPA still match actual processing;
- whether the vendor remains necessary and proportionate to the business need.
What to double-check
Use a transparent scoring rubric
Vendor risk scoring should support judgment, not replace it. One workable model scores four dimensions from 1 to 5:
- Data sensitivity: from public or non-sensitive information to highly confidential or regulated data.
- Access level: from no system access to privileged, production, or identity-system access.
- Business criticality: from easily replaceable service to a dependency whose outage would materially disrupt operations.
- Control confidence: from strong, current evidence to limited, outdated, or unverified evidence.
Document the weighting, if any, and define the resulting bands before reviewing vendors. For example, a low, medium, or high result can determine questionnaire depth, approval authority, evidence frequency, and reassessment timing. Add an override rule: a vendor with privileged production access or highly sensitive data should not receive a low classification merely because another dimension scores well.
Check evidence quality, not just evidence volume
For each document, record its title, issuer, coverage period, scope, review date, owner, and relevant exceptions. Double-check whether a penetration test is recent enough for your policy, whether an insurance certificate is still valid, and whether an assurance report covers the service and environment you are buying. If evidence is unavailable, record the gap and the compensating control or risk acceptance decision rather than marking the item complete.
Maintain useful risk-register fields
Your risk register should link each finding to a specific vendor and decision. Recommended fields include vendor name, finding ID, risk statement, affected asset or data, likelihood, impact, inherent risk, existing controls, residual risk, remediation action, owner, due date, status, evidence link, acceptance authority, and next review date. A finding such as “security issue exists” is too vague. A stronger statement identifies the condition, consequence, and affected service.
Separate contractual gaps from control gaps
A vendor may have a reasonable security practice that is not reflected in the contract, or a contract may require a control that the vendor cannot demonstrate. Track these separately. Contract gaps belong with procurement or legal review; control gaps require technical or operational remediation. Both can affect the final risk decision.
Common mistakes
- Using one questionnaire for every vendor: this creates unnecessary work for low-risk suppliers and can obscure the issues that matter for critical providers.
- Scoring without definitions: reviewers produce inconsistent results when terms such as high impact or sensitive data are not explained.
- Accepting self-attestation as complete evidence: an answer can be useful, but it should be distinguished from an independent report, test result, policy, or contract commitment.
- Ignoring fourth parties: ask how the vendor manages subprocessors and other dependencies that affect your service or data.
- Approving with no expiry: vendor risk changes. Every approval should have an owner and a review trigger.
- Leaving remediation open indefinitely: record interim safeguards, escalation dates, and the authority that accepted the residual risk.
- Failing to involve the service owner: security teams can assess controls, but the business owner must confirm necessity, criticality, and operational alternatives.
- Keeping evidence in disconnected locations: link the questionnaire, contract, reports, findings, approval, and reassessment record from one vendor profile.
When to revisit
Review this vendor risk assessment template before seasonal planning cycles and whenever your workflows or tools change. At a minimum, establish a calendar for reviewing high-risk vendors, expiring assurance reports, open remediation items, upcoming renewals, and vendors with privileged access. The exact interval should follow your documented risk policy and the nature of the relationship.
Refresh your evidence-request list whenever your organization changes its security baseline, privacy obligations, architecture, or procurement process. Reconsider the scoring guidance after a major incident, a material change to a framework or regulatory requirement, or the introduction of a new data category. Evidence such as SOC 2 reports, penetration tests, insurance certificates, and breach-notification terms should be checked again as they expire or when the vendor's service changes; a practical review cadence is every 6–12 months where appropriate.
To put this into practice, choose one vendor scheduled for renewal and run the workflow end to end: confirm its tier, request missing evidence, update the risk register, assign remediation owners, review contract terms, and record an approval or escalation decision. Then use that result to refine the template before applying it to the rest of your supplier inventory. For related control-testing routines, see the SaaS compliance control testing calendar.