Comparison Overview

QNB Türkiye

VS

PT Bank Mandiri (Persero) Tbk.

QNB Türkiye

Turkey, Istanbul, TR, 34394
Last Update: 2026-01-18
View Profile
Between 750 and 799
https://www.qnb.com.tr/

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
View Profile

PT Bank Mandiri (Persero) Tbk.

Jl. Gatot Subroto Kav. 36-38, Jakarta, DKI Jakarta, ID, 12190
Last Update: 2026-01-17
Between 800 and 849
https://www.bankmandiri.co.id/

Bank Mandiri was established on 2 October 1998, as part of the bank restructuring program of the Government of Indonesia. In July 1999, four state-owned banks - Bank Bumi Daya, Bank Dagang Negara, Bank Exim and Bapindo - were amalgamated into Bank Mandiri. The history of these four banks can be traced back to over 140 years, and together they had contributed to the beginning of the Indonesian banking sector. We are continuously seeking mutually beneficial business opportunities that create synergies, building alliances and strengthening our supporting businesses with and through our subsidiaries, notably Bank Syariah Mandiri in Islamic banking, PT. Bank Mandiri Taspen in banking, Mandiri Europe in international banking, AXA Mandiri Financial Services in insurance, Mandiri Sekuritas in investment banking, Mandiri Capital Indonesia in venture capital, Mandiri Tunas Finance in multi-finance, Mandiri Utama Finance in multi-finance, and Mandiri International Remittance in remittance. With various subsidiaries that support our businesses, we have further strengthened our position as a prominent financial holdings institution in Indonesia.

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

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/bankmandiri.jpeg
PT Bank Mandiri (Persero) Tbk.
—
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
PT Bank Mandiri (Persero) Tbk.
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 PT Bank Mandiri (Persero) Tbk. 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 — PT Bank Mandiri (Persero) Tbk. (X = Date, Y = Severity)

PT Bank Mandiri (Persero) Tbk. 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/bankmandiri.jpeg
PT Bank Mandiri (Persero) Tbk.
Incidents

No Incident

FAQ

PT Bank Mandiri (Persero) Tbk. company demonstrates a stronger AI Cybersecurity Score compared to QNB Türkiye company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Historically, PT Bank Mandiri (Persero) Tbk. company has disclosed a higher number of cyber incidents compared to QNB Türkiye company.

In the current year, PT Bank Mandiri (Persero) Tbk. company and QNB Türkiye company have not reported any cyber incidents.

Neither PT Bank Mandiri (Persero) Tbk. company nor QNB Türkiye company has reported experiencing a ransomware attack publicly.

Neither PT Bank Mandiri (Persero) Tbk. company nor QNB Türkiye company has reported experiencing a data breach publicly.

Neither PT Bank Mandiri (Persero) Tbk. company nor QNB Türkiye company has reported experiencing targeted cyberattacks publicly.

Neither QNB Türkiye company nor PT Bank Mandiri (Persero) Tbk. company has reported experiencing or disclosing vulnerabilities publicly.

Neither QNB Türkiye nor PT Bank Mandiri (Persero) Tbk. holds any compliance certifications.

Neither company holds any compliance certifications.

PT Bank Mandiri (Persero) Tbk. company has more subsidiaries worldwide compared to QNB Türkiye company.

PT Bank Mandiri (Persero) Tbk. company employs more people globally than QNB Türkiye company, reflecting its scale as a Banking.

Neither QNB Türkiye nor PT Bank Mandiri (Persero) Tbk. holds SOC 2 Type 1 certification.

Neither QNB Türkiye nor PT Bank Mandiri (Persero) Tbk. holds SOC 2 Type 2 certification.

Neither QNB Türkiye nor PT Bank Mandiri (Persero) Tbk. holds ISO 27001 certification.

Neither QNB Türkiye nor PT Bank Mandiri (Persero) Tbk. holds PCI DSS certification.

Neither QNB Türkiye nor PT Bank Mandiri (Persero) Tbk. holds HIPAA certification.

Neither QNB Türkiye nor PT Bank Mandiri (Persero) Tbk. 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.

Published
Date
2026-01-20
Updated
Date
2026-01-20
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
References
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).

Published
Date
2026-01-20
Updated
Date
2026-01-20
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
References
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).

Published
Date
2026-01-20
Updated
Date
2026-01-20
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
References
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).

Published
Date
2026-01-20
Updated
Date
2026-01-20
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
References
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).

Published
Date
2026-01-20
Updated
Date
2026-01-20
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
References