Comparison Overview

Brigham and Women's Hospital

VS

OhioHealth

Brigham and Women's Hospital

US
Last Update: 2026-01-18

Boston's Brigham and Women's Hospital (BWH) is an international leader in virtually every area of medicine and has been the site of pioneering breakthroughs that have improved lives around the world. A major teaching hospital of Harvard Medical School, BWH has a legacy of excellence that continues to grow. With two outstanding hospitals, over 150 outpatient practices, and over 1,200 physicians, we serve patients from New England, throughout the United States, and from 120 countries around the world. The BWH name is a reflection of our history. In 1980 three of Boston’s oldest and most prestigious Harvard Medical School teaching hospitals - the Peter Bent Brigham Hospital, the Robert Breck Brigham Hospital, and the Boston Hospital for Women – merged to form Brigham and Women’s Hospital. As a national leader in improving health care quality and safety, we have helped to develop some of the industry’s best practices including computerized physician order entry (CPOE) to prevent medication errors. The CPOE is now a nationally-accepted safety practice. The BWH Biomedical Research Institute (BRI) is one of the most powerful biomedical research institutes in the world and the second largest recipient of National Institutes of Health (NIH) funding among independent hospitals in the United States. BWH has long had great success in research as measured by the number of important discoveries made, the size and scope of its research portfolio and the volume of publications annually. BWH is a training ground for physicians, nurses, and allied health professionals. We have 1,100 trainees in over 140 of the most sought after training programs in the world, and also host Harvard Medical School students in rotations throughout our programs. As our global health services expand, our clinical trainees have rich opportunities to contribute and learn in challenging environments around the world. Brigham and Women's Hospital is an EEO, AA, VEVRAA Employer.

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

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

Compliance Badges Comparison

Security & Compliance Standards Overview

https://images.rankiteo.com/companyimages/brigham-and-women's-hospital.jpeg
Brigham and Women's Hospital
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/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
Compliance Summary
Brigham and Women's Hospital
100%
Compliance Rate
0/4 Standards Verified
OhioHealth
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 Brigham and Women's Hospital in 2026.

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

No incidents recorded for OhioHealth in 2026.

Incident History — Brigham and Women's Hospital (X = Date, Y = Severity)

Brigham and Women's Hospital cyber incidents detection timeline including parent company and subsidiaries

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

OhioHealth cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/brigham-and-women's-hospital.jpeg
Brigham and Women's Hospital
Incidents

Date Detected: 7/2023
Type:Breach
Blog: Blog

Date Detected: 11/2020
Type:Breach
Attack Vector: Human Error
Blog: Blog
https://images.rankiteo.com/companyimages/ohiohealth.jpeg
OhioHealth
Incidents

No Incident

FAQ

Brigham and Women's Hospital company demonstrates a stronger AI Cybersecurity Score compared to OhioHealth company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Brigham and Women's Hospital company has historically faced a number of disclosed cyber incidents, whereas OhioHealth company has not reported any.

In the current year, OhioHealth company and Brigham and Women's Hospital company have not reported any cyber incidents.

Neither OhioHealth company nor Brigham and Women's Hospital company has reported experiencing a ransomware attack publicly.

Brigham and Women's Hospital company has disclosed at least one data breach, while the other OhioHealth company has not reported such incidents publicly.

Neither OhioHealth company nor Brigham and Women's Hospital company has reported experiencing targeted cyberattacks publicly.

Neither Brigham and Women's Hospital company nor OhioHealth company has reported experiencing or disclosing vulnerabilities publicly.

Neither Brigham and Women's Hospital nor OhioHealth holds any compliance certifications.

Neither company holds any compliance certifications.

Brigham and Women's Hospital company has more subsidiaries worldwide compared to OhioHealth company.

Brigham and Women's Hospital company employs more people globally than OhioHealth company, reflecting its scale as a Hospitals and Health Care.

Neither Brigham and Women's Hospital nor OhioHealth holds SOC 2 Type 1 certification.

Neither Brigham and Women's Hospital nor OhioHealth holds SOC 2 Type 2 certification.

Neither Brigham and Women's Hospital nor OhioHealth holds ISO 27001 certification.

Neither Brigham and Women's Hospital nor OhioHealth holds PCI DSS certification.

Neither Brigham and Women's Hospital nor OhioHealth holds HIPAA certification.

Neither Brigham and Women's Hospital nor OhioHealth 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