Incident Score: Analysis & Impact (AUS1781591338)

In this Rankiteo incident briefing, we review the Australian Medical Council breach identified under incident ID AUS1781591338.

The analysis begins with a detailed overview of Australian Medical Council's information like the linkedin page: https://www.linkedin.com/company/australian-medical-council, the number of followers: 13715, the industry type: Non-profit Organizations and the number of employees: 244 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 763 and after the incident was 660 with a difference of -103 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 Australian Medical Council and their customers.

On 12 June 2024, Australian Medical Council (AMC) disclosed Ransomware issues under the banner "ThreeAM Ransomware Group Falsely Claims Australian Medical Council as Victim".

On 12 June, the ThreeAM ransomware group listed the Australian Medical Council (AMC) as one of a dozen victims on its darknet leak site.

The disruption is felt across the environment, and exposing Business processes, blank forms, correspondence.

In response, and stakeholders are being briefed through Public denial of breach and clarification of data ownership.

The case underscores how Ongoing (ACSC investigation), teams are taking away lessons such as Ransomware groups may misrepresent breaches or exaggerate the significance of stolen data. Organizations should verify claims and communicate transparently with stakeholders, and recommending next steps like Enhance monitoring for false breach claims, maintain clear communication with regulatory bodies, and ensure robust incident response plans to address misinformation, with advisories going out to stakeholders covering AMC clarified that it does not hold patient data and is not responsible for the leaked information.

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.