Comparison Overview

Capital One

VS

Lloyds Banking Group

Capital One

1680 Capital One Drive, McLean, Va, US, 22102
Last Update: 2025-12-09
Between 600 and 649

At Capital One, we're making things better for our customers and associates through innovation and collaboration. We were founded on the belief that everyone deserves financial freedom—and are dedicated to a world where all have equal opportunity to prosper. Banking is in our DNA, but we are so much more than a bank. We always think about what’s next—and how we can bring our customers the tools needed to improve their financial lives. Your ideas, experiences and skills will help make banking better. You’ll be part of a supportive culture while earning amazing benefits. That’s life at Capital One. Capital One is an equal opportunity employer (EOE, including disability/vet) committed to non-discrimination in compliance with applicable federal, state, and local laws. View our Social Media Community Guidelines https://www.capitalone.com/digital/social-media/

NAICS: 52
NAICS Definition: Finance and Insurance
Employees: 81,373
Subsidiaries: 4
12-month incidents
1
Known data breaches
11
Attack type number
1

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/capital-one.jpeg
Capital One
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
Capital One
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)

Capital One has 21.95% more incidents than the average of same-industry companies with at least one recorded incident.

Incidents vs Financial Services Industry Average (This Year)

No incidents recorded for Lloyds Banking Group in 2025.

Incident History — Capital One (X = Date, Y = Severity)

Capital One 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/capital-one.jpeg
Capital One
Incidents

Date Detected: 5/2025
Type:Breach
Attack Vector: Misconfigured Firewall
Motivation: Data Theft
Blog: Blog

Date Detected: 2/2023
Type:Breach
Blog: Blog

Date Detected: 8/2022
Type:Breach
Attack Vector: Insider Wrongdoing
Blog: Blog
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 Capital One company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Capital One company has faced a higher number of disclosed cyber incidents historically compared to Lloyds Banking Group company.

In the current year, Capital One company has reported more cyber incidents than Lloyds Banking Group company.

Neither Lloyds Banking Group company nor Capital One company has reported experiencing a ransomware attack publicly.

Both Lloyds Banking Group company and Capital One company have disclosed experiencing at least one data breach.

Neither Lloyds Banking Group company nor Capital One company has reported experiencing targeted cyberattacks publicly.

Neither Capital One company nor Lloyds Banking Group company has reported experiencing or disclosing vulnerabilities publicly.

Neither Capital One nor Lloyds Banking Group holds any compliance certifications.

Neither company holds any compliance certifications.

Capital One company has more subsidiaries worldwide compared to Lloyds Banking Group company.

Capital One company employs more people globally than Lloyds Banking Group company, reflecting its scale as a Financial Services.

Neither Capital One nor Lloyds Banking Group holds SOC 2 Type 1 certification.

Neither Capital One nor Lloyds Banking Group holds SOC 2 Type 2 certification.

Neither Capital One nor Lloyds Banking Group holds ISO 27001 certification.

Neither Capital One nor Lloyds Banking Group holds PCI DSS certification.

Neither Capital One nor Lloyds Banking Group holds HIPAA certification.

Neither Capital One 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