Comparison Overview

Select Health Network

VS

SSM Health

Select Health Network

314 W Catalpa Dr, Mishawaka, Indiana, 46545, US
Last Update: 2025-12-27

Select Health Network is a Physician Hospital Organization which began operations in 1994 and provides a comprehensive physician network in St. Joseph and Marshall Counties, Indiana. In total, Select Health Network offers access to over 770 providers including specialists, primary care physicians and mid-level providers.

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

SSM Health

10101 Woodfield Ln, St Louis, Missouri, US, 63132
Last Update: 2025-12-25
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/selecthealthnetwork.jpeg
Select Health Network
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
Select Health Network
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 Select Health Network in 2025.

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

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

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

Select Health Network 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/selecthealthnetwork.jpeg
Select Health Network
Incidents

Date Detected: 5/2019
Type:Data Leak
Attack Vector: Email Account Compromise
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

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

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

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

Neither SSM Health company nor Select Health Network company has reported experiencing a ransomware attack publicly.

SSM Health company has disclosed at least one data breach, while Select Health Network company has not reported such incidents publicly.

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

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

Neither Select Health Network nor SSM Health holds any compliance certifications.

Neither company holds any compliance certifications.

Neither Select Health Network company nor SSM Health company has publicly disclosed detailed information about the number of their subsidiaries.

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

Neither Select Health Network nor SSM Health holds SOC 2 Type 1 certification.

Neither Select Health Network nor SSM Health holds SOC 2 Type 2 certification.

Neither Select Health Network nor SSM Health holds ISO 27001 certification.

Neither Select Health Network nor SSM Health holds PCI DSS certification.

Neither Select Health Network nor SSM Health holds HIPAA certification.

Neither Select Health Network nor SSM Health holds GDPR certification.

Latest Global CVEs (Not Company-Specific)

Description

In GnuPG through 2.4.8, if a signed message has \f at the end of a plaintext line, an adversary can construct a modified message that places additional text after the signed material, such that signature verification of the modified message succeeds (although an "invalid armor" message is printed during verification). This is related to use of \f as a marker to denote truncation of a long plaintext line.

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

A vulnerability has been found in jackq XCMS up to 3fab5342cc509945a7ce1b8ec39d19f701b89261. Affected is the function Upload of the file Admin/Home/Controller/ProductImageController.class.php of the component Backend. Such manipulation of the argument File leads to unrestricted upload. It is possible to launch the attack remotely. The exploit has been disclosed to the public and may be used. This product takes the approach of rolling releases to provide continious delivery. Therefore, version details for affected and updated releases are not available. The project was informed of the problem early through an issue report but has not responded yet.

Risk Information
cvss2
Base: 5.8
Severity: LOW
AV:N/AC:L/Au:M/C:P/I:P/A:P
cvss3
Base: 4.7
Severity: LOW
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:L/A:L
cvss4
Base: 5.1
Severity: LOW
CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:L/VI:L/VA:L/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

In PHP versions 8.1.* before 8.1.34, 8.2.* before 8.2.30, 8.3.* before 8.3.29, 8.4.* before 8.4.16, 8.5.* before 8.5.1 when using the PDO PostgreSQL driver with PDO::ATTR_EMULATE_PREPARES enabled, an invalid character sequence (such as \x99) in a prepared statement parameter may cause the quoting function PQescapeStringConn to return NULL, leading to a null pointer dereference in pdo_parse_params() function. This may lead to crashes (segmentation fault) and affect the availability of the target server.

Risk Information
cvss4
Base: 8.2
Severity: HIGH
CVSS:4.0/AV:N/AC:H/AT:P/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

In PHP versions:8.1.* before 8.1.34, 8.2.* before 8.2.30, 8.3.* before 8.3.29, 8.4.* before 8.4.16, 8.5.* before 8.5.1, a heap buffer overflow occurs in array_merge() when the total element count of packed arrays exceeds 32-bit limits or HT_MAX_SIZE, due to an integer overflow in the precomputation of element counts using zend_hash_num_elements(). This may lead to memory corruption or crashes and affect the integrity and availability of the target server.

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

In PHP versions:8.1.* before 8.1.34, 8.2.* before 8.2.30, 8.3.* before 8.3.29, 8.4.* before 8.4.16, 8.5.* before 8.5.1, the getimagesize() function may leak uninitialized heap memory into the APPn segments (e.g., APP1) when reading images in multi-chunk mode (such as via php://filter). This occurs due to a bug in php_read_stream_all_chunks() that overwrites the buffer without advancing the pointer, leaving tail bytes uninitialized. This may lead to information disclosure of sensitive heap data and affect the confidentiality of the target server.

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