Security

Vendor Risk Assessment: Process, Criteria, and Report Template

OraSecOctober 16, 20269 min read
Vendor Risk Assessment

A vendor risk assessment decides whether a supplier can be trusted with your data, systems, or a service you can't run without. You check what the vendor will touch, how well they protect it, and whether the remaining risk is acceptable before you sign.

What is a vendor risk assessment?

A review of the security, privacy, compliance, and business risks a supplier brings, ending in a clear approval decision.

What are some examples of vendor risk?

Data leaks at a vendor, stolen supplier credentials, malicious software updates, vendor outages, and breaches at a vendor's subcontractors.

How do you manage vendor risk?

Keep a vendor inventory, tier vendors by risk, assess them before onboarding, limit their access, and reassess on a schedule.

What is the first step in a risk assessment?

Define what you're assessing: the vendor, its service, its internal owner, and the data and systems it will touch.

How do you write a good risk assessment?

Keep it specific: state the scope, back every finding with evidence, rate residual risk, and end with a clear recommendation.

Key Takeaways

  • A vendor with access to your data or network is part of your attack surface.
  • Match assessment depth to each vendor's access and importance.
  • Questionnaires and certificates are claims, so verify them when the risk is high.
  • Rate inherent risk first, then decide on residual risk.
  • An assessment is a snapshot, so monitor vendors between reviews.
  • Some major vendor breaches started with remote access that lacked MFA.

What Is a Vendor Risk Assessment?

A vendor risk assessment is a structured review of a third party before and during your work with them. It asks what the vendor could expose you to, how well they control it, and whether the remaining risk is worth the value they bring. The vendor might be a SaaS platform, a managed service provider, or a contractor with VPN access, so the review covers privacy, compliance, resilience, and fourth parties, not just security. It's one part of third-party risk management and your wider security risk management program.

Why Vendor Risk Assessments Matter

When you hand data or access to a vendor, you keep the responsibility, and GDPR requires you to use only processors that provide sufficient guarantees. The scale of third-party risk is growing: Verizon's 2025 Data Breach Investigations Report found third-party involvement in 30% of breaches, double the year before. Recent incidents show the impact:

  • Change Healthcare (2024): attackers used compromised credentials on a Citrix remote access portal that lacked MFA. About 192.7 million people were affected.
  • Snowflake customer accounts (2024): attackers used infostealer credentials on customer accounts without MFA. Around 165 potentially exposed organizations were notified.
  • SolarWinds (2020): attackers inserted malicious code into Orion updates. SolarWinds said fewer than 18,000 customers may have installed them.
  • CrowdStrike outage (2024): a faulty update crashed an estimated 8.5 million Windows devices, with no attacker involved.

A structured process also supports the supplier-related requirements in ISO 27001, SOC 2, PCI DSS, DORA, and NIS2.

Helpful for you: Why MFA Alone Doesn't Stop Account Takeovers

Vendor Risk Assessment Process

Match the depth of each step to the vendor's risk tier.

1. Identify and Classify the Vendor

Record the vendor, service, business owner, and contract value, then assign a tier. Tier 1 handles sensitive data, privileged access, or a critical service. Tier 2 has limited data or system access, or a service you could replace within weeks. Tier 3 has no data or system access and low business impact. Tier 3 may need only a short questionnaire; Tier 1 needs evidence, interviews, and sometimes testing.

2. Understand Vendor Access and Data Exposure

Map what the vendor will reach: data, systems, network segments, accounts, and how they connect (VPN, remote support tool, API, or integration). Vendor accounts often end up with more access than the service needs. The 2013 Target breach began with network credentials stolen from an HVAC contractor and ended with about 40 million payment cards taken, a reminder that over-privileged vendor accounts can be an attacker's route into internal systems.

3. Collect Security and Compliance Information

