Comparison Overview

CIMB

VS

JPMorganChase

CIMB

Menara CIMB, Kuala Lumpur Sentral, Kuala Lumpur, MY, 50470
Last Update: 2025-12-09
Between 750 and 799

CIMB Group is a leading ASEAN universal bank, one of the largest Asian investment banks and one of the world's largest Islamic banks. We are headquartered in Kuala Lumpur, Malaysia and offer consumer banking, commercial banking, wholesale banking, Islamic banking, and asset management products and services. As the fifth largest banking group in ASEAN, we have over 36,000 staff in 16 locations across ASEAN, Asia and beyond. CIMB Bank and CIMB Islamic Bank are members of PIDM.

NAICS: 52
NAICS Definition: Finance and Insurance
Employees: 13,774
Subsidiaries: 3
12-month incidents
0
Known data breaches
0
Attack type number
0

JPMorganChase

270 Park Avenue, New York, NY, US, 10017-2014
Last Update: 2025-12-09
Between 750 and 799

With a history tracing its roots to 1799 in New York City, JPMorganChase is one of the world's oldest, largest, and best-known financial institutions—carrying forth the innovative spirit of our heritage firms in global operations across 100 markets. We serve millions of customers and many of the world’s most prominent corporate, institutional, and government clients daily, managing assets and investments, offering business advice and strategies, and providing innovative banking solutions and services. Social Media Terms and Conditions: https://bit.ly/JPMCSocialTerms © 2024 JPMorgan Chase & Co. All rights reserved. JPMorganChase is an Equal Opportunity Employer, including Disability/Veterans.

NAICS: 52
NAICS Definition: Finance and Insurance
Employees: 215,187
Subsidiaries: 12
12-month incidents
2
Known data breaches
9
Attack type number
2

Compliance Badges Comparison

Security & Compliance Standards Overview

https://images.rankiteo.com/companyimages/cimbmalaysia.jpeg
CIMB
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/jpmorganchase.jpeg
JPMorganChase
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
CIMB
100%
Compliance Rate
0/4 Standards Verified
JPMorganChase
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Financial Services Industry Average (This Year)

No incidents recorded for CIMB in 2025.

Incidents vs Financial Services Industry Average (This Year)

JPMorganChase has 140.96% more incidents than the average of same-industry companies with at least one recorded incident.

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

CIMB cyber incidents detection timeline including parent company and subsidiaries

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

JPMorganChase cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/cimbmalaysia.jpeg
CIMB
Incidents

No Incident

https://images.rankiteo.com/companyimages/jpmorganchase.jpeg
JPMorganChase
Incidents

Date Detected: 11/2025
Type:Breach
Blog: Blog

Date Detected: 5/2025
Type:Ransomware
Attack Vector: Legitimate software and open-source pen-testing tools
Motivation: Financial Gain
Blog: Blog

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

FAQ

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

JPMorganChase company has historically faced a number of disclosed cyber incidents, whereas CIMB company has not reported any.

In the current year, JPMorganChase company has reported more cyber incidents than CIMB company.

JPMorganChase company has confirmed experiencing a ransomware attack, while CIMB company has not reported such incidents publicly.

JPMorganChase company has disclosed at least one data breach, while CIMB company has not reported such incidents publicly.

Neither JPMorganChase company nor CIMB company has reported experiencing targeted cyberattacks publicly.

Neither CIMB company nor JPMorganChase company has reported experiencing or disclosing vulnerabilities publicly.

Neither CIMB nor JPMorganChase holds any compliance certifications.

Neither company holds any compliance certifications.

JPMorganChase company has more subsidiaries worldwide compared to CIMB company.

JPMorganChase company employs more people globally than CIMB company, reflecting its scale as a Financial Services.

Neither CIMB nor JPMorganChase holds SOC 2 Type 1 certification.

Neither CIMB nor JPMorganChase holds SOC 2 Type 2 certification.

Neither CIMB nor JPMorganChase holds ISO 27001 certification.

Neither CIMB nor JPMorganChase holds PCI DSS certification.

Neither CIMB nor JPMorganChase holds HIPAA certification.

Neither CIMB nor JPMorganChase holds GDPR certification.

Latest Global CVEs (Not Company-Specific)

Description

NXLog Agent before 6.11 can load a file specified by the OPENSSL_CONF environment variable.

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

uriparser through 0.9.9 allows unbounded recursion and stack consumption, as demonstrated by ParseMustBeSegmentNzNc with large input containing many commas.

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

A vulnerability was detected in Mayan EDMS up to 4.10.1. The affected element is an unknown function of the file /authentication/. The manipulation results in cross site scripting. The attack may be performed from remote. The exploit is now public and may be used. Upgrading to version 4.10.2 is sufficient to fix this issue. You should upgrade the affected component. The vendor confirms that this is "[f]ixed in version 4.10.2". Furthermore, that "[b]ackports for older versions in process and will be out as soon as their respective CI pipelines complete."

Risk Information
cvss2
Base: 5.0
Severity: LOW
AV:N/AC:L/Au:N/C:N/I:P/A:N
cvss3
Base: 4.3
Severity: LOW
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N
cvss4
Base: 5.3
Severity: LOW
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/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

MJML through 4.18.0 allows mj-include directory traversal to test file existence and (in the type="css" case) read files. NOTE: this issue exists because of an incomplete fix for CVE-2020-12827.

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

A half-blind Server Side Request Forgery (SSRF) vulnerability exists in kube-controller-manager when using the in-tree Portworx StorageClass. This vulnerability allows authorized users to leak arbitrary information from unprotected endpoints in the control plane’s host network (including link-local or loopback services).

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