Comparison Overview

Village Voice

VS

Brilliance Publishing

Village Voice

80 Maiden Lane, New York, 10038, US
Last Update: 2025-11-21
Between 750 and 799

Founded in 1955 by a small group led by Norman Mailer, the Village Voice is the nation's original alternative newsweekly. The winner of three Pulitzers, the paper built a reputation for itself as an aggressive interrogator of the powers that be as well as a reliable resource for finding and promoting cutting-edge arts and culture. Over the years it has been home to a wide range of writers and artists, including literary luminaries e.e. cummings, Katherine Anne Porter, Ezra Pound, and James Baldwin, photographer Sylvia Plachy, cartoonist Lynda Barry, investigative journalists Wayne Barrett and Tom Robbins, “Dean of American Rock Critics” Robert Christgau, and film authority J. Hoberman, among many others.

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

Brilliance Publishing

Last Update: 2025-11-25

We fill the world with stories. We connect authors with fans. We dare to dream, and push to inspire. As a subsidiary of Amazon Publishing, we’re able to give our storytellers incredible reach. Yes, we’re numbers people. But we’re also people-people. We go above and beyond to make our authors happy and add meaning to the lives of book lovers near and far. Because every story needs an audience. And every audience needs a story. Come work with us.

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

Compliance Badges Comparison

Security & Compliance Standards Overview

https://images.rankiteo.com/companyimages/village-voice-media.jpeg
Village Voice
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/brilliance-publishing.jpeg
Brilliance 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
Village Voice
100%
Compliance Rate
0/4 Standards Verified
Brilliance 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 Village Voice in 2025.

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

No incidents recorded for Brilliance Publishing in 2025.

Incident History — Village Voice (X = Date, Y = Severity)

Village Voice cyber incidents detection timeline including parent company and subsidiaries

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

Brilliance Publishing cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/village-voice-media.jpeg
Village Voice
Incidents

No Incident

https://images.rankiteo.com/companyimages/brilliance-publishing.jpeg
Brilliance Publishing
Incidents

Date Detected: 10/2025
Type:Cyber Attack
Blog: Blog

Date Detected: 9/2025
Type:Cyber Attack
Attack Vector: Exposed Docker API, Misconfigured AWS EC2 Instances, Python Docker SDK
Motivation: Financial Gain, Disruption, Cybercrime-as-a-Service
Blog: Blog

Date Detected: 7/2025
Type:Cyber Attack
Attack Vector: Backend Update Bug
Blog: Blog

FAQ

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

Brilliance Publishing company has historically faced a number of disclosed cyber incidents, whereas Village Voice company has not reported any.

In the current year, Brilliance Publishing company has reported more cyber incidents than Village Voice company.

Brilliance Publishing company has confirmed experiencing a ransomware attack, while Village Voice company has not reported such incidents publicly.

Brilliance Publishing company has disclosed at least one data breach, while Village Voice company has not reported such incidents publicly.

Brilliance Publishing company has reported targeted cyberattacks, while Village Voice company has not reported such incidents publicly.

Brilliance Publishing company has disclosed at least one vulnerability, while Village Voice company has not reported such incidents publicly.

Neither Village Voice nor Brilliance Publishing holds any compliance certifications.

Neither company holds any compliance certifications.

Brilliance Publishing company has more subsidiaries worldwide compared to Village Voice company.

Village Voice company employs more people globally than Brilliance Publishing company, reflecting its scale as a Book and Periodical Publishing.

Neither Village Voice nor Brilliance Publishing holds SOC 2 Type 1 certification.

Neither Village Voice nor Brilliance Publishing holds SOC 2 Type 2 certification.

Neither Village Voice nor Brilliance Publishing holds ISO 27001 certification.

Neither Village Voice nor Brilliance Publishing holds PCI DSS certification.

Neither Village Voice nor Brilliance Publishing holds HIPAA certification.

Neither Village Voice nor Brilliance 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.