Comparison Overview

Evolve Bank & Trust

VS

LSEG

Evolve Bank & Trust

6000 Poplar Avenue, Suite 300, Memphis, Tennessee, US, 38119
Last Update: 2025-11-28
Between 0 and 549

For a hundred years, Evolve Bank & Trust has been dedicated to delivering superior financial services. From our roots in Personal and Business Banking & Lending to our work as pioneers in the Banking-as-a-Service (“BaaS”) provider space, Evolve is recognized as a global leader. Nacha named Evolve a Top 50 ACH Originator, and Tearsheet named Evolve Partner Bank of the Year. Evolve has been voted a Top Workplace every year since 2013 and ranked on Inc. Magazine’s 5000 List of the fastest-growing private companies. Member FDIC. Equal Housing Lender. NMLS# 509256

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

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

Compliance Badges Comparison

Security & Compliance Standards Overview

https://images.rankiteo.com/companyimages/evolve-bank-&-trust.jpeg
Evolve Bank & Trust
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/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
Compliance Summary
Evolve Bank & Trust
100%
Compliance Rate
0/4 Standards Verified
LSEG
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Financial Services Industry Average (This Year)

No incidents recorded for Evolve Bank & Trust in 2025.

Incidents vs Financial Services Industry Average (This Year)

No incidents recorded for LSEG in 2025.

Incident History — Evolve Bank & Trust (X = Date, Y = Severity)

Evolve Bank & Trust cyber incidents detection timeline including parent company and subsidiaries

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

LSEG cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/evolve-bank-&-trust.jpeg
Evolve Bank & Trust
Incidents

Date Detected: 7/2024
Type:Breach
Blog: Blog

Date Detected: 6/2024
Type:Ransomware
Motivation: Financial gain and disruption
Blog: Blog

Date Detected: 5/2024
Type:Breach
Blog: Blog
https://images.rankiteo.com/companyimages/london-stock-exchange-group.jpeg
LSEG
Incidents

No Incident

FAQ

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

Evolve Bank & Trust company has historically faced a number of disclosed cyber incidents, whereas LSEG company has not reported any.

In the current year, LSEG company and Evolve Bank & Trust company have not reported any cyber incidents.

Evolve Bank & Trust company has confirmed experiencing a ransomware attack, while LSEG company has not reported such incidents publicly.

Evolve Bank & Trust company has disclosed at least one data breach, while the other LSEG company has not reported such incidents publicly.

Neither LSEG company nor Evolve Bank & Trust company has reported experiencing targeted cyberattacks publicly.

Neither Evolve Bank & Trust company nor LSEG company has reported experiencing or disclosing vulnerabilities publicly.

Neither Evolve Bank & Trust nor LSEG holds any compliance certifications.

Neither company holds any compliance certifications.

LSEG company has more subsidiaries worldwide compared to Evolve Bank & Trust company.

LSEG company employs more people globally than Evolve Bank & Trust company, reflecting its scale as a Financial Services.

Neither Evolve Bank & Trust nor LSEG holds SOC 2 Type 1 certification.

Neither Evolve Bank & Trust nor LSEG holds SOC 2 Type 2 certification.

Neither Evolve Bank & Trust nor LSEG holds ISO 27001 certification.

Neither Evolve Bank & Trust nor LSEG holds PCI DSS certification.

Neither Evolve Bank & Trust nor LSEG holds HIPAA certification.

Neither Evolve Bank & Trust nor LSEG holds GDPR certification.

Latest Global CVEs (Not Company-Specific)

Description

ThingsBoard in versions prior to v4.2.1 allows an authenticated user to upload malicious SVG images via the "Image Gallery", leading to a Stored Cross-Site Scripting (XSS) vulnerability. The exploit can be triggered when any user accesses the public API endpoint of the malicious SVG images, or if the malicious images are embedded in an `iframe` element, during a widget creation, deployed to any page of the platform (e.g., dashboards), and accessed during normal operations. The vulnerability resides in the `ImageController`, which fails to restrict the execution of JavaScript code when an image is loaded by the user's browser. This vulnerability can lead to the execution of malicious code in the context of other users' sessions, potentially compromising their accounts and allowing unauthorized actions.

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

Mattermost versions 11.0.x <= 11.0.2, 10.12.x <= 10.12.1, 10.11.x <= 10.11.4, 10.5.x <= 10.5.12 fail to to verify that the token used during the code exchange originates from the same authentication flow, which allows an authenticated user to perform account takeover via a specially crafted email address used when switching authentication methods and sending a request to the /users/login/sso/code-exchange endpoint. The vulnerability requires ExperimentalEnableAuthenticationTransfer to be enabled (default: enabled) and RequireEmailVerification to be disabled (default: disabled).

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

Mattermost versions 11.0.x <= 11.0.2, 10.12.x <= 10.12.1, 10.11.x <= 10.11.4, 10.5.x <= 10.5.12 fail to sanitize team email addresses to be visible only to Team Admins, which allows any authenticated user to view team email addresses via the GET /api/v4/channels/{channel_id}/common_teams endpoint

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

Exposure of email service credentials to users without administrative rights in Devolutions Server.This issue affects Devolutions Server: before 2025.2.21, before 2025.3.9.

Description

Exposure of credentials in unintended requests in Devolutions Server.This issue affects Server: through 2025.2.20, through 2025.3.8.