Comparison Overview

UT Southwestern Medical Center

VS

Cardinal Health

UT Southwestern Medical Center

5323 Harry Hines Boulevard, Dallas, Texas, 75390, US
Last Update: 2025-11-21

UT Southwestern is an academic medical center, world-renowned for its research, regarded among the best in the country for medical education and for clinical and scientific training, and nationally recognized for the quality of care its faculty provides to patients at UT Southwestern’s University Hospital & Clinics and affiliated institutions. The Medical Center includes three degree-granting institutions: UT Southwestern Medical School, UT Southwestern Graduate School of Biomedical Sciences, and UT Southwestern School of Health Professions. - The schools train nearly 3,700 medical, graduate, and health profession students, residents, and postdoctoral fellows each year. - Ongoing support from federal agencies, along with foundations, individuals, and corporations, provides more than $524 million per year to fund faculty research. - UT Southwestern physicians provide care in about 80 specialties to more than 117,000 hospitalized patients, more than 360,000 emergency room cases, and oversee nearly 3 million outpatient visits a year. - UT Southwestern has approximately 25,000 employees and an operating budget of $3.7 billion. - In U.S. News & World Report’s America’s Best Hospitals 2023-2024 guide, UT Southwestern is ranked the No. 1 hospital in Texas (tie) – and a top 20 hospital in the nation. Additionally, UTSW is nationally ranked in nine specialty-care areas: Cancer; Cardiology, Heart & Vascular Surgery; Diabetes & Endocrinology; Ear, Nose & Throat; Gastroenterology & GI Surgery; Geriatrics; Neurology & Neurosurgery; Obstetrics & Gynecology; Pulmonology & Lung Surgery; Rehabilitation; and Urology.

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

Cardinal Health

7000 Cardinal Place, Dublin, OH, US, 43017
Last Update: 2025-11-21
Between 800 and 849

Cardinal Health is a distributor of pharmaceuticals, a global manufacturer and distributor of medical and laboratory products, and a provider of performance and data solutions for healthcare facilities. With more than 50 years in business, operations in more than 30 countries and approximately 48,000 employees globally, we are moving healthcare forward. Disclaimer: LinkedIn is a third-party site unaffiliated with Cardinal Health. Cardinal Health is not responsible for the privacy or security policies or practices on LinkedIn or on any of the third-party websites that we may link to through LinkedIn. You should carefully review the privacy and security practices of LinkedIn and linked third-party websites. We do not necessarily endorse any information found here nor are we responsible for the accuracy of any information, opinions, claims, or advice found here or shared here by our followers. By posting content, ideas, or pictures, you grant Cardinal Health a non-exclusive, royalty-free, perpetual, and worldwide license to use your content and any images posted by you, including the rights to copy, distribute, transmit, display, reproduce, edit, translate, and reformat, and incorporate into a collective work. Cardinal Health reserves all rights relating to the company's LinkedIn account, including removing postings and prohibiting individuals from participating on the page.

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

Compliance Badges Comparison

Security & Compliance Standards Overview

https://images.rankiteo.com/companyimages/utsw.jpeg
UT Southwestern 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
https://images.rankiteo.com/companyimages/cardinal-health.jpeg
Cardinal 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
UT Southwestern Medical Center
100%
Compliance Rate
0/4 Standards Verified
Cardinal 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 UT Southwestern Medical Center in 2025.

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

No incidents recorded for Cardinal Health in 2025.

Incident History — UT Southwestern Medical Center (X = Date, Y = Severity)

UT Southwestern Medical Center cyber incidents detection timeline including parent company and subsidiaries

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

Cardinal Health cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/utsw.jpeg
UT Southwestern Medical Center
Incidents

No Incident

https://images.rankiteo.com/companyimages/cardinal-health.jpeg
Cardinal Health
Incidents

No Incident

FAQ

Cardinal Health company demonstrates a stronger AI Cybersecurity Score compared to UT Southwestern Medical Center company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Historically, Cardinal Health company has disclosed a higher number of cyber incidents compared to UT Southwestern Medical Center company.

In the current year, Cardinal Health company and UT Southwestern Medical Center company have not reported any cyber incidents.

Neither Cardinal Health company nor UT Southwestern Medical Center company has reported experiencing a ransomware attack publicly.

Neither Cardinal Health company nor UT Southwestern Medical Center company has reported experiencing a data breach publicly.

Neither Cardinal Health company nor UT Southwestern Medical Center company has reported experiencing targeted cyberattacks publicly.

Neither UT Southwestern Medical Center company nor Cardinal Health company has reported experiencing or disclosing vulnerabilities publicly.

Neither UT Southwestern Medical Center nor Cardinal Health holds any compliance certifications.

Neither company holds any compliance certifications.

UT Southwestern Medical Center company has more subsidiaries worldwide compared to Cardinal Health company.

Cardinal Health company employs more people globally than UT Southwestern Medical Center company, reflecting its scale as a Hospitals and Health Care.

Neither UT Southwestern Medical Center nor Cardinal Health holds SOC 2 Type 1 certification.

Neither UT Southwestern Medical Center nor Cardinal Health holds SOC 2 Type 2 certification.

Neither UT Southwestern Medical Center nor Cardinal Health holds ISO 27001 certification.

Neither UT Southwestern Medical Center nor Cardinal Health holds PCI DSS certification.

Neither UT Southwestern Medical Center nor Cardinal Health holds HIPAA certification.

Neither UT Southwestern Medical Center nor Cardinal 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