Comparison Overview

Editoriale Giornalidea

VS

Australian Scholarly Publishing

Editoriale Giornalidea

Piazza della Repubblica 19, Milano, 20124, IT
Last Update: 2025-11-28
Between 750 and 799

Editoriale Giornalidea Srl è una casa editrice specializzata nella comunicazione professionale rivolta al settore farmaceutico. Nata nel 1983 (prima con il marchio Pielle e poi Giornalidea) come studio di consulenze editoriali, si è man mano sviluppata, pur mantenendo struttura, dimensioni e strategie adatte a garantire lavori accurati e di alta specializzazione. Grazie anche ai numerosi giornali editati, sia propri sia per conto terzi, ricopre un ruolo di leadership per fatturato e per importanza nel settore della comunicazione professionale rivolta alla farmacia. La sua attività editoriale, inoltre, viene svolta da redattori altamente specializzati, che garantiscono un lavoro accurato e soprattutto altamente focalizzato. Si tratta di giornalisti professionisti che, operando da anni nel settore dell’informazione sanitaria e farmaceutica in particolare, hanno maturato una profonda conoscenza della farmacia, del farmaco e delle relative problematiche.

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

Australian Scholarly Publishing

7 Little Lothian St N, North Melbourne, Victoria, 3051, AU
Last Update: 2025-11-26
Between 750 and 799

Australian Scholarly Publishing – ASP – has been publishing scholarly and general books for over twenty years. ASP occupies a unique position in the Australian publishing industry as an independent scholarly press with a substantial and increasing annual release of over 70 titles. ASP has since its inception in 1991 published works by scholars from all the major tertiary academic institutions in Australia, and done so widely across the academic disciplines: any field in the Humanities & Social Sciences, and also Law and Environmental Science.

NAICS: 511
NAICS Definition:
Employees: 9
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/editoriale-giornalidea.jpeg
Editoriale Giornalidea
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/australian-scholarly-publishing.jpeg
Australian Scholarly 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
Editoriale Giornalidea
100%
Compliance Rate
0/4 Standards Verified
Australian Scholarly 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 Editoriale Giornalidea in 2025.

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

No incidents recorded for Australian Scholarly Publishing in 2025.

Incident History — Editoriale Giornalidea (X = Date, Y = Severity)

Editoriale Giornalidea cyber incidents detection timeline including parent company and subsidiaries

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

Australian Scholarly Publishing cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/editoriale-giornalidea.jpeg
Editoriale Giornalidea
Incidents

No Incident

https://images.rankiteo.com/companyimages/australian-scholarly-publishing.jpeg
Australian Scholarly Publishing
Incidents

No Incident

FAQ

Australian Scholarly Publishing company demonstrates a stronger AI Cybersecurity Score compared to Editoriale Giornalidea company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Historically, Australian Scholarly Publishing company has disclosed a higher number of cyber incidents compared to Editoriale Giornalidea company.

In the current year, Australian Scholarly Publishing company and Editoriale Giornalidea company have not reported any cyber incidents.

Neither Australian Scholarly Publishing company nor Editoriale Giornalidea company has reported experiencing a ransomware attack publicly.

Neither Australian Scholarly Publishing company nor Editoriale Giornalidea company has reported experiencing a data breach publicly.

Neither Australian Scholarly Publishing company nor Editoriale Giornalidea company has reported experiencing targeted cyberattacks publicly.

Neither Editoriale Giornalidea company nor Australian Scholarly Publishing company has reported experiencing or disclosing vulnerabilities publicly.

Neither Editoriale Giornalidea nor Australian Scholarly Publishing holds any compliance certifications.

Neither company holds any compliance certifications.

Editoriale Giornalidea company has more subsidiaries worldwide compared to Australian Scholarly Publishing company.

Editoriale Giornalidea company employs more people globally than Australian Scholarly Publishing company, reflecting its scale as a Book and Periodical Publishing.

Neither Editoriale Giornalidea nor Australian Scholarly Publishing holds SOC 2 Type 1 certification.

Neither Editoriale Giornalidea nor Australian Scholarly Publishing holds SOC 2 Type 2 certification.

Neither Editoriale Giornalidea nor Australian Scholarly Publishing holds ISO 27001 certification.

Neither Editoriale Giornalidea nor Australian Scholarly Publishing holds PCI DSS certification.

Neither Editoriale Giornalidea nor Australian Scholarly Publishing holds HIPAA certification.

Neither Editoriale Giornalidea nor Australian Scholarly 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.