Incident Score: Analysis & Impact (MAN1779856181)
The details regarding individual company incidents & reports gives you full view from every side.
Rankiteo Score Impact Analysis
Key Highlights From The Incident Analysis
- Timeline of Manage My 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 Manage My 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 Manage My Health breach identified under incident ID MAN1779856181.
The analysis begins with a detailed overview of Manage My Health's information like the linkedin page: https://www.linkedin.com/company/managemyhealth, the number of followers: 1216, the industry type: Wellness and Fitness Services and the number of employees: 23 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 484 and after the incident was 397 with a difference of -87 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 Manage My Health and their customers.
On 21 December 2023, ManageMyHealth disclosed Data Breach issues under the banner "New Zealand’s Largest Health Data Breach Exposes 99,000 Patients Due to Preventable Security Failures".
A preventable cyberattack on ManageMyHealth, a patient portal serving 1.8 million users across 680+ health centers, resulted in the theft of sensitive data belonging to 99,416 individuals, one of New Zealand’s most damaging health sector breaches.
The disruption is felt across the environment, affecting ManageMyHealth patient portal (My Health Documents section), and exposing Clinical notes, intimate imagery, passport scans, personally identifiable information, with nearly 99,416 records at risk.
In response, teams activated the incident response plan, moved swiftly to contain the threat with measures like Security upgrades implemented post-breach, and began remediation that includes Independent advisory board appointed; identity protection and mental health support offered to affected patients, and stakeholders are being briefed through Criticized as confused, overly optimistic, and inaccurate.
The case underscores how Ongoing (police investigation), teams are taking away lessons such as The breach highlighted systemic failures in cybersecurity preparedness, third-party supplier oversight, and patient notification protocols in New Zealand’s health sector, and recommending next steps like Mandatory penetration testing and external compliance assessments for ManageMyHealth, Stronger third-party supplier oversight by Health NZ, moving away from self-assessment models and Clearer protocols for patient notifications during breaches, with advisories going out to stakeholders covering Ministry of Health announced system-wide improvements and reforms.
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 high confidence (90%), supported by evidence indicating exploited a compromised user login and Exploit Public-Facing Application (T1190) with moderate to high confidence (80%), supported by evidence indicating weak API controls exploited to exfiltrate data. Under the Credential Access tactic, the analysis identified Brute Force (T1110) with moderate confidence (50%), supported by evidence indicating compromised user login (implied weak credentials) and Unsecured Credentials: Credentials in Files (T1552.006) with lower confidence (40%), supported by evidence indicating aPI vulnerabilities may have exposed credentials. Under the Lateral Movement tactic, the analysis identified Exploitation of Remote Services (T1210) with moderate to high confidence (70%), supported by evidence indicating aPI exploitation enabled access to sensitive data. Under the Collection tactic, the analysis identified Data from Local System (T1005) with high confidence (90%), supported by evidence indicating clinical notes, intimate imagery, passport scans compromised and Data from Information Repositories (T1213) with moderate to high confidence (80%), supported by evidence indicating data stolen from My Health Documents section. Under the Exfiltration tactic, the analysis identified Exfiltration Over C2 Channel (T1041) with moderate to high confidence (80%), supported by evidence indicating hacker exfiltrated data (99,416 records) and Exfiltration Over Web Service (T1567) with moderate to high confidence (70%), supported by evidence indicating aPI exploitation likely used for exfiltration. Under the Impact tactic, the analysis identified Data Encrypted for Impact (T1486) with lower confidence (30%), supported by evidence indicating ransom demand (US$60,000) implies potential encryption and Data Manipulation: Stored Data Manipulation (T1565.001) with lower confidence (40%), supported by evidence indicating patient notifications were confused and inaccurate. Under the Defense Evasion tactic, the analysis identified Valid Accounts (T1078) with moderate to high confidence (80%), supported by evidence indicating compromised user login used to bypass controls and Code Signing: Code Signing Policy Modification (T1553.006) with lower confidence (30%), supported by evidence indicating weak API controls may have allowed unauthorized access. These correlations help security teams understand the attack chain and develop appropriate defensive measures based on the observed tactics and techniques.
Sources & References
- Manage My Health Rankiteo Cyber Incident Details: https://www.rankiteo.com/company/managemyhealth/incident/MAN1779856181
- Manage My Health CyberSecurity Rating page: https://www.rankiteo.com/company/managemyhealth
- Manage My Health Rankiteo Cyber Incident Blog Article: https://blog.rankiteo.com/man1779856181-managemyhealth-breach-december-2025/
- Manage My Health CyberSecurity Score History: https://www.rankiteo.com/company/managemyhealth/history
- Manage My Health CyberSecurity Incident Source: https://www.1news.co.nz/2026/05/27/managemyhealth-warned-before-massive-data-breach-inquiry/
- Rankiteo A.I CyberSecurity Rating methodology: https://www.rankiteo.com/Images/rankiteo_algo.pdf
- Rankiteo TPRM Scoring methodology: https://static.rankiteo.com/model/rankiteo_tprm_methodology.pdf