Comparison Overview

Trustly

VS

Prudential Financial

Trustly

Rådmansgatan 40, Stockholm, 113 57, SE
Last Update: 2025-12-12
Between 700 and 749

Trustly was launched in 2008 and has grown rapidly over the past 16 years to become a global leader in Open Banking Payment solutions. With a mission to make online payments as seamless as possible, Trustly offers an innovative payment platform, bridging the gap between consumers and merchants. Its technology ensures that transactions are processed in real-time, providing both speed and security for all parties involved. Trustly's dedication to revolutionizing the payments industry is reflected in its collaborations with major brands such as PayPal, eBay, and Hargreaves Lansdown in Europe and FanDuel, T-Mobile, and Coinbase in North America. To date, Trustly has transformed the performance and experience of payments for over 9,000 merchants in 30+ markets, connecting them to 650+ million consumers through 12,000 banks. Trustly is a licensed Payment Institution under the second payment services directive (PSD2). It operates under the supervision of the Swedish Financial Supervisory Authority in the EU, EEA and the Financial Conduct Authority in the UK. In the US, Trustly is state-regulated as required to serve its target markets.

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

Prudential Financial

Broad St, Newark, New Jersey, US, 07102
Last Update: 2025-12-11
Between 700 and 749

Prudential Financial (NYSE:PRU) was founded on the belief that financial security should be within reach for everyone, and for over 140 years, we have helped our customers reach their potential and tackle life's challenges for now and future generations to come. Today, we are one of the world’s largest financial services institutions, offering individual and institutional clients a wide array of financial products and services. With operations in the United States, Asia, Europe and Latin America, we are known for delivering on our promises to our customers, and are recognized as a trusted brand and one of the world’s most admired companies. We also have one of the most recognized and trusted brand symbols: The Rock®, an icon of strength, stability, expertise and innovation. We measure our long-term success on our ability to deliver value for shareholders, meet customer needs, and attract and develop the best talent in our industry. We offer an inclusive work environment where employees can develop to their full potential, and give back to the communities where we live and work. (Pru.us/disclaimer)

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

Compliance Badges Comparison

Security & Compliance Standards Overview

https://images.rankiteo.com/companyimages/trustly.jpeg
Trustly
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/prudential-financial.jpeg
Prudential Financial
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
Trustly
100%
Compliance Rate
0/4 Standards Verified
Prudential Financial
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Financial Services Industry Average (This Year)

Trustly has 20.48% 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 Prudential Financial in 2025.

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

Trustly cyber incidents detection timeline including parent company and subsidiaries

Incident History — Prudential Financial (X = Date, Y = Severity)

Prudential Financial cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/trustly.jpeg
Trustly
Incidents

Date Detected: 12/2025
Type:Cyber Attack
Attack Vector: Phishing Kit
Blog: Blog
https://images.rankiteo.com/companyimages/prudential-financial.jpeg
Prudential Financial
Incidents

Date Detected: 2/2024
Type:Breach
Blog: Blog

Date Detected: 10/2022
Type:Breach
Attack Vector: Email
Blog: Blog

Date Detected: 11/2017
Type:Breach
Attack Vector: Inadvertent Disclosure
Blog: Blog

FAQ

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

Prudential Financial company has faced a higher number of disclosed cyber incidents historically compared to Trustly company.

In the current year, Trustly company has reported more cyber incidents than Prudential Financial company.

Neither Prudential Financial company nor Trustly company has reported experiencing a ransomware attack publicly.

Prudential Financial company has disclosed at least one data breach, while Trustly company has not reported such incidents publicly.

Trustly company has reported targeted cyberattacks, while Prudential Financial company has not reported such incidents publicly.

Neither Trustly company nor Prudential Financial company has reported experiencing or disclosing vulnerabilities publicly.

Neither Trustly nor Prudential Financial holds any compliance certifications.

Neither company holds any compliance certifications.

Prudential Financial company has more subsidiaries worldwide compared to Trustly company.

Prudential Financial company employs more people globally than Trustly company, reflecting its scale as a Financial Services.

Neither Trustly nor Prudential Financial holds SOC 2 Type 1 certification.

Neither Trustly nor Prudential Financial holds SOC 2 Type 2 certification.

Neither Trustly nor Prudential Financial holds ISO 27001 certification.

Neither Trustly nor Prudential Financial holds PCI DSS certification.

Neither Trustly nor Prudential Financial holds HIPAA certification.

Neither Trustly nor Prudential Financial 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