Comparison Overview

University Hospitals Elyria Medical Center

VS

Cardinal Health

University Hospitals Elyria Medical Center

undefined, Elyria, undefined, undefined, US
Last Update: 2025-11-26
Between 750 and 799

Founded in 1908, University Hospitals Elyria Medical Center is a 387-licensed bed hospital with additional campuses in Amherst (University Hospitals Amherst Health Center), Avon (University Hospitals Avon Health Center) and Sheffield (University Hospitals Sheffield Health Center), along with medical offices in Grafton, North Ridgeville and Westlake. A state-of-the-art fitness center, along with physician offices, rehabilitation, outpatient testing and a full-service 24/7 ER are located within the UH Avon Health Center. The Center for Health & Fitness is one of Northeast Ohio’s first medically-based fitness centers, and offers more than 115 weekly group exercise classes, senior programs, a day spa, and more. The UH Amherst Health Center features a full-service 24/7 ER to serve the emergency needs of the community. Also on-site is a dedicated radiology department for 24-hour X-ray, CAT scan and Ultrasound; as well as an around-the-clock laboratory.

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

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/emh-regional-medical-center.jpeg
University Hospitals Elyria 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
University Hospitals Elyria 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 University Hospitals Elyria Medical Center in 2025.

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

No incidents recorded for Cardinal Health in 2025.

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

University Hospitals Elyria 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/emh-regional-medical-center.jpeg
University Hospitals Elyria Medical Center
Incidents

Date Detected: 11/2021
Type:Breach
Attack Vector: Unauthorized Access/Disclosure
Blog: Blog

Date Detected: 1/2016
Type:Breach
Attack Vector: Unauthorized Access
Blog: Blog

Date Detected: 07/2015
Type:Breach
Attack Vector: Insider Threat
Blog: Blog
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 University Hospitals Elyria Medical Center company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

University Hospitals Elyria Medical Center company has historically faced a number of disclosed cyber incidents, whereas Cardinal Health company has not reported any.

In the current year, Cardinal Health company and University Hospitals Elyria Medical Center company have not reported any cyber incidents.

Neither Cardinal Health company nor University Hospitals Elyria Medical Center company has reported experiencing a ransomware attack publicly.

University Hospitals Elyria Medical Center company has disclosed at least one data breach, while the other Cardinal Health company has not reported such incidents publicly.

Neither Cardinal Health company nor University Hospitals Elyria Medical Center company has reported experiencing targeted cyberattacks publicly.

Neither University Hospitals Elyria Medical Center company nor Cardinal Health company has reported experiencing or disclosing vulnerabilities publicly.

Neither University Hospitals Elyria Medical Center nor Cardinal Health holds any compliance certifications.

Neither company holds any compliance certifications.

University Hospitals Elyria Medical Center company has more subsidiaries worldwide compared to Cardinal Health company.

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

Neither University Hospitals Elyria Medical Center nor Cardinal Health holds SOC 2 Type 1 certification.

Neither University Hospitals Elyria Medical Center nor Cardinal Health holds SOC 2 Type 2 certification.

Neither University Hospitals Elyria Medical Center nor Cardinal Health holds ISO 27001 certification.

Neither University Hospitals Elyria Medical Center nor Cardinal Health holds PCI DSS certification.

Neither University Hospitals Elyria Medical Center nor Cardinal Health holds HIPAA certification.

Neither University Hospitals Elyria 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