Comparison Overview
Continental Reinsurance

Continental Reinsurance
Continental Reinsurance Plc. Continental Re Center, 17, Olosa street, Victoria Island, Lagos, Lagos, P.O. Box 2401, NG
Last Update: 03/04/2026
Build your resilience by working with Africa’s largest private pan-African reinsurer. With a rich history of over 30 years, we have established ourselves as the ‘torch bearer’ of the African Reinsurance sector. Our journey began in Nigeria in 1985, where we started as...

IAG
201 Sussex St, Sydney, 2000, AU
Last Update: 04/09/2026
IAG is Australia and New Zealand's largest general insurance company with a purpose to make your world a safer place, whether you are a customer, partner, employee, shareholder or part of the communities IAG serves across Australia and New Zealand. Our businesses have ...
Compliance Ranges Comparison

Continental Reinsurance







IAG






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

Continental Reinsurance

IAG
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.