Comparison Overview
TGI Direct, Inc.

TGI Direct, Inc.
5365 Hill 23 Drive, None, Flint, MI, US, 48507
Last Update: 02/04/2026
As a direct marketing company, we simplify the process of reaching your customers, effectively engaging with them, and elevating their perception of you and your brand. We focus on servicing highly regulated, process-driven industries where secure data transfer and on-t...

Ogilvy
175 Greenwich St, New York, NY, US, 10007
Last Update: 20/09/2026
Ogilvy has been creating impact for brands through iconic, culture-changing, value-driving ideas since the company was founded by David Ogilvy 75 years ago. We build on that rich legacy through Borderless Creativity – innovating at the intersections of its advertising, ...
Compliance Ranges Comparison

TGI Direct, Inc.







Ogilvy






Benchmark & Cyber Underwriting Signals
Incidents vs Advertising Services Industry Avg (This Year)
No incidents recorded for TGI Direct, Inc. in 2026.
Incidents vs Advertising Services Industry Avg (This Year)
No incidents recorded for Ogilvy in 2026.
Incident History - TGI Direct, Inc. (X = Date, Y = Severity)
TGI Direct, Inc. cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Ogilvy (X = Date, Y = Severity)
Ogilvy cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

TGI Direct, Inc.

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