Ask for evidence that matches the vendor's tier: a security questionnaire (SIG Lite, CAIQ, or your own); a SOC 2 Type 2 report or ISO 27001 certificate and Statement of Applicability; the latest penetration test summary and proof of fixes; security, privacy, incident response, and continuity policies; a data processing agreement and subprocessor list; and cyber insurance details and breach history. Read SOC 2 reports closely: the scope, the period covered, auditor exceptions, and the complementary user entity controls (CUECs) you must run yourself.

4. Assess Vendor Security Controls

For high-tier vendors, focus on the controls that matter in real vendor breaches: MFA on remote and admin access, privileged access, patching of internet-facing systems, encryption, logging, and incident response. Don't take answers at face value. If a vendor claims MFA everywhere, ask how it's enforced and what exceptions exist. For critical vendors, an API security test of the integration is often worth the effort.

5. Determine Inherent Risk

Inherent risk is the risk before counting the vendor's controls, based on data sensitivity, access, and criticality. A cloud HR platform holding employee bank details carries high inherent risk, however good its security.

6. Evaluate Residual Risk

Residual risk remains after the vendor's controls and your own mitigations, such as limiting network access. Gaps and missing evidence keep it high. Record mitigations separately from fixes, because mitigation and remediation aren't the same.

7. Prioritize Findings and Remediation

Rate each gap and agree on a fix. Put gaps on a realistic attack path, such as an exposed admin portal without MFA, ahead of paperwork issues. Set owners and deadlines, and put critical items in the contract.

8. Approve, Reject, or Accept the Risk

The business owner and security team decide based on residual risk: approve when it's within your risk appetite; approve with conditions when specific gaps must be fixed by a date; accept the risk when a senior owner signs off on a known gap with a review date; or reject when the risk is too high to reduce. Record who decided and why, because acceptances without an owner or end date tend to become permanent.

9. Monitor and Reassess the Vendor

Reassess by tier, for example yearly for Tier 1, every two years for Tier 2, and at renewal for Tier 3. Reassess sooner after a vendor breach or major change, and remove access when a contract ends.

Also Read: Why Dark Web Monitoring Alone Is Not Enough

Vendor Risk Assessment Criteria

Rate every vendor against the same criteria.

Criteria

What to Assess

Higher Risk When

Data sensitivity

Data the vendor stores, processes, or views

Personal, payment, health, or authentication data

System and network access

Accounts, remote access, API tokens, network paths

Privileged or always-on access, shared accounts, no MFA

Security controls

MFA, patching, encryption, logging, testing, incident response

No independent testing, slow patching, weak access control

Privacy controls

Data location, retention, deletion, subprocessors

Unclear data location or no deletion process

Compliance and assurance

ISO 27001, SOC 2, PCI DSS status, and GDPR, DORA, or NIS2 obligations

Missing, outdated, or out-of-scope evidence, or unmet legal obligations

Business criticality

Dependence on the vendor and ease of replacement

Single point of failure with no alternative

Incident history

Past breaches and outages, and the response

Repeated incidents or late notification

Fourth-party dependencies

The vendor's hosting, support, and subcontractors

Unknown subprocessors with access to your data

Business continuity and recovery

Backups, recovery plans and times, testing

Untested plans or recovery times you can't tolerate

Common Examples of Vendor Risk

  • Stolen vendor credentials: attackers log in through a supplier's access, as in the Target breach.
  • Compromised software updates: malicious code ships in a trusted update, as with SolarWinds and other software supply chain attacks.
  • Vulnerable vendor products: one flaw can be exploited across many customers, as with MOVEit Transfer in 2023.
  • Managed service provider compromise: Kaseya said its 2021 VSA attack reached fewer than 1,500 downstream businesses.
  • Data exposure at the vendor: a misconfigured bucket, database, or tenant leaks your data.
  • Service outages: CDK Global's June 2024 ransomware attack disrupted US car dealers for about two weeks.
  • Fourth-party breaches: your vendor's subcontractor is breached, and your data may go with it.
  • Compliance failures: a vendor breaks GDPR or another rule, and you may share the liability.
  • Vendor failure: the supplier shuts down or is acquired, leaving you without the service.

