Comparison Overview

Nomura

VS

HSBC

Nomura

1-9-1 Nihonbashi, Tokyo, undefined, 103-8645, JP
Last Update: 2025-12-09
Between 750 and 799

Nomura is a global financial services group with an integrated network spanning approximately 30 countries and regions. By connecting markets East & West, Nomura services the needs of individuals, institutions, corporates and governments through its three business divisions: Wealth Management, Investment Management, and Wholesale (Global Markets and Investment Banking). Founded in 1925, the firm is built on a tradition of disciplined entrepreneurship, serving clients with creative solutions and considered thought leadership.

NAICS: 52
NAICS Definition: Finance and Insurance
Employees: 15,162
Subsidiaries: 3
12-month incidents
0
Known data breaches
0
Attack type number
1

HSBC

8 Canada Square, None, London, None, GB, E14 5HQ
Last Update: 2025-12-11
Between 800 and 849

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: 186,976
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/nomura.jpeg
Nomura
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
Nomura
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 Nomura in 2025.

Incidents vs Financial Services Industry Average (This Year)

No incidents recorded for HSBC in 2025.

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

Nomura 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/nomura.jpeg
Nomura
Incidents

Date Detected: 05/2020
Type:Data Leak
Attack Vector: Insider Threat
Blog: Blog
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

HSBC company demonstrates a stronger AI Cybersecurity Score compared to Nomura company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

HSBC company has faced a higher number of disclosed cyber incidents historically compared to Nomura company.

In the current year, HSBC company and Nomura company have not reported any cyber incidents.

Neither HSBC company nor Nomura company has reported experiencing a ransomware attack publicly.

HSBC company has disclosed at least one data breach, while Nomura company has not reported such incidents publicly.

Neither HSBC company nor Nomura company has reported experiencing targeted cyberattacks publicly.

Neither Nomura company nor HSBC company has reported experiencing or disclosing vulnerabilities publicly.

Neither Nomura nor HSBC holds any compliance certifications.

Neither company holds any compliance certifications.

HSBC company has more subsidiaries worldwide compared to Nomura company.

HSBC company employs more people globally than Nomura company, reflecting its scale as a Financial Services.

Neither Nomura nor HSBC holds SOC 2 Type 1 certification.

Neither Nomura nor HSBC holds SOC 2 Type 2 certification.

Neither Nomura nor HSBC holds ISO 27001 certification.

Neither Nomura nor HSBC holds PCI DSS certification.

Neither Nomura nor HSBC holds HIPAA certification.

Neither Nomura nor HSBC holds GDPR certification.

Latest Global CVEs (Not Company-Specific)

Description

NXLog Agent before 6.11 can load a file specified by the OPENSSL_CONF environment variable.

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

uriparser through 0.9.9 allows unbounded recursion and stack consumption, as demonstrated by ParseMustBeSegmentNzNc with large input containing many commas.

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

A vulnerability was detected in Mayan EDMS up to 4.10.1. The affected element is an unknown function of the file /authentication/. The manipulation results in cross site scripting. The attack may be performed from remote. The exploit is now public and may be used. Upgrading to version 4.10.2 is sufficient to fix this issue. You should upgrade the affected component. The vendor confirms that this is "[f]ixed in version 4.10.2". Furthermore, that "[b]ackports for older versions in process and will be out as soon as their respective CI pipelines complete."

Risk Information
cvss2
Base: 5.0
Severity: LOW
AV:N/AC:L/Au:N/C:N/I:P/A:N
cvss3
Base: 4.3
Severity: LOW
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N
cvss4
Base: 5.3
Severity: LOW
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:P/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

MJML through 4.18.0 allows mj-include directory traversal to test file existence and (in the type="css" case) read files. NOTE: this issue exists because of an incomplete fix for CVE-2020-12827.

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

A half-blind Server Side Request Forgery (SSRF) vulnerability exists in kube-controller-manager when using the in-tree Portworx StorageClass. This vulnerability allows authorized users to leak arbitrary information from unprotected endpoints in the control plane’s host network (including link-local or loopback services).

Risk Information
cvss3
Base: 5.8
Severity: HIGH
CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:H/I:N/A:N