Incident Score: Analysis & Impact (SIMLOBROGARDTEL1785321665)
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 TELUS'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 TELUS 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 TELUS breach identified under incident ID SIMLOBROGARDTEL1785321665.
The analysis begins with a detailed overview of TELUS's information like the linkedin page: https://www.linkedin.com/company/telus, the number of followers: 442319, the industry type: Telecommunications and the number of employees: 38811 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 757 and after the incident was 658 with a difference of -99 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 TELUS and their customers.
Rogers recently reported "Canadian Data Breaches Hit Record Costs as AI Emerges as a Key Defense", a noteworthy cybersecurity incident.
Canadian companies faced rising financial and operational fallout from data breaches in 2026, with average costs climbing to $7.11 million per incident.
The disruption is felt across the environment, and exposing 28,500 records (average), with nearly 28,500 (average) records at risk, plus an estimated financial loss of $7.11 million per incident (average).
Formal response steps have not been shared publicly yet.
The case underscores how teams are taking away lessons such as AI is a critical tool in mitigating breaches, reducing costs and response times. However, AI-generated attacks are also on the rise, and recommending next steps like Adopt AI extensively in security operations to lower breach costs and improve response times.
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 Exploit Public-Facing Application (T1190) with moderate confidence (60%), supported by evidence indicating complex networks, sensitive data, and low tolerance for downtime and Valid Accounts (T1078) with moderate to high confidence (70%), supported by evidence indicating breaches exposed an average of 28,500 records. Under the Credential Access tactic, the analysis identified Brute Force (T1110) with moderate confidence (50%), supported by evidence indicating 28% of attacks believed to be AI-generated and Unsecured Credentials (T1552) with moderate confidence (60%), supported by evidence indicating complex networks, sensitive data in energy/tech sectors. Under the Collection tactic, the analysis identified Data from Local System (T1005) with moderate to high confidence (80%), supported by evidence indicating 28,500 records exposed per breach (average). Under the Exfiltration tactic, the analysis identified Exfiltration Over C2 Channel (T1041) with moderate to high confidence (70%), supported by evidence indicating breaches took 205 days to detect and contain and Transfer Data to Cloud Account (T1537) with moderate confidence (50%), supported by evidence indicating aI-generated attacks (28% of cases). Under the Impact tactic, the analysis identified Data Destruction (T1485) with lower confidence (40%), supported by evidence indicating business disruption, recovery efforts, legal obligations and Data Encrypted for Impact (T1486) with lower confidence (30%), supported by evidence indicating aI-generated attacks may involve encryption. Under the Defense Evasion tactic, the analysis identified Valid Accounts (T1078) with moderate to high confidence (70%), supported by evidence indicating 205 days to detect and contain breaches and Impair Defenses: Disable or Modify Tools (T1562.001) with moderate confidence (50%), supported by evidence indicating aI used in 28% of attacks to evade detection. These correlations help security teams understand the attack chain and develop appropriate defensive measures based on the observed tactics and techniques.
Sources & References
- TELUS Rankiteo Cyber Incident Details: https://www.rankiteo.com/company/telus/incident/SIMLOBROGARDTEL1785321665
- TELUS CyberSecurity Rating page: https://www.rankiteo.com/company/telus
- TELUS Rankiteo Cyber Incident Blog Article: https://blog.rankiteo.com/simlobrogardtel1785321665-loblaw-telus-digital-rogers-ardene-fido-breach-march-2025/
- TELUS CyberSecurity Score History: https://www.rankiteo.com/company/telus/history
- TELUS CyberSecurity Incident Source: https://www.bnnbloomberg.ca/business/technology/2026/07/29/average-canadian-data-breach-costs-and-detection-times-are-rising-ibm-report/
- 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