Rankiteo Logo
Rankiteo
Leader in Cyber Underwriting
Loading...
NEWRankiteo Cyber Underwriting Desktop - Score, price, and bind from your desktop
WindowsmacOSLinux
Download
Analyze » Deaconess Health System » DEAMED1773945852

Incident Score: Analysis & Impact (DEAMED1773945852)

The details regarding individual company incidents & reports gives you full view from every side.

Rankiteo Score Impact Analysis

Rankiteo Incident Impact-56
Company Score Before Incident742 / 1000
Company Score After Incident686 / 1000
INCIDENT NUMBERDEAMED1773945852
Type of Cyber IncidentBreach
ATTACK VECTORUnauthorized access to cloud-based file-sharing platform
DATA EXPOSEDSensitive patient information
INCIDENT DATE12/01/2026
STATUSOngoing (investigated by Shamis & Gentile P.A.)

Key Highlights From The Incident Analysis

  • Timeline of Deaconess Health System's Breach and lateral movement inside company's environment.
  • Overview of affected data sets, including SSNs and PHI, and why they materially increase incident severity.
  • How Rankiteo’s incident engine converts technical details into a normalized incident score.
  • How this cyber incident impacts Deaconess Health System Rankiteo cyber scoring and cyber rating.
  • Rankiteo’s MITRE ATT&CK correlation analysis for this incident, with associated confidence level.

Full Incident Analysis Transcript

In this Rankiteo incident briefing, we review the Deaconess Health System breach identified under incident ID DEAMED1773945852.

The analysis begins with a detailed overview of Deaconess Health System's information like the linkedin page: https://www.linkedin.com/company/deaconess-health-system, the number of followers: 15748, the industry type: Hospitals and Health Care and the number of employees: 4101 employees

After the initial compromise, the video explains how Rankiteo's incident engine converts technical details into a normalized incident score. The incident score before the incident was 742 and after the incident was 686 with a difference of -56 which is could be a good indicator of the severity and impact of the incident.

In the next step of the video, we will analyze in more details the incident and the impact it had on Deaconess Health System and their customers.

On 02 February 2026, MediCopy (MRO Corp.) disclosed Data Breach issues under the banner "MediCopy Data Breach Exposes Sensitive Patient Information".

In February 2026, MediCopy, a health information management company specializing in secure data release for healthcare providers, reported a data breach affecting patients of Deaconess Health System.

The disruption is felt across the environment, affecting MediCopy’s cloud-based file-sharing platform, and exposing Sensitive patient information.

Formal response steps have not been shared publicly yet.

The case underscores how Ongoing (investigated by Shamis & Gentile P.A.).

Finally, we try to match the incident with the MITRE ATT&CK framework to see if there is any correlation between the incident and the MITRE ATT&CK framework.

The MITRE ATT&CK framework is a knowledge base of techniques and sub-techniques that are used to describe the tactics and procedures of cyber adversaries. It is a powerful tool for understanding the threat landscape and for developing effective defense strategies.

MITRE ATT&CK® Correlation Analysis

Rankiteo's analysis has identified several MITRE ATT&CK tactics and techniques associated with this incident, each with varying levels of confidence based on available evidence. Under the Initial Access tactic, the analysis identified Exploit Public-Facing Application (T1190) with moderate confidence (60%), supported by evidence indicating unauthorized actor accessing MediCopy’s cloud-based file-sharing platform and Valid Accounts (T1078) with moderate confidence (50%), supported by evidence indicating cloud-based file-sharing platform accessed by unauthorized actor. Under the Credential Access tactic, the analysis identified Steal Application Access Token (T1528) with moderate confidence (60%), supported by evidence indicating unauthorized access to cloud-based file-sharing platform and Brute Force (T1110) with lower confidence (40%), supported by evidence indicating no details on how unauthorized access was obtained. Under the Collection tactic, the analysis identified Data from Local System (T1005) with moderate to high confidence (80%), supported by evidence indicating names, SSNs, medical records, health insurance IDs compromised and Data from Information Repositories (T1213) with high confidence (90%), supported by evidence indicating files downloaded from cloud-based file-sharing platform. Under the Exfiltration tactic, the analysis identified Exfiltration Over C2 Channel (T1041) with moderate to high confidence (70%), supported by evidence indicating unauthorized actor downloading files from cloud platform and Transfer Data to Cloud Account (T1537) with moderate confidence (60%), supported by evidence indicating data exfiltration via cloud-based file-sharing platform. Under the Impact tactic, the analysis identified Data Destruction (T1485) with lower confidence (30%), supported by evidence indicating no evidence of data destruction, but high-risk data exposed and Stored Data Manipulation (T1565.001) with lower confidence (40%), supported by evidence indicating potential manipulation of medical records in cloud platform. These correlations help security teams understand the attack chain and develop appropriate defensive measures based on the observed tactics and techniques.

Initial Access
Exploit Public-Facing Application (60%)
Valid Accounts (50%)
Credential Access
Steal Application Access Token (60%)
Brute Force (40%)
Collection
Data from Local System (80%)
Data from Information Repositories (90%)
Exfiltration
Exfiltration Over C2 Channel (70%)
Transfer Data to Cloud Account (60%)
Impact
Data Destruction (30%)
Stored Data Manipulation (40%)

Sources & References