Vendor risk scoring turns what you know about a third party into a score and a risk tier, and the tier decides how closely you look at that vendor. A healthcare score usually combines four kinds of risk: cybersecurity posture, operational reliability, regulatory compliance, and financial stability. The benchmark data show why the discipline matters. In the Healthcare Cybersecurity Benchmarking Study 2025, Supply Chain Risk Management had the lowest coverage of any NIST CSF 2.0 category at 52%, against 73% for all other categories combined[1]. In a Ponemon Institute report sponsored by Censinet, 46% of respondents said their organizations determine which third parties are critical and high-risk[2].
This guide explains the four risk categories, how scoring models work with an illustrative example, how to tier vendors, what the benchmark and Ponemon data show about how healthcare organizations assess and reassess third parties, a three-phase assessment process, what the proposed HIPAA Security Rule update would ask of vendors, and how Censinet supports the work. Study figures carry their sample sizes. The Ponemon figures describe fiscal 2022 and were published in January 2023, so read them as a dated baseline.
What vendor risk scoring is
Vendor risk scoring is a structured way to evaluate third-party vendors by assigning scores based on factors such as security, compliance, and operational impact. In healthcare, where vendors handle protected health information (PHI), run clinical systems, and supply medical devices, the score helps a team decide which vendors need deep review and which need a lighter check.
Two terms matter. Inherent risk is the exposure a vendor creates before any controls are considered, for example because it holds PHI or can reach a clinical network. Residual risk is what remains after you assess the vendor's controls. A scoring program usually estimates inherent risk first, so it can tier vendors quickly, and refines the picture as evidence comes in.
Why vendor risk scoring matters
The number of third parties keeps growing
In the Ponemon report, respondents had an average of 2,608 third parties under contract for products and services, up from 1,949 in the prior year's survey, and expected an average of 2,905 within 12 months. The report presents these as extrapolated values, so treat them as estimates[2].
Third parties are tied to attacks and breaches
In the same report, 47% of respondents said their organizations had a ransomware attack in the past two years, and 46% of those said a third party caused it, up from 36% in 2021[2]. HIPAA Journal counted 118 of the 741 breaches of 500 or more records reported to the Office for Civil Rights (OCR) in 2024 as filed by business associates, and the year's largest breach, at the business associate Change Healthcare, affected 192.7 million individuals[3]. HIPAA Journal notes that entity counts understate business associate involvement, because covered entities sometimes report business associate breaches themselves[3].
Coverage of third-party controls is thin
Supply Chain Risk Management has been the lowest-covered NIST CSF category in each edition of the Censinet, KLAS, and American Hospital Association benchmarking study: 49% in 2023, lowest again in 2024, and 52% in 2025, the third consecutive year[1][4][5].
The 2023 study also found that organizations reporting higher Supply Chain Risk Management coverage reported smaller year-over-year increases more often in cybersecurity insurance premiums (n=44, correlation coefficient -0.71, p-value 0.02)[4]. This is an association in survey data and does not show that coverage causes lower premium growth.
The four risk categories in a healthcare score
Healthcare organizations commonly assess vendors across four categories. Cybersecurity posture is the backbone, because it covers the policies, procedures, and technical safeguards that protect sensitive data. The other three keep the score from being a security view alone.
A certification is an input, not a substitute for assessment. In the Ponemon report, 52% of respondents required critical and high-risk third parties to complete an internal risk assessment even with a recent SOC 2 certification, and 52% required one even with a recent HITRUST certification, down from 56% the year before[2].
How scoring models work
Likelihood times impact
The Likelihood x Impact model multiplies the probability of an event by its consequence. A vendor that scores 6 out of 10 on likelihood and 9 out of 10 on impact has a risk score of 54 on a 100-point scale, which signals high priority.
Weighted scoring
A weighted model assigns each category a share of the total based on your priorities. A hospital could weight cybersecurity at 40%, regulatory compliance at 30%, operational efficiency at 20%, and financial stability at 10%. The table below applies those weights to a hypothetical vendor. It is an illustration of the arithmetic, not benchmark data.
A total of 48 looks moderate, yet the vendor scores 70 on the category with the heaviest weight. This is the main weakness of averages. Many programs add a floor rule, for example escalating any vendor that scores above a set threshold in one category regardless of its total.
Quantitative, qualitative, internal, and external scores
Quantitative inputs are numbers such as uptime percentages and financial ratios. Qualitative inputs are expert opinion and survey feedback. Most programs blend the two. Internal scores reflect your own risk landscape, and external scores evaluate vendors from publicly available data, which gives a broader market view. External scores are an outside-in estimate, so validate them against evidence from the vendor.
Tiering vendors
Tiered classification groups vendors so that review effort follows risk. The tiers below follow a common pattern. The review cadence is an example to adapt, not a benchmark.
TABLE 04
Set the thresholds in writing, using patient safety, regulatory exposure, and operational impact. A vendor that manages backup systems warrants stricter controls than a cafeteria provider, even if both have some facility access. Document the business need for each vendor. That record helps you prioritize, supports decisions to mitigate or replace a vendor, and shows due diligence in an audit.
What healthcare organizations actually do
The Ponemon report gives a baseline for practice in healthcare delivery organizations (579 respondents, fiscal 2022 data)[2]. Only 46% determine which third parties are critical and high-risk. On average, 43% of critical and high-risk third parties are assessed annually and 38% are reassessed annually, and 13% of respondents said none of their critical and high-risk third parties are assessed annually. When asked, 73% said they would assess all vendors and products regardless of a pre-assessment label if they had the resources and money, up from 65% the year before [2].
Reassessment cadence is uneven. Among organizations that reassess third parties, a quarter do so every two years and 18% have no regular schedule[2].
TABLE 05
Budgets are mixed. Of respondents, 43% had a formal budget for vendor risk management, down from 50%, and those with a budget planned to allocate an average of $945,100 to vendor risk management and automation products in the coming fiscal year, an extrapolated value[2].
When a gap is found in a vendor's practices, the most common response was to require an external audit.
TABLE 06
Two points follow for a scoring program. Tiering is the step many organizations skip, and it is the step that tells you where to spend limited assessment capacity. A written escalation path matters too, because 26% of respondents said they would take none of the listed steps when a gap turns up.
A three-phase assessment process
Phase 1: Identify and classify vendors
List every vendor that touches your systems, data, or facilities. Include the obvious partners, such as electronic health record providers and medical device manufacturers, and the less obvious ones, such as cleaning services, marketing agencies, and software used by administrative teams. Classify each vendor by its access to sensitive data and systems, set the tier thresholds, and record the business need.
Phase 2: Collect and validate evidence
Align your program to a recognized standard, such as NIST, ISO, or HITRUST, and overlay HIPAA requirements. Collect questionnaires, SOC 2 reports, and contract terms, and use automation where it helps with document review and flagging gaps. Then validate what vendors tell you against independent sources, such as security ratings, regulatory databases, and threat intelligence. External data needs its own validation, so resolve conflicts between sources before they reach the score.
Phase 3: Score, prioritize, and monitor
Apply the same scoring method to every vendor. Prioritize high-risk vendors, and write remediation plans with owners, timelines, and success measures. Monitor continuously, with alerts for breaches, regulatory violations, and changes in a vendor's financial or security posture. Prepare contingency plans for high-risk vendors that name alternative vendors, emergency procedures, and communication steps, so a vendor failure does not interrupt patient care. Keep communication open and ask vendors to tell you about operational changes or shifts in their security posture.
HIPAA and other regulatory expectations
What HIPAA requires today
HHS states that a covered entity can disclose PHI to a business associate only after it obtains satisfactory assurances, in the form of a contract or other written arrangement, that the business associate will protect the information[6]. That written arrangement is the business associate agreement (BAA). The agreement is the starting point for scoring, not the end of it, because the score tells you how much evidence to ask for beyond the signature.
What the proposed Security Rule update would ask of vendors
OCR issued a notice of proposed rulemaking to update the HIPAA Security Rule in December 2024, and it was published in the Federal Register on January 6, 2025. It has not become final. HIPAA Journal reported in October 2026 that a final rule had not been issued and that the current Security Rule remains in effect[7][8]. Describe the changes as proposals when you brief leadership.
TABLE 07
Status: proposed, not final, as of October 2026[7][8].
Frameworks from other sectors
The federal banking agencies issued interagency guidance on third-party relationships in June 2023. It describes risk management across five stages: planning, due diligence, contract negotiation, ongoing monitoring, and termination[9]. It was written for financial institutions, but the stages map cleanly onto a healthcare vendor lifecycle, including an exit plan for vendors you retire.
Common challenges
- Static assessments miss change. An annual or biennial review can miss a change in a vendor's security posture. In the Ponemon data, a quarter of reassessing organizations did so every two years[2]. Tie reassessment to tier and trigger it when a vendor's products or services change.
- Unclear handling of findings. Define who owns each finding, the deadline, and the escalation path, and write remediation requirements into vendor contracts.
- Fourth-party risk. Vendors rely on subcontractors that you do not contract with. Ask vendors to disclose key subcontractors and include them in assessments.
- Resource limits. With 43% of respondents reporting a formal vendor risk budget[2], tiering is how a small team focuses effort.
- Inconsistent templates. When departments send different questionnaires to the same vendor, answers diverge. Centralize the templates.
How Censinet supports vendor risk scoring
Censinet describes its third-party risk capability as assessing vendors and products, including medical devices, cloud software, robotics, and consulting services, in a centralized vendor and product inventory that keeps live profiles with assessment history and current risk status. Its question sets are curated for healthcare by a dedicated curation team. The page lists automated rapid inherent risk scoring among its AI-powered capabilities, and it says the Censinet Risk Assessor Agent drafts content for the assessor to validate and that people remain in control of the assessment and every final risk decision. Findings flow into the Risk Register so that prioritized findings translate into action. Breach and ransomware notifications are focused on your inventory, and an incident review workflow takes each alert from triage to resolution. The page refers to the platform as Censinet RiskOps™.
To see where your own third-party program stands against peers, [join the benchmarking study](https://censinet.com/capabilities/healthcare-cybersecurity-peer-benchmarking) and compare your coverage of Supply Chain Risk Management and the HPH CPG vendor goals. To see the capability itself, read the [third-party risk page](https://censinet.com/capabilities/third-party-risk).
Conclusion
Key points
A vendor score is only as useful as the tier and the action attached to it. The benchmark data show where healthcare is thinnest: Supply Chain Risk Management coverage of 52%[1], and, in the Ponemon baseline, 46% of organizations identifying their critical and high-risk third parties[2].
Next steps
- Inventory and tier your vendors. Write the tier definitions and thresholds down, and record the business need for each vendor.
- Choose a scoring method and a floor rule. Use a weighted or likelihood and impact model, and escalate any vendor that scores above a set threshold in one category.
- Set reassessment cadence by tier. Move critical vendors to a regular schedule and add triggers for changes in products or services.
- Plan for the HIPAA proposal. Build annual safeguard verification and 24-hour contingency plan notice into contracts now, and treat them as proposals until a final rule is issued.
FAQs
What is vendor risk scoring?
Vendor risk scoring evaluates the risks associated with third-party vendors by assigning scores based on factors such as security, compliance, and operational impact. The score drives a risk tier, and the tier sets how much evidence and monitoring a vendor receives.
What factors go into a vendor risk score?
Healthcare organizations commonly score four categories: cybersecurity posture, operational efficiency, regulatory compliance, and financial stability. Weights reflect your priorities, for example 40% cybersecurity, 30% compliance, 20% operations, and 10% financial stability.
How often should vendors be reassessed?
Match cadence to tier. A common pattern is quarterly review for critical vendors and annual reassessment for lower tiers. In the Ponemon baseline, 14% of respondents reassessed annually, 25% every two years, and 9% never[2].
Does HIPAA now require annual vendor verification?
Not yet. The HIPAA Security Rule update that would require business associates to verify technical safeguards at least every 12 months is a proposal, and HIPAA Journal reported in October 2026 that no final rule had been issued[7][8]. Today, a covered entity needs a business associate agreement with a vendor that handles PHI[6].
Does a SOC 2 or HITRUST report replace an assessment?
No. Treat a certification as one input to the score. In the Ponemon data, 52% of respondents required an internal risk assessment of critical and high-risk third parties even with a recent SOC 2 certification[2].
How does Censinet support vendor risk scoring?
Censinet's third-party risk capability keeps a centralized vendor and product inventory with assessment history and current risk status, adds automated rapid inherent risk scoring, and routes findings to a Risk Register, with people making every final risk decision. You can read more on the [third-party risk page](https://censinet.com/capabilities/third-party-risk).
References
- KLAS Research and Censinet, with the American Hospital Association. Healthcare Cybersecurity Benchmarking Study 2025, Executive Summary (April 2025). https://censinet.com/2025-healthcare-cybersecurity-benchmarking-study-executive-summary
- Ponemon Institute, sponsored by Censinet. The Impact of Ransomware on Patient Safety and the Value of Cybersecurity Benchmarking (January 2023). https://censinet.com/ponemon-research-report-the-impact-of-ransomware-on-patient-safety-and-the-value-of-cybersecurity-benchmarking
- HIPAA Journal. Healthcare Data Breach Statistics, updated for 2026 (statistics updated October 15, 2026, from OCR data obtained October 10, 2026). https://www.hipaajournal.com/healthcare-data-breach-statistics/
- Censinet, KLAS Research, and the American Hospital Association. Healthcare Cybersecurity Benchmarking Study: How Aligned Is the Industry to NIST and HICP Best Practices? (April 2023). https://www.censinet.com/2023-healthcare-cybersecurity-benchmarking-study-executive-insights
- Censinet, KLAS Research, the American Hospital Association, Health-ISAC, and the Healthcare and Public Health Sector Coordinating Council. Healthcare Cybersecurity Benchmarking Study 2024: Improving Cybersecurity Preparedness through NIST CSF & HICP Best Practices (February 2024). https://www.censinet.com/blog/censinet-klas-and-american-hospital-association-publish-the-2024-healthcare-cybersecurity-benchmarking-study
- U.S. Department of Health and Human Services. Business Associates (HIPAA guidance). https://www.hhs.gov/hipaa/for-professionals/privacy/guidance/business-associates/index.html
- U.S. Department of Health and Human Services, Office for Civil Rights. HIPAA Security Rule Notice of Proposed Rulemaking to Strengthen Cybersecurity for Electronic Protected Health Information, fact sheet. https://www.hhs.gov/hipaa/for-professionals/security/hipaa-security-rule-nprm/factsheet/index.html
- HIPAA Journal. HIPAA Updates and HIPAA Changes in 2026 (page updated October 19, 2026). https://www.hipaajournal.com/hipaa-updates-hipaa-changes/
- Federal Reserve Board, FDIC, and OCC. Interagency Guidance on Third-Party Relationships: Risk Management (June 2023; FDIC FIL-29-2023). https://www.fdic.gov/news/financial-institution-letters/2023/fil23029.html