Comparison Overview

Abdali Hospital

VS

Mercy Health

Abdali Hospital

Al-Istethmar street - Abdali Boulevard, Amman, JO
Last Update: 2025-12-19

Abdali Hospital is a 200 bed multi-specialty hospital. Its mission is to provide the highest quality patient-centered care; and promote research, education and a culture of excellence in the Middle East. Located in Amman, one of the best medical tourism destinations in the Middle East, Abdali Hospital offers highly specialized medical services under one roof. Our goal is to improve the health of our patients by providing inclusive and high standards of medical care to prevent, diagnose, manage and treat health problems, diseases or disorders. The hospital is dedicated to delivering advanced healthcare services. It combines international medical best practices with industry-leading technology and innovation. Abdali Hospital is founded by the investment group behind the Clemenceau Medical Center in Beirut, affiliated with John Hopkins and benefits from the knowledge, insight and expertise of the Middle East’s finest medical professionals.

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

Mercy Health

Cincinnati, Ohio, US, 45237
Last Update: 2025-12-17
Between 750 and 799

At Mercy Health, we understand that every family is a universe. A network of people who love, and support, and count on one other to be there. Everybody means the world to someone and we are committed to care for others so they can be there for the ones they love. With nearly 35,000 employees across regions of Ohio and Kentucky, we’re one of the largest health care systems in the country. At each of our more than 600 points of care, we deliver high-quality, compassionate care with one united purpose: to help our patients be well in mind, body and spirit.

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

Compliance Badges Comparison

Security & Compliance Standards Overview

https://images.rankiteo.com/companyimages/abdali-hospital.jpeg
Abdali Hospital
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/mercyhealth-chp.jpeg
Mercy 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
Abdali Hospital
100%
Compliance Rate
0/4 Standards Verified
Mercy 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 Abdali Hospital in 2025.

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

No incidents recorded for Mercy Health in 2025.

Incident History — Abdali Hospital (X = Date, Y = Severity)

Abdali Hospital cyber incidents detection timeline including parent company and subsidiaries

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

Mercy Health cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/abdali-hospital.jpeg
Abdali Hospital
Incidents

Date Detected: 12/2023
Type:Cyber Attack
Motivation: Ransom (10 BTC)
Blog: Blog
https://images.rankiteo.com/companyimages/mercyhealth-chp.jpeg
Mercy Health
Incidents

Date Detected: 01/2020
Type:Breach
Attack Vector: Invoice Printing Error
Blog: Blog

Date Detected: 08/2016
Type:Breach
Blog: Blog

Date Detected: 4/2016
Type:Breach
Attack Vector: Inadvertent Exposure (Misconfigured Internet-Accessible Files)
Blog: Blog

FAQ

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

Mercy Health company has faced a higher number of disclosed cyber incidents historically compared to Abdali Hospital company.

In the current year, Mercy Health company and Abdali Hospital company have not reported any cyber incidents.

Neither Mercy Health company nor Abdali Hospital company has reported experiencing a ransomware attack publicly.

Mercy Health company has disclosed at least one data breach, while Abdali Hospital company has not reported such incidents publicly.

Abdali Hospital company has reported targeted cyberattacks, while Mercy Health company has not reported such incidents publicly.

Neither Abdali Hospital company nor Mercy Health company has reported experiencing or disclosing vulnerabilities publicly.

Neither Abdali Hospital nor Mercy Health holds any compliance certifications.

Neither company holds any compliance certifications.

Mercy Health company has more subsidiaries worldwide compared to Abdali Hospital company.

Mercy Health company employs more people globally than Abdali Hospital company, reflecting its scale as a Hospitals and Health Care.

Neither Abdali Hospital nor Mercy Health holds SOC 2 Type 1 certification.

Neither Abdali Hospital nor Mercy Health holds SOC 2 Type 2 certification.

Neither Abdali Hospital nor Mercy Health holds ISO 27001 certification.

Neither Abdali Hospital nor Mercy Health holds PCI DSS certification.

Neither Abdali Hospital nor Mercy Health holds HIPAA certification.

Neither Abdali Hospital nor Mercy Health holds GDPR certification.

Latest Global CVEs (Not Company-Specific)

Description

httparty is an API tool. In versions 0.23.2 and prior, httparty is vulnerable to SSRF. This issue can pose a risk of leaking API keys, and it can also allow third parties to issue requests to internal servers. This issue has been patched via commit 0529bcd.

Risk Information
cvss4
Base: 8.8
Severity: LOW
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/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

5ire is a cross-platform desktop artificial intelligence assistant and model context protocol client. In versions 0.15.2 and prior, an RCE vulnerability exists in useMarkdown.ts, where the markdown-it-mermaid plugin is initialized with securityLevel: 'loose'. This configuration explicitly permits the rendering of HTML tags within Mermaid diagram nodes. This issue has not been patched at time of publication.

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

continuwuity is a Matrix homeserver written in Rust. Prior to version 0.5.0, this vulnerability allows a remote, unauthenticated attacker to force the target server to cryptographically sign arbitrary membership events. The flaw exists because the server fails to validate the origin of a signing request, provided the event's state_key is a valid user ID belonging to the target server. This issue has been patched in version 0.5.0. A workaround for this issue involves blocking access to the PUT /_matrix/federation/v2/invite/{roomId}/{eventId} endpoint using the reverse proxy.

Risk Information
cvss4
Base: 9.9
Severity: LOW
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:L/SA:L/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

LangChain is a framework for building LLM-powered applications. Prior to @langchain/core versions 0.3.80 and 1.1.8, and prior to langchain versions 0.3.37 and 1.2.3, a serialization injection vulnerability exists in LangChain JS's toJSON() method (and subsequently when string-ifying objects using JSON.stringify(). The method did not escape objects with 'lc' keys when serializing free-form data in kwargs. The 'lc' key is used internally by LangChain to mark serialized objects. When user-controlled data contains this key structure, it is treated as a legitimate LangChain object during deserialization rather than plain user data. This issue has been patched in @langchain/core versions 0.3.80 and 1.1.8, and langchain versions 0.3.37 and 1.2.3

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

LangChain is a framework for building agents and LLM-powered applications. Prior to versions 0.3.81 and 1.2.5, a serialization injection vulnerability exists in LangChain's dumps() and dumpd() functions. The functions do not escape dictionaries with 'lc' keys when serializing free-form dictionaries. The 'lc' key is used internally by LangChain to mark serialized objects. When user-controlled data contains this key structure, it is treated as a legitimate LangChain object during deserialization rather than plain user data. This issue has been patched in versions 0.3.81 and 1.2.5.

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