Comparison Overview

Uitgeverij Oostland

VS

Red Hen Press

Uitgeverij Oostland

Berkel en Rodenrijs, 2652, NL
Last Update: 2025-11-21

Iedere auteur maakt met zijn/haar boek een creatieve ontwikkeling door en vaak gaat hier (met name bij beginnende schrijvers) maanden, zelfs jaren werk in zitten. Vervolgens wordt met het manuscript stad en land afgelopen om een uitgever te vinden die het boek wil publiceren. Wanneer dat dan gebeurt (áls dat al gebeurd) wordt er door een uitgever een zeer laag royalty percentage uitbetaald. De uitgever slokt het leeuwendeel op, terwijl de diensten van de uitgever veelal niet in verhouding staan. De uitgevers beloven gouden bergen, maar in de praktijk komt er te weinig (of niets) van terecht. De filosofie van Uitgeverij Oostland is als volgt: de schrijvers hebben het werk gedaan. Dat zijn dus ook diegenen die de winst behoren te krijgen. De uitgever krijgt slechts betaald wanneer er specifiek van bepaalde diensten gebruik wordt gemaakt. Bij onze uitgeverij werkt het dan ook heel simpel en transparant.

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

Red Hen Press

91114, US
Last Update: 2025-11-23
Between 750 and 799

The mission of Red Hen Press is to discover, publish, and promote works of literary excellence that have been overlooked by mainstream presses, and to build audiences for literature in two ways: by fostering the literacy of youth and by bringing distinguished and emerging writers to the public stage. Our purpose is first to create and promote good writing. We wish to create a place in the world for good writers, whose work is ignored by the conglomerate publishers, but whose voices deserve to be heard, particularly writers whose work has been marginalized. We seek a diversity of voices that speak to what it means to be human and speak it well. We will endeavor toward the promotion of cultural literacy in the community. We will share books; readings, poetry, literature and ideas. Our goal is to allow good work to swim to the surface and then to share that work so that literature can create a common language space for global, community and individual transformation.

NAICS: 511
NAICS Definition: Publishing Industries (except Internet)
Employees: 60
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/uitgeverij-oostland.jpeg
Uitgeverij Oostland
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/red-hen-press.jpeg
Red Hen Press
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
Uitgeverij Oostland
100%
Compliance Rate
0/4 Standards Verified
Red Hen Press
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 Uitgeverij Oostland in 2025.

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

No incidents recorded for Red Hen Press in 2025.

Incident History — Uitgeverij Oostland (X = Date, Y = Severity)

Uitgeverij Oostland cyber incidents detection timeline including parent company and subsidiaries

Incident History — Red Hen Press (X = Date, Y = Severity)

Red Hen Press cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/uitgeverij-oostland.jpeg
Uitgeverij Oostland
Incidents

No Incident

https://images.rankiteo.com/companyimages/red-hen-press.jpeg
Red Hen Press
Incidents

No Incident

FAQ

Uitgeverij Oostland company demonstrates a stronger AI Cybersecurity Score compared to Red Hen Press company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Historically, Red Hen Press company has disclosed a higher number of cyber incidents compared to Uitgeverij Oostland company.

In the current year, Red Hen Press company and Uitgeverij Oostland company have not reported any cyber incidents.

Neither Red Hen Press company nor Uitgeverij Oostland company has reported experiencing a ransomware attack publicly.

Neither Red Hen Press company nor Uitgeverij Oostland company has reported experiencing a data breach publicly.

Neither Red Hen Press company nor Uitgeverij Oostland company has reported experiencing targeted cyberattacks publicly.

Neither Uitgeverij Oostland company nor Red Hen Press company has reported experiencing or disclosing vulnerabilities publicly.

Neither Uitgeverij Oostland nor Red Hen Press holds any compliance certifications.

Neither company holds any compliance certifications.

Neither Uitgeverij Oostland company nor Red Hen Press company has publicly disclosed detailed information about the number of their subsidiaries.

Red Hen Press company employs more people globally than Uitgeverij Oostland company, reflecting its scale as a Book and Periodical Publishing.

Neither Uitgeverij Oostland nor Red Hen Press holds SOC 2 Type 1 certification.

Neither Uitgeverij Oostland nor Red Hen Press holds SOC 2 Type 2 certification.

Neither Uitgeverij Oostland nor Red Hen Press holds ISO 27001 certification.

Neither Uitgeverij Oostland nor Red Hen Press holds PCI DSS certification.

Neither Uitgeverij Oostland nor Red Hen Press holds HIPAA certification.

Neither Uitgeverij Oostland nor Red Hen Press 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.