Vendor Risk Assessment Checklist

Before the assessment

  • Vendor, service, and business owner recorded.
  • Risk tier assigned.
  • Data, systems, and access methods mapped.

Evidence

  • Questionnaire completed and reviewed.
  • SOC 2 Type 2 report or ISO 27001 certificate current and in scope.
  • Auditor exceptions and CUECs reviewed.
  • Latest pentest summary and remediation evidence provided.
  • Data processing agreement and subprocessor list in place.
  • Continuity and recovery plans tested in the last 12 months.

Key controls

  • MFA enforced on remote, admin, and customer-facing accounts.
  • Vendor staff access limited, logged, and reviewed.
  • Critical internet-facing vulnerabilities patched within agreed timeframes.
  • Data encrypted in transit and at rest.
  • Incident notification within a set time, such as 24 or 72 hours.

Your side

  • Vendor accounts named, not shared, and least-privilege.
  • Remote access restricted by network, time, or approval where possible.
  • Vendor account activity logged and monitored.
  • Contract covers security requirements, audit rights, and breach notification.

Decision and follow-up

  • Inherent and residual risk recorded.
  • Remediation owners and deadlines set.
  • Decision and any risk acceptance signed off.
  • Reassessment date set.
  • Offboarding steps for access and data deletion agreed.

How to Score Vendor Risk

Score each criterion from 1 (low) to 4 (critical). Consider inherent exposure and verified controls separately when rating residual risk; an unresolved critical control gap should not be hidden by an average.

Risk Rating

What It Looks Like

Typical Action

Reassessment

Low

No sensitive access, easy to replace, no meaningful gaps

Approve with a light review

At renewal or every 2 to 3 years

Medium

Limited access, some gaps with compensating controls

Approve and track minor fixes

Every 2 years

High

Sensitive data, privileged access, or a critical service, with gaps

Approve with conditions, or formal risk acceptance

Yearly, plus monitoring

Critical

Deep access plus serious gaps, such as no MFA or an unresolved breach

Don't onboard, or restrict access until fixed

Before go-live, then every 6 months

Vendor Risk Assessment Report Template

A good report lets a decision-maker grasp the risk quickly and a reviewer check the detail.

  • Executive summary: two or three sentences on the vendor, service, residual risk, and recommendation. For example: Acme Payroll will process bank details for 1,200 employees; residual risk is High because admin access lacks MFA; we recommend approval once MFA is enforced.
  • Vendor profile and scope: vendor, service, owner, tier, data, access methods, evidence reviewed, and what was out of scope.
  • Inherent risk rating: the rating before controls, with a one-line reason per criterion.
  • Key findings: the most important results, each with what was found, the evidence, and why it matters. For example: support staff can export customer records without approval (SOC 2 exception 4.2).
  • Security and compliance gaps: gaps against your requirements and standards, rated by severity, with technical and documentation gaps listed separately.
  • Required remediation: each action, its owner, its deadline, and how completion will be verified.
  • Residual risk: the rating after current controls, and after agreed fixes.
  • Final recommendation: approve, approve with conditions, accept, or reject, with the approver and next review date.

For the findings section, our penetration testing report example shows how to present results that both executives and engineers can act on.

Common Vendor Risk Assessment Mistakes

  • One questionnaire for everyone. Critical vendors get no deeper review than low-risk ones.
  • Trusting certificates unread. They may not cover your service.
  • Assessing only at onboarding. Vendors change over time.
  • Ignoring your own side. Shared or over-privileged vendor accounts can undo a good assessment.
  • Unknown vendors. Teams buy SaaS tools that security never hears about.
  • Permanent exceptions. Acceptances with no owner or review date never close.
  • Forgetting offboarding. Vendor accounts and API keys outlive the contract.

