Comparison Overview

DenizBank

VS

State Bank of India

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

State Bank of India

Madame Cama Road, Near Vidhan Bhavan, Nariman Point, Mumbai, Maharashtra, IN, 400021
Last Update: 2025-11-23
Between 800 and 849

We are the largest Indian Public Sector Banking & Financial Services Company. Headquartered in Mumbai, our national presence across the country with over 22,000 branches and globally across all time-zones at 227 locations in 30 countries, makes us the leader in the sector. Our legacy ranges back to the British era through the Imperial Bank of India, founded in 1806. Today, we are a conglomerate employing skilled professionals who are successfully taking the legacy forward through our specialized and customized financial services designed to cater the needs of Corporates, SMEs, NRIs & Retail customers. For more information about Career & Life at SBI, please visit : https://bank.sbi/web/careers Disclaimer: SBI shall bear no responsibility for confidentiality of information shared with SBI through LinkedIn.

NAICS: 52211
NAICS Definition: Commercial Banking
Employees: 119,767
Subsidiaries: 3
12-month incidents
1
Known data breaches
1
Attack type number
2

Compliance Badges Comparison

Security & Compliance Standards Overview

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
https://images.rankiteo.com/companyimages/state-bank-of-india.jpeg
State Bank of India
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
DenizBank
100%
Compliance Rate
0/4 Standards Verified
State Bank of India
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Banking Industry Average (This Year)

No incidents recorded for DenizBank in 2025.

Incidents vs Banking Industry Average (This Year)

State Bank of India has 12.36% more incidents than the average of same-industry companies with at least one recorded incident.

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

DenizBank cyber incidents detection timeline including parent company and subsidiaries

Incident History — State Bank of India (X = Date, Y = Severity)

State Bank of India cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

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

No Incident

https://images.rankiteo.com/companyimages/state-bank-of-india.jpeg
State Bank of India
Incidents

Date Detected: 6/2025
Type:Vulnerability
Attack Vector: Man-in-the-middle (MITM) attacks
Motivation: Data theft, financial fraud
Blog: Blog

Date Detected: 10/2016
Type:Breach
Attack Vector: Compromised ATM Network
Motivation: Fraud
Blog: Blog

FAQ

State Bank of India company demonstrates a stronger AI Cybersecurity Score compared to DenizBank company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

State Bank of India company has historically faced a number of disclosed cyber incidents, whereas DenizBank company has not reported any.

In the current year, State Bank of India company has reported more cyber incidents than DenizBank company.

Neither State Bank of India company nor DenizBank company has reported experiencing a ransomware attack publicly.

State Bank of India company has disclosed at least one data breach, while DenizBank company has not reported such incidents publicly.

Neither State Bank of India company nor DenizBank company has reported experiencing targeted cyberattacks publicly.

State Bank of India company has disclosed at least one vulnerability, while DenizBank company has not reported such incidents publicly.

Neither DenizBank nor State Bank of India holds any compliance certifications.

Neither company holds any compliance certifications.

State Bank of India company has more subsidiaries worldwide compared to DenizBank company.

State Bank of India company employs more people globally than DenizBank company, reflecting its scale as a Banking.

Neither DenizBank nor State Bank of India holds SOC 2 Type 1 certification.

Neither DenizBank nor State Bank of India holds SOC 2 Type 2 certification.

Neither DenizBank nor State Bank of India holds ISO 27001 certification.

Neither DenizBank nor State Bank of India holds PCI DSS certification.

Neither DenizBank nor State Bank of India holds HIPAA certification.

Neither DenizBank nor State Bank of India 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