Comparison Overview

Seattle's Child

VS

Bologna Children’s Book Fair

Seattle's Child

undefined, undefined, undefined, undefined, US
Last Update: 2025-11-26
Between 750 and 799

Seattle's Child was the first local parenting publication in the country when it launched in 1979 and continues to be the industry leader. With our monthly magazine, special publications (Summer, Baby, Explore, School, Family Page), mobile responsive website and enewsletters, Seattle's Child is the guide to all topics relevant to parents and people who work with kids. We're interested in how parents make house a home, how families create community and what parents are talking about. We know there is no one way to be a good parent and seek to reflect real Puget Sound families and their broad range of parenting experiences.

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

Bologna Children’s Book Fair

Piazza Costituzione, 6, Bologna, 40128, IT
Last Update: 2025-11-21

The Bologna Children’s Book Fair is the most important international event dedicated to the children’s publishing and multimedia industry. In Bologna authors, illustrators, literary agents, licensors and licensees, packagers, distributors, printers, booksellers, and librarians meet to sell and buy copyright, find the very best of children’s publishing and multimedia production, generate and gather new contacts while strengthening professional relationships, discover new business opportunities, discuss and debate the latest sector trends.

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

Compliance Badges Comparison

Security & Compliance Standards Overview

https://images.rankiteo.com/companyimages/seattle's-child.jpeg
Seattle's Child
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/bolognachildrensbookfair.jpeg
Bologna Children’s Book Fair
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
Seattle's Child
100%
Compliance Rate
0/4 Standards Verified
Bologna Children’s Book Fair
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 Seattle's Child in 2025.

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

No incidents recorded for Bologna Children’s Book Fair in 2025.

Incident History — Seattle's Child (X = Date, Y = Severity)

Seattle's Child cyber incidents detection timeline including parent company and subsidiaries

Incident History — Bologna Children’s Book Fair (X = Date, Y = Severity)

Bologna Children’s Book Fair cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/seattle's-child.jpeg
Seattle's Child
Incidents

No Incident

https://images.rankiteo.com/companyimages/bolognachildrensbookfair.jpeg
Bologna Children’s Book Fair
Incidents

No Incident

FAQ

Seattle's Child company demonstrates a stronger AI Cybersecurity Score compared to Bologna Children’s Book Fair company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Historically, Bologna Children’s Book Fair company has disclosed a higher number of cyber incidents compared to Seattle's Child company.

In the current year, Bologna Children’s Book Fair company and Seattle's Child company have not reported any cyber incidents.

Neither Bologna Children’s Book Fair company nor Seattle's Child company has reported experiencing a ransomware attack publicly.

Neither Bologna Children’s Book Fair company nor Seattle's Child company has reported experiencing a data breach publicly.

Neither Bologna Children’s Book Fair company nor Seattle's Child company has reported experiencing targeted cyberattacks publicly.

Neither Seattle's Child company nor Bologna Children’s Book Fair company has reported experiencing or disclosing vulnerabilities publicly.

Neither Seattle's Child nor Bologna Children’s Book Fair holds any compliance certifications.

Neither company holds any compliance certifications.

Bologna Children’s Book Fair company has more subsidiaries worldwide compared to Seattle's Child company.

Seattle's Child company employs more people globally than Bologna Children’s Book Fair company, reflecting its scale as a Book and Periodical Publishing.

Neither Seattle's Child nor Bologna Children’s Book Fair holds SOC 2 Type 1 certification.

Neither Seattle's Child nor Bologna Children’s Book Fair holds SOC 2 Type 2 certification.

Neither Seattle's Child nor Bologna Children’s Book Fair holds ISO 27001 certification.

Neither Seattle's Child nor Bologna Children’s Book Fair holds PCI DSS certification.

Neither Seattle's Child nor Bologna Children’s Book Fair holds HIPAA certification.

Neither Seattle's Child nor Bologna Children’s Book Fair 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.