Incident Score: Analysis & Impact (RES1774376779)
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 Resecurity's Ransomware 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 Resecurity 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 Resecurity breach identified under incident ID RES1774376779.
The analysis begins with a detailed overview of Resecurity's information like the linkedin page: https://www.linkedin.com/company/resecurity, the number of followers: 89527, the industry type: Defense and Space Manufacturing and the number of employees: 99 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 674 and after the incident was 558 with a difference of -116 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 Resecurity and their customers.
A newly reported cybersecurity incident, "Rapid SQL Server Ransomware Attacks Highlight Critical Security Gaps", has drawn attention.
Recent investigations reveal that attackers can move from initial SQL Server access to full ransomware deployment in as little as 32 minutes.
The disruption is felt across the environment, affecting SQL Server instances and Backup systems, and exposing True.
Formal response steps have not been shared publicly yet.
The case underscores how teams are taking away lessons such as The speed of modern ransomware attacks (e.g., 32-minute deployment) highlights the need for continuous monitoring, rapid response, and addressing both technical controls and operational drift. Legacy environments often accumulate hidden vulnerabilities like stale permissions, forgotten linked servers, or overprivileged service accounts that attackers exploit, and recommending next steps like Block public exposure of port 1433 (restrict access to VPNs, bastion hosts, or trusted networks), Disable the *sa* account (renaming offers minimal protection; disable it entirely) and Enforce Windows Authentication (reduces brute-force risks but requires clean Active Directory hygiene).
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 high confidence (90%), supported by evidence indicating exploit publicly exposed TCP port 1433 (SQL Server’s default port), Brute Force: Password Guessing (T1110.001) with high confidence (90%), supported by evidence indicating brute-force attacks targeting the built-in *sa* account or weak credentials, and Exploit Public-Facing Application (T1190) with moderate to high confidence (70%), supported by evidence indicating sQL injection remains a distinct but equally dangerous vector. Under the Execution tactic, the analysis identified Command and Scripting Interpreter: Windows Command Shell (T1059.003) with high confidence (90%), supported by evidence indicating xp_cmdshell (disabled by default but easily enabled with *sysadmin* privileges), Command and Scripting Interpreter: PowerShell (T1059.001) with moderate to high confidence (70%), supported by evidence indicating cLR (Common Language Runtime) and OLE Automation, which allow payload staging, and Scheduled Task/Job: Cron (T1053.003) with moderate to high confidence (70%), supported by evidence indicating sQL Agent jobs and linked servers for lateral movement. Under the Privilege Escalation tactic, the analysis identified Valid Accounts (T1078) with high confidence (90%), supported by evidence indicating built-in *sa* account or weak credentials exploited for *sysadmin* privileges and Abuse Elevation Control Mechanism: Bypass User Account Control (T1548.002) with moderate to high confidence (70%), supported by evidence indicating overprivileged service accounts with local admin/domain privileges. Under the Defense Evasion tactic, the analysis identified Impair Defenses: Disable or Modify Tools (T1562.001) with high confidence (90%), supported by evidence indicating disable services, delete backups or Volume Shadow Copies (VSS) to prevent recovery, Indicator Removal: File Deletion (T1070.004) with moderate to high confidence (80%), supported by evidence indicating delete backups or Volume Shadow Copies (VSS) to prevent recovery, and Hide Artifacts: Hidden Files and Directories (T1564.001) with moderate confidence (60%), supported by evidence indicating configuration drift in legacy environments (stale permissions, forgotten linked servers). Under the Credential Access tactic, the analysis identified Brute Force: Password Guessing (T1110.001) with high confidence (90%), supported by evidence indicating brute-force attacks targeting the built-in *sa* account or weak credentials and Valid Accounts (T1078) with high confidence (90%), supported by evidence indicating overprivileged service accounts with local admin/domain privileges. Under the Discovery tactic, the analysis identified Account Discovery: Local Account (T1087.001) with moderate to high confidence (80%), supported by evidence indicating attackers using xp_cmdshell to run discovery commands (*whoami*, *systeminfo*) and System Information Discovery (T1082) with moderate to high confidence (80%), supported by evidence indicating attackers using xp_cmdshell to run discovery commands (*systeminfo*). Under the Lateral Movement tactic, the analysis identified Remote Services: SMB/Windows Admin Shares (T1021.002) with moderate to high confidence (70%), supported by evidence indicating linked servers for lateral movement. Under the Impact tactic, the analysis identified Data Encrypted for Impact (T1486) with high confidence (100%), supported by evidence indicating encrypt MDF/LDF files (SQL database files), ransomware deployment in 32 minutes, Inhibit System Recovery (T1490) with high confidence (90%), supported by evidence indicating delete backups or Volume Shadow Copies (VSS) to prevent recovery, and Service Stop (T1489) with moderate to high confidence (80%), supported by evidence indicating disable services during ransomware deployment. Under the Exfiltration tactic, the analysis identified Exfiltration Over C2 Channel (T1041) with moderate confidence (60%), supported by evidence indicating anomalous outbound connections post-compromise (network telemetry). These correlations help security teams understand the attack chain and develop appropriate defensive measures based on the observed tactics and techniques.
Sources & References
- Resecurity Rankiteo Cyber Incident Details: https://www.rankiteo.com/company/resecurity/incident/RES1774376779
- Resecurity CyberSecurity Rating page: https://www.rankiteo.com/company/resecurity
- Resecurity Rankiteo Cyber Incident Blog Article: https://blog.rankiteo.com/res1774376779-energywater-sector-victims-ransomware-january-2024/
- Resecurity CyberSecurity Score History: https://www.rankiteo.com/company/resecurity/history
- Resecurity CyberSecurity Incident Source: https://gbhackers.com/sql-server-ransomware-attacks-how-they-work-and-how-to-harden-your-database/
- 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