Comparison Overview

the419

VS

Jewellery World

the419

201 W. Market St., Lima, Ohio, 45801, US
Last Update: 2025-11-25
Between 750 and 799

the419 is a community magazine covering Lima and Allen County, Ohio. We publish weekly, and update our website daily. the419 is unique in that we offer a wide range of entertaining features not found in other local media. We share the best of our community, from our evolving downtown to must-see shows and exhibitions, to city development, to the entrepreneurs and leaders shaping the future of our community. We are locally owned, locally operated, community focused. the419.

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

Jewellery World

41 Bridge Road, Glebe, 2037, AU
Last Update: 2025-11-21

Jewellery World has been publishing Australia’s professional industry magazine since 1981. Published six times a year Jewellery World comprises five standard editions plus the indispensable Jewellers Guide annual directory. With a focus on trade news and information, Jewellery World is designed for retail jewellers, manufacturers, wholesalers and sales people. The annual Jewellers Guide directory is the jewellery industry’s source book. Updated each year, the Jewellers Guide lists and cross-references hundreds of suppliers, wholesalers and manufacturers as well as brand names and product categories. In summary the Jewellers Guide is the industry’s prize reference tool for sourcing products, services and supplies. Major manufacturers and distributors find participation in the magazine strengthens trade relations and sales while retailers see Jewellery World as a factual and respected independent source of news and information. Not surprisingly then Jewellery World has the highest audited circulation (CAB audited) of any Australian jewellery industry publication. Complementing its print counterpart, Jewelleryworld.net.au is designed for the personnel of retail jewellery stores, manufacturers and wholesalers with a focus on trade news and information.

NAICS: 511
NAICS Definition: Publishing Industries (except Internet)
Employees: 50
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/the419.jpeg
the419
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/jewellery-world.jpeg
Jewellery World
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
the419
100%
Compliance Rate
0/4 Standards Verified
Jewellery World
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 the419 in 2025.

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

No incidents recorded for Jewellery World in 2025.

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

the419 cyber incidents detection timeline including parent company and subsidiaries

Incident History — Jewellery World (X = Date, Y = Severity)

Jewellery World cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/the419.jpeg
the419
Incidents

No Incident

https://images.rankiteo.com/companyimages/jewellery-world.jpeg
Jewellery World
Incidents

No Incident

FAQ

Both the419 company and Jewellery World company demonstrate a comparable AI Cybersecurity Score, with strong governance and monitoring frameworks in place.

Historically, Jewellery World company has disclosed a higher number of cyber incidents compared to the419 company.

In the current year, Jewellery World company and the419 company have not reported any cyber incidents.

Neither Jewellery World company nor the419 company has reported experiencing a ransomware attack publicly.

Neither Jewellery World company nor the419 company has reported experiencing a data breach publicly.

Neither Jewellery World company nor the419 company has reported experiencing targeted cyberattacks publicly.

Neither the419 company nor Jewellery World company has reported experiencing or disclosing vulnerabilities publicly.

Neither the419 nor Jewellery World holds any compliance certifications.

Neither company holds any compliance certifications.

Neither the419 company nor Jewellery World company has publicly disclosed detailed information about the number of their subsidiaries.

Jewellery World company employs more people globally than the419 company, reflecting its scale as a Book and Periodical Publishing.

Neither the419 nor Jewellery World holds SOC 2 Type 1 certification.

Neither the419 nor Jewellery World holds SOC 2 Type 2 certification.

Neither the419 nor Jewellery World holds ISO 27001 certification.

Neither the419 nor Jewellery World holds PCI DSS certification.

Neither the419 nor Jewellery World holds HIPAA certification.

Neither the419 nor Jewellery World 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.