Comparison Overview

St. John's Riverside Hospital

VS

University of Maryland Medical System

St. John's Riverside Hospital

967 North Broadway, Yonkers, 10701, US
Last Update: 2026-01-20

St. John's Riverside Hospital is a leader in providing the highest quality, compassionate health care utilizing the latest, state-of-the-art medical technology. Serving Yonkers to the Rivertown communities of Hastings-on-Hudson, Ardsley, Dobbs Ferry and Irvington, St. John's Riverside has been and continues to be a unique and comprehensive network of medical professionals dedicated to a tradition of service that spans generations. •superior medical care •dedicated nursing staff •the latest in medical technology and minimally invasive surgeries •highly skilled surgeons, doctors, technicians and counselors •the best in preventative medicine Here at St. John’s, we are committed to making life better for our patients. Our community and lifestyles have gone through many changes and likewise St. John's has evolved in response to these changes. We continue to elevate the services we provide with the goal of increasing the quality of life for all who entrust St. John's Riverside Hospital to their care. St. John's most recent developments have result in: •expedited admission time •expanded and improved emergency rooms and wait times •new, private maternity suites •the addition of industry-leading specialists in all areas of medicine and surgery We've been an integral part of your community since the 1869 and our commitment to provide you with the most advanced medical services available continues to be St. John's vision, mission and value. St. John's Riverside Hospital built itself around an early foundation of nursing and community service. In 1894, the Cochran School of Nursing, the oldest hospital-based school of nursing in the metropolitan area, was founded, thus making the St. John's Nursing Staff more than just the backbone of the hospital, but the heart and soul. Our dedicated nurses give superior attention to those who need it most with a strong emphasis on patient and family-focused nursing care.

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

University of Maryland Medical System

22 S. Greene St, Baltimore, 21201, US
Last Update: 2026-01-17
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,422
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.-john's-riverside-hospital.jpeg
St. John's Riverside Hospital
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. John's Riverside Hospital
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. John's Riverside Hospital in 2026.

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

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

Incident History — St. John's Riverside Hospital (X = Date, Y = Severity)

St. John's Riverside Hospital 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.-john's-riverside-hospital.jpeg
St. John's Riverside Hospital
Incidents

Date Detected: 11/2025
Type:Breach
Attack Vector: Phishing
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. John's Riverside Hospital company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

St. John's Riverside Hospital 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. John's Riverside Hospital company have not reported any cyber incidents.

Neither University of Maryland Medical System company nor St. John's Riverside Hospital company has reported experiencing a ransomware attack publicly.

St. John's Riverside Hospital company has disclosed at least one data breach, while the other University of Maryland Medical System company has not reported such incidents publicly.

Neither University of Maryland Medical System company nor St. John's Riverside Hospital company has reported experiencing targeted cyberattacks publicly.

Neither St. John's Riverside Hospital company nor University of Maryland Medical System company has reported experiencing or disclosing vulnerabilities publicly.

Neither St. John's Riverside Hospital nor University of Maryland Medical System holds any compliance certifications.

Neither company holds any compliance certifications.

University of Maryland Medical System company has more subsidiaries worldwide compared to St. John's Riverside Hospital company.

University of Maryland Medical System company employs more people globally than St. John's Riverside Hospital company, reflecting its scale as a Hospitals and Health Care.

Neither St. John's Riverside Hospital nor University of Maryland Medical System holds SOC 2 Type 1 certification.

Neither St. John's Riverside Hospital nor University of Maryland Medical System holds SOC 2 Type 2 certification.

Neither St. John's Riverside Hospital nor University of Maryland Medical System holds ISO 27001 certification.

Neither St. John's Riverside Hospital nor University of Maryland Medical System holds PCI DSS certification.

Neither St. John's Riverside Hospital nor University of Maryland Medical System holds HIPAA certification.

Neither St. John's Riverside Hospital nor University of Maryland Medical System holds GDPR certification.

Latest Global CVEs (Not Company-Specific)

Description

Improper validation of specified type of input in M365 Copilot allows an unauthorized attacker to disclose information over a network.

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

Improper access control in Azure Front Door (AFD) allows an unauthorized attacker to elevate privileges over a network.

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

Azure Entra ID Elevation of Privilege Vulnerability

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

Moonraker is a Python web server providing API access to Klipper 3D printing firmware. In versions 0.9.3 and below, instances configured with the "ldap" component enabled are vulnerable to LDAP search filter injection techniques via the login endpoint. The 401 error response message can be used to determine whether or not a search was successful, allowing for brute force methods to discover LDAP entries on the server such as user IDs and user attributes. This issue has been fixed in version 0.10.0.

Risk Information
cvss4
Base: 2.7
Severity: LOW
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:U/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

Runtipi is a Docker-based, personal homeserver orchestrator that facilitates multiple services on a single server. Versions 3.7.0 and above allow an authenticated user to execute arbitrary system commands on the host server by injecting shell metacharacters into backup filenames. The BackupManager fails to sanitize the filenames of uploaded backups. The system persists user-uploaded files directly to the host filesystem using the raw originalname provided in the request. This allows an attacker to stage a file containing shell metacharacters (e.g., $(id).tar.gz) at a predictable path, which is later referenced during the restore process. The successful storage of the file is what allows the subsequent restore command to reference and execute it. This issue has been fixed in version 4.7.0.

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