Comparison Overview

REGISTRY Tampa Bay

VS

Aschehoug

REGISTRY Tampa Bay

3051 Tech Dr, St. Petersburg, FL, 33716, US
Last Update: 2025-11-26
View Profile
Between 750 and 799
http://registrytampabay.com

Our multi-media platforms focus on three things: longevity, legitimacy, and luxury. We’re always looking to feature the best-of-the-best in Tampa Bay, and we’re dedicated to our community’s creative and captivating lifestyle. Through our commitment to our neighbors and the community in which we all live, our media platforms feature exciting interviews with local celebrities, the up-and-coming local eateries and fine dining, must-see homes in the Bay area, and more.

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

Aschehoug

Sehestedsgt. 3, Oslo, 0102, NO
Last Update: 2025-11-21
Between 750 and 799
http://www.aschehoug.no

Aschehoug forlag gir lesere, lærere og elever litterære opplevelser og kunnskap gjennom bøkene og læremidlene våre. Vi opplyser, utfordrer og underholder, enten du liker å lese, lytte eller utforske digitalt. Gode lese- og læreopplevelser er nøkkelen til å forstå verden og oss selv. Derfor satser vi på nye stemmer og formater, et litterært mangfold og et rikt læringsunivers. Vi skal være en garantist for ytringsfrihet, som er en forutsetning for demokratiet og at samfunnet stadig utvikler seg. Aschehoug ble grunnlagt i 1872. Forlaget Oktober og Universitetsforlaget inngår i forlagskonsernet, som også eier deler av Norli, De norske Bokklubbene og Lydbokforlaget. Mads Nygaard er konsernsjef og forlegger. Vi holder til på Sehesteds plass, sentralt i Oslo.

NAICS: 511
NAICS Definition: Publishing Industries (except Internet)
Employees: 300
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/dupont-registry-tampa-bay.jpeg
REGISTRY Tampa Bay
—
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/aschehoug.jpeg
Aschehoug
—
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
REGISTRY Tampa Bay
100%
Compliance Rate
0/4 Standards Verified
Aschehoug
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 REGISTRY Tampa Bay in 2025.

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

No incidents recorded for Aschehoug in 2025.

Incident History — REGISTRY Tampa Bay (X = Date, Y = Severity)

REGISTRY Tampa Bay cyber incidents detection timeline including parent company and subsidiaries

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

Aschehoug cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/dupont-registry-tampa-bay.jpeg
REGISTRY Tampa Bay
Incidents

No Incident

https://images.rankiteo.com/companyimages/aschehoug.jpeg
Aschehoug
Incidents

No Incident

FAQ

Aschehoug company demonstrates a stronger AI Cybersecurity Score compared to REGISTRY Tampa Bay company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Historically, Aschehoug company has disclosed a higher number of cyber incidents compared to REGISTRY Tampa Bay company.

In the current year, Aschehoug company and REGISTRY Tampa Bay company have not reported any cyber incidents.

Neither Aschehoug company nor REGISTRY Tampa Bay company has reported experiencing a ransomware attack publicly.

Neither Aschehoug company nor REGISTRY Tampa Bay company has reported experiencing a data breach publicly.

Neither Aschehoug company nor REGISTRY Tampa Bay company has reported experiencing targeted cyberattacks publicly.

Neither REGISTRY Tampa Bay company nor Aschehoug company has reported experiencing or disclosing vulnerabilities publicly.

Neither REGISTRY Tampa Bay nor Aschehoug holds any compliance certifications.

Neither company holds any compliance certifications.

Neither REGISTRY Tampa Bay company nor Aschehoug company has publicly disclosed detailed information about the number of their subsidiaries.

Aschehoug company employs more people globally than REGISTRY Tampa Bay company, reflecting its scale as a Book and Periodical Publishing.

Neither REGISTRY Tampa Bay nor Aschehoug holds SOC 2 Type 1 certification.

Neither REGISTRY Tampa Bay nor Aschehoug holds SOC 2 Type 2 certification.

Neither REGISTRY Tampa Bay nor Aschehoug holds ISO 27001 certification.

Neither REGISTRY Tampa Bay nor Aschehoug holds PCI DSS certification.

Neither REGISTRY Tampa Bay nor Aschehoug holds HIPAA certification.

Neither REGISTRY Tampa Bay nor Aschehoug 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