Comparison Overview
Worksite Communications

Worksite Communications
800 Capital Circle SE, Tallahassee, FL, 32301, US
Last Update: 01/02/2026
Worksite Communications provides employee communication and benefit enrollment services. As one of the nation's most experienced independent communication and enrollment companies, we have the ability to design and implement complex employee communication projects for e...

Manulife
200 Bloor St E, Toronto, M4W, CA
Last Update: 07/10/2026
Manulife is a leading international financial services group that helps people make their decisions easier and lives better. With our global headquarters in Toronto, we operate as Manulife across our offices in Canada, Asia, and Europe, and primarily as John Hancock in ...
Compliance Ranges Comparison

Worksite Communications







Manulife






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

Worksite Communications

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