Comparison Overview

Idaho Press

VS

Metro

Idaho Press

1618 N MIDLAND BLVD, Nampa, ID, 83651, US
Last Update: 2025-11-28
Between 750 and 799

The roots of the Idaho Press go back to December 1883 in Caldwell - with the first paper coming off the press just months after Caldwell was established as a city. Nampa city was established in 1885. The Idaho Press is the second largest daily newspaper in the state of Idaho with a weekly audience reach of over 110,000 people. The Idaho Press is owned by Adams Publishing Group, a privately held, independent family-owned company. The Idaho Press also publishes the Emmett Messenger-Index, the Meridian Press, the Kuna Melba News and Boise Weekly.

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

Metro

Northcliffe House, London, undefined, W8 5TT, GB
Last Update: 2025-11-26
Between 750 and 799

Metro is the UK’s leading urban media brand, helping its consumers get more from city life through its print, mobile and event based platforms. Launched in 1999 as a concise read for Urbanites on the commute, it serves up bite-sized news, sport, entertainment and local information that trigger conversations. Distributing 1.3m copies across 50 UK cities and read by 3.3m readers, Metro appeals to a young, affluent and aspirational audience. Metro also offers an exceptional suite of digital editions; its iPhone iOS edition, Kindle edition and award winning Tablet edition.

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

Compliance Badges Comparison

Security & Compliance Standards Overview

https://images.rankiteo.com/companyimages/idaho-press-tribune.jpeg
Idaho Press
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/metro--.jpeg
Metro
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
Idaho Press
100%
Compliance Rate
0/4 Standards Verified
Metro
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 Idaho Press in 2025.

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

No incidents recorded for Metro in 2025.

Incident History — Idaho Press (X = Date, Y = Severity)

Idaho Press cyber incidents detection timeline including parent company and subsidiaries

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

Metro cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/idaho-press-tribune.jpeg
Idaho Press
Incidents

No Incident

https://images.rankiteo.com/companyimages/metro--.jpeg
Metro
Incidents

No Incident

FAQ

Metro company demonstrates a stronger AI Cybersecurity Score compared to Idaho Press company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Historically, Metro company has disclosed a higher number of cyber incidents compared to Idaho Press company.

In the current year, Metro company and Idaho Press company have not reported any cyber incidents.

Neither Metro company nor Idaho Press company has reported experiencing a ransomware attack publicly.

Neither Metro company nor Idaho Press company has reported experiencing a data breach publicly.

Neither Metro company nor Idaho Press company has reported experiencing targeted cyberattacks publicly.

Neither Idaho Press company nor Metro company has reported experiencing or disclosing vulnerabilities publicly.

Neither Idaho Press nor Metro holds any compliance certifications.

Neither company holds any compliance certifications.

Metro company has more subsidiaries worldwide compared to Idaho Press company.

Metro company employs more people globally than Idaho Press company, reflecting its scale as a Book and Periodical Publishing.

Neither Idaho Press nor Metro holds SOC 2 Type 1 certification.

Neither Idaho Press nor Metro holds SOC 2 Type 2 certification.

Neither Idaho Press nor Metro holds ISO 27001 certification.

Neither Idaho Press nor Metro holds PCI DSS certification.

Neither Idaho Press nor Metro holds HIPAA certification.

Neither Idaho Press nor Metro 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.