Vendor Risk Assessment Best Practices

  • Keep one vendor inventory. Tier, owner, access, and next review date for every vendor.
  • Tier before you assess. Focus where a vendor could hurt you.
  • Ask for evidence. Request test reports or a configuration walkthrough.
  • Focus on access paths. Remote access, admin accounts, and integrations are common entry points.
  • Require MFA. On every vendor account that touches your data or network.
  • Write security into contracts. Notification times, audit rights, and data deletion on exit.
  • Test critical integrations. Include vendor connections and remote access in your pentests.
  • Monitor between reviews. Act quickly on vendor breaches or leaked credentials.

How OraSec Can Help

A questionnaire tells you what a vendor says about its security. A penetration test shows what's actually exposed. We test vendor integrations, APIs, remote access paths, and supplier accounts in your environment, then show how far an attacker could get through each one. Every finding includes a plain-language explanation and a practical fix, and retesting confirms high-risk issues are closed. Our threat intelligence team also watches for leaked credentials linked to your organization.

Conclusion

Every vendor connected to your data or network extends your attack surface. An assessment keeps it in check: know what each vendor can reach, verify their controls, decide clearly, and keep monitoring. Several incidents above didn't need advanced techniques. They involved a contractor's credentials, a portal without MFA, or a trusted update. Those are the gaps a good assessment is designed to find.

Frequently Asked Questions

What is the difference between vendor risk assessment and third-party risk management?

A vendor risk assessment reviews one supplier at a point in time. Third-party risk management is the ongoing program covering every supplier's full lifecycle.

How often should vendors be reassessed?

Review high-risk vendors at least yearly, medium-risk every two years, and low-risk at renewal, plus after any vendor breach.

What questions should a vendor security questionnaire include?

Cover MFA, access control, data handling, patching, penetration testing, logging, incident notification, continuity, subprocessors, and certifications.

Is a SOC 2 report enough for a vendor risk assessment?

Rarely. Check that it's a recent SOC 2 Type 2 covering your service, then review exceptions, CUECs, and anything out of scope.

Who should be responsible for vendor risk assessments?

Security or risk teams usually run them, but the business owner owns the risk, with procurement, legal, and privacy teams supporting.

Can a penetration test be part of a vendor risk assessment?

Yes. For critical vendors, request recent pentest results or, where the contract allows, test the integration, APIs, and vendor accounts in your environment.

Explore related services

Need hands-on help? Our security testing services put this research into practice.

Binance hack 2026

Binance Hack: What We Know About the $6.3 Billion Hot Wallet Theft

On October 29, 2026, attackers drained Binance hot wallets across multiple blockchains in what blockchain analytics firms call the largest crypto theft on record. Binance puts the impact at about $6.3 billion, with roughly $3 billion frozen, and says early findings point to a possibly compromised engineer's laptop, with no evidence of leaked private keys so far. Here's what happened, what's still unconfirmed, and what to check in your own environment. What happened at Binance? Attackers drain

·6 min read
Oracle E-Business Suite RCE (CVE-2026-101767): What to Do Now

Oracle E-Business Suite RCE (CVE-2026-101767): What to Do Now

CVE-2026-101767 is a critical flaw in Oracle E-Business Suite (EBS), rated CVSS 9.8. It lets an unauthenticated attacker send a crafted web request that triggers SQL injection and can be chained into full remote code execution. Oracle patched it in its October 20, 2026 Critical Patch Update, and attackers were already probing for it a week later. If you run EBS, this one needs attention now. What is CVE-2026-101767? An unauthenticated SQL injection in Oracle E-Business Suite that can be chain

·5 min read
Black October 2026: Every Major Vulnerability and Breach

Black October 2026: Every Major Vulnerability and Breach

October 2026 brought so many critical flaws and breaches at once that the security community started calling it "Black October." Two unauthenticated remote code execution bugs in PHP core, a CVSS 10.0 flaw in GitLab reaching back twelve years, an exploited SQL injection in Oracle E-Business Suite, Microsoft's largest-ever Patch Tuesday, and a ~20 million patient breach at Oracle Health all landed in the same few weeks. This roundup covers what broke, who's affected, and what to fix first. What

·6 min read