Comparison Overview

JPMorganChase

VS

Sun Life

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

Sun Life

OO
Last Update: 2025-12-09
Between 750 and 799

Sun Life is a leading financial services organization dedicated to helping people achieve lifetime financial security and live healthier lives. We provide a wide range of insurance and investment products and services in key markets around the world including Canada, the United States, the United Kingdom, Hong Kong, the Philippines and Indonesia. At Sun Life, we have more than 34,000 employees and 112,900 advisors worldwide. Websites: Canada www.sunlife.ca/en/ US www.sunlife.com/us/en/ Vietnam www.sunlife.com.vn Hong Kong www.sunlife.com.hk Indonesia www.sunlife.co.id Malaysia www.sunlife.com.my Philippines www.sunlife.com.ph

NAICS: 52
NAICS Definition: Finance and Insurance
Employees: 37,714
Subsidiaries: 4
12-month incidents
0
Known data breaches
1
Attack type number
1

Compliance Badges Comparison

Security & Compliance Standards Overview

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
https://images.rankiteo.com/companyimages/sun-life-financial.jpeg
Sun Life
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
JPMorganChase
100%
Compliance Rate
0/4 Standards Verified
Sun Life
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Financial Services Industry Average (This Year)

JPMorganChase has 143.9% 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 Sun Life in 2025.

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

JPMorganChase cyber incidents detection timeline including parent company and subsidiaries

Incident History — Sun Life (X = Date, Y = Severity)

Sun Life cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

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
https://images.rankiteo.com/companyimages/sun-life-financial.jpeg
Sun Life
Incidents

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

FAQ

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

JPMorganChase company has faced a higher number of disclosed cyber incidents historically compared to Sun Life company.

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

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

Both Sun Life company and JPMorganChase company have disclosed experiencing at least one data breach.

Neither Sun Life company nor JPMorganChase company has reported experiencing targeted cyberattacks publicly.

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

Neither JPMorganChase nor Sun Life holds any compliance certifications.

Neither company holds any compliance certifications.

JPMorganChase company has more subsidiaries worldwide compared to Sun Life company.

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

Neither JPMorganChase nor Sun Life holds SOC 2 Type 1 certification.

Neither JPMorganChase nor Sun Life holds SOC 2 Type 2 certification.

Neither JPMorganChase nor Sun Life holds ISO 27001 certification.

Neither JPMorganChase nor Sun Life holds PCI DSS certification.

Neither JPMorganChase nor Sun Life holds HIPAA certification.

Neither JPMorganChase nor Sun Life 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