Comparison Overview

TCK Publishing

VS

Inside Cybersecurity

TCK Publishing

None
Last Update: 2025-11-26

TCK Publishing started as a small independent publishing company in 2011. Today, we are an international publishing company specializing in mass-market trade books. We publish fiction and non-fiction eBooks, print books, and audiobooks in all major genres and niches. Our mission is to help our authors earn a full-time income from royalties. We do this by creating a comprehensive publishing and marketing strategy unique to each book and each author. We also pay authors 50% royalties—that’s about six times more than the average traditional publisher pays. Unlike most large publishing companies, we treat our authors like VIP business partners. That’s why we respond to all submissions within 14-21 days, have a full-time tech support team build and maintain websites for our authors at no cost, and provide ongoing coaching and support for our authors.

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

Inside Cybersecurity

1919 S Eads St, Arlington, 22202, US
Last Update: 2025-11-21

Federal cybersecurity policy is at a crossroads as emerging technologies – 5G networks, AI and cloud services – are forcing policymakers within government and industry to rethink managing risks and the possible role for regulations. Inside Cybersecurity is responding to the changing nature of cyber threats and policies with several innovations to better serve our community of readers, building on a well-established reputation for hard-driving news, analysis and perspective on what matters most. Inside Cybersecurity is committed to providing its community of readers the news, analysis and resources for meeting the needs of cybersecurity professionals, and we think these latest innovations will be crucial in collectively addressing these challenges head-on. Inside Cybersecurity is a subscription-based premium news service for policy professionals who need to know about evolving federal policies to protect cyberspace.

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

Compliance Badges Comparison

Security & Compliance Standards Overview

https://images.rankiteo.com/companyimages/tck-publishing.jpeg
TCK 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
https://images.rankiteo.com/companyimages/inside-cybersecurity.jpeg
Inside Cybersecurity
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
TCK Publishing
100%
Compliance Rate
0/4 Standards Verified
Inside Cybersecurity
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 TCK Publishing in 2025.

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

No incidents recorded for Inside Cybersecurity in 2025.

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

TCK Publishing cyber incidents detection timeline including parent company and subsidiaries

Incident History — Inside Cybersecurity (X = Date, Y = Severity)

Inside Cybersecurity cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/tck-publishing.jpeg
TCK Publishing
Incidents

No Incident

https://images.rankiteo.com/companyimages/inside-cybersecurity.jpeg
Inside Cybersecurity
Incidents

No Incident

FAQ

Inside Cybersecurity company demonstrates a stronger AI Cybersecurity Score compared to TCK Publishing company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Historically, Inside Cybersecurity company has disclosed a higher number of cyber incidents compared to TCK Publishing company.

In the current year, Inside Cybersecurity company and TCK Publishing company have not reported any cyber incidents.

Neither Inside Cybersecurity company nor TCK Publishing company has reported experiencing a ransomware attack publicly.

Neither Inside Cybersecurity company nor TCK Publishing company has reported experiencing a data breach publicly.

Neither Inside Cybersecurity company nor TCK Publishing company has reported experiencing targeted cyberattacks publicly.

Neither TCK Publishing company nor Inside Cybersecurity company has reported experiencing or disclosing vulnerabilities publicly.

Neither TCK Publishing nor Inside Cybersecurity holds any compliance certifications.

Neither company holds any compliance certifications.

Inside Cybersecurity company has more subsidiaries worldwide compared to TCK Publishing company.

Neither TCK Publishing nor Inside Cybersecurity holds SOC 2 Type 1 certification.

Neither TCK Publishing nor Inside Cybersecurity holds SOC 2 Type 2 certification.

Neither TCK Publishing nor Inside Cybersecurity holds ISO 27001 certification.

Neither TCK Publishing nor Inside Cybersecurity holds PCI DSS certification.

Neither TCK Publishing nor Inside Cybersecurity holds HIPAA certification.

Neither TCK Publishing nor Inside Cybersecurity 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.