Comparison Overview
GLICO

GLICO
4-6-5, UTAJIMA, NISHIYODOGAWA-KU, Osaka, Osaka Prefecture, JP, 555-0021
Last Update: 16/07/2026
EZAKI GLICO CO.,LTD. is a foods company based out of 4-6-5, Utajima, Nishiyodogawa-ku, Osaka, Osaka Prefecture, Japan. 1. Overview Glico group *(“Glico”) has been engaged in business activities that focus on our corporate goal of “enhancing public health through food” ...

FrieslandCampina
Stationsplein 4, Amersfoort, 3818LE, NL
Last Update: 14/09/2026
FrieslandCampina is a large international dairy company with a cooperative history dating back more than 150 years. The company processes milk into a wide range of dairy products and ingredients. Royal FrieslandCampina N.V. is fully owned by Zuivelcoöperatie FrieslandCa...
Compliance Ranges Comparison

GLICO







FrieslandCampina






Benchmark & Cyber Underwriting Signals
Incidents vs Food and Beverage Manufacturing Industry Avg (This Year)
GLICO has 33.33% fewer incidents than the average of same-industry companies with at least one recorded incident.
Incidents vs Food and Beverage Manufacturing Industry Avg (This Year)
No incidents recorded for FrieslandCampina in 2026.
Incident History - GLICO (X = Date, Y = Severity)
GLICO cyber incidents detection timeline including parent company and subsidiaries.
Incident History - FrieslandCampina (X = Date, Y = Severity)
FrieslandCampina cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

GLICO

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