Comparison Overview

BBVA

VS

Akbank

BBVA

Plaza de San Nicolas 4, Bilbao, Vizcaya, 48005, ES
Last Update: 2025-11-26

At BBVA we are leading the transformation of banking worldwide, united in pursuing our goal of bringing the age of opportunity to everyone. Firmly focused on the future, our on-going digital transformation is already producing disruptive innovations that power our vision of banking. Every one of our 121,486 employees, from branch staff to senior leaders, plays an essential role in giving our 71.5 million customers the cutting edge banking solutions that they deserve. Building on 166 years of history we know the importance of constant development, which is why we place so much confidence in the collaborative working environment that enables our people to grow and excel. If you would like to learn about the culture and opportunities on offer at a company that is leading the way for 21st century banking, head to the ‘Life’ tab to find out more.

NAICS: 52211
NAICS Definition: Commercial Banking
Employees: 119,358
Subsidiaries: 11
12-month incidents
0
Known data breaches
0
Attack type number
0

Akbank

4. Levent Besiktas, Istanbul, 4. Levent, TR, 34330
Last Update: 2025-11-20
Between 750 and 799

Akbank was founded as a local bank in Adana in January 1948. Established originally with the core objective to provide funding to local cotton producers, the Bank opened its first branch in the Sirkeci district of Istanbul on July 14, 1950. In 1954, after relocating its Head Office to Istanbul, the Bank rapidly expanded its branch network and had automated all banking operations by 1963. Floated to the public in 1990, Akbank shares began trading on international markets and as an American Depository Receipt (ADR) after its secondary public offering in 1998. Akbank established AKSecurities in 1996, AKInvestment Trust in 1998, AKAssetManagement Company and its Private Banking Department in 2000 and Ak Pension Company in 2003. Akbank acquired AKLease in 2005 and Ak Pension Company was sold to Ak Insurance in February 2006. Akbank conducts overseas operations through its subsidiaries in Germany (Akbank AG), the Netherlands (Akbank NV) and Dubai (Akbank Dubai Limited) as well as a branch in Malta. As part of the initiative to restructure its overseas subsidiaries, Akbank decided to consolidate Akbank AG and Akbank NV under the corporate umbrella of Akbank AG; the merger is currently underway. In addition to its core banking activities, Akbank offers a wide range of consumer, commercial and SME, corporate and private banking services as well as foreign trade financing. For more information about Akbank, please visit at http://www.akbank.com.

NAICS: 52211
NAICS Definition: Commercial Banking
Employees: 14,432
Subsidiaries: 0
12-month incidents
0
Known data breaches
0
Attack type number
0

Compliance Badges Comparison

Security & Compliance Standards Overview

https://images.rankiteo.com/companyimages/bbva.jpeg
BBVA
ISO 27001
ISO 27001 certification not verified
Not verified
SOC2 Type 1
SOC2 Type 1 certification not verified
Not verified
SOC2 Type 2
SOC2 Type 2 certification not verified
Not verified
GDPR
GDPR certification not verified
Not verified
PCI DSS
PCI DSS certification not verified
Not verified
HIPAA
HIPAA certification not verified
Not verified
https://images.rankiteo.com/companyimages/akbank.jpeg
Akbank
ISO 27001
ISO 27001 certification not verified
Not verified
SOC2 Type 1
SOC2 Type 1 certification not verified
Not verified
SOC2 Type 2
SOC2 Type 2 certification not verified
Not verified
GDPR
GDPR certification not verified
Not verified
PCI DSS
PCI DSS certification not verified
Not verified
HIPAA
HIPAA certification not verified
Not verified
Compliance Summary
BBVA
100%
Compliance Rate
0/4 Standards Verified
Akbank
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Banking Industry Average (This Year)

No incidents recorded for BBVA in 2025.

Incidents vs Banking Industry Average (This Year)

No incidents recorded for Akbank in 2025.

Incident History — BBVA (X = Date, Y = Severity)

BBVA cyber incidents detection timeline including parent company and subsidiaries

Incident History — Akbank (X = Date, Y = Severity)

Akbank cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/bbva.jpeg
BBVA
Incidents

No Incident

https://images.rankiteo.com/companyimages/akbank.jpeg
Akbank
Incidents

No Incident

FAQ

BBVA company demonstrates a stronger AI Cybersecurity Score compared to Akbank company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Historically, Akbank company has disclosed a higher number of cyber incidents compared to BBVA company.

