Comparison Overview
AXA Gulf
AXA Gulf
Floor 39, Churchill Executive Tower, Business Bay, Dubai, undefined, undefined, AE
Last Update: 28/03/2026
Welcome to GIG Gulf, previously AXA. Your 1-stop shop and the most trusted insurance brand in the market, now the #1 regional multi-liner present in 13 countries across the region. We are an ‘A’ rated regional insurer with a top 5 position in each of our markets. We h...
Lockton
Global, US
Last Update: 04/09/2026
What makes Lockton stand apart is also what makes us better: independence. Our private ownership empowers our 13,100+ Associates doing business in over 140+ countries to focus solely on clients' risk and insurance needs. With expertise that reaches around the globe, we ...
Compliance Ranges Comparison
AXA Gulf
Lockton
Benchmark & Cyber Underwriting Signals
Incidents vs Insurance Industry Avg (This Year)
No incidents recorded for AXA Gulf in 2026.
Incidents vs Insurance Industry Avg (This Year)
No incidents recorded for Lockton in 2026.
Incident History - AXA Gulf (X = Date, Y = Severity)
AXA Gulf cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Lockton (X = Date, Y = Severity)
Lockton cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
AXA Gulf
Lockton
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.