Comparison Overview

Pharos-Tribune

VS

dotbooks GmbH

Pharos-Tribune

None
Last Update: 2025-11-21
Between 800 and 849

Founded in 1844 as the Democratic Pharos, the Pharos-Tribune is a 10,250 circulation daily newspaper in Logansport, IN owned by Community Newspaper Holdings Inc. of Birmingham, AL. The Pharos-Tribune covers a six county area including Carroll, Cass, Fulton, Miami, Pulaski and White counties. Robyn McCloskey, publisher Kelly Hawes, managing editor Founded in 1844

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

dotbooks GmbH

None
Last Update: 2025-11-22
Between 750 and 799

dotbooks is a leading digital publisher in Germany, connecting readers with captivating eBooks across crime, romance, and historical fiction genres. With bestsellers from renowned authors like Angela Lautenschläger, Ole Hansen, David Conti, Jennifer Wellen, and Katja Maybach gracing our extensive catalog, we are committed to empower authors to share their stories widely.

NAICS: 511
NAICS Definition: Publishing Industries (except Internet)
Employees: 14
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/pharos-tribune.jpeg
Pharos-Tribune
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/dotbooks-gmbh.jpeg
dotbooks GmbH
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
Pharos-Tribune
100%
Compliance Rate
0/4 Standards Verified
dotbooks GmbH
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 Pharos-Tribune in 2025.

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

No incidents recorded for dotbooks GmbH in 2025.

Incident History — Pharos-Tribune (X = Date, Y = Severity)

Pharos-Tribune cyber incidents detection timeline including parent company and subsidiaries

Incident History — dotbooks GmbH (X = Date, Y = Severity)

dotbooks GmbH cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/pharos-tribune.jpeg
Pharos-Tribune
Incidents

No Incident

https://images.rankiteo.com/companyimages/dotbooks-gmbh.jpeg
dotbooks GmbH
Incidents

No Incident

FAQ

Pharos-Tribune company demonstrates a stronger AI Cybersecurity Score compared to dotbooks GmbH company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Historically, dotbooks GmbH company has disclosed a higher number of cyber incidents compared to Pharos-Tribune company.

In the current year, dotbooks GmbH company and Pharos-Tribune company have not reported any cyber incidents.

Neither dotbooks GmbH company nor Pharos-Tribune company has reported experiencing a ransomware attack publicly.

Neither dotbooks GmbH company nor Pharos-Tribune company has reported experiencing a data breach publicly.

Neither dotbooks GmbH company nor Pharos-Tribune company has reported experiencing targeted cyberattacks publicly.

Neither Pharos-Tribune company nor dotbooks GmbH company has reported experiencing or disclosing vulnerabilities publicly.

Neither Pharos-Tribune nor dotbooks GmbH holds any compliance certifications.

Neither company holds any compliance certifications.

Neither Pharos-Tribune company nor dotbooks GmbH company has publicly disclosed detailed information about the number of their subsidiaries.

Pharos-Tribune company employs more people globally than dotbooks GmbH company, reflecting its scale as a Book and Periodical Publishing.

Neither Pharos-Tribune nor dotbooks GmbH holds SOC 2 Type 1 certification.

Neither Pharos-Tribune nor dotbooks GmbH holds SOC 2 Type 2 certification.

Neither Pharos-Tribune nor dotbooks GmbH holds ISO 27001 certification.

Neither Pharos-Tribune nor dotbooks GmbH holds PCI DSS certification.

Neither Pharos-Tribune nor dotbooks GmbH holds HIPAA certification.

Neither Pharos-Tribune nor dotbooks GmbH 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.