Comparison Overview

NEJM AI

VS

LID Publishing

NEJM AI

860 Winter St, Waltham, 02451, US
Last Update: 2025-11-22
Between 750 and 799

NEJM AI, a new monthly journal from NEJM Group, is the first publication to engage both clinical and technology innovators in applying the rigorous research and publishing standards of the New England Journal of Medicine to evaluate the promises and pitfalls of clinical applications of AI. NEJM AI is leading the way in establishing a stronger evidence base for clinical AI while facilitating dialogue among all parties with a stake in these emerging technologies. We invite you to join your peers on this journey.

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

LID Publishing

Unit 304, London, EC1N 7RJ, GB
Last Update: 2025-11-21

LID Publishing specialises in working with business authors and organisations to help them develop content to promote their brand, message and expertise. Founded in 1993, LID has over 1,700 authors and continues to add approximately 120 new titles each year, around one-third in English and the rest in Spanish and other languages. LID also publishes academic and professional journals like Dialogue. LID books have been translated into over a dozen languages and distributed worldwide. LID employs 60 people in nine offices in seven countries: United States, United Kingdom, China, Spain, Mexico, Colombia and Argentina. It ranks number one in the world in business history and business dictionaries and is the leading publisher of business books in the Spanish-speaking countries. LID is a founding member of Business Publishers Roundtable. LID Speakers promotes a network of over 100 speakers specialising in business topics while LID Learning offers online educational and training courses. OUR MISSION: Guarantee our authors and sponsors the effective communication of their corporate image and ideas throughout the business world by means of printed books, audiovisual products, via Internet and in person.

NAICS: 511
NAICS Definition: Publishing Industries (except Internet)
Employees: 34
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/nejm-ai.jpeg
NEJM AI
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/lid-publishing.jpeg
LID 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
NEJM AI
100%
Compliance Rate
0/4 Standards Verified
LID 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 NEJM AI in 2025.

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

No incidents recorded for LID Publishing in 2025.

Incident History — NEJM AI (X = Date, Y = Severity)

NEJM AI cyber incidents detection timeline including parent company and subsidiaries

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

LID Publishing cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/nejm-ai.jpeg
NEJM AI
Incidents

Date Detected: 10/2024
Type:Breach
Attack Vector: Unauthorized Code Installation
Blog: Blog
https://images.rankiteo.com/companyimages/lid-publishing.jpeg
LID Publishing
Incidents

No Incident

FAQ

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

NEJM AI company has historically faced a number of disclosed cyber incidents, whereas LID Publishing company has not reported any.

In the current year, LID Publishing company and NEJM AI company have not reported any cyber incidents.

Neither LID Publishing company nor NEJM AI company has reported experiencing a ransomware attack publicly.

NEJM AI company has disclosed at least one data breach, while the other LID Publishing company has not reported such incidents publicly.

Neither LID Publishing company nor NEJM AI company has reported experiencing targeted cyberattacks publicly.

Neither NEJM AI company nor LID Publishing company has reported experiencing or disclosing vulnerabilities publicly.

Neither NEJM AI nor LID Publishing holds any compliance certifications.

Neither company holds any compliance certifications.

NEJM AI company has more subsidiaries worldwide compared to LID Publishing company.

Neither NEJM AI nor LID Publishing holds SOC 2 Type 1 certification.

Neither NEJM AI nor LID Publishing holds SOC 2 Type 2 certification.

Neither NEJM AI nor LID Publishing holds ISO 27001 certification.

Neither NEJM AI nor LID Publishing holds PCI DSS certification.

Neither NEJM AI nor LID Publishing holds HIPAA certification.

Neither NEJM AI nor LID 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.