Comparison Overview

Moody's Analytics

VS

Lloyds Banking Group

Moody's Analytics

7 World Trade Center, New York, 10007, US
Last Update: 2025-12-07
Between 750 and 799

In an era where risks are multiplying and increasingly interconnected, Moody’s helps organizations make sense of the complexities. By combining data, intelligence, and risk expertise with groundbreaking technologies and a seamless customer experience, we deliver relevant insights on interconnected risk to thousands of organizations worldwide – enabling business and financial leaders to act decisively and thrive amid uncertainty. → Follow Moody’s Corporation for updates about our company, people, careers, and more

NAICS: 52
NAICS Definition: Finance and Insurance
Employees: 11,739
Subsidiaries: 5
12-month incidents
0
Known data breaches
0
Attack type number
0

Lloyds Banking Group

25 Gresham Street, London, UK, GB, EC2V 7HN
Last Update: 2025-12-09

Our purpose is Helping Britain Prosper. We do this by creating a more sustainable and inclusive future for people and businesses, shaping finance as a force for good. We're part of an ever-changing industry and are currently on a journey to shape the financial services of the future, whilst supporting our customers’ changing needs. The scale and reach of our Group means we can offer a broad range of opportunities to learn, grow and develop. Our values-led culture and approach to inclusion and diversity means we can all make a real difference together.

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

Compliance Badges Comparison

Security & Compliance Standards Overview

https://images.rankiteo.com/companyimages/moodys-analytics.jpeg
Moody's Analytics
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/lloyds-banking-group.jpeg
Lloyds Banking 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
Compliance Summary
Moody's Analytics
100%
Compliance Rate
0/4 Standards Verified
Lloyds Banking Group
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Financial Services Industry Average (This Year)

No incidents recorded for Moody's Analytics in 2025.

Incidents vs Financial Services Industry Average (This Year)

No incidents recorded for Lloyds Banking Group in 2025.

Incident History — Moody's Analytics (X = Date, Y = Severity)

Moody's Analytics cyber incidents detection timeline including parent company and subsidiaries

Incident History — Lloyds Banking Group (X = Date, Y = Severity)

Lloyds Banking Group cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/moodys-analytics.jpeg
Moody's Analytics
Incidents

No Incident

https://images.rankiteo.com/companyimages/lloyds-banking-group.jpeg
Lloyds Banking Group
Incidents

Date Detected: 6/2006
Type:Breach
Attack Vector: Physical Theft
Blog: Blog

FAQ

Lloyds Banking Group company demonstrates a stronger AI Cybersecurity Score compared to Moody's Analytics company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Lloyds Banking Group company has historically faced a number of disclosed cyber incidents, whereas Moody's Analytics company has not reported any.

In the current year, Lloyds Banking Group company and Moody's Analytics company have not reported any cyber incidents.

Neither Lloyds Banking Group company nor Moody's Analytics company has reported experiencing a ransomware attack publicly.

Lloyds Banking Group company has disclosed at least one data breach, while Moody's Analytics company has not reported such incidents publicly.

Neither Lloyds Banking Group company nor Moody's Analytics company has reported experiencing targeted cyberattacks publicly.

Neither Moody's Analytics company nor Lloyds Banking Group company has reported experiencing or disclosing vulnerabilities publicly.

Neither Moody's Analytics nor Lloyds Banking Group holds any compliance certifications.

Neither company holds any compliance certifications.

Moody's Analytics company has more subsidiaries worldwide compared to Lloyds Banking Group company.

Lloyds Banking Group company employs more people globally than Moody's Analytics company, reflecting its scale as a Financial Services.

Neither Moody's Analytics nor Lloyds Banking Group holds SOC 2 Type 1 certification.

Neither Moody's Analytics nor Lloyds Banking Group holds SOC 2 Type 2 certification.

Neither Moody's Analytics nor Lloyds Banking Group holds ISO 27001 certification.

Neither Moody's Analytics nor Lloyds Banking Group holds PCI DSS certification.

Neither Moody's Analytics nor Lloyds Banking Group holds HIPAA certification.

Neither Moody's Analytics nor Lloyds Banking Group holds GDPR certification.

Latest Global CVEs (Not Company-Specific)

Description

FreePBX Endpoint Manager is a module for managing telephony endpoints in FreePBX systems. Versions prior to 16.0.96 and 17.0.1 through 17.0.9 have a weak default password. By default, this is a 6 digit numeric value which can be brute forced. (This is the app_password parameter). Depending on local configuration, this password could be the extension, voicemail, user manager, DPMA or EPM phone admin password. This issue is fixed in versions 16.0.96 and 17.0.10.

Risk Information
cvss4
Base: 6.9
Severity: LOW
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/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

Neuron is a PHP framework for creating and orchestrating AI Agents. In versions 2.8.11 and below, the MySQLWriteTool executes arbitrary SQL provided by the caller using PDO::prepare() + execute() without semantic restrictions. This is consistent with the name (“write tool”), but in an LLM/agent context it becomes a high-risk capability: prompt injection or indirect prompt manipulation can cause execution of destructive queries such as DROP TABLE, TRUNCATE, DELETE, ALTER, or privilege-related statements (subject to DB permissions). Deployments that expose an agent with MySQLWriteTool enabled to untrusted input and/or run the tool with a DB user that has broad privileges are impacted. This issue is fixed in version 2.8.12.

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

Neuron is a PHP framework for creating and orchestrating AI Agents. Versions 2.8.11 and below use MySQLSelectTool, which is vulnerable to Read-Only Bypass. MySQLSelectTool is intended to be a read-only SQL tool (e.g., for LLM agent querying, however, validation based on the first keyword (e.g., SELECT) and a forbidden-keyword list does not block file-writing constructs such as INTO OUTFILE / INTO DUMPFILE. As a result, an attacker who can influence the tool input (e.g., via prompt injection through a public agent endpoint) may write arbitrary files to the DB server if the MySQL/MariaDB account has the FILE privilege and server configuration permits writes to a useful location (e.g., a web-accessible directory). This issue is fixed in version 2.8.12.

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

Okta Java Management SDK facilitates interactions with the Okta management API. In versions 11.0.0 through 20.0.0, race conditions may arise from concurrent requests using the ApiClient class. This could cause a status code or response header from one request’s response to influence another request’s response. This issue is fixed in version 20.0.1.

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

The Auth0 Next.js SDK is a library for implementing user authentication in Next.js applications. When using versions 4.11.0 through 4.11.2 and 4.12.0, simultaneous requests on the same client may result in improper lookups in the TokenRequestCache for the request results. This issue is fixed in versions 4.11.2 and 4.12.1.

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