Comparison Overview

The University of Texas Medical Branch

VS

Advocate Aurora Health

The University of Texas Medical Branch

301 University Blvd, Galveston, Texas, US, 77550
Last Update: 2026-03-29
Between 750 and 799

The first academic health center in Texas opened its doors in 1891 and today has four campuses, five health sciences schools, seven institutes for advanced study, a research enterprise that includes one of only two national laboratories dedicated to the safe study of infectious threats to human health, a Level 1 Trauma Center and a health system offering a full range of primary and specialized medical services throughout the Texas Gulf Coast region. UTMB is an institution in The University of Texas System and a member of the Texas Medical Center.

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

Advocate Aurora Health

750 W Virginia St, Milwaukee, 53204, US
Last Update: 2026-03-25

Advocate Aurora Health and Atrium Health are now Advocate Health – the fifth-largest nonprofit integrated health system in the U.S. Advocate Health is the fifth-largest nonprofit integrated health system in the United States –created from the combination of Advocate Aurora Health and Atrium Health. Providing care under the names Advocate Health Care in Illinois, Atrium Health in the Carolinas, Georgia and Alabama, and Aurora Health Care in Wisconsin, Advocate Health is a national leader in clinical innovation, health outcomes, consumer experience and value-based care, with Wake Forest University School of Medicine serving as the academic core of the enterprise. Headquartered in Charlotte, North Carolina, Advocate Health serves nearly 6 million patients and is engaged in hundreds of clinical trials and research studies. It is nationally recognized for its expertise in cardiology, neurosciences, oncology, pediatrics and rehabilitation, as well as organ transplants, burn treatments and specialized musculoskeletal programs. Advocate Health employs nearly 150,000 team members across 67 hospitals and over 1,000 care locations, and offers one of the nation’s largest graduate medical education programs with over 2,000 residents and fellows across more than 200 programs. Committed to equitable care for all, Advocate Health provides nearly $5 billion in annual community benefits. Learn more: advocatehealth.org Read our social media community engagement guidelines: aah.org/social

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

Compliance Badges Comparison

Security & Compliance Standards Overview

https://images.rankiteo.com/companyimages/utmb.jpeg
The University of Texas Medical Branch
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/advocate-aurora-health.jpeg
Advocate Aurora 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
The University of Texas Medical Branch
100%
Compliance Rate
0/4 Standards Verified
Advocate Aurora 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 The University of Texas Medical Branch in 2026.

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

No incidents recorded for Advocate Aurora Health in 2026.

Incident History — The University of Texas Medical Branch (X = Date, Y = Severity)

The University of Texas Medical Branch cyber incidents detection timeline including parent company and subsidiaries

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

Advocate Aurora Health cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/utmb.jpeg
The University of Texas Medical Branch
Incidents

No Incident

https://images.rankiteo.com/companyimages/advocate-aurora-health.jpeg
Advocate Aurora Health
Incidents

Date Detected: 10/2022
Type:Breach
Attack Vector: Improper use of Meta Pixel
Blog: Blog

FAQ

The University of Texas Medical Branch company demonstrates a stronger AI Cybersecurity Score compared to Advocate Aurora Health company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Advocate Aurora Health company has historically faced a number of disclosed cyber incidents, whereas The University of Texas Medical Branch company has not reported any.

In the current year, Advocate Aurora Health company and The University of Texas Medical Branch company have not reported any cyber incidents.

Neither Advocate Aurora Health company nor The University of Texas Medical Branch company has reported experiencing a ransomware attack publicly.

Advocate Aurora Health company has disclosed at least one data breach, while The University of Texas Medical Branch company has not reported such incidents publicly.

Neither Advocate Aurora Health company nor The University of Texas Medical Branch company has reported experiencing targeted cyberattacks publicly.

Neither The University of Texas Medical Branch company nor Advocate Aurora Health company has reported experiencing or disclosing vulnerabilities publicly.

Neither The University of Texas Medical Branch nor Advocate Aurora Health holds any compliance certifications.

Neither company holds any compliance certifications.

Neither The University of Texas Medical Branch company nor Advocate Aurora Health company has publicly disclosed detailed information about the number of their subsidiaries.

Advocate Aurora Health company employs more people globally than The University of Texas Medical Branch company, reflecting its scale as a Hospitals and Health Care.

Neither The University of Texas Medical Branch nor Advocate Aurora Health holds SOC 2 Type 1 certification.

Neither The University of Texas Medical Branch nor Advocate Aurora Health holds SOC 2 Type 2 certification.

Neither The University of Texas Medical Branch nor Advocate Aurora Health holds ISO 27001 certification.

Neither The University of Texas Medical Branch nor Advocate Aurora Health holds PCI DSS certification.

Neither The University of Texas Medical Branch nor Advocate Aurora Health holds HIPAA certification.

Neither The University of Texas Medical Branch nor Advocate Aurora Health 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