Comparison Overview

Health PEI

VS

SSM Health

Health PEI

16 Garfield St, Charlottetown, Prince Edward Island, C1A, CA
Last Update: 2025-12-17
Between 700 and 749

Health PEI is a crown corporation responsible for the operation and delivery of publicly funded health services in Prince Edward Island, Canada. The organization operates hospitals, health centres, public long-term care nursing facilities and community-based programs and services.

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

SSM Health

10101 Woodfield Ln, St Louis, Missouri, US, 63132
Last Update: 2025-12-17
Between 700 and 749

SSM Health is a Catholic, not-for-profit, fully integrated health system dedicated to advancing innovative, sustainable, and compassionate care for patients and communities throughout the Midwest and beyond. The organization’s 40,000 team members and 13,900 providers are committed to fulfilling SSM Health’s Mission: “Through our exceptional health care services, we reveal the healing presence of God.” With care delivery sites in Illinois, Missouri, Oklahoma and Wisconsin, SSM Health includes hospitals, physician offices, outpatient and virtual care services, comprehensive home care and hospice services, a fully transparent pharmacy benefit company, a health insurance company and an accountable care organization. It is one of the largest employers in every community it serves. For more information, visit ssmhealth.com Visit jobs.ssmhealth.com to fulfill your calling with SSM Health. Together – We Care.

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

Compliance Badges Comparison

Security & Compliance Standards Overview

https://images.rankiteo.com/companyimages/health-pei.jpeg
Health PEI
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/ssm-health-care.jpeg
SSM 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
Health PEI
100%
Compliance Rate
0/4 Standards Verified
SSM 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 Health PEI in 2025.

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

SSM Health has 19.05% more incidents than the average of same-industry companies with at least one recorded incident.

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

Health PEI cyber incidents detection timeline including parent company and subsidiaries

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

SSM Health cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/health-pei.jpeg
Health PEI
Incidents

Date Detected: 06/2022
Type:Breach
Attack Vector: Laptop Theft
Motivation: Theft
Blog: Blog

Date Detected: 4/2022
Type:Breach
Attack Vector: Theft of Laptop
Blog: Blog

Date Detected: 03/2020
Type:Malware
Blog: Blog
https://images.rankiteo.com/companyimages/ssm-health-care.jpeg
SSM Health
Incidents

Date Detected: 11/2025
Type:Cyber Attack
Blog: Blog

Date Detected: 12/2020
Type:Breach
Attack Vector: Unauthorized Access/Disclosure
Blog: Blog

FAQ

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

Health PEI company has faced a higher number of disclosed cyber incidents historically compared to SSM Health company.

In the current year, SSM Health company has reported more cyber incidents than Health PEI company.

Health PEI company has confirmed experiencing a ransomware attack, while SSM Health company has not reported such incidents publicly.

Both SSM Health company and Health PEI company have disclosed experiencing at least one data breach.

SSM Health company has reported targeted cyberattacks, while Health PEI company has not reported such incidents publicly.

Neither Health PEI company nor SSM Health company has reported experiencing or disclosing vulnerabilities publicly.

Neither Health PEI nor SSM Health holds any compliance certifications.

Neither company holds any compliance certifications.

Health PEI company has more subsidiaries worldwide compared to SSM Health company.

SSM Health company employs more people globally than Health PEI company, reflecting its scale as a Hospitals and Health Care.

Neither Health PEI nor SSM Health holds SOC 2 Type 1 certification.

Neither Health PEI nor SSM Health holds SOC 2 Type 2 certification.

Neither Health PEI nor SSM Health holds ISO 27001 certification.

Neither Health PEI nor SSM Health holds PCI DSS certification.

Neither Health PEI nor SSM Health holds HIPAA certification.

Neither Health PEI nor SSM Health holds GDPR certification.

Latest Global CVEs (Not Company-Specific)

Description

Improper Authorization (CWE-285) in Kibana can lead to privilege escalation (CAPEC-233) by allowing an authenticated user to bypass intended permission restrictions via a crafted HTTP request. This allows an attacker who lacks the live queries - read permission to successfully retrieve the list of live queries.

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

Weblate is a web based localization tool. In versions prior to 5.15.1, it was possible to overwrite Git configuration remotely and override some of its behavior. Version 5.15.1 fixes the issue.

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

Allocation of Resources Without Limits or Throttling (CWE-770) in Elasticsearch can allow an authenticated user with snapshot restore privileges to cause Excessive Allocation (CAPEC-130) of memory and a denial of service (DoS) via crafted HTTP request.

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

Allocation of Resources Without Limits or Throttling (CWE-770) in Kibana can allow a low-privileged authenticated user to cause Excessive Allocation (CAPEC-130) of computing resources and a denial of service (DoS) of the Kibana process via a crafted HTTP request.

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

Improper neutralization of input during web page generation ('Cross-site Scripting') (CWE-79) allows an unauthenticated user to embed a malicious script in content that will be served to web browsers causing cross-site scripting (XSS) (CAPEC-63) via a vulnerability a function handler in the Vega AST evaluator.

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