Comparison Overview

KeyBank

VS

BNP Paribas

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

BNP Paribas

16 boulevard des Italiens, None, Paris, None, FR, 75009
Last Update: 2025-12-17
Between 800 and 849

BNP Paribas is a leading bank in Europe with an international reach. It has a presence in 64 countries, with more than 178,000 employees, including more than 144,000 in Europe. BNP Paribas holds leading positions in its three major operating divisions: ⚆ Commercial, Personal Banking & Services for all the Group’s retail banking networks and several specialised businesses, including BNP Paribas Personal Finance and Arval; ⚆ Investment & Protection Services for savings, investment and protection solutions; ⚆ Corporate & Institutional Banking, which is focused on corporate and institutional clients. The Group helps all its clients (individuals, community associations, entrepreneurs, SMEs, corporates and institutional clients) to realise their projects through solutions spanning financing, investment, savings and protection insurance. In Europe, the Group has four domestic markets (Belgium, France, Italy and Luxembourg) and BNP Paribas Personal Finance is the European leader in consumer lending. BNP Paribas is rolling out its integrated retail-banking model in Mediterranean countries, in Turkey, in Eastern Europe and a large network in the western part of the United States. In its Corporate & Institutional Banking and Investment & Protection Services activities, BNP Paribas also enjoys top positions in Europe, a strong presence in the Americas as well as a solid and fast-growing business in Asia-Pacific. To learn more about our social media terms and Data Protection Notice: https://group.bnpparibas/en/data-protection

NAICS: 52211
NAICS Definition: Commercial Banking
Employees: 153,712
Subsidiaries: 90
12-month incidents
0
Known data breaches
8
Attack type number
1

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/bnp-paribas.jpeg
BNP Paribas
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
BNP Paribas
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 BNP Paribas in 2025.

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

KeyBank cyber incidents detection timeline including parent company and subsidiaries

Incident History — BNP Paribas (X = Date, Y = Severity)

BNP Paribas 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/bnp-paribas.jpeg
BNP Paribas
Incidents

Date Detected: 11/2021
Type:Breach
Attack Vector: Physical ATM Skimming Device
Motivation: Financial Gain (Likely)
Blog: Blog

Date Detected: 12/2018
Type:Breach
Attack Vector: ATM Skimming
Motivation: Financial Gain
Blog: Blog

Date Detected: 05/2018
Type:Breach
Motivation: Financial Gain
Blog: Blog

FAQ

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

BNP Paribas company has faced a higher number of disclosed cyber incidents historically compared to KeyBank company.

In the current year, BNP Paribas company and KeyBank company have not reported any cyber incidents.

Neither BNP Paribas company nor KeyBank company has reported experiencing a ransomware attack publicly.

Both BNP Paribas company and KeyBank company have disclosed experiencing at least one data breach.

Neither BNP Paribas company nor KeyBank company has reported experiencing targeted cyberattacks publicly.

Neither KeyBank company nor BNP Paribas company has reported experiencing or disclosing vulnerabilities publicly.

Neither KeyBank nor BNP Paribas holds any compliance certifications.

Neither company holds any compliance certifications.

BNP Paribas company has more subsidiaries worldwide compared to KeyBank company.

BNP Paribas company employs more people globally than KeyBank company, reflecting its scale as a Banking.

Neither KeyBank nor BNP Paribas holds SOC 2 Type 1 certification.

Neither KeyBank nor BNP Paribas holds SOC 2 Type 2 certification.

Neither KeyBank nor BNP Paribas holds ISO 27001 certification.

Neither KeyBank nor BNP Paribas holds PCI DSS certification.

Neither KeyBank nor BNP Paribas holds HIPAA certification.

Neither KeyBank nor BNP Paribas 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