Comparison Overview

Sumitomo Mitsui Banking Corporation – SMBC Group

VS

HSBC

Sumitomo Mitsui Banking Corporation – SMBC Group

1丁目 1-2, Marunouchi Chiyoda-Ku,, Tokyo, undefined, undefined, JP
Last Update: 2026-01-18
View Profile
Between 800 and 849
http://www.smfg.co.jp/english/

SMBC Group is a top-tier global financial group. Headquartered in Tokyo and with a 400-year history, SMBC Group offers a diverse range of financial services, including banking, leasing, securities, credit cards, and consumer finance. The Group has more than 150 offices and 86,000 employees worldwide in nearly 40 countries. Sumitomo Mitsui Financial Group, Inc. (SMFG) is the holding company of SMBC Group, one of the three largest banking groups in Japan. SMFG's shares trade on the Tokyo and Nagoya stock exchanges, and its ADRs trade on the New York Stock Exchange (NYSE: SMFG). Americas: https://www.smbcgroup.com/ EMEA: https://www.smbcgroup.com/emea/ APAC: https://www.smbc.co.jp/asia/ Tokyo: https://www.smfg.co.jp/english/

NAICS: 52
NAICS Definition: Finance and Insurance
Employees: 12,849
Subsidiaries: 2
12-month incidents
0
Known data breaches
0
Attack type number
0
View Profile

HSBC

8 Canada Square, London, E14 5HQ, GB
Last Update: 2026-01-17
Between 800 and 849
http://www.hsbc.com

Opening up a world of opportunity for our customers, investors, ourselves and the planet. We're a financial services organisation that serves more than 40 million customers, ranging from individual savers and investors to some of the world’s biggest companies and governments. Our network covers 58 countries and territories, and we’re here to use our unique expertise, capabilities, breadth and perspectives to open up a world of opportunity for our customers. HSBC is listed on the London, Hong Kong, New York, and Bermuda stock exchanges. To view our social media terms and conditions please visit the following webpage: http://www.hsbc.com/social-TandCs

NAICS: 52
NAICS Definition: Finance and Insurance
Employees: 192,405
Subsidiaries: 8
12-month incidents
0
Known data breaches
6
Attack type number
1

Compliance Badges Comparison

Security & Compliance Standards Overview

https://images.rankiteo.com/companyimages/sumitomo-mitsui-banking-corporation.jpeg
Sumitomo Mitsui Banking Corporation – SMBC Group
—
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/hsbc.jpeg
HSBC
—
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
Sumitomo Mitsui Banking Corporation – SMBC Group
100%
Compliance Rate
0/4 Standards Verified
HSBC
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Financial Services Industry Average (This Year)

No incidents recorded for Sumitomo Mitsui Banking Corporation – SMBC Group in 2026.

Incidents vs Financial Services Industry Average (This Year)

No incidents recorded for HSBC in 2026.

Incident History — Sumitomo Mitsui Banking Corporation – SMBC Group (X = Date, Y = Severity)

Sumitomo Mitsui Banking Corporation – SMBC Group cyber incidents detection timeline including parent company and subsidiaries

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

HSBC cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/sumitomo-mitsui-banking-corporation.jpeg
Sumitomo Mitsui Banking Corporation – SMBC Group
Incidents

No Incident

https://images.rankiteo.com/companyimages/hsbc.jpeg
HSBC
Incidents

Date Detected: 10/2018
Type:Breach
Blog: Blog

Date Detected: 12/2015
Type:Breach
Attack Vector: Unauthorized Access
Blog: Blog

Date Detected: 6/2015
Type:Breach
Attack Vector: Mistakenly Sent Data
Blog: Blog

FAQ

Sumitomo Mitsui Banking Corporation – SMBC Group company demonstrates a stronger AI Cybersecurity Score compared to HSBC company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

HSBC company has historically faced a number of disclosed cyber incidents, whereas Sumitomo Mitsui Banking Corporation – SMBC Group company has not reported any.

In the current year, HSBC company and Sumitomo Mitsui Banking Corporation – SMBC Group company have not reported any cyber incidents.

Neither HSBC company nor Sumitomo Mitsui Banking Corporation – SMBC Group company has reported experiencing a ransomware attack publicly.

HSBC company has disclosed at least one data breach, while Sumitomo Mitsui Banking Corporation – SMBC Group company has not reported such incidents publicly.

Neither HSBC company nor Sumitomo Mitsui Banking Corporation – SMBC Group company has reported experiencing targeted cyberattacks publicly.

Neither Sumitomo Mitsui Banking Corporation – SMBC Group company nor HSBC company has reported experiencing or disclosing vulnerabilities publicly.

Neither Sumitomo Mitsui Banking Corporation – SMBC Group nor HSBC holds any compliance certifications.

Neither company holds any compliance certifications.

HSBC company has more subsidiaries worldwide compared to Sumitomo Mitsui Banking Corporation – SMBC Group company.

HSBC company employs more people globally than Sumitomo Mitsui Banking Corporation – SMBC Group company, reflecting its scale as a Financial Services.

Neither Sumitomo Mitsui Banking Corporation – SMBC Group nor HSBC holds SOC 2 Type 1 certification.

Neither Sumitomo Mitsui Banking Corporation – SMBC Group nor HSBC holds SOC 2 Type 2 certification.

Neither Sumitomo Mitsui Banking Corporation – SMBC Group nor HSBC holds ISO 27001 certification.

Neither Sumitomo Mitsui Banking Corporation – SMBC Group nor HSBC holds PCI DSS certification.

Neither Sumitomo Mitsui Banking Corporation – SMBC Group nor HSBC holds HIPAA certification.

Neither Sumitomo Mitsui Banking Corporation – SMBC Group nor HSBC 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