Comparison Overview

Brookes Publishing

VS

Seattle University Law Review

Brookes Publishing

409 Washington Ave., Towson, Maryland, 21204, US
Last Update: 2025-11-26

Brookes delivers innovative, evidence-based books, assessments, and training that help professionals make a real difference in the lives of children and families. Developed by top experts, our resources provide both essential knowledge and practical strategies for building the foundations of learning and supporting student success. We focus on developing products and services that can have the biggest impact on outcomes throughout a child’s life. As the publisher of ASQ and other tools, we are worldwide leaders in screening and assessment. We break new ground in child development, literacy and language, and inclusion—areas vital to getting children off to the best start as early as possible. We understand our customers’ goals and challenges and develop trusted, long-term, collaborative partnerships that promote success for all learners.

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

Seattle University Law Review

901 12th Ave, None, Seattle, Washington, US, 98122
Last Update: 2025-11-26

The Seattle University Law Review was originally published as the University of Puget Sound Law Review. Its inaugural issue was published in 1975, with the first Editor in Chief writing, "Striving to attain a quality of legal writing and analysis commensurate with the nascent tradition at this law school, the Editorial Board publishes this intramural edition. Hopefully this volume... represents a first and significant step toward a national law review that will serve the legal community..."​ The Law Review continues to maintain this dedication to legal scholarship. The Fall Issue of Volume 1 in 1977 marked the beginning of our publication in earnest as the University of Puget Sound Law Review. On August 19, 1994, the Law School was transferred to Seattle University under the stewardship of SU President Father William J. Sullivan, S.J. The Law School joined the Seattle University main campus for Fall Term, 1999, and the Seattle University Law Review continues to advance legal education, writing, and scholarship. The Seattle University Law Review provides valuable educational experiences to its members. The journal’s writing and editing assignments give student members opportunities to improve their writing skills and research techniques. Law Review work also strengthens a student’s ability to analyze problems in unfamiliar areas of the law. Finally, the self-discipline and analytical proficiency needed to succeed while on the Law Review proves invaluable to students after leaving law school.

NAICS: 511
NAICS Definition: Publishing Industries (except Internet)
Employees: 28
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/paul-h.-brookes-publishing-co..jpeg
Brookes 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
https://images.rankiteo.com/companyimages/sulr.jpeg
Seattle University Law Review
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
Brookes Publishing
100%
Compliance Rate
0/4 Standards Verified
Seattle University Law Review
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 Brookes Publishing in 2025.

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

No incidents recorded for Seattle University Law Review in 2025.

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

Brookes Publishing cyber incidents detection timeline including parent company and subsidiaries

Incident History — Seattle University Law Review (X = Date, Y = Severity)

Seattle University Law Review cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/paul-h.-brookes-publishing-co..jpeg
Brookes Publishing
Incidents

No Incident

https://images.rankiteo.com/companyimages/sulr.jpeg
Seattle University Law Review
Incidents

No Incident

FAQ

Brookes Publishing company demonstrates a stronger AI Cybersecurity Score compared to Seattle University Law Review company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Historically, Seattle University Law Review company has disclosed a higher number of cyber incidents compared to Brookes Publishing company.

In the current year, Seattle University Law Review company and Brookes Publishing company have not reported any cyber incidents.

Neither Seattle University Law Review company nor Brookes Publishing company has reported experiencing a ransomware attack publicly.

Neither Seattle University Law Review company nor Brookes Publishing company has reported experiencing a data breach publicly.

Neither Seattle University Law Review company nor Brookes Publishing company has reported experiencing targeted cyberattacks publicly.

Neither Brookes Publishing company nor Seattle University Law Review company has reported experiencing or disclosing vulnerabilities publicly.

Neither Brookes Publishing nor Seattle University Law Review holds any compliance certifications.

Neither company holds any compliance certifications.

Neither Brookes Publishing company nor Seattle University Law Review company has publicly disclosed detailed information about the number of their subsidiaries.

Brookes Publishing company employs more people globally than Seattle University Law Review company, reflecting its scale as a Book and Periodical Publishing.

Neither Brookes Publishing nor Seattle University Law Review holds SOC 2 Type 1 certification.

Neither Brookes Publishing nor Seattle University Law Review holds SOC 2 Type 2 certification.

Neither Brookes Publishing nor Seattle University Law Review holds ISO 27001 certification.

Neither Brookes Publishing nor Seattle University Law Review holds PCI DSS certification.

Neither Brookes Publishing nor Seattle University Law Review holds HIPAA certification.

Neither Brookes Publishing nor Seattle University Law Review 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.