Comparison Overview

Yapı Kredi

VS

DenizBank

Yapı Kredi

Levent, İstanbul, Levent, 34740, TR
Last Update: 2025-11-22
Between 750 and 799

Yapı Kredi has been sustainably strengthening its market positioning in the sector since its establishment in 1944 through a customer-centric approach and focus on innovation. Yapı Kredi is the 3rd largest private bank in Turkey with total assets worth TL 411 billion as of the end of 2019. Constantly seeking to increase its contribution to the financing of the Turkish economy with its customer-centric approach, Yapı Kredi enlarged the volume of its total cash and non-cash loans by 4% in 2019 to TL 319 billion. Thus, Yapı Kredi maintained its position in 2nd place among private banks in this respect. The Bank serves its customers with its 846 branches covering all regions of Turkey and 16,631 employees. Yapı Kredi delivers its products and services via its advanced Alternative Delivery Channels (ADCs) that comprise 4,330 ATMs, innovative internet banking, leading mobile banking, 3 call centers and approximately 709 thousand POS terminals. 94% of the Bank’s transactions went through non-branch channels as at year-end 2019. Yapı Kredi is a fully integrated financial services group supported by its domestic and international subsidiaries. Yapı Kredi serves its customers through retail banking (comprising of individual banking, Small and Medium Size Enterprises (SME) banking and card payment systems, private banking and wealth management), as well as corporate and commercial banking. The Bank’s operations are supported by domestic subsidiaries in asset management, brokerage, leasing and factoring as well as international banking subsidiaries in the Netherlands, Malta and Azerbaijan. Yapı Kredi has a strong shareholding structure which ensures sustainable and profitable growth. 40.95% of the Bank’s shares are owned by Koç Financial Services, 9.02% of the shares are owned by Koç Holding A.Ş. The total direct and indirect shares of Koç Group amount to 49.99%. 20.00% of Bank’s shares are owned by UniCredit S.P.A. The remaining 30.03% is publicly traded on Borsa Istanbul

NAICS: 522
NAICS Definition:
Employees: 14,355
Subsidiaries: 53
12-month incidents
0
Known data breaches
0
Attack type number
0

DenizBank

Büyükdere Caddesi 141, Esentepe, Istanbul, TR, 34394
Last Update: 2025-11-27
Between 750 and 799

In 1997, DenizBank was acquired by the Zorlu Holding in the form of a banking license from the Privatization Administration. Undergoing three shareholder changes and done public offering in its short history, the Bank was acquired in October 2006 by Dexia, one of the leading financial groups of Europe. Later on, being subject to the biggest one-time investment made by Russia in Turkey, DenizBank started to serve under the umbrella of Sberbank, one of the biggest banks in the world, as of September 28, 2012. Finally, the Bank’s shares were transferred to Emirates NBD as of August 2019, again one of the leading institutions in its region.

NAICS: 52211
NAICS Definition: Commercial Banking
Employees: 10,943
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/yapikredi.jpeg
Yapı Kredi
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/denizbank.jpeg
DenizBank
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
Yapı Kredi
100%
Compliance Rate
0/4 Standards Verified
DenizBank
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Banking Industry Average (This Year)

No incidents recorded for Yapı Kredi in 2025.

Incidents vs Banking Industry Average (This Year)

No incidents recorded for DenizBank in 2025.

Incident History — Yapı Kredi (X = Date, Y = Severity)

Yapı Kredi cyber incidents detection timeline including parent company and subsidiaries

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

DenizBank cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/yapikredi.jpeg
Yapı Kredi
Incidents

No Incident

https://images.rankiteo.com/companyimages/denizbank.jpeg
DenizBank
Incidents

No Incident

FAQ

DenizBank company demonstrates a stronger AI Cybersecurity Score compared to Yapı Kredi company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Historically, DenizBank company has disclosed a higher number of cyber incidents compared to Yapı Kredi company.

In the current year, DenizBank company and Yapı Kredi company have not reported any cyber incidents.

Neither DenizBank company nor Yapı Kredi company has reported experiencing a ransomware attack publicly.

Neither DenizBank company nor Yapı Kredi company has reported experiencing a data breach publicly.

Neither DenizBank company nor Yapı Kredi company has reported experiencing targeted cyberattacks publicly.

Neither Yapı Kredi company nor DenizBank company has reported experiencing or disclosing vulnerabilities publicly.

Neither Yapı Kredi nor DenizBank holds any compliance certifications.

Neither company holds any compliance certifications.

Yapı Kredi company has more subsidiaries worldwide compared to DenizBank company.

Yapı Kredi company employs more people globally than DenizBank company, reflecting its scale as a Banking.

Neither Yapı Kredi nor DenizBank holds SOC 2 Type 1 certification.

Neither Yapı Kredi nor DenizBank holds SOC 2 Type 2 certification.

Neither Yapı Kredi nor DenizBank holds ISO 27001 certification.

Neither Yapı Kredi nor DenizBank holds PCI DSS certification.

Neither Yapı Kredi nor DenizBank holds HIPAA certification.

Neither Yapı Kredi nor DenizBank 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