Incident Score: Analysis & Impact (COL1778841048)
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 Columbia Bank'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 Columbia Bank 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 Columbia Bank breach identified under incident ID COL1778841048.
The analysis begins with a detailed overview of Columbia Bank's information like the linkedin page: https://www.linkedin.com/company/columbiabank, the number of followers: 44440, the industry type: Banking and the number of employees: 6178 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 767 and after the incident was 676 with a difference of -91 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 Columbia Bank and their customers.
On 17 April 2024, Columbia Bank disclosed Data Breach issues under the banner "Columbia Bank Data Breach and Delayed Notification".
Columbia Bank faced a data breach involving unauthorized access to sensitive customer information, including names, Social Security numbers, driver’s license numbers, and financial account details.
The disruption is felt across the environment, and exposing Sensitive personal information, including names, Social Security numbers, driver’s license numbers, and financial account details, with nearly 7,067 records at risk, plus an estimated financial loss of $700 (reported by one customer).
In response, moved swiftly to contain the threat with measures like Cut off attacker access on December 22, 2023, and stakeholders are being briefed through Mailed notices to affected customers beginning April 17, 2024; no public statement on website.
The case underscores how Completed (review finished on March 6, 2024), with advisories going out to stakeholders covering Mailed notices sent to affected customers beginning April 17, 2024.
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 unauthorized access to customer data...persisted from October 2 to December 22, 2023 and Valid Accounts (T1078) with moderate confidence (50%), supported by evidence indicating data was stored unencrypted in an internet-accessible environment. Under the Credential Access tactic, the analysis identified Unsecured Credentials: Credentials In Files (T1552.001) with moderate to high confidence (70%), supported by evidence indicating data stored unencrypted in an internet-accessible environment and Unsecured Credentials: Credentials in Files (T1552.006) with moderate to high confidence (70%), supported by evidence indicating exposure of Social Security numbers, driver’s license numbers, financial account details. Under the Collection tactic, the analysis identified Data from Local System (T1005) with moderate to high confidence (80%), supported by evidence indicating names, Social Security numbers, driver’s license numbers, financial account details compromised. Under the Exfiltration tactic, the analysis identified Exfiltration Over C2 Channel (T1041) with moderate to high confidence (70%), supported by evidence indicating 7,067 individuals affected; unauthorized access persisted for ~2.5 months and Transfer Data to Cloud Account (T1537) with moderate confidence (50%), supported by evidence indicating data stored in an internet-accessible environment. Under the Impact tactic, the analysis identified Data Destruction (T1485) with lower confidence (30%), supported by evidence indicating no details on attack’s origin or extent of breach and Data Manipulation: Stored Data Manipulation (T1565.001) with lower confidence (40%), supported by evidence indicating fraudulent charges reported on customer debit card. Under the Defense Evasion tactic, the analysis identified Impair Defenses: Disable or Modify Tools (T1562.001) with moderate confidence (50%), supported by evidence indicating breach persisted for ~2.5 months before containment and Indicator Removal: Clear Windows Event Logs (T1070.001) with lower confidence (40%), supported by evidence indicating no public statement on breach; delayed notification. These correlations help security teams understand the attack chain and develop appropriate defensive measures based on the observed tactics and techniques.
Sources & References
- Columbia Bank Rankiteo Cyber Incident Details: https://www.rankiteo.com/company/columbiabank/incident/COL1778841048
- Columbia Bank CyberSecurity Rating page: https://www.rankiteo.com/company/columbiabank
- Columbia Bank Rankiteo Cyber Incident Blog Article: https://blog.rankiteo.com/col1778841048-columbia-bank-breach-december-2025/
- Columbia Bank CyberSecurity Score History: https://www.rankiteo.com/company/columbiabank/history
- Columbia Bank CyberSecurity Incident Source: https://www.americanbanker.com/news/how-columbia-bank-kept-a-breach-quiet-for-119-days
- 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