Comparison Overview

Sberbank

VS

National Bank of Egypt (NBE)

Sberbank

RU
Last Update: 2026-01-18
View Profile
Between 800 and 849
https://sber.ru

Сбер — крупнейший банк в России, поставщик надёжных технологических решений и один из ведущих финансовых институтов страны. Мы не боимся меняться и открывать новые горизонты, но в то же время остаёмся верными принципам, сформированным за нашу 180-летнюю историю. Такой подход позволяет нам создавать и развивать десятки технологичных направлений. Нашими сервисами пользуются миллионы людей, а над их созданием и совершенствованием работают десятки тысяч сотрудников. Sber is the largest bank in Russia, supplier of reliable technological solutions and one of the leading national financial institutions. We are not afraid to change and open up new horizons, but at the same time we remain true to the principles that have been formed over our 180-year history. This approach allows us to create and develop dozens of technological areas. Our services are used by millions of people, and thousands of employees are working on their creation and improvement.

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

National Bank of Egypt (NBE)

1187 Cornish El Nile Street, Boulak, Cairo, undefined, EG
Last Update: 2026-01-18
Between 750 and 799
http://www.nbe.com.eg

Since its inception in 1898 with a capital of GBP1 million, NBE has been regarded as one of the oldest and most respected commercial banks in Egypt.Never isolated from national issues or concerns, NBE has been the primary supporter of Egypt’s national economy by financing the major Egyptian national projects. NBE’s missions and operations have continuously evolved throughout history and the economic and political changes experienced by the country.NBE was entrusted with issuing banknotes and handling government accounts, then in the 1950’s its activities evolved to undertaking the duties of the Central Bank. In the 1960’s it focused on commercial banking while still handling the central banking duties in locations where the Central Bank had no branches. Eventually, issuing and managing Investment Certificates for the State.NBE currently controls 23.6% of the market share of total assets in the Egyptian banking sector, 25.8% of total deposits, and 21.8% of total loans. NBE owns a large network includes over 337 branches, offices and banking units across the country, alongside an international presence through NBE (United Kingdom), NBE (Republic of the Sudan) and NBE’s branches in New York (United States of America) and Shanghai (People’s Republic of China), as well as representative offices in Johannesburg (South Africa), Dubai (United Arab Emirates), and Adis Ababa (Republic of Ethiopia), in addition to a branch in the Dubai International Finance Center.NBE also has a network of correspondents throughout the world, but centered in Europe— Egypt’s primary trade partner.NBE is always keen on an effective presence in brokerage, financing different sectors, and maintaining the client’s trust by offing the best and latest services.Whilst leading the local banking market,NBE is continuously upgrading its network of branches and channels of electronic communication, and strives to refine its human resources through advanced national and international training programs.

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

Compliance Badges Comparison

Security & Compliance Standards Overview

https://images.rankiteo.com/companyimages/sberbank.jpeg
Sberbank
—
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/national-bank-of-egypt.jpeg
National Bank of Egypt (NBE)
—
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
Sberbank
100%
Compliance Rate
0/4 Standards Verified
National Bank of Egypt (NBE)
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Banking Industry Average (This Year)

No incidents recorded for Sberbank in 2026.

Incidents vs Banking Industry Average (This Year)

No incidents recorded for National Bank of Egypt (NBE) in 2026.

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

Sberbank cyber incidents detection timeline including parent company and subsidiaries

Incident History — National Bank of Egypt (NBE) (X = Date, Y = Severity)

National Bank of Egypt (NBE) cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/sberbank.jpeg
Sberbank
Incidents

No Incident

https://images.rankiteo.com/companyimages/national-bank-of-egypt.jpeg
National Bank of Egypt (NBE)
Incidents

No Incident

FAQ

Sberbank company demonstrates a stronger AI Cybersecurity Score compared to National Bank of Egypt (NBE) company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Historically, National Bank of Egypt (NBE) company has disclosed a higher number of cyber incidents compared to Sberbank company.

In the current year, National Bank of Egypt (NBE) company and Sberbank company have not reported any cyber incidents.

Neither National Bank of Egypt (NBE) company nor Sberbank company has reported experiencing a ransomware attack publicly.

Neither National Bank of Egypt (NBE) company nor Sberbank company has reported experiencing a data breach publicly.

Neither National Bank of Egypt (NBE) company nor Sberbank company has reported experiencing targeted cyberattacks publicly.

Neither Sberbank company nor National Bank of Egypt (NBE) company has reported experiencing or disclosing vulnerabilities publicly.

Neither Sberbank nor National Bank of Egypt (NBE) holds any compliance certifications.

Neither company holds any compliance certifications.

Sberbank company has more subsidiaries worldwide compared to National Bank of Egypt (NBE) company.

National Bank of Egypt (NBE) company employs more people globally than Sberbank company, reflecting its scale as a Banking.

Neither Sberbank nor National Bank of Egypt (NBE) holds SOC 2 Type 1 certification.

Neither Sberbank nor National Bank of Egypt (NBE) holds SOC 2 Type 2 certification.

Neither Sberbank nor National Bank of Egypt (NBE) holds ISO 27001 certification.

Neither Sberbank nor National Bank of Egypt (NBE) holds PCI DSS certification.

Neither Sberbank nor National Bank of Egypt (NBE) holds HIPAA certification.

Neither Sberbank nor National Bank of Egypt (NBE) 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