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

Incident Score: Analysis & Impact (MYD1786983836)

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

Rankiteo Score Impact Analysis

Rankiteo Incident Impact-51
Company Score Before Incident766 / 1000
Company Score After Incident715 / 1000
Company LinkView MyDr Profile
INCIDENT NUMBERMYD1786983836
Type of Cyber IncidentCyber Attack
ATTACK VECTORNA
DATA EXPOSEDNames, dates of birth, identification...
INCIDENT DATE31/03/2024
STATUSOngoing

Key Highlights From The Incident Analysis

  • Timeline of MyDr's Cyber Attack 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 MyDr 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 MyDr breach identified under incident ID MYD1786983836.

The analysis begins with a detailed overview of MyDr's information like the linkedin page: https://www.linkedin.com/company/mydredm, the number of followers: 2036, the industry type: Technology, Information and Internet and the number of employees: 55 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 766 and after the incident was 715 with a difference of -51 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 MyDr and their customers.

On 07 June 2024, MyDr disclosed Data Breach issues under the banner "Polish Healthcare Software Provider MyDr Hit by Cyberattack Affecting Millions".

Polish authorities are investigating a cyberattack on MyDr, a healthcare software provider, that may have exposed data belonging to nearly 19 million people and over 12,000 medical facilities.

The disruption is felt across the environment, affecting MyDr’s healthcare software systems, integration with Poland’s e-health platform (P1), and exposing Names, dates of birth, identification numbers, prescription details, medical records, with nearly Nearly 19 million people records at risk.

In response, teams activated the incident response plan, moved swiftly to contain the threat with measures like Mitigated the incident, implemented additional security measures, and began remediation that includes Replacement of digital certificates for medical systems connecting to P1, and stakeholders are being briefed through Public disclosure, assurances from Health Minister.

The case underscores how Ongoing, with advisories going out to stakeholders covering Health Minister assured no threat to public healthcare systems; Digital Affairs Minister warned of potential legal consequences.

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 confidence (60%), supported by evidence indicating unauthorized access to historical data stored in MyDr’s systems and Exploit Public-Facing Application (T1190) with moderate confidence (50%), supported by evidence indicating myDr supplies software to doctors, clinics, and healthcare providers. Under the Credential Access tactic, the analysis identified Unsecured Credentials (T1552) with moderate to high confidence (70%), supported by evidence indicating digital certificates for medical systems connecting to P1 replaced as precaution and OS Credential Dumping (T1003) with moderate confidence (50%), supported by evidence indicating unauthorized access to historical data up to April 2024. Under the Collection tactic, the analysis identified Data from Local System (T1005) with high confidence (90%), supported by evidence indicating names, dates of birth, identification numbers, prescription details, medical records. Under the Exfiltration tactic, the analysis identified Exfiltration Over C2 Channel (T1041) with moderate to high confidence (80%), supported by evidence indicating nearly 19 million people and over 12,000 medical facilities affected and Exfiltration Over Web Service (T1567) with moderate confidence (60%), supported by evidence indicating unverified claims of data being offered; screenshot of data linked to politician. Under the Impact tactic, the analysis identified Data Destruction (T1485) with lower confidence (40%), supported by evidence indicating external, intentional criminal activity described and Data Manipulation: Stored Data Manipulation (T1565.001) with lower confidence (30%), supported by evidence indicating integration with Poland’s nationwide e-health platform (P1). Under the Defense Evasion tactic, the analysis identified Valid Accounts (T1078) with moderate to high confidence (70%), supported by evidence indicating attackers gained access but no disclosure on how and Hide Artifacts (T1564) with moderate confidence (50%), supported by evidence indicating no evidence that the stolen data had been published. 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 (60%)
Exploit Public-Facing Application (50%)
Credential Access
Unsecured Credentials (70%)
OS Credential Dumping (50%)
Collection
Data from Local System (90%)
Exfiltration
Exfiltration Over C2 Channel (80%)
Exfiltration Over Web Service (60%)
Impact
Data Destruction (40%)
Data Manipulation: Stored Data Manipulation (30%)
Defense Evasion
Valid Accounts (70%)
Hide Artifacts (50%)

Sources & References