Comparison Overview

Vanguard Seattle

VS

TIMGlobal Media

Vanguard Seattle

2200 Alaskan Way , Seattle, WA, 98121, US
Last Update: 2025-11-26

CULTURED & CURATED FOR YOU. Covering the most important art and fashion events in the city, including excellent reviews for smart people. Follow us on Instagram @vanguardseattle Be in the know for FREE & SUBSCRIBE TODAY as you stay informed about upcoming arts, culture and fashion events with our monthly newsletter. We’ll highlight the best activities in Seattle and our latest coverage and critiques. http://vanguardseattle.com/subscribe-vanguard-newsletter/ (B2B) Want to promote your event or advertise your business on Vanguard Seattle? contact us at: [email protected]

NAICS: 511
NAICS Definition:
Employees: 4
Subsidiaries: 0
12-month incidents
0
Known data breaches
0
Attack type number
0

TIMGlobal Media

Chaussée de La Hulpe 177, Watermael-Boitsfort, 1170, BE
Last Update: 2025-11-21
Between 750 and 799

TIMGlobal Media, headquartered in Uccle (Belgium), concentrates fully upon meeting the vital need of industry for up-to-date product information. Since 1975, the company has been serving the European market with industrial publications, websites, online directories and e-services. TIMGlobal Media provides information for the purchasing process via in-depth information available on the Internet and publications which facilitate product marketing and brand recognition. TIMGlobal Media serves the whole of Europe with IEN Europe, PCN Europe, icatalogs and Energy Efficiency: business & industry, and serves local markets with IEN D-A-CH in Germany, PEI in France, IEN Italia, Il Distributore Industriale, Manutenzione & Asset Management and CMI (Costruzione e Manutenzione Impianti) in Italy and Endüstri Dünyası in Turkey.

NAICS: 511
NAICS Definition: Publishing Industries (except Internet)
Employees: 34
Subsidiaries: 0
12-month incidents
0
Known data breaches
0
Attack type number
0

Compliance Badges Comparison

Security & Compliance Standards Overview

https://images.rankiteo.com/companyimages/vanguard-seattle.jpeg
Vanguard Seattle
ISO 27001
ISO 27001 certification not verified
Not verified
SOC2 Type 1
SOC2 Type 1 certification not verified
Not verified
SOC2 Type 2
SOC2 Type 2 certification not verified
Not verified
GDPR
GDPR certification not verified
Not verified
PCI DSS
PCI DSS certification not verified
Not verified
HIPAA
HIPAA certification not verified
Not verified
https://images.rankiteo.com/companyimages/timglobal-media.jpeg
TIMGlobal Media
ISO 27001
ISO 27001 certification not verified
Not verified
SOC2 Type 1
SOC2 Type 1 certification not verified
Not verified
SOC2 Type 2
SOC2 Type 2 certification not verified
Not verified
GDPR
GDPR certification not verified
Not verified
PCI DSS
PCI DSS certification not verified
Not verified
HIPAA
HIPAA certification not verified
Not verified
Compliance Summary
Vanguard Seattle
100%
Compliance Rate
0/4 Standards Verified
TIMGlobal Media
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Book and Periodical Publishing Industry Average (This Year)

No incidents recorded for Vanguard Seattle in 2025.

Incidents vs Book and Periodical Publishing Industry Average (This Year)

No incidents recorded for TIMGlobal Media in 2025.

Incident History — Vanguard Seattle (X = Date, Y = Severity)

Vanguard Seattle cyber incidents detection timeline including parent company and subsidiaries

Incident History — TIMGlobal Media (X = Date, Y = Severity)

TIMGlobal Media cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/vanguard-seattle.jpeg
Vanguard Seattle
Incidents

No Incident

https://images.rankiteo.com/companyimages/timglobal-media.jpeg
TIMGlobal Media
Incidents

No Incident

FAQ

