Comparison Overview

Bellingham Alive Magazine

VS

The Lorenz Corporation

Bellingham Alive Magazine

851 Coho Way, Bellingham, 98225, US
Last Update: 2025-11-22
Between 750 and 799

Bellingham Alive is dedicated to bringing a positive voice to the North Puget Sound community through an upscale lifestyle magazine and "home page" website designed to celebrate ourselves and our accomplishments, while promoting local businesses and community dialogue with fresh, informative and provocative feature articles and a unique public forum for all stakeholders to be heard.

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

The Lorenz Corporation

501 E. Third St., Dayton, OH, 45402, US
Last Update: 2025-11-23
Between 750 and 799

Lorenz proudly serves as the publishing home for today’s leading choral composers, elementary music educators, and church musicians of all disciplines. We are located in downtown Dayton, OH, and our team members—music educators, worship musicians, performers, and admirers—embody the innovative spirit of this famous city. Our mission is to discover, develop, and deliver publications that worship musicians and music educators use to inspire their communities. Our work to achieve this mission covers music sourcing and editing, advertising and selling, printing and fulfillment, and accounting and finance. We have a skilled, experienced, flexible, and dedicated team of employees empowered to serve this work, and with it, the composers, writers, and musicians who look to us.

NAICS: 511
NAICS Definition: Publishing Industries (except Internet)
Employees: 36
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/bellingham-alive-magazine.jpeg
Bellingham Alive Magazine
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/the-lorenz-corporation.jpeg
The Lorenz Corporation
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
Bellingham Alive Magazine
100%
Compliance Rate
0/4 Standards Verified
The Lorenz Corporation
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 Bellingham Alive Magazine in 2025.

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

No incidents recorded for The Lorenz Corporation in 2025.

Incident History — Bellingham Alive Magazine (X = Date, Y = Severity)

Bellingham Alive Magazine cyber incidents detection timeline including parent company and subsidiaries

Incident History — The Lorenz Corporation (X = Date, Y = Severity)

The Lorenz Corporation cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/bellingham-alive-magazine.jpeg
Bellingham Alive Magazine
Incidents

No Incident

https://images.rankiteo.com/companyimages/the-lorenz-corporation.jpeg
The Lorenz Corporation
Incidents

No Incident

FAQ

The Lorenz Corporation company demonstrates a stronger AI Cybersecurity Score compared to Bellingham Alive Magazine company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Historically, The Lorenz Corporation company has disclosed a higher number of cyber incidents compared to Bellingham Alive Magazine company.

In the current year, The Lorenz Corporation company and Bellingham Alive Magazine company have not reported any cyber incidents.

Neither The Lorenz Corporation company nor Bellingham Alive Magazine company has reported experiencing a ransomware attack publicly.

Neither The Lorenz Corporation company nor Bellingham Alive Magazine company has reported experiencing a data breach publicly.

Neither The Lorenz Corporation company nor Bellingham Alive Magazine company has reported experiencing targeted cyberattacks publicly.

Neither Bellingham Alive Magazine company nor The Lorenz Corporation company has reported experiencing or disclosing vulnerabilities publicly.

Neither Bellingham Alive Magazine nor The Lorenz Corporation holds any compliance certifications.

Neither company holds any compliance certifications.

Neither Bellingham Alive Magazine company nor The Lorenz Corporation company has publicly disclosed detailed information about the number of their subsidiaries.

The Lorenz Corporation company employs more people globally than Bellingham Alive Magazine company, reflecting its scale as a Book and Periodical Publishing.

Neither Bellingham Alive Magazine nor The Lorenz Corporation holds SOC 2 Type 1 certification.

Neither Bellingham Alive Magazine nor The Lorenz Corporation holds SOC 2 Type 2 certification.

Neither Bellingham Alive Magazine nor The Lorenz Corporation holds ISO 27001 certification.

Neither Bellingham Alive Magazine nor The Lorenz Corporation holds PCI DSS certification.

Neither Bellingham Alive Magazine nor The Lorenz Corporation holds HIPAA certification.

Neither Bellingham Alive Magazine nor The Lorenz Corporation 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.