Comparison Overview
JLT Re

JLT Re
138 Houndsditch, London, EC3A 7AW, GB
Last Update: 24/12/2025
Following Marsh & McLennan’s acquisition of JLT Group, JLT Re will be joining Guy Carpenter. To follow our reinsurance insights, please follow Guy Carpenter here: https://www.linkedin.com/company/guy-carpenter About Guy Carpenter: Guy Carpenter & Company, LLC, a leadin...

MetLife
200 Park Ave, New York, NY, US, 10166
Last Update: 07/10/2026
We live in a time of unprecedented change. A time when economies, regulations, and social safety nets are all in flux. Customers around the globe have told us they’re overwhelmed by the pace of change and are looking for a trusted partner to help them manage life’s twi...
Compliance Ranges Comparison

JLT Re







MetLife






Benchmark & Cyber Underwriting Signals
Incidents vs Insurance Industry Avg (This Year)
No incidents recorded for JLT Re in 2026.
Incidents vs Insurance Industry Avg (This Year)
No incidents recorded for MetLife in 2026.
Incident History - JLT Re (X = Date, Y = Severity)
JLT Re cyber incidents detection timeline including parent company and subsidiaries.
Incident History - MetLife (X = Date, Y = Severity)
MetLife cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

JLT Re

MetLife
FAQ
Latest Global CVEs
IBM TRIRIGA Application Platform 5.0.0 through 5.0.8 could allow a remote authenticated attacker to obtain sensitive information due to exposure of session tokens in the HTML response.
IBM TRIRIGA Application Platform 5.0.0 through 5.0.8 could allow a remote authenticated attacker to obtain sensitive information due to an XML external entity (XXE) injection flaw.
IBM Aspera Enterprise WebApps 1.0.0 through 1.0.6 could allow a local attacker to obtain sensitive information due to cleartext transmission of sensitive information.
IBM Planning Analytics 2.0, and 2.1 could allow a remote authenticated attacker to execute arbitrary code due to a stack-based buffer overflow.
IBM DataStage on Cloud Pak for Data 5.4.0.0 can allow a man-in-the-middle attacker to present a forged TLS certificate, intercept the connection, and capture the IAM bearer Authorization header automatically attached by the session adapter. The captured token grants full platform-scope tenant API access, enabling the attacker to read and manipulate the victim's DataStage projects, flows, assets, and pipeline definitions. This is client-side SDK code running on the user's own machine, so exploitation requires an external network interceptor rather than a co-tenant in the shared cluster.