Comparison Overview

Geisinger

VS

Hospital Sisters Health System

Geisinger

100 North Academy Avenue, Danville, 17822, US
Last Update: 2025-11-22
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,443
Subsidiaries: 4
12-month incidents
0
Known data breaches
4
Attack type number
1

Hospital Sisters Health System

4936 LaVerna Road, P.O. Box 19456, Springfield, Illinois, US, 62707
Last Update: 2025-11-20
Between 700 and 749

Since 1875, the Hospital Sisters of St. Francis have been caring for patients in Illinois, Wisconsin and other locations in the United States and across the world. Today, Hospital Sisters Health System (HSHS) is a multi-institutional health care system that cares for patients in 14 communities in Illinois and Wisconsin. With 15 hospitals, scores of community-based health centers and clinics, nearly 2,300 physician partners, and more than 14,600 colleagues, HSHS is committed to its mission “to reveal and embody Christ’s healing love for all people through our high quality Franciscan health care ministry.” HSHS continues to advance its mission through its care integration strategy by working closely with physician partners in Illinois and Wisconsin to deliver high quality, patient-centered care. Together, we strive to ensure each patient who enters our system has seamless access to health and wellness programs, primary and specialty care, and acute and post-acute care. Through their commitment to our care integration strategy, HSHS physician partners coordinate closely with our hospital and clinic colleagues to provide our patients with holistic care that meets their individual needs. By leveraging the latest technology, emphasizing the importance of relationships, and living its values, HSHS is making a positive difference in the lives of the patients and families it is privileged to serve.

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

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/hospital-sisters-health-system.jpeg
Hospital Sisters 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
Hospital Sisters 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 2025.

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

No incidents recorded for Hospital Sisters Health System in 2025.

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

Geisinger cyber incidents detection timeline including parent company and subsidiaries

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

Hospital Sisters 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: 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

Date Detected: 06/2020
Type:Breach
Attack Vector: Insider Threat
Blog: Blog
https://images.rankiteo.com/companyimages/hospital-sisters-health-system.jpeg
Hospital Sisters Health System
Incidents

Date Detected: 8/2023
Type:Cyber Attack
Attack Vector: Network Intrusion (Unauthorized Access)
Blog: Blog

Date Detected: 8/2023
Type:Cyber Attack
Blog: Blog

FAQ

Hospital Sisters 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 Hospital Sisters Health System company.

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

Neither Hospital Sisters Health System company nor Geisinger company has reported experiencing a ransomware attack publicly.

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

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

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

Neither Geisinger nor Hospital Sisters Health System holds any compliance certifications.

Neither company holds any compliance certifications.

Geisinger company has more subsidiaries worldwide compared to Hospital Sisters Health System company.

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

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

Neither Geisinger nor Hospital Sisters Health System holds SOC 2 Type 2 certification.

Neither Geisinger nor Hospital Sisters Health System holds ISO 27001 certification.

Neither Geisinger nor Hospital Sisters Health System holds PCI DSS certification.

Neither Geisinger nor Hospital Sisters Health System holds HIPAA certification.

Neither Geisinger nor Hospital Sisters Health System holds GDPR certification.

Latest Global CVEs (Not Company-Specific)

Description

Angular is a development platform for building mobile and desktop web applications using TypeScript/JavaScript and other languages. Prior to versions 19.2.16, 20.3.14, and 21.0.1, there is a XSRF token leakage via protocol-relative URLs in angular HTTP clients. The vulnerability is a Credential Leak by App Logic that leads to the unauthorized disclosure of the Cross-Site Request Forgery (XSRF) token to an attacker-controlled domain. Angular's HttpClient has a built-in XSRF protection mechanism that works by checking if a request URL starts with a protocol (http:// or https://) to determine if it is cross-origin. If the URL starts with protocol-relative URL (//), it is incorrectly treated as a same-origin request, and the XSRF token is automatically added to the X-XSRF-TOKEN header. This issue has been patched in versions 19.2.16, 20.3.14, and 21.0.1. A workaround for this issue involves avoiding using protocol-relative URLs (URLs starting with //) in HttpClient requests. All backend communication URLs should be hardcoded as relative paths (starting with a single /) or fully qualified, trusted absolute URLs.

Risk Information
cvss4
Base: 7.7
Severity: LOW
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:N/SC:H/SI:N/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

Forge (also called `node-forge`) is a native implementation of Transport Layer Security in JavaScript. An Uncontrolled Recursion vulnerability in node-forge versions 1.3.1 and below enables remote, unauthenticated attackers to craft deep ASN.1 structures that trigger unbounded recursive parsing. This leads to a Denial-of-Service (DoS) via stack exhaustion when parsing untrusted DER inputs. This issue has been patched in version 1.3.2.

Risk Information
cvss4
Base: 8.7
Severity: LOW
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/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

Forge (also called `node-forge`) is a native implementation of Transport Layer Security in JavaScript. An Integer Overflow vulnerability in node-forge versions 1.3.1 and below enables remote, unauthenticated attackers to craft ASN.1 structures containing OIDs with oversized arcs. These arcs may be decoded as smaller, trusted OIDs due to 32-bit bitwise truncation, enabling the bypass of downstream OID-based security decisions. This issue has been patched in version 1.3.2.

Risk Information
cvss4
Base: 6.3
Severity: LOW
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/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

Suricata is a network IDS, IPS and NSM engine developed by the OISF (Open Information Security Foundation) and the Suricata community. Prior to versions 7.0.13 and 8.0.2, working with large buffers in Lua scripts can lead to a stack overflow. Users of Lua rules and output scripts may be affected when working with large buffers. This includes a rule passing a large buffer to a Lua script. This issue has been patched in versions 7.0.13 and 8.0.2. A workaround for this issue involves disabling Lua rules and output scripts, or making sure limits, such as stream.depth.reassembly and HTTP response body limits (response-body-limit), are set to less than half the stack size.

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

Suricata is a network IDS, IPS and NSM engine developed by the OISF (Open Information Security Foundation) and the Suricata community. In versions from 8.0.0 to before 8.0.2, a NULL dereference can occur when the entropy keyword is used in conjunction with base64_data. This issue has been patched in version 8.0.2. A workaround involves disabling rules that use entropy in conjunction with base64_data.

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