Comparison Overview

Marquette County Medical Care Facility

VS

St. Luke's Health System

Marquette County Medical Care Facility

200 Saginaw St, Ishpeming, 49849, US
Last Update: 2026-01-17
Between 700 and 749

The Marquette County Medical Care Facility provides a family oriented environment, where people both young and old can share their lives together. Whether you or your family member are in need of long-term care, or short-term recovery care, Marquette County Medical Care Facility is here to support your quality of life goals.

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

St. Luke's Health System

190 East Bannock Street, Boise, Idaho, US, 83712
Last Update: 2026-01-24
Between 700 and 749

As the only Idaho-based, not-for-profit health system, St. Luke’s Health System is dedicated to our mission “To improve the health of people in the communities we serve.” Today that means not only treating you when you’re sick or hurt, but doing everything we can to help you be as healthy as possible. Working together, we share resources, skills, and knowledge to provide the best possible care, no matter which of our hospitals you choose. Each St. Luke’s Health System hospital is nationally recognized for excellence in patient care, with prestigious awards and designations reflecting the exceptional care that is synonymous with the St. Luke's name.

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

Compliance Badges Comparison

Security & Compliance Standards Overview

https://images.rankiteo.com/companyimages/mcmcf.jpeg
Marquette County Medical Care Facility
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/stlukeshealthsystem.jpeg
St. Luke's Health 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
Marquette County Medical Care Facility
100%
Compliance Rate
0/4 Standards Verified
St. Luke's Health 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 Marquette County Medical Care Facility in 2026.

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

No incidents recorded for St. Luke's Health System in 2026.

Incident History — Marquette County Medical Care Facility (X = Date, Y = Severity)

Marquette County Medical Care Facility cyber incidents detection timeline including parent company and subsidiaries

Incident History — St. Luke's Health System (X = Date, Y = Severity)

St. Luke's Health System cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/mcmcf.jpeg
Marquette County Medical Care Facility
Incidents

Date Detected: 6/2025
Type:Breach
Attack Vector: Phishing
Blog: Blog
https://images.rankiteo.com/companyimages/stlukeshealthsystem.jpeg
St. Luke's Health System
Incidents

Date Detected: 5/2022
Type:Breach
Blog: Blog

FAQ

St. Luke's Health System company demonstrates a stronger AI Cybersecurity Score compared to Marquette County Medical Care Facility company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Marquette County Medical Care Facility and St. Luke's Health System have experienced a similar number of publicly disclosed cyber incidents.

In the current year, St. Luke's Health System company and Marquette County Medical Care Facility company have not reported any cyber incidents.

Neither St. Luke's Health System company nor Marquette County Medical Care Facility company has reported experiencing a ransomware attack publicly.

Both St. Luke's Health System company and Marquette County Medical Care Facility company have disclosed experiencing at least one data breach.

Neither St. Luke's Health System company nor Marquette County Medical Care Facility company has reported experiencing targeted cyberattacks publicly.

Neither Marquette County Medical Care Facility company nor St. Luke's Health System company has reported experiencing or disclosing vulnerabilities publicly.

Neither Marquette County Medical Care Facility nor St. Luke's Health System holds any compliance certifications.

Neither company holds any compliance certifications.

Neither Marquette County Medical Care Facility company nor St. Luke's Health System company has publicly disclosed detailed information about the number of their subsidiaries.

St. Luke's Health System company employs more people globally than Marquette County Medical Care Facility company, reflecting its scale as a Hospitals and Health Care.

Neither Marquette County Medical Care Facility nor St. Luke's Health System holds SOC 2 Type 1 certification.

Neither Marquette County Medical Care Facility nor St. Luke's Health System holds SOC 2 Type 2 certification.

Neither Marquette County Medical Care Facility nor St. Luke's Health System holds ISO 27001 certification.

Neither Marquette County Medical Care Facility nor St. Luke's Health System holds PCI DSS certification.

Neither Marquette County Medical Care Facility nor St. Luke's Health System holds HIPAA certification.

Neither Marquette County Medical Care Facility nor St. Luke's Health System holds GDPR certification.

Latest Global CVEs (Not Company-Specific)

Description

Typemill is a flat-file, Markdown-based CMS designed for informational documentation websites. A reflected Cross-Site Scripting (XSS) exists in the login error view template `login.twig` of versions 2.19.1 and below. The `username` value can be echoed back without proper contextual encoding when authentication fails. An attacker can execute script in the login page context. This issue has been fixed in version 2.19.2.

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

A DOM-based Cross-Site Scripting (XSS) vulnerability exists in the DomainCheckerApp class within domain/script.js of Sourcecodester Domain Availability Checker v1.0. The vulnerability occurs because the application improperly handles user-supplied data in the createResultElement method by using the unsafe innerHTML property to render domain search results.

Description

A Remote Code Execution (RCE) vulnerability exists in Sourcecodester Modern Image Gallery App v1.0 within the gallery/upload.php component. The application fails to properly validate uploaded file contents. Additionally, the application preserves the user-supplied file extension during the save process. This allows an unauthenticated attacker to upload arbitrary PHP code by spoofing the MIME type as an image, leading to full system compromise.

Description

A UNIX symbolic link following issue in the jailer component in Firecracker version v1.13.1 and earlier and 1.14.0 on Linux may allow a local host user with write access to the pre-created jailer directories to overwrite arbitrary host files via a symlink attack during the initialization copy at jailer startup, if the jailer is executed with root privileges. To mitigate this issue, users should upgrade to version v1.13.2 or 1.14.1 or above.

Risk Information
cvss3
Base: 6.0
Severity: LOW
CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:N/I:H/A:H
cvss4
Base: 6.0
Severity: LOW
CVSS:4.0/AV:L/AC:L/AT:N/PR:H/UI:N/VC:N/VI:N/VA:N/SC:N/SI:H/SA:H/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

An information disclosure vulnerability exists in the /srvs/membersrv/getCashiers endpoint of the Aptsys gemscms backend platform thru 2025-05-28. This unauthenticated endpoint returns a list of cashier accounts, including names, email addresses, usernames, and passwords hashed using MD5. As MD5 is a broken cryptographic function, the hashes can be easily reversed using public tools, exposing user credentials in plaintext. This allows remote attackers to perform unauthorized logins and potentially gain access to sensitive POS operations or backend functions.