Comparison Overview

The Lancet Group

VS

Uitgeverij Podium

The Lancet Group

125 London Wall, London, GB, EC2Y 5AS
Last Update: 2025-11-22
Between 750 and 799

The Lancet was founded in 1823 by Thomas Wakley and began as an independent, international weekly general medical journal. Since then, The Lancet has sought to address urgent topics, initiate debate, put science into context, and influence decision-makers worldwide. Evolving as a group of health and medical journals, we retain the belief that the best science must lead to better lives. Visit our website to learn more.

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

Uitgeverij Podium

Amsterdam, NL
Last Update: 2025-11-21

Uitgeverij Podium werd in 1997 opgericht door Joost Nijsen, mede mogelijk gemaakt door de loyaliteit van Nederlandse auteurs die hij eerder uitgaf bij Nijgh & Van Ditmar en Balans, zoals Herman Franke, Ronald Giphart, Nicolaas Klei, Manon Uphoff en Henk van Woerden. Podium is vanaf de oprichting een zelfstandige uitgeverij, gespecialiseerd in hedendaagse Nederlandse en vertaalde literatuur (proza, poëzie) en literaire en journalistieke non-fictie. Dankzij een selectieve fondsvorming en beheerste titelproductie, kan door het enthousiaste en deskundige team aan de uitgegeven titels veel zorg worden besteed, zowel aan redactie en productie als aan verkoop en marketing.

NAICS: 511
NAICS Definition: Publishing Industries (except Internet)
Employees: 23
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/the-lancet.jpeg
The Lancet Group
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/uitgeverij-podium.jpeg
Uitgeverij Podium
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
The Lancet Group
100%
Compliance Rate
0/4 Standards Verified
Uitgeverij Podium
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 The Lancet Group in 2025.

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

No incidents recorded for Uitgeverij Podium in 2025.

Incident History — The Lancet Group (X = Date, Y = Severity)

The Lancet Group cyber incidents detection timeline including parent company and subsidiaries

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

Uitgeverij Podium cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/the-lancet.jpeg
The Lancet Group
Incidents

No Incident

https://images.rankiteo.com/companyimages/uitgeverij-podium.jpeg
Uitgeverij Podium
Incidents

No Incident

FAQ

Uitgeverij Podium company demonstrates a stronger AI Cybersecurity Score compared to The Lancet Group company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Historically, Uitgeverij Podium company has disclosed a higher number of cyber incidents compared to The Lancet Group company.

In the current year, Uitgeverij Podium company and The Lancet Group company have not reported any cyber incidents.

Neither Uitgeverij Podium company nor The Lancet Group company has reported experiencing a ransomware attack publicly.

Neither Uitgeverij Podium company nor The Lancet Group company has reported experiencing a data breach publicly.

Neither Uitgeverij Podium company nor The Lancet Group company has reported experiencing targeted cyberattacks publicly.

Neither The Lancet Group company nor Uitgeverij Podium company has reported experiencing or disclosing vulnerabilities publicly.

Neither The Lancet Group nor Uitgeverij Podium holds any compliance certifications.

Neither company holds any compliance certifications.

Neither The Lancet Group company nor Uitgeverij Podium company has publicly disclosed detailed information about the number of their subsidiaries.

The Lancet Group company employs more people globally than Uitgeverij Podium company, reflecting its scale as a Book and Periodical Publishing.

Neither The Lancet Group nor Uitgeverij Podium holds SOC 2 Type 1 certification.

Neither The Lancet Group nor Uitgeverij Podium holds SOC 2 Type 2 certification.

Neither The Lancet Group nor Uitgeverij Podium holds ISO 27001 certification.

Neither The Lancet Group nor Uitgeverij Podium holds PCI DSS certification.

Neither The Lancet Group nor Uitgeverij Podium holds HIPAA certification.

Neither The Lancet Group nor Uitgeverij Podium 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.