Comparison Overview

QNB Türkiye

VS

Crédit Mutuel

QNB Türkiye

Turkey, Istanbul, TR, 34394
Last Update: 2026-01-18
Between 750 and 799

Finansbank A.Ş. 26 Ekim 1987 tarihinde iş insanı Hüsnü Özyeğin liderliğinde 100 ortakla Bankalar Kanunu ve Türk Ticaret Kanunu hükümleri uyarınca kuruldu. Sektörde hızlı büyeme ile ilk 5 büyük özel banka arasına giren QNB Finansbank, 2006 yılında Yunanistan'ın en büyük bankası National Bank of Greece (NBG) tarafından satın alındı. Bu birleşme sonucunda NBG'nin Güneydoğu Avrupa'da sahip olduğu lider konumu ile bankanın Türkiye'deki yüksek büyüme potansiyeli bir araya geldi. 2006 yılından itibaren bireysel bankacılıkta da hızla büyüyen Finansbank; kredi kartı, dijitalleşme, teknoloji alanındaki yatırımları ve yarattığı çözümleri ile sektörde ilklere imza atan banka konumuna geldi. Ekim 2012'de tüm hizmetlerini sadece dijital kanallar üzerinden sunan ve Türkiye'nin ilk şubesiz dijital bankası olan Enpara.com'u kuran Finansbank, bu alanda Türkiye'de sektörde yeni bir dönemin kapılarını açtı. 2016 yılının haziran ayında Orta Doğu ve Afrika bölgesinin lider finansal kuruluşu olan Katar'ın en büyük bankası Qatar National Bank S.A.Q (QNB Group) tarafından satın alınan QNB Finansbank, uluslararası bir yapının parçası haline geldi. Böylelikle bankanın yeni ismi Ekim 2016 itibarıyla QNB Finansbank oldu. QNB Group'un, global bir marka olma vizyonu doğrultusunda ismini 2024 yılının Ekim ayı itibarıyla QNB Türkiye olarak yeniledi. QNB Türkiye, kurum kültürünü geleceğe taşıyan dinamik ve yenilikçi bir yapıya sahip. "Önce İnsan'' anlayışıyla çalışanların gelişimine öncelik veren banka, "Güven'' ile güçlü bir iş birliği ortamı kuruyor. Bankanın değerleri arasında yer alan "Adaptasyon'' ile değişimlere hızla uyum sağlarken, "Öncü Olmak'' vizyonuyla sektörde fark yaratıyor, "Birlikte Gelişim'' ilkesiyle de başarıya hep birlikte ulaşıyor. QNB Türkiye, çatısı altındaki iştirakleri QNB Leasing, QNB Invest, QNB Portföy, QNB Faktoring, QNB Sağlık, IBTech ve QNB eSolutions ile müşterilerinin tüm finansal ihtiyaçlarına yaratıcı, hızlı ve kolay çözümler sunmaya devam ediyor.

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

Crédit Mutuel

46 rue Bastion, Paris, 75017, FR
Last Update: 2026-01-17
Between 750 and 799

Un modèle mutualiste au service des clients et des salariés. Réseau bancaire mutualiste constitué de 2124 Caisses locales le Crédit Mutuel se compose de 18 fédérations régionales, couvrant tout le territoire français. Société de personnes et non de capitaux, le Crédit Mutuel n’est pas coté en Bourse. Sa stratégie est ainsi dégagée de la recherche de la seule rentabilité à court terme, au profit d’un développement pensé sur le long terme. Son objectif central : rendre un service de qualité au coût le plus juste à tous ses sociétaires. Son organisation décentralisée favorise ainsi la qualité de service aux clients et la réactivité, par des circuits de décision courts. Reconnu à la fois par ses clients et les professionnels de la finance, le Crédit Mutuel décroche régulièrement des titres qui confortent son modèle mutualiste et ses valeurs de solidarité, responsabilité, égalité, proximité et responsabilité sociale portées par les salariés et les clients- sociétaires. Au-delà de son réseau, le Crédit Mutuel constitue un Groupe qui comprend également plusieurs filiales dont certaines sont implantées à l’étranger. Les nouveaux collaborateurs du Crédit Mutuel apprécient tout particulièrement : - un circuit de recrutement court, axé sur des entretiens évaluant notamment la personnalité et la motivation ; - un parcours d’intégration précis, suivi par la fonction Ressources Humaines. Les salariés apprécient tout particulièrement : - le Système d’Information au service du développement commercial ; - un management au travers d’objectifs collectifs ; - des démarches et outils de gestion des carrières et des compétences facilitant la progression dans l’entreprise ; - la qualité des formations de préparation ou d’accompagnement des changements d’emploi ; - la diversité des opportunités d’évolution, principalement commerciale, sur tous les marchés, dans toutes les entités du Groupe.

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

Compliance Badges Comparison

Security & Compliance Standards Overview

https://images.rankiteo.com/companyimages/3ikqnb.jpeg
QNB Türkiye
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/credit-mutuel.jpeg
Crédit Mutuel
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
QNB Türkiye
100%
Compliance Rate
0/4 Standards Verified
Crédit Mutuel
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Banking Industry Average (This Year)

No incidents recorded for QNB Türkiye in 2026.

Incidents vs Banking Industry Average (This Year)

No incidents recorded for Crédit Mutuel in 2026.

Incident History — QNB Türkiye (X = Date, Y = Severity)

QNB Türkiye cyber incidents detection timeline including parent company and subsidiaries

Incident History — Crédit Mutuel (X = Date, Y = Severity)

Crédit Mutuel cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/3ikqnb.jpeg
QNB Türkiye
Incidents

No Incident

https://images.rankiteo.com/companyimages/credit-mutuel.jpeg
Crédit Mutuel
Incidents

