Comparison Overview

Head of Zeus

VS

Entourage Yearbooks

Head of Zeus

Clerkenwell House,, London, undefined, EC1R 0HT, GB
Last Update: 2025-11-22
View Profile
Between 750 and 799
http://www.headofzeus.com

Head of Zeus is a young and vibrant publishing house dedicated to new authors, great storytelling and fabulous ideas. We opened for business on 3 January 2012 and we published our first books in July 2012. Our list is a mix of general and literary fiction, genre fiction and non fiction. Find out what we publish, who we are and why we are called Head of Zeus at our website, headofzeus.com. Or Follow us @HoZ_Books.

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

Entourage Yearbooks

39 Everett Dr, Princeton Junction, New Jersey, 08550, US
Last Update: 2025-11-27
Between 750 and 799
http://www.EntourageYearbooks.com

Entourage Yearbooks is one of the fastest growing yearbook companies in the US. The company serves thousands of schools and organization across the country from elementary schools, high schools through to colleges and universities. Entourage has one of the fastest production turnaround times in the yearbook industry and offers an expansive array of online tools and services to help make the process of publishing yearbooks easy. The company has a variety of employment and partnership opportunities for individuals and companies looking to lead innovation and service in the education industry.

NAICS: 511
NAICS Definition: Publishing Industries (except Internet)
Employees: 63
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/head-of-zeus.jpeg
Head of Zeus
—
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/entourage-yearbooks.jpeg
Entourage Yearbooks
—
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
Head of Zeus
100%
Compliance Rate
0/4 Standards Verified
Entourage Yearbooks
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 Head of Zeus in 2025.

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

No incidents recorded for Entourage Yearbooks in 2025.

Incident History — Head of Zeus (X = Date, Y = Severity)

Head of Zeus cyber incidents detection timeline including parent company and subsidiaries

Incident History — Entourage Yearbooks (X = Date, Y = Severity)

Entourage Yearbooks cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/head-of-zeus.jpeg
Head of Zeus
Incidents

No Incident

https://images.rankiteo.com/companyimages/entourage-yearbooks.jpeg
Entourage Yearbooks
Incidents

No Incident

FAQ

Both Head of Zeus company and Entourage Yearbooks company demonstrate a comparable AI Cybersecurity Score, with strong governance and monitoring frameworks in place.

Historically, Entourage Yearbooks company has disclosed a higher number of cyber incidents compared to Head of Zeus company.

In the current year, Entourage Yearbooks company and Head of Zeus company have not reported any cyber incidents.

Neither Entourage Yearbooks company nor Head of Zeus company has reported experiencing a ransomware attack publicly.

Neither Entourage Yearbooks company nor Head of Zeus company has reported experiencing a data breach publicly.

Neither Entourage Yearbooks company nor Head of Zeus company has reported experiencing targeted cyberattacks publicly.

Neither Head of Zeus company nor Entourage Yearbooks company has reported experiencing or disclosing vulnerabilities publicly.

Neither Head of Zeus nor Entourage Yearbooks holds any compliance certifications.

Neither company holds any compliance certifications.

Neither Head of Zeus company nor Entourage Yearbooks company has publicly disclosed detailed information about the number of their subsidiaries.

Head of Zeus company employs more people globally than Entourage Yearbooks company, reflecting its scale as a Book and Periodical Publishing.

Neither Head of Zeus nor Entourage Yearbooks holds SOC 2 Type 1 certification.

Neither Head of Zeus nor Entourage Yearbooks holds SOC 2 Type 2 certification.

Neither Head of Zeus nor Entourage Yearbooks holds ISO 27001 certification.

Neither Head of Zeus nor Entourage Yearbooks holds PCI DSS certification.

Neither Head of Zeus nor Entourage Yearbooks holds HIPAA certification.

Neither Head of Zeus nor Entourage Yearbooks 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.

Published
Date
2025-11-27
Updated
Date
2025-11-27
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
References
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).

Published
Date
2025-11-27
Updated
Date
2025-11-27
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
References
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

Published
Date
2025-11-27
Updated
Date
2025-11-27
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
References
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.

Published
Date
2025-11-27
Updated
Date
2025-11-27
References
Description

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

Published
Date
2025-11-27
Updated
Date
2025-11-27
References