Comparison Overview
Beesafe sp. z o.o.
Beesafe sp. z o.o.
Aleje Jerozolimskie 181 b, Warszawa, 02-222, PL
Last Update: 27/03/2026
Beesafe to marka ubezpieczeniowa z internetowym charakterem. To co nas wyróżnia, to unikalne produkty ubezpieczeniowe oraz użyteczne usługi, z których chce się korzystać. Co więcej, każda zakupiona polisa i każdy dzień z nami zbliża Cię do zdobycia nagród dostarczanych ...
Intact
700 University Avenue, Toronto, M5G 0A1, CA
Last Update: 06/09/2026
We created a purpose-driven company based on Values and a belief that insurance is about people, not things. This is the foundation on which we have built Intact and it lives every day through our purpose, Values, what we aim to achieve and how. ___ Nous sommes là pour...
Compliance Ranges Comparison
Beesafe sp. z o.o.
Intact
Benchmark & Cyber Underwriting Signals
Incidents vs Insurance Industry Avg (This Year)
No incidents recorded for Beesafe sp. z o.o. in 2026.
Incidents vs Insurance Industry Avg (This Year)
No incidents recorded for Intact in 2026.
Incident History - Beesafe sp. z o.o. (X = Date, Y = Severity)
Beesafe sp. z o.o. cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Intact (X = Date, Y = Severity)
Intact cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Beesafe sp. z o.o.
Intact
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.