Vanguard Seattle company demonstrates a stronger AI Cybersecurity Score compared to TIMGlobal Media company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Historically, TIMGlobal Media company has disclosed a higher number of cyber incidents compared to Vanguard Seattle company.

In the current year, TIMGlobal Media company and Vanguard Seattle company have not reported any cyber incidents.

Neither TIMGlobal Media company nor Vanguard Seattle company has reported experiencing a ransomware attack publicly.

Neither TIMGlobal Media company nor Vanguard Seattle company has reported experiencing a data breach publicly.

Neither TIMGlobal Media company nor Vanguard Seattle company has reported experiencing targeted cyberattacks publicly.

Neither Vanguard Seattle company nor TIMGlobal Media company has reported experiencing or disclosing vulnerabilities publicly.

Neither Vanguard Seattle nor TIMGlobal Media holds any compliance certifications.

Neither company holds any compliance certifications.

Neither Vanguard Seattle company nor TIMGlobal Media company has publicly disclosed detailed information about the number of their subsidiaries.

TIMGlobal Media company employs more people globally than Vanguard Seattle company, reflecting its scale as a Book and Periodical Publishing.

Neither Vanguard Seattle nor TIMGlobal Media holds SOC 2 Type 1 certification.

Neither Vanguard Seattle nor TIMGlobal Media holds SOC 2 Type 2 certification.

Neither Vanguard Seattle nor TIMGlobal Media holds ISO 27001 certification.

Neither Vanguard Seattle nor TIMGlobal Media holds PCI DSS certification.

Neither Vanguard Seattle nor TIMGlobal Media holds HIPAA certification.

Neither Vanguard Seattle nor TIMGlobal Media holds GDPR certification.

Latest Global CVEs (Not Company-Specific)

Description

ThingsBoard in versions prior to v4.2.1 allows an authenticated user to upload malicious SVG images via the "Image Gallery", leading to a Stored Cross-Site Scripting (XSS) vulnerability. The exploit can be triggered when any user accesses the public API endpoint of the malicious SVG images, or if the malicious images are embedded in an `iframe` element, during a widget creation, deployed to any page of the platform (e.g., dashboards), and accessed during normal operations. The vulnerability resides in the `ImageController`, which fails to restrict the execution of JavaScript code when an image is loaded by the user's browser. This vulnerability can lead to the execution of malicious code in the context of other users' sessions, potentially compromising their accounts and allowing unauthorized actions.

Risk Information
cvss4
Base: 6.2
Severity: LOW
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:N/VI:N/VA:N/SC:H/SI:L/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Description

Mattermost versions 11.0.x <= 11.0.2, 10.12.x <= 10.12.1, 10.11.x <= 10.11.4, 10.5.x <= 10.5.12 fail to to verify that the token used during the code exchange originates from the same authentication flow, which allows an authenticated user to perform account takeover via a specially crafted email address used when switching authentication methods and sending a request to the /users/login/sso/code-exchange endpoint. The vulnerability requires ExperimentalEnableAuthenticationTransfer to be enabled (default: enabled) and RequireEmailVerification to be disabled (default: disabled).

Risk Information
cvss3
Base: 9.9
Severity: LOW
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
Description

Mattermost versions 11.0.x <= 11.0.2, 10.12.x <= 10.12.1, 10.11.x <= 10.11.4, 10.5.x <= 10.5.12 fail to sanitize team email addresses to be visible only to Team Admins, which allows any authenticated user to view team email addresses via the GET /api/v4/channels/{channel_id}/common_teams endpoint

Risk Information
cvss3
Base: 4.3
Severity: LOW
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
Description

Exposure of email service credentials to users without administrative rights in Devolutions Server.This issue affects Devolutions Server: before 2025.2.21, before 2025.3.9.

Description

Exposure of credentials in unintended requests in Devolutions Server.This issue affects Server: through 2025.2.20, through 2025.3.8.