In the current year, Akbank company and BBVA company have not reported any cyber incidents.

Neither Akbank company nor BBVA company has reported experiencing a ransomware attack publicly.

Neither Akbank company nor BBVA company has reported experiencing a data breach publicly.

Neither Akbank company nor BBVA company has reported experiencing targeted cyberattacks publicly.

Neither BBVA company nor Akbank company has reported experiencing or disclosing vulnerabilities publicly.

Neither BBVA nor Akbank holds any compliance certifications.

Neither company holds any compliance certifications.

BBVA company has more subsidiaries worldwide compared to Akbank company.

BBVA company employs more people globally than Akbank company, reflecting its scale as a Banking.

Neither BBVA nor Akbank holds SOC 2 Type 1 certification.

Neither BBVA nor Akbank holds SOC 2 Type 2 certification.

Neither BBVA nor Akbank holds ISO 27001 certification.

Neither BBVA nor Akbank holds PCI DSS certification.

Neither BBVA nor Akbank holds HIPAA certification.

Neither BBVA nor Akbank holds GDPR certification.

Latest Global CVEs (Not Company-Specific)

Description

Angular is a development platform for building mobile and desktop web applications using TypeScript/JavaScript and other languages. Prior to versions 19.2.16, 20.3.14, and 21.0.1, there is a XSRF token leakage via protocol-relative URLs in angular HTTP clients. The vulnerability is a Credential Leak by App Logic that leads to the unauthorized disclosure of the Cross-Site Request Forgery (XSRF) token to an attacker-controlled domain. Angular's HttpClient has a built-in XSRF protection mechanism that works by checking if a request URL starts with a protocol (http:// or https://) to determine if it is cross-origin. If the URL starts with protocol-relative URL (//), it is incorrectly treated as a same-origin request, and the XSRF token is automatically added to the X-XSRF-TOKEN header. This issue has been patched in versions 19.2.16, 20.3.14, and 21.0.1. A workaround for this issue involves avoiding using protocol-relative URLs (URLs starting with //) in HttpClient requests. All backend communication URLs should be hardcoded as relative paths (starting with a single /) or fully qualified, trusted absolute URLs.

Risk Information
cvss4
Base: 7.7
Severity: LOW
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:N/SC:H/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Description

Forge (also called `node-forge`) is a native implementation of Transport Layer Security in JavaScript. An Uncontrolled Recursion vulnerability in node-forge versions 1.3.1 and below enables remote, unauthenticated attackers to craft deep ASN.1 structures that trigger unbounded recursive parsing. This leads to a Denial-of-Service (DoS) via stack exhaustion when parsing untrusted DER inputs. This issue has been patched in version 1.3.2.

Risk Information
cvss4
Base: 8.7
Severity: LOW
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Description

Forge (also called `node-forge`) is a native implementation of Transport Layer Security in JavaScript. An Integer Overflow vulnerability in node-forge versions 1.3.1 and below enables remote, unauthenticated attackers to craft ASN.1 structures containing OIDs with oversized arcs. These arcs may be decoded as smaller, trusted OIDs due to 32-bit bitwise truncation, enabling the bypass of downstream OID-based security decisions. This issue has been patched in version 1.3.2.

Risk Information
cvss4
Base: 6.3
Severity: LOW
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Description

Suricata is a network IDS, IPS and NSM engine developed by the OISF (Open Information Security Foundation) and the Suricata community. Prior to versions 7.0.13 and 8.0.2, working with large buffers in Lua scripts can lead to a stack overflow. Users of Lua rules and output scripts may be affected when working with large buffers. This includes a rule passing a large buffer to a Lua script. This issue has been patched in versions 7.0.13 and 8.0.2. A workaround for this issue involves disabling Lua rules and output scripts, or making sure limits, such as stream.depth.reassembly and HTTP response body limits (response-body-limit), are set to less than half the stack size.

Risk Information
cvss3
Base: 7.5
Severity: LOW
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Description

Suricata is a network IDS, IPS and NSM engine developed by the OISF (Open Information Security Foundation) and the Suricata community. In versions from 8.0.0 to before 8.0.2, a NULL dereference can occur when the entropy keyword is used in conjunction with base64_data. This issue has been patched in version 8.0.2. A workaround involves disabling rules that use entropy in conjunction with base64_data.

Risk Information
cvss3
Base: 7.5
Severity: LOW
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H