Incident Score: Analysis & Impact (REL1787576460)
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 ReliaQuest'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 ReliaQuest 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 ReliaQuest breach identified under incident ID REL1787576460.
The analysis begins with a detailed overview of ReliaQuest's information like the linkedin page: https://www.linkedin.com/company/reliaquest, the number of followers: 60907, the industry type: Computer and Network Security and the number of employees: 1096 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 663 and after the incident was 600 with a difference of -63 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 ReliaQuest and their customers.
On 22 August 2026, ReliaQuest disclosed Social Engineering issues under the banner "ReliaQuest Thwarts Targeted Social Engineering Attack with Defense-in-Depth Controls".
On August 22, 2026, cybersecurity firm ReliaQuest detected a sophisticated social engineering attack in which threat actors impersonated the company’s security personnel to gain access to an employee’s credentials.
Impact assessments are still underway, so the full scope is not yet clear.
In response, teams activated the incident response plan, moved swiftly to contain the threat with measures like Terminated the session, Reset compromised credentials and Revoked all linked authentication factors.
The case underscores how Completed, teams are taking away lessons such as The attack highlights a growing trend in identity-focused intrusions, where threat actors exploit MFA fatigue by tricking users into approving fraudulent prompts. While MFA remains a critical security layer, the incident underscores the need for phishing-resistant authentication methods, such as FIDO2 security keys, alongside continuous monitoring of identity provider sessions, and recommending next steps like Implement phishing-resistant authentication methods (e.g., FIDO2 security keys) and Continuous monitoring of identity provider sessions.
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 Phishing: Spearphishing Voice (T1566.004) with high confidence (90%), supported by evidence indicating using phone-based vishing tactics...contacted multiple employees and Phishing: Spearphishing Link (T1566.001) with high confidence (90%), supported by evidence indicating deployed a fake single sign-on (SSO) portal...directed one employee to authenticate. Under the Credential Access tactic, the analysis identified Multi-Factor Authentication Request Generation (T1621) with high confidence (95%), supported by evidence indicating approved a malicious multi-factor authentication (MFA) push notification and Valid Accounts: Cloud Accounts (T1078.004) with high confidence (90%), supported by evidence indicating granted the attackers a temporary, view-only session within ReliaQuest’s identity dashboard. Under the Defense Evasion tactic, the analysis identified Modify Authentication Process: Multi-Factor Authentication (T1556.006) with moderate to high confidence (80%), supported by evidence indicating exploit MFA fatigue by tricking users into approving fraudulent prompts, Acquire Infrastructure: Domains (T1583.001) with moderate to high confidence (85%), supported by evidence indicating registered a spoofed domain mimicking ReliaQuest’s legitimate infrastructure, and Compromise Infrastructure: Web Services (T1584.006) with moderate to high confidence (80%), supported by evidence indicating fake single sign-on (SSO) portal hosted on a content delivery network (CDN). Under the Reconnaissance tactic, the analysis identified Gather Victim Org Information: Determine Physical Locations (T1591.001) with moderate to high confidence (70%), supported by evidence indicating posing as named members of ReliaQuest’s security team and Gather Victim Identity Information: Email Addresses (T1589.002) with moderate to high confidence (70%), supported by evidence indicating contacted multiple employees. Under the Resource Development tactic, the analysis identified Acquire Infrastructure: Domains (T1583.001) with high confidence (90%), supported by evidence indicating registered a spoofed domain mimicking ReliaQuest’s legitimate infrastructure and Develop Capabilities: Malware (T1587.001) with moderate to high confidence (70%), supported by evidence indicating fake single sign-on (SSO) portal. These correlations help security teams understand the attack chain and develop appropriate defensive measures based on the observed tactics and techniques.