Comparison Overview

Geisinger

VS

MultiCare Health System

Geisinger

100 North Academy Avenue, Danville, Pa., US, 17822
Last Update: 2026-01-15
Between 600 and 649

Geisinger is among the nation’s leading providers of value-based care, serving 1.2 million people in urban and rural communities across Pennsylvania. Founded in 1915 by philanthropist Abigail Geisinger, the nonprofit system generates $10 billion in annual revenues across 126 care sites — including 10 hospital campuses — and Geisinger Health Plan, with more than half a million members in commercial and government plans. Geisinger College of Health Sciences educates more than 5,000 medical professionals annually and conducts more than 1,400 clinical research studies. With 26,000 employees, including 1,700 employed physicians, Geisinger is among Pennsylvania’s largest employers with an estimated economic impact of $15 billion to the state’s economy. On March 31, 2024, Geisinger became the first member of Risant Health, a new nonprofit charitable organization created to expand and accelerate value-based care across the country. For more information, visit geisinger.org/careers or connect with us on Facebook, Instagram, LinkedIn and Twitter.

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

MultiCare Health System

315 Martin Luther King Jr. Way, Tacoma, WA, US, 98415
Last Update: 2026-01-18
Between 700 and 749

MultiCare’s roots in the Pacific Northwest go back to 1882, with the founding of Tacoma’s first hospital. Over the years, we’ve grown from a Tacoma-centric, hospital-based organization into the largest, community-based, locally governed health system in the state of Washington. Today, our comprehensive system of health includes more than 300 primary, urgent, pediatric and specialty care locations across Washington, Idaho and Oregon, as well as 13 hospitals. We welcome patients from the entire Pacific Northwest region and our 20,000-plus team members — including employees, providers and volunteers — proudly care for the communities we serve. Without a doubt, our organization has changed over the years. But what has never changed, throughout our long history, has been our dedication to health and wellness of the people of the Pacific Northwest. Guided by our mission, vision and values, we are on continuous journey to deliver the services that our communities need, and to ensure access to those services, now and in the future.

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

Compliance Badges Comparison

Security & Compliance Standards Overview

https://images.rankiteo.com/companyimages/geisinger.jpeg
Geisinger
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/multicare-health-system.jpeg
MultiCare Health System
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
Geisinger
100%
Compliance Rate
0/4 Standards Verified
MultiCare Health System
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 Geisinger in 2026.

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

No incidents recorded for MultiCare Health System in 2026.

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

Geisinger cyber incidents detection timeline including parent company and subsidiaries

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

MultiCare Health System cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/geisinger.jpeg
Geisinger
Incidents

Date Detected: 6/2025
Type:Cyber Attack
Attack Vector: Initial Access Broker
Motivation: Financial Gain
Blog: Blog

Date Detected: 11/2023
Type:Breach
Attack Vector: insider threat, privilege abuse
Motivation: unauthorized data access, potential financial gain (unconfirmed), malicious intent
Blog: Blog

Date Detected: 6/2023
Type:Breach
Attack Vector: Insider Access (Former Employee)
Motivation: Financial Gain, Unauthorized Data Access
Blog: Blog
https://images.rankiteo.com/companyimages/multicare-health-system.jpeg
MultiCare Health System
Incidents

Date Detected: 05/2022
Type:Data Leak
Attack Vector: Third-party vendor compromise
Blog: Blog

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

FAQ

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

Geisinger company has faced a higher number of disclosed cyber incidents historically compared to MultiCare Health System company.

In the current year, MultiCare Health System company and Geisinger company have not reported any cyber incidents.

MultiCare Health System company has confirmed experiencing a ransomware attack, while Geisinger company has not reported such incidents publicly.

Geisinger company has disclosed at least one data breach, while the other MultiCare Health System company has not reported such incidents publicly.

Geisinger company has reported targeted cyberattacks, while MultiCare Health System company has not reported such incidents publicly.

Neither Geisinger company nor MultiCare Health System company has reported experiencing or disclosing vulnerabilities publicly.

Neither Geisinger nor MultiCare Health System holds any compliance certifications.

Neither company holds any compliance certifications.

Geisinger company has more subsidiaries worldwide compared to MultiCare Health System company.

Geisinger company employs more people globally than MultiCare Health System company, reflecting its scale as a Hospitals and Health Care.

Neither Geisinger nor MultiCare Health System holds SOC 2 Type 1 certification.

Neither Geisinger nor MultiCare Health System holds SOC 2 Type 2 certification.

Neither Geisinger nor MultiCare Health System holds ISO 27001 certification.

Neither Geisinger nor MultiCare Health System holds PCI DSS certification.

Neither Geisinger nor MultiCare Health System holds HIPAA certification.

Neither Geisinger nor MultiCare Health System 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