Comparison Overview

Manulife

VS

MAPFRE

Manulife

200 Bloor St E, Toronto, Ontario, M4W, CA
Last Update: 2025-11-21
Between 800 and 849

Manulife is a leading international financial services group that helps people make their decisions easier and lives better. With our global headquarters in Toronto, we operate as Manulife across our offices in Canada, Asia, and Europe, and primarily as John Hancock in the United States. We have more than 40,000 employees, over 116,000 agents serving ~34 million customers worldwide, and over $1.3 trillion in assets under management and administration. Visit www.Manulife.com to find out more. For Manulife terms of use, please visit http://bit.ly/SM_Terms

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

MAPFRE

Carretera de Pozuelo, 52, Majadahonda, 28220, ES
Last Update: 2025-11-20
Between 750 and 799

At MAPFRE, we’re committed to protecting what matters most to you. That’s why we’re the largest Spanish-owned insurer in the world, the largest multinational insurance company in Latin America and among the 15 largest European groups by premium volume. With a legacy spanning more than 90 years, we’re proud to provide innovative insurance and service solutions to protect people and companies around the world. Our purpose is to be by your side, accompanying you to move forward with peace of mind, contributing to the development of a more sustainable and caring society, while our global footprint enables us to guarantee solvency, promote innovation, and provide the best service, all the while acting with the utmost integrity. At MAPFRE, we believe in the power of people. Our multicultural and diverse team is the driving force behind our success, bringing our vision and mission to life, contributing their talent, passion and experience day after day. If you want to learn more about MAPFRE, please visit our website or the Life in the Company section here. Welcome to MAPFRE!

NAICS: 524
NAICS Definition: Insurance Carriers and Related Activities
Employees: 36,726
Subsidiaries: 4
12-month incidents
0
Known data breaches
0
Attack type number
0

Compliance Badges Comparison

Security & Compliance Standards Overview

https://images.rankiteo.com/companyimages/manulife-financial.jpeg
Manulife
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/mapfre.jpeg
MAPFRE
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
Manulife
100%
Compliance Rate
0/4 Standards Verified
MAPFRE
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Insurance Industry Average (This Year)

No incidents recorded for Manulife in 2025.

Incidents vs Insurance Industry Average (This Year)

No incidents recorded for MAPFRE in 2025.

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

Manulife cyber incidents detection timeline including parent company and subsidiaries

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

MAPFRE cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/manulife-financial.jpeg
Manulife
Incidents

No Incident

https://images.rankiteo.com/companyimages/mapfre.jpeg
MAPFRE
Incidents

No Incident

FAQ

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

Historically, MAPFRE company has disclosed a higher number of cyber incidents compared to Manulife company.

In the current year, MAPFRE company and Manulife company have not reported any cyber incidents.

Neither MAPFRE company nor Manulife company has reported experiencing a ransomware attack publicly.

Neither MAPFRE company nor Manulife company has reported experiencing a data breach publicly.

Neither MAPFRE company nor Manulife company has reported experiencing targeted cyberattacks publicly.

Neither Manulife company nor MAPFRE company has reported experiencing or disclosing vulnerabilities publicly.

Neither Manulife nor MAPFRE holds any compliance certifications.

Neither company holds any compliance certifications.

MAPFRE company has more subsidiaries worldwide compared to Manulife company.

MAPFRE company employs more people globally than Manulife company, reflecting its scale as a Insurance.

Neither Manulife nor MAPFRE holds SOC 2 Type 1 certification.

Neither Manulife nor MAPFRE holds SOC 2 Type 2 certification.

Neither Manulife nor MAPFRE holds ISO 27001 certification.

Neither Manulife nor MAPFRE holds PCI DSS certification.

Neither Manulife nor MAPFRE holds HIPAA certification.

Neither Manulife nor MAPFRE 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