Incident Score: Analysis & Impact (REG1781807543)
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 Regent'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 Regent 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 Regent breach identified under incident ID REG1781807543.
The analysis begins with a detailed overview of Regent's information like the linkedin page: https://www.linkedin.com/company/regent-global, the number of followers: 3829, the industry type: Education and the number of employees: 82 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 772 and after the incident was 672 with a difference of -100 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 Regent and their customers.
Global Schools Group (GSG) recently reported "Global Schools Group Suffers Massive Data Breach Exposing 183,000+ Accounts", a noteworthy cybersecurity incident.
A recent cyberattack on Global Schools Group (GSG), a network of international schools, has exposed sensitive data belonging to over 183,000 students, parents, and staff across 12 school brands.
The disruption is felt across the environment, and exposing 183,000+ accounts (students, parents, staff), 9.4 million internal messages, 8.6 million attendance records, 122,862 Twilio SMS messages, 112 source code repositories, 168 AWS secrets, 46,901 job applicant document folders, with nearly 183,000+ accounts records at risk.
Formal response steps have not been shared publicly yet.
The case underscores how teams are taking away lessons such as Poor security practices (plaintext passwords, default passwords, lack of encryption, no access restrictions or detection mechanisms) led to a massive data breach with high-risk exposure of sensitive information, and recommending next steps like Implement encryption for sensitive data, Enforce strong password policies and eliminate default passwords and Restrict access to sensitive systems and data.
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 teacher/staff authentication database stored 12,303 passwords in plaintext and Valid Accounts: Default Accounts (T1078.001) with high confidence (95%), supported by evidence indicating 12,301 using the default password giis123. Under the Credential Access tactic, the analysis identified Credentials from Password Stores (T1555) with high confidence (90%), supported by evidence indicating plaintext password storage...allowed attackers to extract data undetected and Brute Force: Password Cracking (T1110.002) with moderate to high confidence (70%), supported by evidence indicating default password giis123 used for 12,301 accounts. Under the Discovery tactic, the analysis identified Account Discovery (T1087) with moderate to high confidence (80%), supported by evidence indicating 83,132 student accounts, 88,856 parent accounts, 11,176 staff accounts exposed and File and Directory Discovery (T1083) with moderate to high confidence (80%), supported by evidence indicating 9.4M internal messages, 8.6M attendance records, 112 source code repos exfiltrated. Under the Collection tactic, the analysis identified Data from Local System (T1005) with high confidence (90%), supported by evidence indicating passport numbers, government IDs, family PII, 9.4M internal messages collected and Data from Information Repositories (T1213) with moderate to high confidence (85%), supported by evidence indicating 112 source code repositories and 46,901 job applicant folders exfiltrated. Under the Exfiltration tactic, the analysis identified Exfiltration Over C2 Channel (T1041) with high confidence (90%), supported by evidence indicating data breach exposing 183,000+ accounts and 9.4M internal messages and Transfer Data to Cloud Account (T1537) with moderate to high confidence (70%), supported by evidence indicating 168 AWS secrets exfiltrated, suggesting cloud data transfer. Under the Defense Evasion tactic, the analysis identified Impair Defenses: Disable or Modify Tools (T1562.001) with moderate to high confidence (80%), supported by evidence indicating lack of encryption, access restrictions, or detection mechanisms and Valid Accounts: Local Accounts (T1078.003) with moderate to high confidence (85%), supported by evidence indicating plaintext passwords and default credentials allowed undetected access. Under the Impact tactic, the analysis identified Data Destruction (T1485) with lower confidence (40%), supported by evidence indicating no evidence of destruction, but massive exfiltration occurred and Data Manipulation: Stored Data Manipulation (T1565.001) with lower confidence (30%), supported by evidence indicating no evidence of manipulation, but data integrity at risk. These correlations help security teams understand the attack chain and develop appropriate defensive measures based on the observed tactics and techniques.
Sources & References
- Regent Rankiteo Cyber Incident Details: https://www.rankiteo.com/company/regent-global/incident/REG1781807543
- Regent CyberSecurity Rating page: https://www.rankiteo.com/company/regent-global
- Regent Rankiteo Cyber Incident Blog Article: https://blog.rankiteo.com/reg1781807543-regent-international-school-breach-january-2025/
- Regent CyberSecurity Score History: https://www.rankiteo.com/company/regent-global/history
- Regent CyberSecurity Incident Source: https://databreaches.net/2026/06/18/data-analysis-of-the-global-schools-group-breach-part-2/
- 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