Comparison Overview

OhioHealth

VS

UCSF Health

OhioHealth

3430 OhioHealth Parkway, Columbus, 43202, US
Last Update: 2026-01-18
Between 750 and 799

OhioHealth is a nationally recognized, not-for-profit, faith-based health system of more than 35,000 associates, providers and volunteers. We lead with our mission to improve the health of those we serve throughout our 16 hospitals and 200+ urgent, primary and specialty care sites spanning 50 Ohio counties. Headquartered in Columbus, Ohio, we’re proud to be consistently recognized by FORTUNE as one of the “100 Best Companies to Work For” and rated a Top Hospital & Health System by Fair360 in 2024.

NAICS: 62
NAICS Definition: Health Care and Social Assistance
Employees: 14,756
Subsidiaries: 0
12-month incidents
0
Known data breaches
0
Attack type number
0

UCSF Health

505 Parnassus Avenue, San Francisco, 94143, US
Last Update: 2026-01-17
Between 700 and 749

UCSF Health is an integrated health care network encompassing several entities, including UCSF Medical Center, one of the nation’s top 10 hospitals according to U.S. News & World Report, and UCSF Benioff Children’s Hospitals, with campuses in Oakland and San Francisco. We are recognized throughout the world for our innovative patient care, advanced technology and pioneering research. For more than a century, we have offered the highest quality medical treatment. Today, our expertise covers virtually all specialties, from cancer to women's health. In addition, the compassionate care provided by our doctors, nurses and other staff is a key to our success. Our services generate about 1.1 million patient visits to our clinics a year and $3.2 billion in annual revenue. We have 12,000 employees and dozens of locations throughout San Francisco as well as outreach clinics throughout Northern California and beyond.

NAICS: 62
NAICS Definition: Health Care and Social Assistance
Employees: 11,303
Subsidiaries: 0
12-month incidents
0
Known data breaches
2
Attack type number
2

Compliance Badges Comparison

Security & Compliance Standards Overview

https://images.rankiteo.com/companyimages/ohiohealth.jpeg
OhioHealth
ISO 27001
ISO 27001 certification not verified
Not verified
SOC2 Type 1
SOC2 Type 1 certification not verified
Not verified
SOC2 Type 2
SOC2 Type 2 certification not verified
Not verified
GDPR
GDPR certification not verified
Not verified
PCI DSS
PCI DSS certification not verified
Not verified
HIPAA
HIPAA certification not verified
Not verified
https://images.rankiteo.com/companyimages/ucsfhealth.jpeg
UCSF Health
ISO 27001
ISO 27001 certification not verified
Not verified
SOC2 Type 1
SOC2 Type 1 certification not verified
Not verified
SOC2 Type 2
SOC2 Type 2 certification not verified
Not verified
GDPR
GDPR certification not verified
Not verified
PCI DSS
PCI DSS certification not verified
Not verified
HIPAA
HIPAA certification not verified
Not verified
Compliance Summary
OhioHealth
100%
Compliance Rate
0/4 Standards Verified
UCSF Health
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Hospitals and Health Care Industry Average (This Year)

No incidents recorded for OhioHealth in 2026.

Incidents vs Hospitals and Health Care Industry Average (This Year)

No incidents recorded for UCSF Health in 2026.

Incident History — OhioHealth (X = Date, Y = Severity)

OhioHealth cyber incidents detection timeline including parent company and subsidiaries

Incident History — UCSF Health (X = Date, Y = Severity)

UCSF Health cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/ohiohealth.jpeg
OhioHealth
Incidents

No Incident

https://images.rankiteo.com/companyimages/ucsfhealth.jpeg
UCSF Health
Incidents

Date Detected: 2/2023
Type:Breach
Attack Vector: Phishing
Blog: Blog

Date Detected: 6/2020
Type:Ransomware
Blog: Blog

Date Detected: 9/2013
Type:Breach
Attack Vector: Physical Theft
Motivation: Unknown
Blog: Blog

FAQ

OhioHealth company demonstrates a stronger AI Cybersecurity Score compared to UCSF Health company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

UCSF Health company has historically faced a number of disclosed cyber incidents, whereas OhioHealth company has not reported any.

In the current year, UCSF Health company and OhioHealth company have not reported any cyber incidents.

UCSF Health company has confirmed experiencing a ransomware attack, while OhioHealth company has not reported such incidents publicly.

UCSF Health company has disclosed at least one data breach, while OhioHealth company has not reported such incidents publicly.

Neither UCSF Health company nor OhioHealth company has reported experiencing targeted cyberattacks publicly.

Neither OhioHealth company nor UCSF Health company has reported experiencing or disclosing vulnerabilities publicly.

Neither OhioHealth nor UCSF Health holds any compliance certifications.

Neither company holds any compliance certifications.

Neither OhioHealth company nor UCSF Health company has publicly disclosed detailed information about the number of their subsidiaries.

