Comparison Overview

St. Lawrence Health

VS

University of Maryland Medical System

St. Lawrence Health

50 Leroy Street, Potsdam, New York, US, 13676
Last Update: 2025-12-09

St. Lawrence Health (SLH) was established in December 2013 with the mission to improve health and to expand access through coordination and integration of services. Canton-Potsdam Hospital, Potsdam; Gouverneur Hospital, Gouverneur; and Massena Hospital, Massena, operate under the umbrella of St. Lawrence Health. SLH became an affiliate of Rochester Regional Health (RRH) in January 2021. RRH is an internationally recognized integrated health services organization, and its industry distinctions include year-after-year Healthgrades awards, America’s 50 Best Hospitals™, multiple Magnet® Awards for nursing excellence, and the greatest number of Beacon Awards for Excellence of any hospital system in the nation. Canton-Potsdam Hospital (CPH) is a not-for-profit community hospital certified for 94 beds. Its core programs in emergency medicine, acute care, hospitalist medicine, critical care, and a Level III Trauma Center are supplemented by outpatient health services in Brasher Falls, Canton, Colton, Massena, Norfolk, Norwood, and Potsdam, NY. CPH offers specialty care in over 35 different specialties, including a robust orthopedic surgery and sports medicine program, and the Center for Cancer Care. Gouverneur Hospital, located in its namesake city in Northern New York, is a not-for-profit critical access hospital founded in 2013 and certified for 25 beds. Services include inpatient detox, substance use disorder rehabilitation, behavioral health services, emergency care, imaging and EKGs, physical rehabilitation, and respiratory therapy. Massena Hospital is a 25-bed community hospital providing inpatient, medical, and surgical services in addition to emergency care. MH’s main campus also provides imaging and laboratory services, nutritional counseling, respiratory care, and inpatient physical and speech therapies. cardiology, infusion, nephrology, neurology, OB-GYN and women’s health, pediatrics, and primary care.

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

University of Maryland Medical System

22 S. Greene St, Baltimore, MD, US, 21201
Last Update: 2025-12-09
Between 750 and 799

The University of Maryland Medical System (UMMS) was created in 1984 when the state-owned University Hospital became a private, nonprofit organization. It has evolved into a multi-hospital system with academic, community and specialty service missions reaching every part of the state and beyond. UMMS is a national and regional referral center for trauma, cancer care, neurocare, cardiac care, women's and children's health and physical rehabilitation. It also has one of the world's largest kidney transplant programs, as well as scores of other programs that improve the physical and mental health of thousands of people daily. The hospitals and health systems that comprise UMMS are: University of Maryland Medical Center University of Maryland Medical Center Midtown Campus UM Rehabilitation and Orthopaedic Institute UM Baltimore Washington Medical Center UM Capital Region Health UM Charles Regional Medical Center UM St. Joseph Medical Center UM Upper Chesapeake Health UM Shore Regional Health Mt. Washington Pediatric Hospital UM Community Medical Group

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

Compliance Badges Comparison

Security & Compliance Standards Overview

https://images.rankiteo.com/companyimages/st-lawrence-health.jpeg
St. Lawrence 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/ummedicalsystem.jpeg
University of Maryland Medical 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
St. Lawrence Health
100%
Compliance Rate
0/4 Standards Verified
University of Maryland Medical 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 St. Lawrence Health in 2025.

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

No incidents recorded for University of Maryland Medical System in 2025.

Incident History — St. Lawrence Health (X = Date, Y = Severity)

St. Lawrence Health cyber incidents detection timeline including parent company and subsidiaries

Incident History — University of Maryland Medical System (X = Date, Y = Severity)

University of Maryland Medical System cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/st-lawrence-health.jpeg
St. Lawrence Health
Incidents

Date Detected: 10/2020
Type:Ransomware
Blog: Blog
https://images.rankiteo.com/companyimages/ummedicalsystem.jpeg
University of Maryland Medical System
Incidents

No Incident

FAQ

University of Maryland Medical System company demonstrates a stronger AI Cybersecurity Score compared to St. Lawrence Health company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

St. Lawrence Health company has historically faced a number of disclosed cyber incidents, whereas University of Maryland Medical System company has not reported any.

In the current year, University of Maryland Medical System company and St. Lawrence Health company have not reported any cyber incidents.

St. Lawrence Health company has confirmed experiencing a ransomware attack, while University of Maryland Medical System company has not reported such incidents publicly.

Neither University of Maryland Medical System company nor St. Lawrence Health company has reported experiencing a data breach publicly.

Neither University of Maryland Medical System company nor St. Lawrence Health company has reported experiencing targeted cyberattacks publicly.

Neither St. Lawrence Health company nor University of Maryland Medical System company has reported experiencing or disclosing vulnerabilities publicly.

Neither St. Lawrence Health nor University of Maryland Medical System holds any compliance certifications.

Neither company holds any compliance certifications.

St. Lawrence Health company has more subsidiaries worldwide compared to University of Maryland Medical System company.

University of Maryland Medical System company employs more people globally than St. Lawrence Health company, reflecting its scale as a Hospitals and Health Care.

Neither St. Lawrence Health nor University of Maryland Medical System holds SOC 2 Type 1 certification.

Neither St. Lawrence Health nor University of Maryland Medical System holds SOC 2 Type 2 certification.

Neither St. Lawrence Health nor University of Maryland Medical System holds ISO 27001 certification.

Neither St. Lawrence Health nor University of Maryland Medical System holds PCI DSS certification.

Neither St. Lawrence Health nor University of Maryland Medical System holds HIPAA certification.

Neither St. Lawrence Health nor University of Maryland Medical System 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