Comparison Overview

LSEG

VS

HSBC

LSEG

10 Paternoster Square, London, England, GB, EC4M 7DX
Last Update: 2025-11-23
Between 750 and 799

LSEG (London Stock Exchange Group) is a diversified international markets infrastructure business —earning our clients’ trust for over 300 years. That legacy of customer-focused excellence ensures that you can rely on our expertise in capital formation, intellectual property and risk and balance sheet management. As global leaders in financial indexing, benchmarking and analytic services, we offer unrivalled access to international capital markets. Our high-performance technology solutions enable companies worldwide to access funds for growth and development. And with our Data & Analytics, Capital Markets and Post Trade divisions, we provide a comprehensive, integrated suite of trusted financial market infrastructure services that help our customers pursue—and achieve—their ambitions. You can count on our open access model for unparalleled partnership, flexibility, stability, and support across all of our businesses. That’s how we make a difference— ensuring people can meet their potential—worldwide.

NAICS: 52
NAICS Definition: Finance and Insurance
Employees: 22,998
Subsidiaries: 19
12-month incidents
0
Known data breaches
0
Attack type number
0

HSBC

8 Canada Square, None, London, None, GB, E14 5HQ
Last Update: 2025-11-26
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
7
Attack type number
1

Compliance Badges Comparison

Security & Compliance Standards Overview

https://images.rankiteo.com/companyimages/london-stock-exchange-group.jpeg
LSEG
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
LSEG
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 LSEG in 2025.

Incidents vs Financial Services Industry Average (This Year)

No incidents recorded for HSBC in 2025.

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

LSEG 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/london-stock-exchange-group.jpeg
LSEG
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: 12/2015
Type:Breach
Attack Vector: Physical Media Loss
Blog: Blog

FAQ

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

HSBC company has historically faced a number of disclosed cyber incidents, whereas LSEG company has not reported any.

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

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

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

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

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

Neither LSEG nor HSBC holds any compliance certifications.

Neither company holds any compliance certifications.

LSEG company has more subsidiaries worldwide compared to HSBC company.

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

Neither LSEG nor HSBC holds SOC 2 Type 1 certification.

Neither LSEG nor HSBC holds SOC 2 Type 2 certification.

Neither LSEG nor HSBC holds ISO 27001 certification.

Neither LSEG nor HSBC holds PCI DSS certification.

Neither LSEG nor HSBC holds HIPAA certification.

Neither LSEG nor HSBC holds GDPR certification.

Latest Global CVEs (Not Company-Specific)

Description

Angular is a development platform for building mobile and desktop web applications using TypeScript/JavaScript and other languages. Prior to versions 19.2.16, 20.3.14, and 21.0.1, there is a XSRF token leakage via protocol-relative URLs in angular HTTP clients. The vulnerability is a Credential Leak by App Logic that leads to the unauthorized disclosure of the Cross-Site Request Forgery (XSRF) token to an attacker-controlled domain. Angular's HttpClient has a built-in XSRF protection mechanism that works by checking if a request URL starts with a protocol (http:// or https://) to determine if it is cross-origin. If the URL starts with protocol-relative URL (//), it is incorrectly treated as a same-origin request, and the XSRF token is automatically added to the X-XSRF-TOKEN header. This issue has been patched in versions 19.2.16, 20.3.14, and 21.0.1. A workaround for this issue involves avoiding using protocol-relative URLs (URLs starting with //) in HttpClient requests. All backend communication URLs should be hardcoded as relative paths (starting with a single /) or fully qualified, trusted absolute URLs.

Risk Information
cvss4
Base: 7.7
Severity: LOW
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:N/SC:H/SI:N/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

Forge (also called `node-forge`) is a native implementation of Transport Layer Security in JavaScript. An Uncontrolled Recursion vulnerability in node-forge versions 1.3.1 and below enables remote, unauthenticated attackers to craft deep ASN.1 structures that trigger unbounded recursive parsing. This leads to a Denial-of-Service (DoS) via stack exhaustion when parsing untrusted DER inputs. This issue has been patched in version 1.3.2.

Risk Information
cvss4
Base: 8.7
Severity: LOW
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/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

Forge (also called `node-forge`) is a native implementation of Transport Layer Security in JavaScript. An Integer Overflow vulnerability in node-forge versions 1.3.1 and below enables remote, unauthenticated attackers to craft ASN.1 structures containing OIDs with oversized arcs. These arcs may be decoded as smaller, trusted OIDs due to 32-bit bitwise truncation, enabling the bypass of downstream OID-based security decisions. This issue has been patched in version 1.3.2.

Risk Information
cvss4
Base: 6.3
Severity: LOW
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/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

Suricata is a network IDS, IPS and NSM engine developed by the OISF (Open Information Security Foundation) and the Suricata community. Prior to versions 7.0.13 and 8.0.2, working with large buffers in Lua scripts can lead to a stack overflow. Users of Lua rules and output scripts may be affected when working with large buffers. This includes a rule passing a large buffer to a Lua script. This issue has been patched in versions 7.0.13 and 8.0.2. A workaround for this issue involves disabling Lua rules and output scripts, or making sure limits, such as stream.depth.reassembly and HTTP response body limits (response-body-limit), are set to less than half the stack size.

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

Suricata is a network IDS, IPS and NSM engine developed by the OISF (Open Information Security Foundation) and the Suricata community. In versions from 8.0.0 to before 8.0.2, a NULL dereference can occur when the entropy keyword is used in conjunction with base64_data. This issue has been patched in version 8.0.2. A workaround involves disabling rules that use entropy in conjunction with base64_data.

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