Comparison Overview

AXA

VS

Unum

AXA

25, avenue Matignon, Paris, FR, FR, 75008
Last Update: 2025-11-26
Between 800 and 849

As one of the largest global insurers, our purpose is to act for human progress by protecting what matters. Protection has always been at the core of our business, helping individuals, businesses and societies to thrive. And AXA has always been a leader, an innovator, an entrepreneurial company, fostering progress in all its dimensions. Our purpose also links back to the Group's roots. From the outset, AXA has been committed to acting as a force for collective good. From solidarity-based actions with AXA Hearts In Action to work on prevention issues with the AXA Research Fund and the fight against climate change, AXA has always been attentive to its social environment and embraced its responsibility as an insurer: responsibility for taking action upstream in order to better understand risks, with one goal in mind: to ensure better protection. Discover more: https://www.axa.com/en/about-us/our-purpose To know more about AXA's Privacy Policy - https://www-axa-com.cdn.axa-contento-118412.eu/www-axa-com/1cd44dfb-3b7a-4cf7-933b-06024cf7f25b_axa_privacypolicy_internetusers_va.pdf

NAICS: 524
NAICS Definition: Insurance Carriers and Related Activities
Employees: 139,913
Subsidiaries: 41
12-month incidents
0
Known data breaches
0
Attack type number
1

Unum

1 Fountain Sq., None, Chattanooga, TN, US, 37402
Last Update: 2025-11-26
Between 700 and 749

Since our founding in 1848, Unum has been a leader in the employee benefits business through innovation, integrity and an unwavering commitment to our customers. This simple philosophy has guided us through America’s fledgling insurance landscape and helped us become an international leader in financial protection benefits, offering disability, life, accident, critical illness, dental, vision and stop-loss insurance; leave and absence management support and behavioral health services.

NAICS: 524
NAICS Definition: Insurance Carriers and Related Activities
Employees: 11,338
Subsidiaries: 2
12-month incidents
0
Known data breaches
2
Attack type number
2

Compliance Badges Comparison

Security & Compliance Standards Overview

https://images.rankiteo.com/companyimages/axa.jpeg
AXA
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/unum.jpeg
Unum
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
AXA
100%
Compliance Rate
0/4 Standards Verified
Unum
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Insurance Industry Average (This Year)

No incidents recorded for AXA in 2025.

Incidents vs Insurance Industry Average (This Year)

No incidents recorded for Unum in 2025.

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

AXA cyber incidents detection timeline including parent company and subsidiaries

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

Unum cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/axa.jpeg
AXA
Incidents

Date Detected: 5/2021
Type:Ransomware
Motivation: Data Theft, Financial Gain
Blog: Blog
https://images.rankiteo.com/companyimages/unum.jpeg
Unum
Incidents

Date Detected: 5/2023
Type:Vulnerability
Attack Vector: Exploitation of Vulnerability
Blog: Blog

Date Detected: 10/2021
Type:Breach
Attack Vector: Unauthorized Access
Blog: Blog

Date Detected: 10/2021
Type:Breach
Attack Vector: Unauthorized Access
Blog: Blog

FAQ

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

Unum company has faced a higher number of disclosed cyber incidents historically compared to AXA company.

In the current year, Unum company and AXA company have not reported any cyber incidents.

AXA company has confirmed experiencing a ransomware attack, while Unum company has not reported such incidents publicly.

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

Neither Unum company nor AXA company has reported experiencing targeted cyberattacks publicly.

Unum company has disclosed at least one vulnerability, while AXA company has not reported such incidents publicly.

Neither AXA nor Unum holds any compliance certifications.

Neither company holds any compliance certifications.

AXA company has more subsidiaries worldwide compared to Unum company.

AXA company employs more people globally than Unum company, reflecting its scale as a Insurance.

Neither AXA nor Unum holds SOC 2 Type 1 certification.

Neither AXA nor Unum holds SOC 2 Type 2 certification.

Neither AXA nor Unum holds ISO 27001 certification.

Neither AXA nor Unum holds PCI DSS certification.

Neither AXA nor Unum holds HIPAA certification.

Neither AXA nor Unum 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