Comparison Overview

Standard Chartered

VS

BNP Paribas Fortis

Standard Chartered

1 Basinghall Avenue, London, EC2V 5DD, GB
Last Update: 2026-01-17
Between 800 and 849

We are a leading international banking group, with a presence in 54 of the world’s most dynamic markets. Our purpose is to drive commerce and prosperity through our unique diversity, and our heritage and values are expressed in our brand promise, here for good. If you’re interested joining Standard Chartered sign up to our Talent Network. Link: https://www.sc.com/careers/talentnetwork Standard Chartered PLC is listed on the London and Hong Kong stock exchanges.

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

BNP Paribas Fortis

Rue Montagne du Parc 3, Brussels, 1000, BE
Last Update: 2026-01-17

For over 200 years, BNP Paribas Fortis has helped drive the growth and prosperity of Belgium’s economy and communities. The mission of our 12,000 colleagues is clear: be the trusted financial partner for four million individual customers, businesses and organisations. We do this by offering advice and solutions via the channels they prefer: digitally, by phone, via video call or in a bank or post office branch.

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

Compliance Badges Comparison

Security & Compliance Standards Overview

https://images.rankiteo.com/companyimages/standardchartered.jpeg
Standard Chartered
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/bnpparibasfortis.jpeg
BNP Paribas Fortis
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
Standard Chartered
100%
Compliance Rate
0/4 Standards Verified
BNP Paribas Fortis
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Banking Industry Average (This Year)

No incidents recorded for Standard Chartered in 2026.

Incidents vs Banking Industry Average (This Year)

No incidents recorded for BNP Paribas Fortis in 2026.

Incident History — Standard Chartered (X = Date, Y = Severity)

Standard Chartered cyber incidents detection timeline including parent company and subsidiaries

Incident History — BNP Paribas Fortis (X = Date, Y = Severity)

BNP Paribas Fortis cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/standardchartered.jpeg
Standard Chartered
Incidents

Date Detected: 10/2016
Type:Breach
Attack Vector: Compromised ATM Network
Blog: Blog
https://images.rankiteo.com/companyimages/bnpparibasfortis.jpeg
BNP Paribas Fortis
Incidents

Date Detected: 11/2021
Type:Breach
Attack Vector: Physical ATM Skimming Device
Motivation: Financial Gain (Likely)
Blog: Blog

Date Detected: 12/2018
Type:Breach
Attack Vector: ATM Skimming
Motivation: Financial Gain
Blog: Blog

Date Detected: 3/2018
Type:Breach
Attack Vector: Email Account Compromise
Blog: Blog

FAQ

Standard Chartered company demonstrates a stronger AI Cybersecurity Score compared to BNP Paribas Fortis company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

BNP Paribas Fortis company has faced a higher number of disclosed cyber incidents historically compared to Standard Chartered company.

In the current year, BNP Paribas Fortis company and Standard Chartered company have not reported any cyber incidents.

Neither BNP Paribas Fortis company nor Standard Chartered company has reported experiencing a ransomware attack publicly.

Both BNP Paribas Fortis company and Standard Chartered company have disclosed experiencing at least one data breach.

Neither BNP Paribas Fortis company nor Standard Chartered company has reported experiencing targeted cyberattacks publicly.

Neither Standard Chartered company nor BNP Paribas Fortis company has reported experiencing or disclosing vulnerabilities publicly.

Neither Standard Chartered nor BNP Paribas Fortis holds any compliance certifications.

Neither company holds any compliance certifications.

BNP Paribas Fortis company has more subsidiaries worldwide compared to Standard Chartered company.

Standard Chartered company employs more people globally than BNP Paribas Fortis company, reflecting its scale as a Banking.

Neither Standard Chartered nor BNP Paribas Fortis holds SOC 2 Type 1 certification.

Neither Standard Chartered nor BNP Paribas Fortis holds SOC 2 Type 2 certification.

Neither Standard Chartered nor BNP Paribas Fortis holds ISO 27001 certification.

Neither Standard Chartered nor BNP Paribas Fortis holds PCI DSS certification.

Neither Standard Chartered nor BNP Paribas Fortis holds HIPAA certification.

Neither Standard Chartered nor BNP Paribas Fortis 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