Comparison Overview

Encompass Health

VS

Bon Secours Mercy Health

Encompass Health

9001 Liberty Pkwy, Birmingham, Alabama, 35242, US
Last Update: 2025-11-26
Between 750 and 799

Encompass Health is the largest owner and operator of rehabilitation hospitals in the United States. With a national footprint that includes 158 hospitals in 37 states and Puerto Rico, the Company provides high-quality, compassionate rehabilitative care for patients recovering from a major injury or illness, using advanced technology and innovative treatments to maximize recovery. Encompass Health is ranked as one of Fortune’s 100 Best Companies to Work For and Modern Healthcare’s Best Places to Work in Healthcare.

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

Bon Secours Mercy Health

Cincinnati, Ohio, US, 45237
Last Update: 2025-11-27
Between 750 and 799

On September 1, 2018 Bon Secours Health System and Mercy Health combined to become the United States’ fifth largest Catholic health care ministry and one of the nation’s 20 largest health care systems. With 48 hospitals, thousands of providers, over 1,000 points of care and over 60,000 employees Bon Secours Mercy Health serves communities across seven states and Ireland. We are dedicated to continually improving health care quality, safety and cost effectiveness. Our hospitals, care sites and clinicians are recognized for clinical and operational excellence. By utilizing robust measurement and reporting processes, we hold ourselves accountable for enhancing care and improving outcomes for our patients, residents and clients.

NAICS: 62
NAICS Definition: Health Care and Social Assistance
Employees: 30,908
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/encompasshealth.jpeg
Encompass 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/bon-secours-mercy-health-system.jpeg
Bon Secours 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
Encompass Health
100%
Compliance Rate
0/4 Standards Verified
Bon Secours 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 Encompass Health in 2025.

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

No incidents recorded for Bon Secours Mercy Health in 2025.

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

Encompass Health cyber incidents detection timeline including parent company and subsidiaries

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

Bon Secours 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/encompasshealth.jpeg
Encompass Health
Incidents

No Incident

https://images.rankiteo.com/companyimages/bon-secours-mercy-health-system.jpeg
Bon Secours 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

Both Encompass Health company and Bon Secours Mercy Health company demonstrate a comparable AI Cybersecurity Score, with strong governance and monitoring frameworks in place.

Bon Secours Mercy Health company has historically faced a number of disclosed cyber incidents, whereas Encompass Health company has not reported any.

In the current year, Bon Secours Mercy Health company and Encompass Health company have not reported any cyber incidents.

Neither Bon Secours Mercy Health company nor Encompass Health company has reported experiencing a ransomware attack publicly.

Bon Secours Mercy Health company has disclosed at least one data breach, while Encompass Health company has not reported such incidents publicly.

Neither Bon Secours Mercy Health company nor Encompass Health company has reported experiencing targeted cyberattacks publicly.

Neither Encompass Health company nor Bon Secours Mercy Health company has reported experiencing or disclosing vulnerabilities publicly.

Neither Encompass Health nor Bon Secours Mercy Health holds any compliance certifications.

Neither company holds any compliance certifications.

Bon Secours Mercy Health company has more subsidiaries worldwide compared to Encompass Health company.

Bon Secours Mercy Health company employs more people globally than Encompass Health company, reflecting its scale as a Hospitals and Health Care.

Neither Encompass Health nor Bon Secours Mercy Health holds SOC 2 Type 1 certification.

Neither Encompass Health nor Bon Secours Mercy Health holds SOC 2 Type 2 certification.

Neither Encompass Health nor Bon Secours Mercy Health holds ISO 27001 certification.

Neither Encompass Health nor Bon Secours Mercy Health holds PCI DSS certification.

Neither Encompass Health nor Bon Secours Mercy Health holds HIPAA certification.

Neither Encompass Health nor Bon Secours Mercy 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