Comparison Overview

School Datebooks

VS

Vogue Business

School Datebooks

2880 Old US Hwy 231 S, Lafayette, IN, 47909, US
Last Update: 2025-11-26

School Datebooks is a private company, started in 1985 by Sharon Powers. Sitting at her kitchen table, Sharon created the Central Catholic “Knightline” datebook. Immediately understanding the potential national market for datebooks, Sharon began to sell datebooks to the surrounding schools. The Knightline, West Lafayette HS Docket, Harrison HS Barn Door, McCutcheon HS Maveranda, and Lafayette Jeff HS Broncho Board helped thousands of kids throughout the local community succeed. One of those kids, Tim Powers, came home to run and grow the family business in 1993. Many current employees are sure the idea for a datebook was due to Tim’s (now company President) inability to keep track of assignments. While that story has never been substantiated, we’re pretty sure it’s true. From 5 local schools in 1985 to more than 15,000 today, and with Sharon’s entrepreneurial spirit, School Datebooks continues to be an innovative, enthusiastic company looking to grow and share our unique corporate culture. With offices in Lafayette, Indiana and Bellingham, Washington, we strive to continue our long-standing work in education.

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

Vogue Business

London, WC2N, GB
Last Update: 2025-11-21
Between 750 and 799

Vogue Business is an online fashion industry publication launched in 2019. Headquartered at Condé Nast International in London, we offer a truly global perspective on the fashion industry, drawing on insights from Condé Nast’s network of journalists and business leaders in 29 markets to empower fashion professionals to make better business decisions.

NAICS: 511
NAICS Definition: Publishing Industries (except Internet)
Employees: 238
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/school-datebooks.jpeg
School Datebooks
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/voguebusiness.jpeg
Vogue Business
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
School Datebooks
100%
Compliance Rate
0/4 Standards Verified
Vogue Business
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 School Datebooks in 2025.

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

No incidents recorded for Vogue Business in 2025.

Incident History — School Datebooks (X = Date, Y = Severity)

School Datebooks cyber incidents detection timeline including parent company and subsidiaries

Incident History — Vogue Business (X = Date, Y = Severity)

Vogue Business cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/school-datebooks.jpeg
School Datebooks
Incidents

No Incident

https://images.rankiteo.com/companyimages/voguebusiness.jpeg
Vogue Business
Incidents

No Incident

FAQ

Vogue Business company demonstrates a stronger AI Cybersecurity Score compared to School Datebooks company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Historically, Vogue Business company has disclosed a higher number of cyber incidents compared to School Datebooks company.

In the current year, Vogue Business company and School Datebooks company have not reported any cyber incidents.

Neither Vogue Business company nor School Datebooks company has reported experiencing a ransomware attack publicly.

Neither Vogue Business company nor School Datebooks company has reported experiencing a data breach publicly.

Neither Vogue Business company nor School Datebooks company has reported experiencing targeted cyberattacks publicly.

Neither School Datebooks company nor Vogue Business company has reported experiencing or disclosing vulnerabilities publicly.

Neither School Datebooks nor Vogue Business holds any compliance certifications.

Neither company holds any compliance certifications.

Neither School Datebooks company nor Vogue Business company has publicly disclosed detailed information about the number of their subsidiaries.

Vogue Business company employs more people globally than School Datebooks company, reflecting its scale as a Book and Periodical Publishing.

Neither School Datebooks nor Vogue Business holds SOC 2 Type 1 certification.

Neither School Datebooks nor Vogue Business holds SOC 2 Type 2 certification.

Neither School Datebooks nor Vogue Business holds ISO 27001 certification.

Neither School Datebooks nor Vogue Business holds PCI DSS certification.

Neither School Datebooks nor Vogue Business holds HIPAA certification.

Neither School Datebooks nor Vogue Business 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.