Comparison Overview

Thomas Nelson Publishers

VS

Skagit Publishing

Thomas Nelson Publishers

PO Box 141000, Nashville, TN, 37214, US
Last Update: 2025-11-27
Between 750 and 799

Thomas Nelson, Inc., part of HarperCollins Christian Publishing, is a world leading provider of Christian content and has been providing readers with quality inspirational product for more than 200 years. The publishing group provides multiple formats of award-winning Bibles, books, gift books, cookbooks, curriculum and digital content, with distribution of its products in more than 100 countries. Thomas Nelson, is headquartered in Nashville, TN with additional offices in Plano, TX. For additional information, please visit www.thomasnelson.com or www.harpercollinschristian.com. Recruitment Fraud Alert Information: www.harpercollinschristian.com/recruitment-fraud-alert/

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

Skagit Publishing

US, 98274
Last Update: 2025-11-28
Between 750 and 799

Skagit Publishing is a multi-media company which publishes the daily Skagit Valley Herald, the weekly Anacortes American, Stanwood Camano News, Your Fidalgo, The Argus and Courier-Times, and various specialty publications and websites. In addition, we are a full service commercial printer serving customers on the I-5 corridor. Skagit County is a beautiful area of Northwestern Washington state - roughly an hour North of Seattle - with much to offer, and Skagit Publishing offers outstanding content each day, across multiple platforms. Skagit Publishing is owned by Adams Publishing Group, a family-owned multimedia company. EOE Equal Opportunity Employer

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/thomas-nelson-publishers.jpeg
Thomas Nelson Publishers
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/skagit-publishing.jpeg
Skagit Publishing
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
Thomas Nelson Publishers
100%
Compliance Rate
0/4 Standards Verified
Skagit Publishing
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 Thomas Nelson Publishers in 2025.

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

No incidents recorded for Skagit Publishing in 2025.

Incident History — Thomas Nelson Publishers (X = Date, Y = Severity)

Thomas Nelson Publishers cyber incidents detection timeline including parent company and subsidiaries

Incident History — Skagit Publishing (X = Date, Y = Severity)

Skagit Publishing cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/thomas-nelson-publishers.jpeg
Thomas Nelson Publishers
Incidents

No Incident

https://images.rankiteo.com/companyimages/skagit-publishing.jpeg
Skagit Publishing
Incidents

No Incident

FAQ

Thomas Nelson Publishers company demonstrates a stronger AI Cybersecurity Score compared to Skagit Publishing company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Historically, Skagit Publishing company has disclosed a higher number of cyber incidents compared to Thomas Nelson Publishers company.

In the current year, Skagit Publishing company and Thomas Nelson Publishers company have not reported any cyber incidents.

Neither Skagit Publishing company nor Thomas Nelson Publishers company has reported experiencing a ransomware attack publicly.

Neither Skagit Publishing company nor Thomas Nelson Publishers company has reported experiencing a data breach publicly.

Neither Skagit Publishing company nor Thomas Nelson Publishers company has reported experiencing targeted cyberattacks publicly.

Neither Thomas Nelson Publishers company nor Skagit Publishing company has reported experiencing or disclosing vulnerabilities publicly.

Neither Thomas Nelson Publishers nor Skagit Publishing holds any compliance certifications.

Neither company holds any compliance certifications.

Neither Thomas Nelson Publishers company nor Skagit Publishing company has publicly disclosed detailed information about the number of their subsidiaries.

Thomas Nelson Publishers company employs more people globally than Skagit Publishing company, reflecting its scale as a Book and Periodical Publishing.

Neither Thomas Nelson Publishers nor Skagit Publishing holds SOC 2 Type 1 certification.

Neither Thomas Nelson Publishers nor Skagit Publishing holds SOC 2 Type 2 certification.

Neither Thomas Nelson Publishers nor Skagit Publishing holds ISO 27001 certification.

Neither Thomas Nelson Publishers nor Skagit Publishing holds PCI DSS certification.

Neither Thomas Nelson Publishers nor Skagit Publishing holds HIPAA certification.

Neither Thomas Nelson Publishers nor Skagit Publishing 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.