Rankiteo Logo
Rankiteo
Leader in Cyber Underwriting
Loading...
NEWRankiteo Cyber Underwriting Desktop - Score, price, and bind from your desktop
WindowsmacOSLinux
Download
Analyze » Baltimore City Office of Emergency Management » BAL1782779427

Incident Score: Analysis & Impact (BAL1782779427)

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

Rankiteo Score Impact Analysis

Rankiteo Incident Impact-27
Company Score Before Incident758 / 1000
Company Score After Incident731 / 1000
Company LinkView Baltimore City Office of Emergency Management Profile
INCIDENT NUMBERBAL1782779427
Type of Cyber IncidentCyber Attack
ATTACK VECTORNA
DATA EXPOSEDNA
INCIDENT DATE27/03/2018
STATUSOngoing

Key Highlights From The Incident Analysis

  • Timeline of Baltimore City Office of Emergency Management'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 Baltimore City Office of Emergency Management 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 Baltimore City Office of Emergency Management breach identified under incident ID BAL1782779427.

The analysis begins with a detailed overview of Baltimore City Office of Emergency Management's information like the linkedin page: https://www.linkedin.com/company/baltimoreoem, the number of followers: 654, the industry type: Public Safety and the number of employees: 16 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 758 and after the incident was 731 with a difference of -27 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 Baltimore City Office of Emergency Management and their customers.

On 26 March 2023, City of Baltimore disclosed Cyberattack issues under the banner "Baltimore’s Emergency Dispatch System Hit by Cyberattack".

Baltimore’s computer-assisted dispatch (CAD) system, which supports 911 and emergency call operations, suffered a 'limited breach' over the weekend, forcing city officials to switch to manual processes.

The disruption is felt across the environment, affecting Computer-assisted dispatch (CAD) system.

In response, moved swiftly to contain the threat with measures like Affected server taken offline, while recovery efforts such as System fully restored continue.

The case underscores how Ongoing.

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 cAD system, which supports 911 and emergency call operations, suffered a limited breach and Valid Accounts (T1078) with moderate confidence (50%), supported by evidence indicating attack threatening the organizations existence; manual processes required. Under the Impact tactic, the analysis identified Endpoint Denial of Service (T1499) with moderate to high confidence (80%), supported by evidence indicating forcing city officials to switch to manual processes; system fully restored after 17 hours and Data Encrypted for Impact (T1486) with lower confidence (40%), supported by evidence indicating limited breach; declined to disclose whether data was stolen. Under the Defense Evasion tactic, the analysis identified Impair Defenses: Disable or Modify Tools (T1562.001) with moderate to high confidence (70%), supported by evidence indicating affected server was taken offline to contain the threat. Under the Exfiltration tactic, the analysis identified Exfiltration Over C2 Channel (T1041) with moderate confidence (50%), supported by evidence indicating declined to disclose whether data was stolen, citing ongoing investigation. These correlations help security teams understand the attack chain and develop appropriate defensive measures based on the observed tactics and techniques.

Initial Access
Exploit Public-Facing Application (60%)
Valid Accounts (50%)
Impact
Endpoint Denial of Service (80%)
Data Encrypted for Impact (40%)
Defense Evasion
Impair Defenses: Disable or Modify Tools (70%)
Exfiltration
Exfiltration Over C2 Channel (50%)

Sources & References