Comparison Overview
A1 Belarus
A1 Belarus
улица Интернациональная 36-2 , Минск, Минская область, BY, 220030
Last Update: 29/03/2026
A1 began operations in Belarus in 1999. Since November 2007, A1 is part of A1 Telekom Austria Group (A1 Group), one of the most successful telecom holdings in Central and Eastern Europe. Until August 2019, the company conducted operations under the brand name velcom. O...
Millicom (Tigo)
2 Rue du Fort Bourbon, Luxembourg, 1249, LU
Last Update: 07/10/2026
Millicom (NASDAQ U.S.: TIGO, Nasdaq) is a leading provider of fixed and mobile telecommunications services in Latin America. Through our TIGO® and Tigo Business® brands, we provide a wide range of digital services and products, including TIGO Money for mobile financial ...
Compliance Ranges Comparison
A1 Belarus
Millicom (Tigo)
Benchmark & Cyber Underwriting Signals
Incidents vs Telecommunications Industry Avg (This Year)
No incidents recorded for A1 Belarus in 2026.
Incidents vs Telecommunications Industry Avg (This Year)
No incidents recorded for Millicom (Tigo) in 2026.
Incident History - A1 Belarus (X = Date, Y = Severity)
A1 Belarus cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Millicom (Tigo) (X = Date, Y = Severity)
Millicom (Tigo) cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
A1 Belarus
Millicom (Tigo)
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.