Comparison Overview

National Bank of Canada

VS

Banque Misr

National Bank of Canada

800 Rue Saint-Jacques, Montreal, Quebec, H3C 1A3, CA
Last Update: 2026-01-17
View Profile
Between 750 and 799
http://www.bnc.ca

At National Bank, we believe in the potential of each individual, and that even the smallest gestures can make a big difference. When we help others accomplish their projects, we help empower them and the community at large. We try to make a difference through innovation, but above all, by putting people first. By taking the time to listen and letting our actions speak for themselves. By remaining bold and passionate. By developing lasting relationships as partners and allies. Together we can achieve great things and create a positive impact. Want to learn more about us? For advice on your personal finances, visit: nbc.ca/advice For advice on your business, visit: nbc.ca/business For career opportunities, visit: jobs.nbc.ca For all the latest news, visit: nbc.ca/news By clicking "Follow" above, you may receive communications from National Bank, either in your LinkedIn inbox or by other means via LinkedIn, about products and services that could interest you. Learn more at: www.nbc.ca/socialnetworks.

NAICS: 52211
NAICS Definition: Commercial Banking
Employees: 19,281
Subsidiaries: 11
12-month incidents
0
Known data breaches
0
Attack type number
0
View Profile

Banque Misr

151 Mohamed Farid st.,Cairo Egypt, Call Center 19888, Cairo, EG
Last Update: 2026-01-18
Between 750 and 799
http://www.banquemisr.com

Banque Misr (BM) was established in 1920 by the pioneer economist and financial expert Mohamed Talaat Harb Pasha, who spearheaded the concept of investing in national savings and directing them toward economic and social development. Thus, Banque Misr was established as the first wholly Egyptian-owned bank. Banque Misr has funded many businesses spanning across multiple domestic sectors, such as: textiles, insurance, transportation, aviation, entertainment, and filmmaking. Currently, BM owns shares in 157 companies across different fields, ranging from finance, tourism, housing, agriculture and food, and communication and information technology. A true pioneer in the region, Banque Misr became the first bank in Egypt and North Africa to comply with PCI data security standards, upon obtaining the latest version of the global Payment Card Industry Data Security Standard (PCI DSS 3.2.1) certification. Utilizing the latest technology in the banking sector, Banque Misr is constantly looking to expand customer access to banking services. Today, Banque Misr is proud to offer one of Egypt’s largest ATM networks, located across all areas of Egypt. Banque Misr’s role is visible in all economic fields due to its geographic outreach. The bank has more than 20,000 employees, serving a large base of more than 13 million clients in Egypt, with a total paid-up capital amounting to EGP 15 billion. The bank has more than 800 electronically integrated local branches located nationwide to provide the best and most accessible services to customers. Banque Misr also values its regional and international presence, which includes its five branches in the United Arab Emirates and one in France. In addition, the bank’s international presence includes subsidiaries in Lebanon and Germany, as well as representative offices in China, Russia, South Korea, and Italy and a global network of correspondents.

NAICS: 52211
NAICS Definition: Commercial Banking
Employees: 20,739
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/national-bank-of-canada.jpeg
National Bank of Canada
—
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/banque-misr.jpeg
Banque Misr
—
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
National Bank of Canada
100%
Compliance Rate
0/4 Standards Verified
Banque Misr
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Banking Industry Average (This Year)

No incidents recorded for National Bank of Canada in 2026.

Incidents vs Banking Industry Average (This Year)

No incidents recorded for Banque Misr in 2026.

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

National Bank of Canada cyber incidents detection timeline including parent company and subsidiaries

Incident History — Banque Misr (X = Date, Y = Severity)

Banque Misr cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/national-bank-of-canada.jpeg
National Bank of Canada
Incidents

No Incident

https://images.rankiteo.com/companyimages/banque-misr.jpeg
Banque Misr
Incidents

No Incident

FAQ

Banque Misr company demonstrates a stronger AI Cybersecurity Score compared to National Bank of Canada company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Historically, Banque Misr company has disclosed a higher number of cyber incidents compared to National Bank of Canada company.

In the current year, Banque Misr company and National Bank of Canada company have not reported any cyber incidents.

Neither Banque Misr company nor National Bank of Canada company has reported experiencing a ransomware attack publicly.

Neither Banque Misr company nor National Bank of Canada company has reported experiencing a data breach publicly.

Neither Banque Misr company nor National Bank of Canada company has reported experiencing targeted cyberattacks publicly.

Neither National Bank of Canada company nor Banque Misr company has reported experiencing or disclosing vulnerabilities publicly.

Neither National Bank of Canada nor Banque Misr holds any compliance certifications.

Neither company holds any compliance certifications.

National Bank of Canada company has more subsidiaries worldwide compared to Banque Misr company.

Banque Misr company employs more people globally than National Bank of Canada company, reflecting its scale as a Banking.

Neither National Bank of Canada nor Banque Misr holds SOC 2 Type 1 certification.

Neither National Bank of Canada nor Banque Misr holds SOC 2 Type 2 certification.

Neither National Bank of Canada nor Banque Misr holds ISO 27001 certification.

Neither National Bank of Canada nor Banque Misr holds PCI DSS certification.

Neither National Bank of Canada nor Banque Misr holds HIPAA certification.

Neither National Bank of Canada nor Banque Misr 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