Comparison Overview

St. Luke's Health System

VS

Rush University Medical Center

St. Luke's Health System

190 East Bannock Street, Boise, Idaho, US, 83712
Last Update: 2026-03-24
Between 750 and 799

As the only Idaho-based, not-for-profit health system, St. Luke’s Health System is dedicated to our mission “To improve the health of people in the communities we serve.” Today that means not only treating you when you’re sick or hurt, but doing everything we can to help you be as healthy as possible. Working together, we share resources, skills, and knowledge to provide the best possible care, no matter which of our hospitals you choose. Each St. Luke’s Health System hospital is nationally recognized for excellence in patient care, with prestigious awards and designations reflecting the exceptional care that is synonymous with the St. Luke's name.

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

Rush University Medical Center

1620 W Harrison St, Chicago, 60612, US
Last Update: 2026-03-22
Between 750 and 799

Rush University Medical Center is an academic medical center that includes a 671-bed hospital serving adults and children, the 61-bed Johnston R. Bowman Health Center and Rush University. Rush University is home to one of the first medical colleges in the Midwest and one of the nation's top-ranked nursing colleges, as well as graduate programs in allied health, health systems management and biomedical research. The medical center also offers more than 70 highly selective residency and fellowship programs in medical and surgical specialties and subspecialties. For more than 170 years, Rush has been leading the way in developing innovative and often life-saving treatments. Today, Rush is a thriving center for basic and clinical research, with physicians and scientists involved in hundreds of research projects developing and testing the effectiveness and safety of new therapies and medical devices. In addition to its mission in patient care, education and research, Rush maintains a strong commitment to the community. Rush reaches out to the Chicago community through such offerings as the Rush Community Services Initiatives Program, an umbrella for several student-led outreach programs designed to address the social and health care needs of residents in neighboring communities.

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

Compliance Badges Comparison

Security & Compliance Standards Overview

https://images.rankiteo.com/companyimages/stlukeshealthsystem.jpeg
St. Luke's 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
https://images.rankiteo.com/companyimages/rush-university-medical-center.jpeg
Rush University Medical Center
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
St. Luke's Health System
100%
Compliance Rate
0/4 Standards Verified
Rush University Medical Center
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 St. Luke's Health System in 2026.

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

No incidents recorded for Rush University Medical Center in 2026.

Incident History — St. Luke's Health System (X = Date, Y = Severity)

St. Luke's Health System cyber incidents detection timeline including parent company and subsidiaries

Incident History — Rush University Medical Center (X = Date, Y = Severity)

Rush University Medical Center cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/stlukeshealthsystem.jpeg
St. Luke's Health System
Incidents

Date Detected: 5/2022
Type:Breach
Blog: Blog
https://images.rankiteo.com/companyimages/rush-university-medical-center.jpeg
Rush University Medical Center
Incidents

Date Detected: 01/2019
Type:Data Leak
Attack Vector: Unauthorized Access/Disclosure
Blog: Blog

FAQ

Rush University Medical Center company demonstrates a stronger AI Cybersecurity Score compared to St. Luke's Health System company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

St. Luke's Health System and Rush University Medical Center have experienced a similar number of publicly disclosed cyber incidents.

In the current year, Rush University Medical Center company and St. Luke's Health System company have not reported any cyber incidents.

Neither Rush University Medical Center company nor St. Luke's Health System company has reported experiencing a ransomware attack publicly.

St. Luke's Health System company has disclosed at least one data breach, while the other Rush University Medical Center company has not reported such incidents publicly.

Neither Rush University Medical Center company nor St. Luke's Health System company has reported experiencing targeted cyberattacks publicly.

Neither St. Luke's Health System company nor Rush University Medical Center company has reported experiencing or disclosing vulnerabilities publicly.

Neither St. Luke's Health System nor Rush University Medical Center holds any compliance certifications.

Neither company holds any compliance certifications.

Rush University Medical Center company has more subsidiaries worldwide compared to St. Luke's Health System company.

Rush University Medical Center company employs more people globally than St. Luke's Health System company, reflecting its scale as a Hospitals and Health Care.

Neither St. Luke's Health System nor Rush University Medical Center holds SOC 2 Type 1 certification.

Neither St. Luke's Health System nor Rush University Medical Center holds SOC 2 Type 2 certification.

Neither St. Luke's Health System nor Rush University Medical Center holds ISO 27001 certification.

Neither St. Luke's Health System nor Rush University Medical Center holds PCI DSS certification.

Neither St. Luke's Health System nor Rush University Medical Center holds HIPAA certification.

Neither St. Luke's Health System nor Rush University Medical Center holds GDPR certification.

Latest Global CVEs (Not Company-Specific)

Description

A vulnerability was identified in Totolink A3300R 17.0.0cu.557_b20221024. This affects the function setLanCfg of the file /cgi-bin/cstecgi.cgi of the component Parameter Handler. The manipulation of the argument lanIp leads to command injection. Remote exploitation of the attack is possible. The exploit is publicly available and might be used.

Risk Information
cvss2
Base: 6.5
Severity: LOW
AV:N/AC:L/Au:S/C:P/I:P/A:P
cvss3
Base: 6.3
Severity: LOW
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L
cvss4
Base: 5.3
Severity: LOW
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P/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

Perl versions from 5.9.4 before 5.40.4-RC1, from 5.41.0 before 5.42.2-RC1, from 5.43.0 before 5.43.9 contain a vulnerable version of Compress::Raw::Zlib. Compress::Raw::Zlib is included in the Perl package as a dual-life core module, and is vulnerable to CVE-2026-3381 due to a vendored version of zlib which has several vulnerabilities, including CVE-2026-27171. The bundled Compress::Raw::Zlib was updated to version 2.221 in Perl blead commit c75ae9cc164205e1b6d6dbd57bd2c65c8593fe94.

Description

Ghidra versions prior to 12.0.3 improperly process annotation directives embedded in automatically extracted binary data, resulting in arbitrary command execution when an analyst interacts with the UI. Specifically, the @execute annotation (which is intended for trusted, user-authored comments) is also parsed in comments generated during auto-analysis (such as CFStrings in Mach-O binaries). This allows a crafted binary to present seemingly benign clickable text which, when clicked, executes attacker-controlled commands on the analyst’s machine.

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

A critical security vulnerability in parisneo/lollms versions up to 2.2.0 allows any authenticated user to accept or reject friend requests belonging to other users. The `respond_request()` function in `backend/routers/friends.py` does not implement proper authorization checks, enabling Insecure Direct Object Reference (IDOR) attacks. Specifically, the `/api/friends/requests/{friendship_id}` endpoint fails to verify whether the authenticated user is part of the friendship or the intended recipient of the request. This vulnerability can lead to unauthorized access, privacy violations, and potential social engineering attacks. The issue has been addressed in version 2.2.0.

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

A Server-Side Request Forgery (SSRF) vulnerability exists in parisneo/lollms versions prior to 2.2.0, specifically in the `/api/files/export-content` endpoint. The `_download_image_to_temp()` function in `backend/routers/files.py` fails to validate user-controlled URLs, allowing attackers to make arbitrary HTTP requests to internal services and cloud metadata endpoints. This vulnerability can lead to internal network access, cloud metadata access, information disclosure, port scanning, and potentially remote code execution.

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