Comparison Overview

KeyBank

VS

Groupe BPCE

KeyBank

127 Public Square, Cleveland , Ohio, US, 44114
Last Update: 2025-12-19
Between 550 and 599

At KeyBank we’ve made a promise to our clients that they will always have a champion in us. To deliver on our promise, we’re committed to building a team of engaged employees who do the right thing for our clients and shareholders, and help them achieve financial wellness each and every day. Headquartered in Cleveland, Ohio, KeyCorp is one of the nation’s largest financial services companies. Key Companies provide investment management, retail and commercial banking, consumer finance and investment banking products to individuals and companies throughout the United States and, for certain businesses, internationally. Follow along for business and industry insights, expert advice and more resources to help you achieve your financial goals. KeyCorp is an Equal Opportunity Employer committed to sustaining an inclusive culture. All qualified applicants will receive consideration for employment without regard to race, color, religion, sex, sexual orientation, gender identity, national origin, disability or veteran status. KeyBank is Member FDIC. Equal Housing Lender. Credit applications are subject to credit approval.

NAICS: 52211
NAICS Definition: Commercial Banking
Employees: 18,726
Subsidiaries: 0
12-month incidents
0
Known data breaches
6
Attack type number
1

Groupe BPCE

7, Promenade Germaine Sablon, Paris, 75013, FR
Last Update: 2025-12-22
Between 750 and 799

Groupe BPCE, at the service of its customers and the French economy Groupe BPCE pursues a full range of banking and insurance activities, working through its two major Banque Populaire and Caisse d’Epargne cooperative banking networks and through its different subsidiaries. Groupe BPCE, the 2nd largest banking group in France, has put down deep roots in its local markets. Its 117,000 employees serve a total of 36 million customers, 8.6 of whom have decided to become cooperative shareholders. The Group’s different subsidiaries pursue their activities in banking and insurance, tailoring their services as closely as possible to the needs of the individuals and regions they serve. With a total of 19 Banque Populaire banks, 17 Caisses d’Epargne, Natixis, Crédit Foncier, Banque Palatine, etc., Groupe BPCE offers its customers a comprehensive range of products and services: savings and investment solutions, cash management services, financing solutions, insurance, and wholesale banking services. Faithful to its status as a cooperative banking institution, the Group accompanies its customers in the realization of their different projects and develops long-lasting relationships with them, thereby contributing 20% to the drive to finance the French economy.

NAICS: 52211
NAICS Definition: Commercial Banking
Employees: 45,986
Subsidiaries: 44
12-month incidents
0
Known data breaches
0
Attack type number
0

Compliance Badges Comparison

Security & Compliance Standards Overview

https://images.rankiteo.com/companyimages/keybank.jpeg
KeyBank
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/bpce.jpeg
Groupe BPCE
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
KeyBank
100%
Compliance Rate
0/4 Standards Verified
Groupe BPCE
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Banking Industry Average (This Year)

No incidents recorded for KeyBank in 2025.

Incidents vs Banking Industry Average (This Year)

No incidents recorded for Groupe BPCE in 2025.

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

KeyBank cyber incidents detection timeline including parent company and subsidiaries

Incident History — Groupe BPCE (X = Date, Y = Severity)

Groupe BPCE cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/keybank.jpeg
KeyBank
Incidents

Date Detected: 12/2024
Type:Breach
Attack Vector: External System Breach (Hacking)
Blog: Blog

Date Detected: 5/2023
Type:Breach
Attack Vector: Insider Threat
Blog: Blog

Date Detected: 09/2022
Type:Breach
Attack Vector: Third-Party Vendor
Blog: Blog
https://images.rankiteo.com/companyimages/bpce.jpeg
Groupe BPCE
Incidents

No Incident

FAQ

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

KeyBank company has historically faced a number of disclosed cyber incidents, whereas Groupe BPCE company has not reported any.

In the current year, Groupe BPCE company and KeyBank company have not reported any cyber incidents.

Neither Groupe BPCE company nor KeyBank company has reported experiencing a ransomware attack publicly.

KeyBank company has disclosed at least one data breach, while the other Groupe BPCE company has not reported such incidents publicly.

Neither Groupe BPCE company nor KeyBank company has reported experiencing targeted cyberattacks publicly.

Neither KeyBank company nor Groupe BPCE company has reported experiencing or disclosing vulnerabilities publicly.

Neither KeyBank nor Groupe BPCE holds any compliance certifications.

Neither company holds any compliance certifications.

Groupe BPCE company has more subsidiaries worldwide compared to KeyBank company.

Groupe BPCE company employs more people globally than KeyBank company, reflecting its scale as a Banking.

Neither KeyBank nor Groupe BPCE holds SOC 2 Type 1 certification.

Neither KeyBank nor Groupe BPCE holds SOC 2 Type 2 certification.

Neither KeyBank nor Groupe BPCE holds ISO 27001 certification.

Neither KeyBank nor Groupe BPCE holds PCI DSS certification.

Neither KeyBank nor Groupe BPCE holds HIPAA certification.

Neither KeyBank nor Groupe BPCE holds GDPR certification.

Latest Global CVEs (Not Company-Specific)

Description

httparty is an API tool. In versions 0.23.2 and prior, httparty is vulnerable to SSRF. This issue can pose a risk of leaking API keys, and it can also allow third parties to issue requests to internal servers. This issue has been patched via commit 0529bcd.

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

5ire is a cross-platform desktop artificial intelligence assistant and model context protocol client. In versions 0.15.2 and prior, an RCE vulnerability exists in useMarkdown.ts, where the markdown-it-mermaid plugin is initialized with securityLevel: 'loose'. This configuration explicitly permits the rendering of HTML tags within Mermaid diagram nodes. This issue has not been patched at time of publication.

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

continuwuity is a Matrix homeserver written in Rust. Prior to version 0.5.0, this vulnerability allows a remote, unauthenticated attacker to force the target server to cryptographically sign arbitrary membership events. The flaw exists because the server fails to validate the origin of a signing request, provided the event's state_key is a valid user ID belonging to the target server. This issue has been patched in version 0.5.0. A workaround for this issue involves blocking access to the PUT /_matrix/federation/v2/invite/{roomId}/{eventId} endpoint using the reverse proxy.

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

LangChain is a framework for building LLM-powered applications. Prior to @langchain/core versions 0.3.80 and 1.1.8, and prior to langchain versions 0.3.37 and 1.2.3, a serialization injection vulnerability exists in LangChain JS's toJSON() method (and subsequently when string-ifying objects using JSON.stringify(). The method did not escape objects with 'lc' keys when serializing free-form data in kwargs. The 'lc' key is used internally by LangChain to mark serialized objects. When user-controlled data contains this key structure, it is treated as a legitimate LangChain object during deserialization rather than plain user data. This issue has been patched in @langchain/core versions 0.3.80 and 1.1.8, and langchain versions 0.3.37 and 1.2.3

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

LangChain is a framework for building agents and LLM-powered applications. Prior to versions 0.3.81 and 1.2.5, a serialization injection vulnerability exists in LangChain's dumps() and dumpd() functions. The functions do not escape dictionaries with 'lc' keys when serializing free-form dictionaries. The 'lc' key is used internally by LangChain to mark serialized objects. When user-controlled data contains this key structure, it is treated as a legitimate LangChain object during deserialization rather than plain user data. This issue has been patched in versions 0.3.81 and 1.2.5.

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