Comparison Overview

Bon Secours

VS

MultiCare Health System

Bon Secours

1505 Marriottsville Road, Marriottsville, Maryland, US, 21104
Last Update: 2025-11-22
Between 750 and 799

Bon Secours Health System, Inc. based in Marriottsville, Maryland, is a $3.2 billion dollar not-for-profit Catholic health system that owns, manages or joint ventures 18 acute care, 5 long term care, 4 assisted living, 6 retirement communities/senior housing, 14 home care and hospice services, and other facilities, primarily on the East Coast. Bon Secours Health System consists of more than 24,000 caregivers helping people in seven states. Its vision is to be a prophetic Catholic health ministry partnering with communities to create a more humane world, build health and social justice and provide exceptional value for those served.

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

MultiCare Health System

315 Martin Luther King Jr. Way, None, Tacoma, WA, US, 98415
Last Update: 2025-11-27
Between 650 and 699

MultiCare’s roots in the Pacific Northwest go back to 1882, with the founding of Tacoma’s first hospital. Over the years, we’ve grown from a Tacoma-centric, hospital-based organization into the largest, community-based, locally governed health system in the state of Washington. Today, our comprehensive system of health includes more than 300 primary, urgent, pediatric and specialty care locations across Washington, Idaho and Oregon, as well as 13 hospitals. We welcome patients from the entire Pacific Northwest region and our 20,000-plus team members — including employees, providers and volunteers — proudly care for the communities we serve. Without a doubt, our organization has changed over the years. But what has never changed, throughout our long history, has been our dedication to health and wellness of the people of the Pacific Northwest. Guided by our mission, vision and values, we are on continuous journey to deliver the services that our communities need, and to ensure access to those services, now and in the future.

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

Compliance Badges Comparison

Security & Compliance Standards Overview

https://images.rankiteo.com/companyimages/bon-secours-health-system.jpeg
Bon Secours
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/multicare-health-system.jpeg
MultiCare Health System
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
Bon Secours
100%
Compliance Rate
0/4 Standards Verified
MultiCare Health System
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 Bon Secours in 2025.

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

No incidents recorded for MultiCare Health System in 2025.

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

Bon Secours cyber incidents detection timeline including parent company and subsidiaries

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

MultiCare Health System cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/bon-secours-health-system.jpeg
Bon Secours
Incidents

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

Date Detected: 4/2016
Type:Breach
Attack Vector: Inadvertent Exposure (Misconfigured Internet-Accessible Files)
Blog: Blog
https://images.rankiteo.com/companyimages/multicare-health-system.jpeg
MultiCare Health System
Incidents

Date Detected: 5/2022
Type:Breach
Attack Vector: Hacking
Blog: Blog

Date Detected: 05/2022
Type:Data Leak
Attack Vector: Third-party vendor compromise
Blog: Blog

Date Detected: 2/2020
Type:Ransomware
Blog: Blog

FAQ

Bon Secours company demonstrates a stronger AI Cybersecurity Score compared to MultiCare Health System company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

MultiCare Health System company has faced a higher number of disclosed cyber incidents historically compared to Bon Secours company.

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

MultiCare Health System company has confirmed experiencing a ransomware attack, while Bon Secours company has not reported such incidents publicly.

Both MultiCare Health System company and Bon Secours company have disclosed experiencing at least one data breach.

Neither MultiCare Health System company nor Bon Secours company has reported experiencing targeted cyberattacks publicly.

Neither Bon Secours company nor MultiCare Health System company has reported experiencing or disclosing vulnerabilities publicly.

Neither Bon Secours nor MultiCare Health System holds any compliance certifications.

Neither company holds any compliance certifications.

Neither Bon Secours company nor MultiCare Health System company has publicly disclosed detailed information about the number of their subsidiaries.

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

Neither Bon Secours nor MultiCare Health System holds SOC 2 Type 1 certification.

Neither Bon Secours nor MultiCare Health System holds SOC 2 Type 2 certification.

Neither Bon Secours nor MultiCare Health System holds ISO 27001 certification.

Neither Bon Secours nor MultiCare Health System holds PCI DSS certification.

Neither Bon Secours nor MultiCare Health System holds HIPAA certification.

Neither Bon Secours nor MultiCare Health System 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