Comparison Overview

Root Literary

VS

Caribe Media, Inc.

Root Literary

Downtown Los Angeles, Los Angeles, California, 90014, US
Last Update: 2025-11-26
View Profile
Between 750 and 799
https://www.rootliterary.com/

Root Literary combines a big-agency business perspective with a boutique hands-on approach to literary representation. Literary agent Holly Root launched over two dozen New York Times bestsellers before founding Root Literary in 2017. The agency's clients benefit from our agents'​ proven skills in identifying talent, negotiating advantageous deals, and advocating for our books all the way from submission to publication. We offer our clients broad-based industry insights as well as individualized strategic thinking to empower each author to define and pursue their own unique path to success. We love what we do, and we do it best in partnership with storytellers who combine artistry with the drive to build a lasting body of work. In short, we’re more than just literary agents—we’re career builders.

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

Caribe Media, Inc.

PO Box 192819, San Juan, Puerto Rico, 00919, US
Last Update: 2025-11-26
Between 750 and 799
http://www.caribemediainc.com

Caribe Media, Inc. is the holding company that owns Axesa Servicios de Información, S. en C., Caribe Media, S. A. and Axesa Digital Network, Inc. For over 80 and 50 years respectively, Axesa Servicios de Información, S. en C. and Caribe Media, S. A. have been the official publishers of Caribe Media Directories in Puerto Rico and Dominican Republic; with a dominating market share (Axesa 80%, Caribe Media, S. A. 98%). Axesa Digital Network, Inc. is the group’s most recent company, created to provide digital services and solutions with a high level of sophistication and customization located at Panamá.

NAICS: 511
NAICS Definition:
Employees: 33
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/root-literary.jpeg
Root Literary
—
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/caribe-media.jpeg
Caribe Media, 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
Root Literary
100%
Compliance Rate
0/4 Standards Verified
Caribe Media, 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 Root Literary in 2025.

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

No incidents recorded for Caribe Media, Inc. in 2025.

Incident History — Root Literary (X = Date, Y = Severity)

Root Literary cyber incidents detection timeline including parent company and subsidiaries

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

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

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/root-literary.jpeg
Root Literary
Incidents

No Incident

https://images.rankiteo.com/companyimages/caribe-media.jpeg
Caribe Media, Inc.
Incidents

No Incident

FAQ

Caribe Media, Inc. company demonstrates a stronger AI Cybersecurity Score compared to Root Literary company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Historically, Caribe Media, Inc. company has disclosed a higher number of cyber incidents compared to Root Literary company.

In the current year, Caribe Media, Inc. company and Root Literary company have not reported any cyber incidents.

Neither Caribe Media, Inc. company nor Root Literary company has reported experiencing a ransomware attack publicly.

Neither Caribe Media, Inc. company nor Root Literary company has reported experiencing a data breach publicly.

Neither Caribe Media, Inc. company nor Root Literary company has reported experiencing targeted cyberattacks publicly.

Neither Root Literary company nor Caribe Media, Inc. company has reported experiencing or disclosing vulnerabilities publicly.

Neither Root Literary nor Caribe Media, Inc. holds any compliance certifications.

Neither company holds any compliance certifications.

Neither Root Literary company nor Caribe Media, Inc. company has publicly disclosed detailed information about the number of their subsidiaries.

Caribe Media, Inc. company employs more people globally than Root Literary company, reflecting its scale as a Book and Periodical Publishing.

Neither Root Literary nor Caribe Media, Inc. holds SOC 2 Type 1 certification.

Neither Root Literary nor Caribe Media, Inc. holds SOC 2 Type 2 certification.

Neither Root Literary nor Caribe Media, Inc. holds ISO 27001 certification.

Neither Root Literary nor Caribe Media, Inc. holds PCI DSS certification.

Neither Root Literary nor Caribe Media, Inc. holds HIPAA certification.

Neither Root Literary nor Caribe Media, 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