Comparison Overview

Vancouver Coastal Health

VS

Mercy Health

Vancouver Coastal Health

11th floor - 601 West Broadway, Vancouver, BC, CA, V5Z 4C2
Last Update: 2025-12-09
Between 750 and 799

Join a team connected by collaboration, support and most importantly, the goal of providing quality patient care. We value career growth with employer-supported training, encourage a culture where everyone’s voice is heard and strive to create a supportive team environment. To learn more, visit vch.ca/careers Facebook - https://www.facebook.com/VCHhealthcare/ Twitter - https://twitter.com/VCHhealthcare YouTube - https://www.youtube.com/@VCHhealthcare Instagram - https://www.instagram.com/vchhealthcare/

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

Mercy Health

Cincinnati, Ohio, US, 45237
Last Update: 2025-12-09
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/vancouver-coastal-health.jpeg
Vancouver Coastal 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/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
Vancouver Coastal Health
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 Vancouver Coastal Health in 2025.

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

No incidents recorded for Mercy Health in 2025.

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

Vancouver Coastal Health 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/vancouver-coastal-health.jpeg
Vancouver Coastal Health
Incidents

Date Detected: 05/2020
Type:Ransomware
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 Vancouver Coastal Health 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 Vancouver Coastal Health company.

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

Vancouver Coastal Health company has confirmed experiencing a ransomware attack, while Mercy Health company has not reported such incidents publicly.

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

Neither Mercy Health company nor Vancouver Coastal Health company has reported experiencing targeted cyberattacks publicly.

Neither Vancouver Coastal Health company nor Mercy Health company has reported experiencing or disclosing vulnerabilities publicly.

Neither Vancouver Coastal Health nor Mercy Health holds any compliance certifications.

Neither company holds any compliance certifications.

Mercy Health company has more subsidiaries worldwide compared to Vancouver Coastal Health company.

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

Neither Vancouver Coastal Health nor Mercy Health holds SOC 2 Type 1 certification.

Neither Vancouver Coastal Health nor Mercy Health holds SOC 2 Type 2 certification.

Neither Vancouver Coastal Health nor Mercy Health holds ISO 27001 certification.

Neither Vancouver Coastal Health nor Mercy Health holds PCI DSS certification.

Neither Vancouver Coastal Health nor Mercy Health holds HIPAA certification.

Neither Vancouver Coastal Health nor Mercy Health holds GDPR certification.

Latest Global CVEs (Not Company-Specific)

Description

NXLog Agent before 6.11 can load a file specified by the OPENSSL_CONF environment variable.

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

uriparser through 0.9.9 allows unbounded recursion and stack consumption, as demonstrated by ParseMustBeSegmentNzNc with large input containing many commas.

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

A vulnerability was detected in Mayan EDMS up to 4.10.1. The affected element is an unknown function of the file /authentication/. The manipulation results in cross site scripting. The attack may be performed from remote. The exploit is now public and may be used. Upgrading to version 4.10.2 is sufficient to fix this issue. You should upgrade the affected component. The vendor confirms that this is "[f]ixed in version 4.10.2". Furthermore, that "[b]ackports for older versions in process and will be out as soon as their respective CI pipelines complete."

Risk Information
cvss2
Base: 5.0
Severity: LOW
AV:N/AC:L/Au:N/C:N/I:P/A:N
cvss3
Base: 4.3
Severity: LOW
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N
cvss4
Base: 5.3
Severity: LOW
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/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

MJML through 4.18.0 allows mj-include directory traversal to test file existence and (in the type="css" case) read files. NOTE: this issue exists because of an incomplete fix for CVE-2020-12827.

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

A half-blind Server Side Request Forgery (SSRF) vulnerability exists in kube-controller-manager when using the in-tree Portworx StorageClass. This vulnerability allows authorized users to leak arbitrary information from unprotected endpoints in the control plane’s host network (including link-local or loopback services).

Risk Information
cvss3
Base: 5.8
Severity: HIGH
CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:H/I:N/A:N