Comparison Overview
A1 Makedonija
A1 Makedonija
N/A
Last Update: 20/03/2026
За A1 Компанијата А1 Македонија е член на А1 Телеком Австрија Групацијата, водечки провајдер за комуникациски и дигитални решенија во Централна и Источна Европа кој работи во седум држави и обезбедува услуги на над 25 милиони корисници. На македонскиот пазар компанија...
stc
King Abdul Aziz Complex, Riyadh, SA
Last Update: 07/10/2026
We are a forward-focused digital champion always been focused on innovation and evolution. Our purpose is to create and bring greater dimension and richness to people’s personal and professional lives. With stc, You will always be empowered to focus on delivering w...
Compliance Ranges Comparison
A1 Makedonija
stc
Benchmark & Cyber Underwriting Signals
Incidents vs Telecommunications Industry Avg (This Year)
No incidents recorded for A1 Makedonija in 2026.
Incidents vs Telecommunications Industry Avg (This Year)
No incidents recorded for stc in 2026.
Incident History - A1 Makedonija (X = Date, Y = Severity)
A1 Makedonija cyber incidents detection timeline including parent company and subsidiaries.
Incident History - stc (X = Date, Y = Severity)
stc cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
A1 Makedonija
stc
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.