Comparison Overview

Greenleaf Book Group

VS

St Albans Messenger

Greenleaf Book Group

PO Box 91869, Austin, TX, 78709, US
Last Update: 2025-11-26

Greenleaf Book Group is a publisher and distributor that specializes in the development of independent authors and the growth of small presses. Our publishing model was designed to support the independent author and to make it possible for writers to retain the rights to their work and still compete with the major publishing houses. In addition to the books we publish, we distribute select titles from small and independent publishers to major trade outlets, including bookstores, libraries, and airport retailers. We serve the small and independent publishing community by offering industry guidance, business development, and unmatched production, distribution, and marketing services.

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

St Albans Messenger

281 N Main St, St Albans, Vermont 05478-2503, US
Last Update: 2025-11-26
Between 750 and 799

Currently owned by Jim O'Rourke, The Messenger has been an integral part of the community keeping readers educated and informed about local news and events. The Messenger has received numerous journalism awards in national, regional, and statewide competitions. To address greater commercial printing demands for small local businesses, the Messenger opened a print shop in the building – Messenger Marketing. Over the last thirty years, Messenger Marketing, previously Messenger Print & Design, has grown from a print shop to a full-service design studio handling traditional print jobs, while helping local businesses with branding and integrated marketing strategies executed via print, web and social media channels.

NAICS: 511
NAICS Definition:
Employees: 11
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/greenleaf-book-group.jpeg
Greenleaf Book Group
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/st-albans-messenger.jpeg
St Albans Messenger
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
Greenleaf Book Group
100%
Compliance Rate
0/4 Standards Verified
St Albans Messenger
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 Greenleaf Book Group in 2025.

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

No incidents recorded for St Albans Messenger in 2025.

Incident History — Greenleaf Book Group (X = Date, Y = Severity)

Greenleaf Book Group cyber incidents detection timeline including parent company and subsidiaries

Incident History — St Albans Messenger (X = Date, Y = Severity)

St Albans Messenger cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/greenleaf-book-group.jpeg
Greenleaf Book Group
Incidents

No Incident

https://images.rankiteo.com/companyimages/st-albans-messenger.jpeg
St Albans Messenger
Incidents

No Incident

FAQ

St Albans Messenger company demonstrates a stronger AI Cybersecurity Score compared to Greenleaf Book Group company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Historically, St Albans Messenger company has disclosed a higher number of cyber incidents compared to Greenleaf Book Group company.

In the current year, St Albans Messenger company and Greenleaf Book Group company have not reported any cyber incidents.

Neither St Albans Messenger company nor Greenleaf Book Group company has reported experiencing a ransomware attack publicly.

Neither St Albans Messenger company nor Greenleaf Book Group company has reported experiencing a data breach publicly.

Neither St Albans Messenger company nor Greenleaf Book Group company has reported experiencing targeted cyberattacks publicly.

Neither Greenleaf Book Group company nor St Albans Messenger company has reported experiencing or disclosing vulnerabilities publicly.

Neither Greenleaf Book Group nor St Albans Messenger holds any compliance certifications.

Neither company holds any compliance certifications.

Neither Greenleaf Book Group company nor St Albans Messenger company has publicly disclosed detailed information about the number of their subsidiaries.

Greenleaf Book Group company employs more people globally than St Albans Messenger company, reflecting its scale as a Book and Periodical Publishing.

Neither Greenleaf Book Group nor St Albans Messenger holds SOC 2 Type 1 certification.

Neither Greenleaf Book Group nor St Albans Messenger holds SOC 2 Type 2 certification.

Neither Greenleaf Book Group nor St Albans Messenger holds ISO 27001 certification.

Neither Greenleaf Book Group nor St Albans Messenger holds PCI DSS certification.

Neither Greenleaf Book Group nor St Albans Messenger holds HIPAA certification.

Neither Greenleaf Book Group nor St Albans Messenger 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.