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

Incident Score: Analysis & Impact (CAN1768202785)

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

Rankiteo Score Impact Analysis

Rankiteo Incident Impact-163
Company Score Before Incident759 / 1000
Company Score After Incident596 / 1000
INCIDENT NUMBERCAN1768202785
Type of Cyber IncidentBreach
ATTACK VECTORUnauthorized Access
DATA EXPOSEDBank account numbers, personal health...
INCIDENT DATE17/07/2025
STATUSOngoing

Key Highlights From The Incident Analysis

  • Timeline of Canopy Health'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 Canopy Health 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 Canopy Health breach identified under incident ID CAN1768202785.

The analysis begins with a detailed overview of Canopy Health's information like the linkedin page: https://www.linkedin.com/company/canopy-health, the number of followers: 4868, the industry type: Hospitals and Health Care and the number of employees: 33 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 759 and after the incident was 596 with a difference of -163 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 Canopy Health and their customers.

On 18 July 2025, Canopy Health disclosed Data Breach issues under the banner "Canopy Health Cyber Intrusion and Data Breach".

Canopy Health suffered a cyber intrusion that went undisclosed to patients for six months.

The disruption is felt across the environment, affecting Internal administration systems, servers, and exposing Bank account numbers, personal health information.

In response, teams activated the incident response plan, moved swiftly to contain the threat with measures like Incident contained, and stakeholders are being briefed through Delayed notifications to affected individuals, website updates.

The case underscores how Ongoing, teams are taking away lessons such as Delayed communication erodes patient trust; need for improved transparency and data security measures in healthcare, and recommending next steps like Implement stricter data protection protocols, ensure timely breach notifications, enhance monitoring of internal systems, and improve communication strategies with affected individuals, with advisories going out to stakeholders covering Patients advised to contact their banks if concerned about financial information exposure.

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 Valid Accounts (T1078) with moderate to high confidence (70%), supported by evidence indicating unauthorized access to its internal administrative systems and Exploit Public-Facing Application (T1190) with moderate confidence (50%), supported by evidence indicating cyber intrusion...internal administrative systems. Under the Persistence tactic, the analysis identified Valid Accounts (T1078) with moderate confidence (60%), supported by evidence indicating hackers likely copied data from one of its servers. Under the Credential Access tactic, the analysis identified Unsecured Credentials (T1552) with moderate confidence (60%), supported by evidence indicating internal administrative systems accessed unauthorized. Under the Collection tactic, the analysis identified Data from Local System (T1005) with moderate to high confidence (80%), supported by evidence indicating hackers likely copied data from one of its servers and Data from Information Repositories (T1213) with moderate to high confidence (70%), supported by evidence indicating bank account numbers, personal health information compromised. Under the Exfiltration tactic, the analysis identified Exfiltration Over C2 Channel (T1041) with moderate to high confidence (70%), supported by evidence indicating hackers likely copied data from one of its servers. Under the Impact tactic, the analysis identified Data Destruction (T1485) with lower confidence (30%), supported by evidence indicating full scope remains under review and Defacement (T1491) with lower confidence (40%), supported by evidence indicating website later acknowledged...accessed bank account numbers. Under the Defense Evasion tactic, the analysis identified Indicator Removal (T1070) with moderate confidence (60%), supported by evidence indicating breach was first detected on 18 July 2025, undisclosed for six months. These correlations help security teams understand the attack chain and develop appropriate defensive measures based on the observed tactics and techniques.

Initial Access
Valid Accounts (70%)
Exploit Public-Facing Application (50%)
Persistence
Valid Accounts (60%)
Credential Access
Unsecured Credentials (60%)
Collection
Data from Local System (80%)
Data from Information Repositories (70%)
Exfiltration
Exfiltration Over C2 Channel (70%)
Impact
Data Destruction (30%)
Defacement (40%)
Defense Evasion
Indicator Removal (60%)

Sources & References