Comparison Overview
Amdocs Optima

Amdocs Optima
Hapnina St. #8, Raanana , 43000, IL
Last Update: 23/04/2026
We help those who build the future to make it amazing. In an era where new technologies are born every minute, and the demand for meaningful digital experiences has never been so intense, we unlock our customers’ innovative potential, empowering them to transform their ...

Telkom Indonesia
Jalan Jenderal Gatot Subroto Kav. 52, Jakarta Selatan, 40264, ID
Last Update: 13/09/2026
PT Telkom Indonesia (Persero) Tbk (Telkom) is a state-owned information and communications technology enterprise and telecommunications network in Indonesia. The Government of Indonesia is the majority shareholder with 52.09 percent shares while the remaining 47.91 perc...
Compliance Ranges Comparison

Amdocs Optima







Telkom Indonesia






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

Amdocs Optima

Telkom Indonesia
FAQ
Latest Global CVEs
HTTP/2 servers could end up crashing due to inadvertently modifying its HPACK encoder concurrently. This happens because the server modifies the HPACK encoder from two goroutines without synchronization: one uses the encoder to encode a HEADERS frame as part of a response sent to a client and the other modifies the encoder's table size when handling a SETTINGS frame containing SETTINGS_HEADER_TABLE_SIZE that a client sends. A malicious client can repeatedly send a request while changing the header table size to crash the server.
Multiple ECH outer extension references are not permitted under RFC 9849; previously, a client could send a well-crafted packet that could trigger memory exhaustion in the server process by specifying multiple references. We now reject these as malformed and curb the memory amplification vector as a result.
A trusted template author may have previously written a valid template wherein the use of the 'yield' keyword would not be correctly escaped. We now ensure that valid keyword uses are escaped and non-keyword uses are not escaped.
Improper certificate validation in Microsoft Partner Center allows an unauthorized attacker to elevate privileges over a network.
Authorization bypass through user-controlled key in Microsoft Bookings allows an unauthorized attacker to elevate privileges over a network.