Comparison Overview

SEB

VS

QNB Türkiye

SEB

Kungsträdgårdsgatan 8, Stockholm, Stockholm, SE, 10640
Last Update: 2025-12-17
Between 800 and 849

SEB is a leading northern European financial services group with a strong belief that entrepreneurial minds and innovative companies are key in creating a better world. SEB takes a long-term perspective and supports its customers in good times and bad. In Sweden and the Baltic countries, SEB offers financial advice and a wide range of financial services. In Denmark, Finland, Norway and Germany the bank's operations have a strong focus on corporate and investment banking based on a full-service offering to corporate and institutional clients. The international nature of SEB's business is reflected in its presence in some 20 countries worldwide. Read more about SEB at www.sebgroup.com Privacy note about SEB’s processing of your personal data can be found at: www.sebgroup.com/legal-and-regulatory-information/privacy-at-seb-group Content shared on this page may contain commercial information from SEB.

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

QNB Türkiye

Turkey, Istanbul, undefined, 34394, TR
Last Update: 2025-12-17
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: 12,618
Subsidiaries: 14
12-month incidents
0
Known data breaches
0
Attack type number
1

Compliance Badges Comparison

Security & Compliance Standards Overview

https://images.rankiteo.com/companyimages/seb.jpeg
SEB
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/qnbturkiye.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
Compliance Summary
SEB
100%
Compliance Rate
0/4 Standards Verified
QNB Türkiye
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Banking Industry Average (This Year)

No incidents recorded for SEB in 2025.

Incidents vs Banking Industry Average (This Year)

No incidents recorded for QNB Türkiye in 2025.

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

SEB cyber incidents detection timeline including parent company and subsidiaries

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

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

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/seb.jpeg
SEB
Incidents

No Incident

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

Date Detected: 05/2016
Type:Data Leak
Blog: Blog

Date Detected: 04/2016
Type:Data Leak
Blog: Blog

FAQ

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

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

In the current year, QNB Türkiye company and SEB company have not reported any cyber incidents.

Neither QNB Türkiye company nor SEB company has reported experiencing a ransomware attack publicly.

Neither QNB Türkiye company nor SEB company has reported experiencing a data breach publicly.

Neither QNB Türkiye company nor SEB company has reported experiencing targeted cyberattacks publicly.

Neither SEB company nor QNB Türkiye company has reported experiencing or disclosing vulnerabilities publicly.

Neither SEB nor QNB Türkiye holds any compliance certifications.

Neither company holds any compliance certifications.

QNB Türkiye company has more subsidiaries worldwide compared to SEB company.

SEB company employs more people globally than QNB Türkiye company, reflecting its scale as a Banking.

Neither SEB nor QNB Türkiye holds SOC 2 Type 1 certification.

Neither SEB nor QNB Türkiye holds SOC 2 Type 2 certification.

Neither SEB nor QNB Türkiye holds ISO 27001 certification.

Neither SEB nor QNB Türkiye holds PCI DSS certification.

Neither SEB nor QNB Türkiye holds HIPAA certification.

Neither SEB nor QNB Türkiye holds GDPR certification.

Latest Global CVEs (Not Company-Specific)

Description

Marshmallow is a lightweight library for converting complex objects to and from simple Python datatypes. In versions from 3.0.0rc1 to before 3.26.2 and from 4.0.0 to before 4.1.2, Schema.load(data, many=True) is vulnerable to denial of service attacks. A moderately sized request can consume a disproportionate amount of CPU time. This issue has been patched in version 3.26.2 and 4.1.2.

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

KEDA is a Kubernetes-based Event Driven Autoscaling component. Prior to versions 2.17.3 and 2.18.3, an Arbitrary File Read vulnerability has been identified in KEDA, potentially affecting any KEDA resource that uses TriggerAuthentication to configure HashiCorp Vault authentication. The vulnerability stems from an incorrect or insufficient path validation when loading the Service Account Token specified in spec.hashiCorpVault.credential.serviceAccount. An attacker with permissions to create or modify a TriggerAuthentication resource can exfiltrate the content of any file from the node's filesystem (where the KEDA pod resides) by directing the file's content to a server under their control, as part of the Vault authentication request. The potential impact includes the exfiltration of sensitive system information, such as secrets, keys, or the content of files like /etc/passwd. This issue has been patched in versions 2.17.3 and 2.18.3.

Risk Information
cvss4
Base: 8.2
Severity: LOW
CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/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

Fedify is a TypeScript library for building federated server apps powered by ActivityPub. Prior to versions 1.6.13, 1.7.14, 1.8.15, and 1.9.2, a Regular Expression Denial of Service (ReDoS) vulnerability exists in Fedify's document loader. The HTML parsing regex at packages/fedify/src/runtime/docloader.ts:259 contains nested quantifiers that cause catastrophic backtracking when processing maliciously crafted HTML responses. This issue has been patched in versions 1.6.13, 1.7.14, 1.8.15, and 1.9.2.

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

Authenticated Remote Code Execution (RCE) in PluXml CMS 5.8.22 allows an attacker with administrator panel access to inject a malicious PHP webshell into a theme file (e.g., home.php).

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

An issue was discovered in Xiongmai XM530 IP cameras on firmware V5.00.R02.000807D8.10010.346624.S.ONVIF 21.06. The GetStreamUri exposes RTSP URIs containing hardcoded credentials enabling direct unauthorized video stream access.

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