Date Detected: 12/2025
Type:Cyber Attack
Attack Vector: Inondation de requêtes et connexions
Motivation: Perturbation des services critiques, possible motivation géopolitique
Blog: Blog

FAQ

QNB Türkiye company demonstrates a stronger AI Cybersecurity Score compared to Crédit Mutuel company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Crédit Mutuel company has historically faced a number of disclosed cyber incidents, whereas QNB Türkiye company has not reported any.

In the current year, Crédit Mutuel company and QNB Türkiye company have not reported any cyber incidents.

Neither Crédit Mutuel company nor QNB Türkiye company has reported experiencing a ransomware attack publicly.

Neither Crédit Mutuel company nor QNB Türkiye company has reported experiencing a data breach publicly.

Crédit Mutuel company has reported targeted cyberattacks, while QNB Türkiye company has not reported such incidents publicly.

Neither QNB Türkiye company nor Crédit Mutuel company has reported experiencing or disclosing vulnerabilities publicly.

Neither QNB Türkiye nor Crédit Mutuel holds any compliance certifications.

Neither company holds any compliance certifications.

Neither QNB Türkiye company nor Crédit Mutuel company has publicly disclosed detailed information about the number of their subsidiaries.

Crédit Mutuel company employs more people globally than QNB Türkiye company, reflecting its scale as a Banking.

Neither QNB Türkiye nor Crédit Mutuel holds SOC 2 Type 1 certification.

Neither QNB Türkiye nor Crédit Mutuel holds SOC 2 Type 2 certification.

Neither QNB Türkiye nor Crédit Mutuel holds ISO 27001 certification.

Neither QNB Türkiye nor Crédit Mutuel holds PCI DSS certification.

Neither QNB Türkiye nor Crédit Mutuel holds HIPAA certification.

Neither QNB Türkiye nor Crédit Mutuel holds GDPR certification.

Latest Global CVEs (Not Company-Specific)

Description

SummaryA command injection vulnerability (CWE-78) has been found to exist in the `wrangler pages deploy` command. The issue occurs because the `--commit-hash` parameter is passed directly to a shell command without proper validation or sanitization, allowing an attacker with control of `--commit-hash` to execute arbitrary commands on the system running Wrangler. Root causeThe commitHash variable, derived from user input via the --commit-hash CLI argument, is interpolated directly into a shell command using template literals (e.g.,  execSync(`git show -s --format=%B ${commitHash}`)). Shell metacharacters are interpreted by the shell, enabling command execution. ImpactThis vulnerability is generally hard to exploit, as it requires --commit-hash to be attacker controlled. The vulnerability primarily affects CI/CD environments where `wrangler pages deploy` is used in automated pipelines and the --commit-hash parameter is populated from external, potentially untrusted sources. An attacker could exploit this to: * Run any shell command. * Exfiltrate environment variables. * Compromise the CI runner to install backdoors or modify build artifacts. Credits Disclosed responsibly by kny4hacker. Mitigation * Wrangler v4 users are requested to upgrade to Wrangler v4.59.1 or higher. * Wrangler v3 users are requested to upgrade to Wrangler v3.114.17 or higher. * Users on Wrangler v2 (EOL) should upgrade to a supported major version.

Risk Information
cvss4
Base: 7.7
Severity: LOW
CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:H/SC:L/SI:L/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

Vulnerability in the Oracle VM VirtualBox product of Oracle Virtualization (component: Core). Supported versions that are affected are 7.1.14 and 7.2.4. Easily exploitable vulnerability allows high privileged attacker with logon to the infrastructure where Oracle VM VirtualBox executes to compromise Oracle VM VirtualBox. While the vulnerability is in Oracle VM VirtualBox, attacks may significantly impact additional products (scope change). Successful attacks of this vulnerability can result in takeover of Oracle VM VirtualBox. CVSS 3.1 Base Score 8.2 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H).

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

Vulnerability in the Oracle VM VirtualBox product of Oracle Virtualization (component: Core). Supported versions that are affected are 7.1.14 and 7.2.4. Easily exploitable vulnerability allows high privileged attacker with logon to the infrastructure where Oracle VM VirtualBox executes to compromise Oracle VM VirtualBox. While the vulnerability is in Oracle VM VirtualBox, attacks may significantly impact additional products (scope change). Successful attacks of this vulnerability can result in unauthorized creation, deletion or modification access to critical data or all Oracle VM VirtualBox accessible data as well as unauthorized access to critical data or complete access to all Oracle VM VirtualBox accessible data and unauthorized ability to cause a partial denial of service (partial DOS) of Oracle VM VirtualBox. CVSS 3.1 Base Score 8.1 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:L).

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

Vulnerability in the Oracle VM VirtualBox product of Oracle Virtualization (component: Core). Supported versions that are affected are 7.1.14 and 7.2.4. Easily exploitable vulnerability allows high privileged attacker with logon to the infrastructure where Oracle VM VirtualBox executes to compromise Oracle VM VirtualBox. While the vulnerability is in Oracle VM VirtualBox, attacks may significantly impact additional products (scope change). Successful attacks of this vulnerability can result in takeover of Oracle VM VirtualBox. CVSS 3.1 Base Score 8.2 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H).

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

Vulnerability in the Oracle VM VirtualBox product of Oracle Virtualization (component: Core). Supported versions that are affected are 7.1.14 and 7.2.4. Easily exploitable vulnerability allows high privileged attacker with logon to the infrastructure where Oracle VM VirtualBox executes to compromise Oracle VM VirtualBox. While the vulnerability is in Oracle VM VirtualBox, attacks may significantly impact additional products (scope change). Successful attacks of this vulnerability can result in takeover of Oracle VM VirtualBox. CVSS 3.1 Base Score 8.2 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H).

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