Comparison Overview

Ascension

VS

UCLA Health

Ascension

101 South Hanley Rd., Suite 450, St. Louis, MO, US, 63105
Last Update: 2025-12-11
Between 0 and 549

Answering God's call to bring health, healing and hope to all. Ascension is one of the nation’s leading non-profit and Catholic health systems, with a Mission of delivering compassionate, personalized care to all, with special attention to those most vulnerable. In FY2025, Ascension provided $1.7 billion in care of persons living in poverty and other community benefit programs along with $1.8 billion of unreimbursed care for Medicare patients. Across 16 states and the District of Columbia, Ascension’s network encompasses approximately 99,000 associates, 22,300 aligned providers, 95 wholly owned or consolidated hospitals, and ownership interests in 26 additional hospitals through partnerships. Ascension also operates 30 senior living facilities and a variety of other care sites offering a range of healthcare services.

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

UCLA Health

757 Westwood Plaza, Los Angeles, 90095, US
Last Update: 2025-12-10
Between 700 and 749

For more than half a century, UCLA Health has provided the best in healthcare and the latest in medical technology to the people of Los Angeles and throughout the world. Comprised of Ronald Reagan UCLA Medical Center, UCLA Medical Center Santa Monica, Resnick Neuropsychiatric Hospital at UCLA, UCLA Mattel Children's Hospital, UCLA West Valley Medical Center and the UCLA Medical Group with its wide-reaching system of primary-care and specialty-care offices throughout the region, UCLA Health is among the most comprehensive and advanced healthcare systems in the world. Our physicians are world leaders in the diagnosis and treatment of complex illnesses, and our hospitals are among the best in the country. Consistently ranked one of the top ten hospitals in the nation and the best medical center in the western United States by U.S. News & World Report, Ronald Reagan UCLA Medical Center is at the cutting edge of biomedical research, and our doctors and scientists are leaders in performing pioneering work across an astounding range of disciplines, from organ transplantation and cardiac surgery to neurosurgery and cancer treatment, and bringing the latest discoveries to virtually every field of medicine.

NAICS: 62
NAICS Definition: Health Care and Social Assistance
Employees: 17,400
Subsidiaries: 50
12-month incidents
0
Known data breaches
13
Attack type number
3

Compliance Badges Comparison

Security & Compliance Standards Overview

https://images.rankiteo.com/companyimages/ascensionorg.jpeg
Ascension
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/ucla-health.jpeg
UCLA 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
Ascension
100%
Compliance Rate
0/4 Standards Verified
UCLA Health
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

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

Ascension has 19.05% more incidents than the average of same-industry companies with at least one recorded incident.

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

No incidents recorded for UCLA Health in 2025.

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

Ascension cyber incidents detection timeline including parent company and subsidiaries

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

UCLA Health cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/ascensionorg.jpeg
Ascension
Incidents

Date Detected: 4/2025
Type:Breach
Attack Vector: Vulnerability in third-party software
Motivation: Data theft
Blog: Blog

Date Detected: 12/2024
Type:Ransomware
Attack Vector: Social Engineering
Motivation: Financial
Blog: Blog

Date Detected: 6/2024
Type:Ransomware
Blog: Blog
https://images.rankiteo.com/companyimages/ucla-health.jpeg
UCLA Health
Incidents

Date Detected: 12/2024
Type:Ransomware
Motivation: Financial Gain
Blog: Blog

Date Detected: 1/2024
Type:Breach
Attack Vector: Phishing
Blog: Blog

Date Detected: 10/2023
Type:Ransomware
Motivation: Financial Gain
Blog: Blog

FAQ

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

UCLA Health company has faced a higher number of disclosed cyber incidents historically compared to Ascension company.

In the current year, Ascension company has reported more cyber incidents than UCLA Health company.

Both UCLA Health company and Ascension company have confirmed experiencing at least one ransomware attack.

Both UCLA Health company and Ascension company have disclosed experiencing at least one data breach.

Neither UCLA Health company nor Ascension company has reported experiencing targeted cyberattacks publicly.

Neither Ascension company nor UCLA Health company has reported experiencing or disclosing vulnerabilities publicly.

Neither Ascension nor UCLA Health holds any compliance certifications.

Neither company holds any compliance certifications.

UCLA Health company has more subsidiaries worldwide compared to Ascension company.

Ascension company employs more people globally than UCLA Health company, reflecting its scale as a Hospitals and Health Care.

Neither Ascension nor UCLA Health holds SOC 2 Type 1 certification.

Neither Ascension nor UCLA Health holds SOC 2 Type 2 certification.

Neither Ascension nor UCLA Health holds ISO 27001 certification.

Neither Ascension nor UCLA Health holds PCI DSS certification.

Neither Ascension nor UCLA Health holds HIPAA certification.

Neither Ascension nor UCLA Health holds GDPR certification.

Latest Global CVEs (Not Company-Specific)

Description

NXLog Agent before 6.11 can load a file specified by the OPENSSL_CONF environment variable.

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

uriparser through 0.9.9 allows unbounded recursion and stack consumption, as demonstrated by ParseMustBeSegmentNzNc with large input containing many commas.

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

A vulnerability was detected in Mayan EDMS up to 4.10.1. The affected element is an unknown function of the file /authentication/. The manipulation results in cross site scripting. The attack may be performed from remote. The exploit is now public and may be used. Upgrading to version 4.10.2 is sufficient to fix this issue. You should upgrade the affected component. The vendor confirms that this is "[f]ixed in version 4.10.2". Furthermore, that "[b]ackports for older versions in process and will be out as soon as their respective CI pipelines complete."

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

MJML through 4.18.0 allows mj-include directory traversal to test file existence and (in the type="css" case) read files. NOTE: this issue exists because of an incomplete fix for CVE-2020-12827.

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

A half-blind Server Side Request Forgery (SSRF) vulnerability exists in kube-controller-manager when using the in-tree Portworx StorageClass. This vulnerability allows authorized users to leak arbitrary information from unprotected endpoints in the control plane’s host network (including link-local or loopback services).

Risk Information
cvss3
Base: 5.8
Severity: HIGH
CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:H/I:N/A:N