Incident Score: Analysis & Impact (EVOBAN1777652813)

In this Rankiteo incident briefing, we review the Bankinter breach identified under incident ID EVOBAN1777652813.

The analysis begins with a detailed overview of Bankinter's information like the linkedin page: https://www.linkedin.com/company/bankinter, the number of followers: 114802, the industry type: Banking and the number of employees: 6439 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 792 and after the incident was 694 with a difference of -98 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 Bankinter and their customers.

On 18 April 2024, EVO Banco disclosed Data Breach issues under the banner "Spain’s AEPD Fines Bankinter €240,000 Over 2024 EVO Banco Data Breach".

Spain’s data protection authority (AEPD) has concluded its investigation into a 2024 cyberattack on EVO Banco, imposing a €240,000 fine on Bankinter after the lender absorbed EVO Banco through a merger.

The disruption is felt across the environment, affecting Customer onboarding API, and exposing Personal and financial data of over 1.27 million individuals, with nearly 1.27 million records at risk, plus an estimated financial loss of €240,000 fine.

In response, and began remediation that includes API access control restoration, forensic analysis, and stakeholders are being briefed through Mandatory disclosures under GDPR Article 34 (ordered by AEPD).

The case underscores how Concluded, teams are taking away lessons such as Risks of inadequate API security, limitations of internal risk assessments for financial data, importance of access control testing in change management processes, and recommending next steps like Enhance API security controls, implement encryption for sensitive data, improve change management testing for access control vulnerabilities, and ensure timely breach notifications, with advisories going out to stakeholders covering Mandatory disclosures under GDPR Article 34.

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.