Comparison Overview

J.P. Morgan

VS

FactSet

J.P. Morgan

270 Park Avenue, New York, NY, US, 10017
Last Update: 2025-12-11
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
1
Attack type number
1

FactSet

43 Glover Ave, Norwalk, Connecticut, US, 06850
Last Update: 2025-12-09
Between 750 and 799

FactSet creates flexible, open data and software solutions for tens of thousands of investment professionals around the world, providing instant access to financial data and analytics that investors use to make crucial decisions. For 40 years, through market changes and technological progress, our focus has always been to provide exceptional client service. From more than 60 offices in 23 countries, we’re all working together toward the goal of creating value for our clients, and we’re proud that 95% of asset managers who use FactSet continue to use FactSet, year after year. As big as we grow, as far as we reach, and as successful as we become, we stay connected to our clients and to each other.

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

Compliance Badges Comparison

Security & Compliance Standards Overview

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

Benchmark & Cyber Underwriting Signals

Incidents vs Financial Services Industry Average (This Year)

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

Incidents vs Financial Services Industry Average (This Year)

No incidents recorded for FactSet in 2025.

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

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

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

FactSet cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/jpmorgan.jpeg
J.P. Morgan
Incidents

Date Detected: 8/2021
Type:Breach
Blog: Blog
https://images.rankiteo.com/companyimages/factset.jpeg
FactSet
Incidents

No Incident

FAQ

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

J.P. Morgan company has historically faced a number of disclosed cyber incidents, whereas FactSet company has not reported any.

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

Neither FactSet company nor J.P. Morgan company has reported experiencing a ransomware attack publicly.

J.P. Morgan company has disclosed at least one data breach, while the other FactSet company has not reported such incidents publicly.

Neither FactSet company nor J.P. Morgan company has reported experiencing targeted cyberattacks publicly.

Neither J.P. Morgan company nor FactSet company has reported experiencing or disclosing vulnerabilities publicly.

Neither J.P. Morgan nor FactSet holds any compliance certifications.

Neither company holds any compliance certifications.

Neither J.P. Morgan company nor FactSet company has publicly disclosed detailed information about the number of their subsidiaries.

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

Neither J.P. Morgan nor FactSet holds SOC 2 Type 1 certification.

Neither J.P. Morgan nor FactSet holds SOC 2 Type 2 certification.

Neither J.P. Morgan nor FactSet holds ISO 27001 certification.

Neither J.P. Morgan nor FactSet holds PCI DSS certification.

Neither J.P. Morgan nor FactSet holds HIPAA certification.

Neither J.P. Morgan nor FactSet 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