Comparison Overview

MARTI YAYIN GRUBU

VS

Future Media Group, Inc.

MARTI YAYIN GRUBU

None
Last Update: 2025-11-27
View Profile
Between 800 and 849
http://www.martiyayinlari.com

Marti Publishing Group was founded in 2006. Previously being a bookstore for more than 10 years, Marti decided to publish books to contribute to the shelves and add a new vision to publishing industry in Turkey. Despite the fact that the number of readers are really low in Turkey, Marti showed a great process and progress upwards in the market. The vision of Marti was and always has been publishing good literatüre from around the world, focusing mostly on upmarket fiction.

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

Future Media Group, Inc.

1 World Trade Center, New York, NY, 10007, US
Last Update: 2025-11-26
Between 700 and 749
http://fmg.inc

Future Media Group is a company of thinkers, strategists, curators, and creators sharing technology, intelligence, talent, and experience to create best-in-class content covering the worlds of luxury, style, culture, and design. Founded in 2019, we are preparing legacy editorial brands and brand-new properties to survive and thrive in media’s competitive future. Our current portfolio of media brands includes W Magazine, Surface Magazine, and Watch Journal.

NAICS: 511
NAICS Definition:
Employees: 4
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/marti-yayin-grubu.jpeg
MARTI YAYIN GRUBU
—
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/future-media-group-inc.jpeg
Future Media Group, Inc.
—
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
MARTI YAYIN GRUBU
100%
Compliance Rate
0/4 Standards Verified
Future Media Group, Inc.
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 MARTI YAYIN GRUBU in 2025.

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

No incidents recorded for Future Media Group, Inc. in 2025.

Incident History — MARTI YAYIN GRUBU (X = Date, Y = Severity)

MARTI YAYIN GRUBU cyber incidents detection timeline including parent company and subsidiaries

Incident History — Future Media Group, Inc. (X = Date, Y = Severity)

Future Media Group, Inc. cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/marti-yayin-grubu.jpeg
MARTI YAYIN GRUBU
Incidents

No Incident

https://images.rankiteo.com/companyimages/future-media-group-inc.jpeg
Future Media Group, Inc.
Incidents

No Incident

FAQ

MARTI YAYIN GRUBU company demonstrates a stronger AI Cybersecurity Score compared to Future Media Group, Inc. company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Historically, Future Media Group, Inc. company has disclosed a higher number of cyber incidents compared to MARTI YAYIN GRUBU company.

In the current year, Future Media Group, Inc. company and MARTI YAYIN GRUBU company have not reported any cyber incidents.

Neither Future Media Group, Inc. company nor MARTI YAYIN GRUBU company has reported experiencing a ransomware attack publicly.

Neither Future Media Group, Inc. company nor MARTI YAYIN GRUBU company has reported experiencing a data breach publicly.

Neither Future Media Group, Inc. company nor MARTI YAYIN GRUBU company has reported experiencing targeted cyberattacks publicly.

Neither MARTI YAYIN GRUBU company nor Future Media Group, Inc. company has reported experiencing or disclosing vulnerabilities publicly.

Neither MARTI YAYIN GRUBU nor Future Media Group, Inc. holds any compliance certifications.

Neither company holds any compliance certifications.

Neither MARTI YAYIN GRUBU company nor Future Media Group, Inc. company has publicly disclosed detailed information about the number of their subsidiaries.

MARTI YAYIN GRUBU company employs more people globally than Future Media Group, Inc. company, reflecting its scale as a Book and Periodical Publishing.

Neither MARTI YAYIN GRUBU nor Future Media Group, Inc. holds SOC 2 Type 1 certification.

Neither MARTI YAYIN GRUBU nor Future Media Group, Inc. holds SOC 2 Type 2 certification.

Neither MARTI YAYIN GRUBU nor Future Media Group, Inc. holds ISO 27001 certification.

Neither MARTI YAYIN GRUBU nor Future Media Group, Inc. holds PCI DSS certification.

Neither MARTI YAYIN GRUBU nor Future Media Group, Inc. holds HIPAA certification.

Neither MARTI YAYIN GRUBU nor Future Media Group, Inc. 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.

Published
Date
2025-11-27
Updated
Date
2025-11-27
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
References
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).

Published
Date
2025-11-27
Updated
Date
2025-11-27
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
References
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

Published
Date
2025-11-27
Updated
Date
2025-11-27
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
References
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.

Published
Date
2025-11-27
Updated
Date
2025-11-27
References
Description

Exposure of credentials in unintended requests in Devolutions Server.This issue affects Server: through 2025.2.20, through 2025.3.8.

Published
Date
2025-11-27
Updated
Date
2025-11-27
References