Comparison Overview

Elevance Health

VS

Baylor Scott & White Health

Elevance Health

220 Virginia Ave, Indianapolis, Indiana, US, 46204
Last Update: 2025-11-27

Fueled by our bold purpose to improve the health of humanity, we are transforming from a traditional health benefits organization into a lifetime trusted health partner. Our nearly 100,000 associates serve more than 118 million people, at every stage of health. We address a full range of needs with an integrated whole health approach, powered by industry-leading capabilities and a digital platform for health. We believe that improving health for everyone is possible. It begins by redefining health, reimagining the health system, and strengthening our communities.

NAICS: 62
NAICS Definition: Health Care and Social Assistance
Employees: 42,630
Subsidiaries: 19
12-month incidents
0
Known data breaches
7
Attack type number
3

Baylor Scott & White Health

3500 Gaston Ave, Dallas, Texas, 75246, US
Last Update: 2025-11-21
Between 750 and 799

With us by your side, there's no stopping you. It's why we're creating a new kind of healthcare at Baylor Scott & White. And we're just getting started. As the largest not-for-profit health system in the state of Texas, Baylor Scott & White promotes the health and well-being of every individual, family and community it serves. It is committed to making quality care more accessible, convenient and affordable through its integrated delivery network, which includes the Baylor Scott & White Health Plan, Baylor Scott & White Research Institute, the Baylor Scott & White Quality Alliance and its leading digital health platform — MyBSWHealth. Through 52 hospitals and more than 1,300 access points, including flagship academic medical centers in Dallas, Fort Worth and Temple, the system offers the full continuum of care, from primary to award-winning specialty care. Founded as a Christian ministry of healing more than a century ago, Baylor Scott & White today serves more than three million Texans. For more information visit: BSWHealth.com.

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

Compliance Badges Comparison

Security & Compliance Standards Overview

https://images.rankiteo.com/companyimages/elevance-health.jpeg
Elevance 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
https://images.rankiteo.com/companyimages/bswhealth.jpeg
Baylor Scott & White 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
Elevance Health
100%
Compliance Rate
0/4 Standards Verified
Baylor Scott & White 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 Elevance Health in 2025.

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

No incidents recorded for Baylor Scott & White Health in 2025.

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

Elevance Health cyber incidents detection timeline including parent company and subsidiaries

Incident History — Baylor Scott & White Health (X = Date, Y = Severity)

Baylor Scott & White Health cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/elevance-health.jpeg
Elevance Health
Incidents

Date Detected: 11/2025
Type:Breach
Blog: Blog

Date Detected: 10/2025
Type:Breach
Blog: Blog

Date Detected: 10/2022
Type:Breach
Blog: Blog
https://images.rankiteo.com/companyimages/bswhealth.jpeg
Baylor Scott & White Health
Incidents

No Incident

FAQ

Elevance Health company demonstrates a stronger AI Cybersecurity Score compared to Baylor Scott & White Health company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Elevance Health company has historically faced a number of disclosed cyber incidents, whereas Baylor Scott & White Health company has not reported any.

In the current year, Elevance Health company has reported more cyber incidents than Baylor Scott & White Health company.

Elevance Health company has confirmed experiencing a ransomware attack, while Baylor Scott & White Health company has not reported such incidents publicly.

Elevance Health company has disclosed at least one data breach, while the other Baylor Scott & White Health company has not reported such incidents publicly.

Elevance Health company has reported targeted cyberattacks, while Baylor Scott & White Health company has not reported such incidents publicly.

Neither Elevance Health company nor Baylor Scott & White Health company has reported experiencing or disclosing vulnerabilities publicly.

Neither Elevance Health nor Baylor Scott & White Health holds any compliance certifications.

Neither company holds any compliance certifications.

Elevance Health company has more subsidiaries worldwide compared to Baylor Scott & White Health company.

Elevance Health company employs more people globally than Baylor Scott & White Health company, reflecting its scale as a Hospitals and Health Care.

Neither Elevance Health nor Baylor Scott & White Health holds SOC 2 Type 1 certification.

Neither Elevance Health nor Baylor Scott & White Health holds SOC 2 Type 2 certification.

Neither Elevance Health nor Baylor Scott & White Health holds ISO 27001 certification.

Neither Elevance Health nor Baylor Scott & White Health holds PCI DSS certification.

Neither Elevance Health nor Baylor Scott & White Health holds HIPAA certification.

Neither Elevance Health nor Baylor Scott & White Health 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