Comparison Overview

Relay Publishing

VS

MEES

Relay Publishing

Oxford Street, London, GB
Last Update: 2025-11-21

We started Relay Publishing over 10 years ago as a group of driven self publishing authors, editors, designers and marketers. We had one goal in mind: create amazing stories. We have since published hundreds of books over a variety of genres, totalling sales of over two million. Our experience in publishing, with the use of reader analytics, allows us to target gaps in the market and provide content that readers are desperate to read. Relay's Core Values are: * Collaboration * Honesty with sensitivity * Problem-solving * Pride in work * Fun & Friendly https://www.facebook.com/RelayPublishingRecruitment

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

MEES

32 Cubitt Street, London, WC1X 0LR, GB
Last Update: 2025-11-21
Between 750 and 799

MEES (abbreviated from the former name Middle East Economic Survey) is a weekly energy publications that focuses on Middle East and North Africa energy news, data and analysis. Our weekly coverage include Oil & Gas, Transportation/LNG, Refining & Petrochemicals, Power & Water, OPEC, Geopolitical Risk, Corporate Strategy, Economics & Finance, and Data. We invest our time to delve into the details that will empower you with forward-looking analysis, enabling you to attain your objectives efficiently and successfully within the Middle East region's constantly changing energy, economic, political and social landscape. These factors directly and indirectly influence the risks involved in a region, that is and will remain vital to global energy supplies. The importance of the Middle East and North Africa cannot be understated given the proven reserves of the region (53% of world reserves) the low cost of production, as well as being home to 5 of the 10 top world oil producers. Even with the US 'shale revolution, theMiddle East's massive reserves means the region will continue to increase its market share by 2050.

NAICS: 511
NAICS Definition: Publishing Industries (except Internet)
Employees: 74
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/relay-publishing.jpeg
Relay 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
https://images.rankiteo.com/companyimages/mees.jpeg
MEES
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
Relay Publishing
100%
Compliance Rate
0/4 Standards Verified
MEES
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 Relay Publishing in 2025.

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

No incidents recorded for MEES in 2025.

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

Relay Publishing cyber incidents detection timeline including parent company and subsidiaries

Incident History — MEES (X = Date, Y = Severity)

MEES cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/relay-publishing.jpeg
Relay Publishing
Incidents

No Incident

https://images.rankiteo.com/companyimages/mees.jpeg
MEES
Incidents

No Incident

FAQ

Both Relay Publishing company and MEES company demonstrate a comparable AI Cybersecurity Score, with strong governance and monitoring frameworks in place.

Historically, MEES company has disclosed a higher number of cyber incidents compared to Relay Publishing company.

In the current year, MEES company and Relay Publishing company have not reported any cyber incidents.

Neither MEES company nor Relay Publishing company has reported experiencing a ransomware attack publicly.

Neither MEES company nor Relay Publishing company has reported experiencing a data breach publicly.

Neither MEES company nor Relay Publishing company has reported experiencing targeted cyberattacks publicly.

Neither Relay Publishing company nor MEES company has reported experiencing or disclosing vulnerabilities publicly.

Neither Relay Publishing nor MEES holds any compliance certifications.

Neither company holds any compliance certifications.

Neither Relay Publishing company nor MEES company has publicly disclosed detailed information about the number of their subsidiaries.

MEES company employs more people globally than Relay Publishing company, reflecting its scale as a Book and Periodical Publishing.

Neither Relay Publishing nor MEES holds SOC 2 Type 1 certification.

Neither Relay Publishing nor MEES holds SOC 2 Type 2 certification.

Neither Relay Publishing nor MEES holds ISO 27001 certification.

Neither Relay Publishing nor MEES holds PCI DSS certification.

Neither Relay Publishing nor MEES holds HIPAA certification.

Neither Relay Publishing nor MEES 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.