Comparison Overview

Heyday

VS

Payson Roundup

Heyday

PO Box 9145, Berkeley, CA, undefined, US
Last Update: 2025-11-26
View Profile
Between 750 and 799
http://www.heydaybooks.com/

Heyday is an independent, nonprofit publisher founded in 1974 in Berkeley, California. We are a diverse community of writers and readers, activists and thinkers. Heyday promotes civic engagement and social justice, celebrates nature’s beauty, supports California Indian cultural renewal, and explores the state’s rich history, culture, and influence. Heyday works to realize the California dream of equity and enfranchisement.

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

Payson Roundup

708 N. Beeline Highway, Payson, 85541, US
Last Update: 2025-11-21
Between 750 and 799
http://www.paysonroundup.com

The Payson Roundup is a leader in both print and digital media. Located in the heart of Arizona in Rim Country, The Payson Roundup newspaper publishes twice weekly on Tuesday and Friday, the Rim Review, publishes Wednesday. In addition, a variety of special sections and two annual glossy magazines, The Rim Country Relocation Guide and The Rim Country Visitors Guide. In addition to the Payson Roundup's print products, our flagship website www.paysonroundup.com attracts an average of 245,000 pageviews per month and is the premier digital business advertising platform in Rim Country. Awarded Best Newspaper of the Year for 12 consecutive years by the Arizona Newspapers Association, the Payson Roundup's employees are also recipients of many individual awards across disciplines, journalism, design, and advertising. The Payson Roundup is part of a group of newspapers owned by WorldWest Limited Liability Company. Offices of WorldWest are located at 609 New Hampshire, Lawrence, Kan. 66044. The Payson Roundup is the central source of news, business consulting, advertising and digital media in Rim Country, and is a respected and trusted partner in the community.

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

Compliance Badges Comparison

Security & Compliance Standards Overview

https://images.rankiteo.com/companyimages/heydaybooks.jpeg
Heyday
—
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/payson-roundup.jpeg
Payson Roundup
—
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
Heyday
100%
Compliance Rate
0/4 Standards Verified
Payson Roundup
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 Heyday in 2025.

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

No incidents recorded for Payson Roundup in 2025.

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

Heyday cyber incidents detection timeline including parent company and subsidiaries

Incident History — Payson Roundup (X = Date, Y = Severity)

Payson Roundup cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/heydaybooks.jpeg
Heyday
Incidents

No Incident

https://images.rankiteo.com/companyimages/payson-roundup.jpeg
Payson Roundup
Incidents

No Incident

FAQ

Payson Roundup company demonstrates a stronger AI Cybersecurity Score compared to Heyday company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Historically, Payson Roundup company has disclosed a higher number of cyber incidents compared to Heyday company.

In the current year, Payson Roundup company and Heyday company have not reported any cyber incidents.

Neither Payson Roundup company nor Heyday company has reported experiencing a ransomware attack publicly.

Neither Payson Roundup company nor Heyday company has reported experiencing a data breach publicly.

Neither Payson Roundup company nor Heyday company has reported experiencing targeted cyberattacks publicly.

Neither Heyday company nor Payson Roundup company has reported experiencing or disclosing vulnerabilities publicly.

Neither Heyday nor Payson Roundup holds any compliance certifications.

Neither company holds any compliance certifications.

Payson Roundup company has more subsidiaries worldwide compared to Heyday company.

Heyday company employs more people globally than Payson Roundup company, reflecting its scale as a Book and Periodical Publishing.

Neither Heyday nor Payson Roundup holds SOC 2 Type 1 certification.

Neither Heyday nor Payson Roundup holds SOC 2 Type 2 certification.

Neither Heyday nor Payson Roundup holds ISO 27001 certification.

Neither Heyday nor Payson Roundup holds PCI DSS certification.

Neither Heyday nor Payson Roundup holds HIPAA certification.

Neither Heyday nor Payson Roundup 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