Comparison Overview

Octopus Publishing Group

VS

National Geographic Partners

Octopus Publishing Group

50 Victoria Embankment, London, London, EC4Y 0DZ, GB
Last Update: 2025-11-26

Octopus is a leading publisher of non-fiction books. We have extensive experience of working with high profile authors, trusted partners and associations to produce exciting, market leading books. Our imprints each have their own identity and all publish highly successful titles of outstanding quality and content. They include Aster, Cassell, Conran Octopus, Endeavour, Gaia Books, Godsfield, Hamlyn, Ilex, Kyle, Miller’s, Mitchell Beazley, Monoray, Philip's, Pyramid, Spruce and Summersdale.

NAICS: 511
NAICS Definition:
Employees: 108
Subsidiaries: 15
12-month incidents
0
Known data breaches
0
Attack type number
0

National Geographic Partners

1145 17th St NW, Washington, 20036, US
Last Update: 2025-11-21

National Geographic Partners is a joint venture between The Walt Disney Company and the National Geographic Society. We return 27% of our proceeds to the nonprofit Society to fund work in the areas of science, exploration, conservation, and education. This unique partnership creates a virtuous cycle of storytelling and exploration that inspires people to act, enlightens their perspective, and often provides the spark to new ideas and innovation.

NAICS: 511
NAICS Definition: Publishing Industries (except Internet)
Employees: 78
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/octopus-publishing-group.jpeg
Octopus Publishing 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/national-geographic-partners.jpeg
National Geographic Partners
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
Octopus Publishing Group
100%
Compliance Rate
0/4 Standards Verified
National Geographic Partners
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 Octopus Publishing Group in 2025.

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

No incidents recorded for National Geographic Partners in 2025.

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

Octopus Publishing Group cyber incidents detection timeline including parent company and subsidiaries

Incident History — National Geographic Partners (X = Date, Y = Severity)

National Geographic Partners cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/octopus-publishing-group.jpeg
Octopus Publishing Group
Incidents

No Incident

https://images.rankiteo.com/companyimages/national-geographic-partners.jpeg
National Geographic Partners
Incidents

No Incident

FAQ

Both Octopus Publishing Group company and National Geographic Partners company demonstrate a comparable AI Cybersecurity Score, with strong governance and monitoring frameworks in place.

Historically, National Geographic Partners company has disclosed a higher number of cyber incidents compared to Octopus Publishing Group company.

In the current year, National Geographic Partners company and Octopus Publishing Group company have not reported any cyber incidents.

Neither National Geographic Partners company nor Octopus Publishing Group company has reported experiencing a ransomware attack publicly.

Neither National Geographic Partners company nor Octopus Publishing Group company has reported experiencing a data breach publicly.

Neither National Geographic Partners company nor Octopus Publishing Group company has reported experiencing targeted cyberattacks publicly.

Neither Octopus Publishing Group company nor National Geographic Partners company has reported experiencing or disclosing vulnerabilities publicly.

Neither Octopus Publishing Group nor National Geographic Partners holds any compliance certifications.

Neither company holds any compliance certifications.

Octopus Publishing Group company has more subsidiaries worldwide compared to National Geographic Partners company.

Octopus Publishing Group company employs more people globally than National Geographic Partners company, reflecting its scale as a Book and Periodical Publishing.

Neither Octopus Publishing Group nor National Geographic Partners holds SOC 2 Type 1 certification.

Neither Octopus Publishing Group nor National Geographic Partners holds SOC 2 Type 2 certification.

Neither Octopus Publishing Group nor National Geographic Partners holds ISO 27001 certification.

Neither Octopus Publishing Group nor National Geographic Partners holds PCI DSS certification.

Neither Octopus Publishing Group nor National Geographic Partners holds HIPAA certification.

Neither Octopus Publishing Group nor National Geographic Partners 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.