OhioHealth company employs more people globally than UCSF Health company, reflecting its scale as a Hospitals and Health Care.

Neither OhioHealth nor UCSF Health holds SOC 2 Type 1 certification.

Neither OhioHealth nor UCSF Health holds SOC 2 Type 2 certification.

Neither OhioHealth nor UCSF Health holds ISO 27001 certification.

Neither OhioHealth nor UCSF Health holds PCI DSS certification.

Neither OhioHealth nor UCSF Health holds HIPAA certification.

Neither OhioHealth nor UCSF Health holds GDPR certification.

Latest Global CVEs (Not Company-Specific)

Description

SummaryA command injection vulnerability (CWE-78) has been found to exist in the `wrangler pages deploy` command. The issue occurs because the `--commit-hash` parameter is passed directly to a shell command without proper validation or sanitization, allowing an attacker with control of `--commit-hash` to execute arbitrary commands on the system running Wrangler. Root causeThe commitHash variable, derived from user input via the --commit-hash CLI argument, is interpolated directly into a shell command using template literals (e.g.,  execSync(`git show -s --format=%B ${commitHash}`)). Shell metacharacters are interpreted by the shell, enabling command execution. ImpactThis vulnerability is generally hard to exploit, as it requires --commit-hash to be attacker controlled. The vulnerability primarily affects CI/CD environments where `wrangler pages deploy` is used in automated pipelines and the --commit-hash parameter is populated from external, potentially untrusted sources. An attacker could exploit this to: * Run any shell command. * Exfiltrate environment variables. * Compromise the CI runner to install backdoors or modify build artifacts. Credits Disclosed responsibly by kny4hacker. Mitigation * Wrangler v4 users are requested to upgrade to Wrangler v4.59.1 or higher. * Wrangler v3 users are requested to upgrade to Wrangler v3.114.17 or higher. * Users on Wrangler v2 (EOL) should upgrade to a supported major version.

Risk Information
cvss4
Base: 7.7
Severity: LOW
CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:H/SC:L/SI:L/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Description

Vulnerability in the Oracle VM VirtualBox product of Oracle Virtualization (component: Core). Supported versions that are affected are 7.1.14 and 7.2.4. Easily exploitable vulnerability allows high privileged attacker with logon to the infrastructure where Oracle VM VirtualBox executes to compromise Oracle VM VirtualBox. While the vulnerability is in Oracle VM VirtualBox, attacks may significantly impact additional products (scope change). Successful attacks of this vulnerability can result in takeover of Oracle VM VirtualBox. CVSS 3.1 Base Score 8.2 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H).

Risk Information
cvss3
Base: 8.2
Severity: LOW
CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H
Description

Vulnerability in the Oracle VM VirtualBox product of Oracle Virtualization (component: Core). Supported versions that are affected are 7.1.14 and 7.2.4. Easily exploitable vulnerability allows high privileged attacker with logon to the infrastructure where Oracle VM VirtualBox executes to compromise Oracle VM VirtualBox. While the vulnerability is in Oracle VM VirtualBox, attacks may significantly impact additional products (scope change). Successful attacks of this vulnerability can result in unauthorized creation, deletion or modification access to critical data or all Oracle VM VirtualBox accessible data as well as unauthorized access to critical data or complete access to all Oracle VM VirtualBox accessible data and unauthorized ability to cause a partial denial of service (partial DOS) of Oracle VM VirtualBox. CVSS 3.1 Base Score 8.1 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:L).

Risk Information
cvss3
Base: 8.1
Severity: LOW
CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:L
Description

Vulnerability in the Oracle VM VirtualBox product of Oracle Virtualization (component: Core). Supported versions that are affected are 7.1.14 and 7.2.4. Easily exploitable vulnerability allows high privileged attacker with logon to the infrastructure where Oracle VM VirtualBox executes to compromise Oracle VM VirtualBox. While the vulnerability is in Oracle VM VirtualBox, attacks may significantly impact additional products (scope change). Successful attacks of this vulnerability can result in takeover of Oracle VM VirtualBox. CVSS 3.1 Base Score 8.2 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H).

Risk Information
cvss3
Base: 8.2
Severity: LOW
CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H
Description

Vulnerability in the Oracle VM VirtualBox product of Oracle Virtualization (component: Core). Supported versions that are affected are 7.1.14 and 7.2.4. Easily exploitable vulnerability allows high privileged attacker with logon to the infrastructure where Oracle VM VirtualBox executes to compromise Oracle VM VirtualBox. While the vulnerability is in Oracle VM VirtualBox, attacks may significantly impact additional products (scope change). Successful attacks of this vulnerability can result in takeover of Oracle VM VirtualBox. CVSS 3.1 Base Score 8.2 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H).

Risk Information
cvss3
Base: 8.2
Severity: LOW
CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H