Comparison Overview

BNP Paribas CIB

VS

J.P. Morgan

BNP Paribas CIB

16 Boulevard des Italiens, None, Paris, France, FR, 75009
Last Update: 2025-11-22
Between 750 and 799

In a changing world, we aim at anticipating transformation and driving your company for success. We are convinced to have the expertise and networks you need to develop your business. BNP Paribas Corporate and Institutional Banking is a leading global financial partner, offering you a wide range of tailored solutions in Capital Markets, Securities Services, Financing, Treasury and Advisory Services. If you want to know more about us, visit www.cib.bnpparibas.com

NAICS: 52
NAICS Definition: Finance and Insurance
Employees: 14,971
Subsidiaries: 80
12-month incidents
0
Known data breaches
7
Attack type number
1

J.P. Morgan

270 Park Avenue, New York, NY, US, 10017
Last Update: 2025-11-21
Between 800 and 849

J.P. Morgan is a leader in financial services, offering solutions to clients in more than 100 countries with one of the most comprehensive global product platforms available. We have been helping our clients to do business and manage their wealth for more than 200 years. Our business has been built upon our core principle of putting our clients'​ interests first. J.P. Morgan is part of JPMorgan Chase & Co. (NYSE: JPM), a global financial services firm. Social Media Terms and Conditions: https://bit.ly/JPMCSocialTerms © 2017 JPMorgan Chase & Co. JPMorgan Chase is an equal opportunity and affirmative action employer Disability/Veteran.

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

Compliance Badges Comparison

Security & Compliance Standards Overview

https://images.rankiteo.com/companyimages/bnpparibascorporateandinstitutionalbanking.jpeg
BNP Paribas CIB
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/jpmorgan.jpeg
J.P. Morgan
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
BNP Paribas CIB
100%
Compliance Rate
0/4 Standards Verified
J.P. Morgan
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Financial Services Industry Average (This Year)

No incidents recorded for BNP Paribas CIB in 2025.

Incidents vs Financial Services Industry Average (This Year)

No incidents recorded for J.P. Morgan in 2025.

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

BNP Paribas CIB cyber incidents detection timeline including parent company and subsidiaries

Incident History — J.P. Morgan (X = Date, Y = Severity)

J.P. Morgan cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/bnpparibascorporateandinstitutionalbanking.jpeg
BNP Paribas CIB
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
https://images.rankiteo.com/companyimages/jpmorgan.jpeg
J.P. Morgan
Incidents

Date Detected: 8/2021
Type:Breach
Attack Vector: Software Vulnerability
Blog: Blog

Date Detected: 8/2021
Type:Breach
Blog: Blog

FAQ

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

BNP Paribas CIB company has faced a higher number of disclosed cyber incidents historically compared to J.P. Morgan company.

In the current year, J.P. Morgan company and BNP Paribas CIB company have not reported any cyber incidents.

Neither J.P. Morgan company nor BNP Paribas CIB company has reported experiencing a ransomware attack publicly.

Both J.P. Morgan company and BNP Paribas CIB company have disclosed experiencing at least one data breach.

Neither J.P. Morgan company nor BNP Paribas CIB company has reported experiencing targeted cyberattacks publicly.

Neither BNP Paribas CIB company nor J.P. Morgan company has reported experiencing or disclosing vulnerabilities publicly.

Neither BNP Paribas CIB nor J.P. Morgan holds any compliance certifications.

Neither company holds any compliance certifications.

BNP Paribas CIB company has more subsidiaries worldwide compared to J.P. Morgan company.

J.P. Morgan company employs more people globally than BNP Paribas CIB company, reflecting its scale as a Financial Services.

Neither BNP Paribas CIB nor J.P. Morgan holds SOC 2 Type 1 certification.

Neither BNP Paribas CIB nor J.P. Morgan holds SOC 2 Type 2 certification.

Neither BNP Paribas CIB nor J.P. Morgan holds ISO 27001 certification.

Neither BNP Paribas CIB nor J.P. Morgan holds PCI DSS certification.

Neither BNP Paribas CIB nor J.P. Morgan holds HIPAA certification.

Neither BNP Paribas CIB nor J.P. Morgan holds GDPR certification.

Latest Global CVEs (Not Company-Specific)

Description

Angular is a development platform for building mobile and desktop web applications using TypeScript/JavaScript and other languages. Prior to versions 19.2.16, 20.3.14, and 21.0.1, there is a XSRF token leakage via protocol-relative URLs in angular HTTP clients. The vulnerability is a Credential Leak by App Logic that leads to the unauthorized disclosure of the Cross-Site Request Forgery (XSRF) token to an attacker-controlled domain. Angular's HttpClient has a built-in XSRF protection mechanism that works by checking if a request URL starts with a protocol (http:// or https://) to determine if it is cross-origin. If the URL starts with protocol-relative URL (//), it is incorrectly treated as a same-origin request, and the XSRF token is automatically added to the X-XSRF-TOKEN header. This issue has been patched in versions 19.2.16, 20.3.14, and 21.0.1. A workaround for this issue involves avoiding using protocol-relative URLs (URLs starting with //) in HttpClient requests. All backend communication URLs should be hardcoded as relative paths (starting with a single /) or fully qualified, trusted absolute URLs.

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

Forge (also called `node-forge`) is a native implementation of Transport Layer Security in JavaScript. An Uncontrolled Recursion vulnerability in node-forge versions 1.3.1 and below enables remote, unauthenticated attackers to craft deep ASN.1 structures that trigger unbounded recursive parsing. This leads to a Denial-of-Service (DoS) via stack exhaustion when parsing untrusted DER inputs. This issue has been patched in version 1.3.2.

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

Forge (also called `node-forge`) is a native implementation of Transport Layer Security in JavaScript. An Integer Overflow vulnerability in node-forge versions 1.3.1 and below enables remote, unauthenticated attackers to craft ASN.1 structures containing OIDs with oversized arcs. These arcs may be decoded as smaller, trusted OIDs due to 32-bit bitwise truncation, enabling the bypass of downstream OID-based security decisions. This issue has been patched in version 1.3.2.

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

Suricata is a network IDS, IPS and NSM engine developed by the OISF (Open Information Security Foundation) and the Suricata community. Prior to versions 7.0.13 and 8.0.2, working with large buffers in Lua scripts can lead to a stack overflow. Users of Lua rules and output scripts may be affected when working with large buffers. This includes a rule passing a large buffer to a Lua script. This issue has been patched in versions 7.0.13 and 8.0.2. A workaround for this issue involves disabling Lua rules and output scripts, or making sure limits, such as stream.depth.reassembly and HTTP response body limits (response-body-limit), are set to less than half the stack size.

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

Suricata is a network IDS, IPS and NSM engine developed by the OISF (Open Information Security Foundation) and the Suricata community. In versions from 8.0.0 to before 8.0.2, a NULL dereference can occur when the entropy keyword is used in conjunction with base64_data. This issue has been patched in version 8.0.2. A workaround involves disabling rules that use entropy in conjunction with base64_data.

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