Rankiteo Logo
Rankiteo
Leader in Cyber Underwriting
Loading...
NEWRankiteo Cyber Underwriting Desktop - Score, price, and bind from your desktop
WindowsmacOSLinux
Download
Analyze » Connect2Hackney » CON4893848112625

Incident Score: Analysis & Impact (CON4893848112625)

The details regarding individual company incidents & reports gives you full view from every side.

Rankiteo Score Impact Analysis

Rankiteo Incident Impact-24
Company Score Before Incident756 / 1000
Company Score After Incident732 / 1000
Company LinkView Connect2Hackney Profile
INCIDENT NUMBERCON4893848112625
Type of Cyber IncidentCyber Attack
ATTACK VECTORPhishing (suspected), Network Intrusion
DATA EXPOSEDNA
INCIDENT DATE15/06/2020
STATUSOngoing (RBKC, Westminster, and cyber specialists investigating)

Key Highlights From The Incident Analysis

  • Timeline of Connect2Hackney's Cyber Attack 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 Connect2Hackney 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 Connect2Hackney breach identified under incident ID CON4893848112625.

The analysis begins with a detailed overview of Connect2Hackney's information like the linkedin page: https://www.linkedin.com/company/connect2hackney, the number of followers: 954, the industry type: Staffing and Recruiting and the number of employees: 7 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 756 and after the incident was 732 with a difference of -24 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 Connect2Hackney and their customers.

On 13 February 2024, Royal Borough of Kensington & Chelsea (RBKC) disclosed Cyber-attack, Phishing (suspected) and IT Disruption issues under the banner "Cyber-attacks on Multiple London Councils (2024)".

Several London councils—including the Royal Borough of Kensington & Chelsea (RBKC), Hackney, Westminster, and Hammersmith & Fulham—reported cyber-attacks within the past 48 hours, leading to IT system disruptions and service outages.

The disruption is felt across the environment, affecting IT systems, Networks (shut down in Westminster) and Resident contact services.

In response, teams activated the incident response plan, moved swiftly to contain the threat with measures like Network shutdown (Westminster), Business continuity arrangements (Westminster) and Urgent phishing warnings (Hackney), and began remediation that includes Investigation into root cause and System restoration (RBKC), and stakeholders are being briefed through Public apologies (RBKC), Internal memos (Hackney, Westminster, Hammersmith & Fulham) and Social media updates (RBKC on X).

The case underscores how Ongoing (RBKC, Westminster, and cyber specialists investigating), teams are taking away lessons such as Mayor Sadiq Khan emphasized the need for improved cyber-resilience among London councils, citing lessons from past attacks (e.g., Transport for London, Marks & Spencer, Heathrow Airport). The London Office of Technology and Innovation and National Crime Agency are supporting councils in bolstering safeguards, and recommending next steps like Enhance phishing defenses, Improve network segmentation and Strengthen business continuity plans, with advisories going out to stakeholders covering Internal memos to staff (Hackney, Westminster, Hammersmith & Fulham) and Public statements (RBKC on X).

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 (T1566) with high confidence (95%), with evidence including phishing (suspected) listed under attack_vector and initial_access_broker.entry_point, and urgent internal memos warning staff about phishing risks. Under the Impact tactic, the analysis identified Data Encrypted for Impact (T1486) with moderate to high confidence (85%), with evidence including criminals encrypted 440,000 files (historical context in description), and iT system disruptions and service outages (2024 incident) and Endpoint Denial of Service: Application or System Exploitation (T1499.004) with moderate to high confidence (80%), supported by evidence indicating network shutdown (Westminster) and disrupted resident services. Under the Defense Evasion tactic, the analysis identified Indicator Removal: File Deletion (T1070.004) with moderate to high confidence (70%), with evidence including 440,000 files affected in 2020 (potential cleanup post-encryption), and lack of forensic details in 2024 incident suggests possible tampering. Under the Lateral Movement tactic, the analysis identified Remote Services: Remote Desktop Protocol (T1021.001) with moderate confidence (65%), with evidence including network Intrusion listed under attack_vector (common post-phishing), and multi-council impact suggests internal spread (e.g., shared systems). Under the Command and Control tactic, the analysis identified Application Layer Protocol: Web Protocols (T1071.001) with moderate confidence (60%), with evidence including cyber specialists investigating (implies C2 traffic likely present), and historical context of ransomware (2020) suggests C2 for exfil/encryption. Under the Exfiltration tactic, the analysis identified Exfiltration Over Alternative Protocol: Exfiltration Over Unencrypted/Obfuscated Non-C2 Protocol (T1048.003) with moderate confidence (50%), with evidence including protect residents data (implied risk of exfiltration), and no confirmed exfiltration but high-risk context (municipal data). These correlations help security teams understand the attack chain and develop appropriate defensive measures based on the observed tactics and techniques.

Sources & References