Comparison Overview

Türkiye İş Bankası

VS

Banco de Crédito BCP

Türkiye İş Bankası

Last Update: 2025-11-27
Between 750 and 799

In the nearly 100 years since its founding by the Great Leader Mustafa Kemal Atatürk on August 26, 1924, İşbank has undertaken various roles and made significant contributions to the development of our country in many fields, especially in industry and trade. İşbank offers products and services to its customers in corporate, commercial, SME, retail and private banking areas with its around 22 thousand employees, nearly 1,200 domestic branches and approximately 6,400 ATMs by the end of 2021, together with its advanced digital banking channels. İşbank also operates abroad with its branches abroad located in the Turkish Republic of Northern Cyprus, England, Kosovo, Iraq and Bahrain; 100% owned subsidiaries in Germany, Russia and Georgia; and with its representative offices in China and Egypt. The Bank is the largest private bank in Turkey in terms of total assets, loans, deposits and shareholders’equity; number of branches and ATMs. The largest share of the Bank's capital is held by the İşbank Pension Fund, which was founded by its employees. İşbank, an organization synonymous with trust, consistency and dignity, works for an inclusive and environment-friendly economy with its sense of responsibility stemming from its history. For further deteails, you can visit https://www.isbank.com.tr/en/about-us page.

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

Banco de Crédito BCP

Calle Centenario 156, La Molina, PE, Lima 12
Last Update: 2025-11-27

Somos el banco peruano que desde hace más de 130 años viene liderando el sistema financiero a nivel nacional. A lo largo de todo este tiempo hemos contribuido con el desarrollo económico de nuestro país, transformando planes en realidad. Todo esto es posible gracias al equipo de profesionales de primer nivel que forman parte de nuestro equipo y que se caracterizan por su pasión por metas y resultados y capacidad de innovar y buscar siempre ser los mejores. Nuestra diversidad de negocios y áreas nos permite ofrecer múltiples experiencias de trabajo, en muchas especialidades que requieren diferentes competencias y habilidades. Por ello, estamos en permanente búsqueda de profesionales talentosos y dispuestos a afrontar nuevos retos, con capacidad para innovar y con ganas de desafiarse en grande para impactar en grande. ¡Únete al Equipo BCP!

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

Compliance Badges Comparison

Security & Compliance Standards Overview

https://images.rankiteo.com/companyimages/isbankasi.jpeg
Türkiye İş Bankası
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/banco-de-credito-bcp.jpeg
Banco de Crédito BCP
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
Türkiye İş Bankası
100%
Compliance Rate
0/4 Standards Verified
Banco de Crédito BCP
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Banking Industry Average (This Year)

No incidents recorded for Türkiye İş Bankası in 2025.

Incidents vs Banking Industry Average (This Year)

No incidents recorded for Banco de Crédito BCP in 2025.

Incident History — Türkiye İş Bankası (X = Date, Y = Severity)

Türkiye İş Bankası cyber incidents detection timeline including parent company and subsidiaries

Incident History — Banco de Crédito BCP (X = Date, Y = Severity)

Banco de Crédito BCP cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/isbankasi.jpeg
Türkiye İş Bankası
Incidents

No Incident

https://images.rankiteo.com/companyimages/banco-de-credito-bcp.jpeg
Banco de Crédito BCP
Incidents

No Incident

FAQ

Banco de Crédito BCP company demonstrates a stronger AI Cybersecurity Score compared to Türkiye İş Bankası company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Historically, Banco de Crédito BCP company has disclosed a higher number of cyber incidents compared to Türkiye İş Bankası company.

In the current year, Banco de Crédito BCP company and Türkiye İş Bankası company have not reported any cyber incidents.

Neither Banco de Crédito BCP company nor Türkiye İş Bankası company has reported experiencing a ransomware attack publicly.

Neither Banco de Crédito BCP company nor Türkiye İş Bankası company has reported experiencing a data breach publicly.

Neither Banco de Crédito BCP company nor Türkiye İş Bankası company has reported experiencing targeted cyberattacks publicly.

Neither Türkiye İş Bankası company nor Banco de Crédito BCP company has reported experiencing or disclosing vulnerabilities publicly.

Neither Türkiye İş Bankası nor Banco de Crédito BCP holds any compliance certifications.

Neither company holds any compliance certifications.

Banco de Crédito BCP company has more subsidiaries worldwide compared to Türkiye İş Bankası company.

Banco de Crédito BCP company employs more people globally than Türkiye İş Bankası company, reflecting its scale as a Banking.

Neither Türkiye İş Bankası nor Banco de Crédito BCP holds SOC 2 Type 1 certification.

Neither Türkiye İş Bankası nor Banco de Crédito BCP holds SOC 2 Type 2 certification.

Neither Türkiye İş Bankası nor Banco de Crédito BCP holds ISO 27001 certification.

Neither Türkiye İş Bankası nor Banco de Crédito BCP holds PCI DSS certification.

Neither Türkiye İş Bankası nor Banco de Crédito BCP holds HIPAA certification.

Neither Türkiye İş Bankası nor Banco de Crédito BCP 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