Comparison Overview

Book in a Box

VS

Publishing Concepts, Inc.

Book in a Box

815 Brazos Street, Austin, TX, 78702, US
Last Update: 2025-11-26
View Profile
Between 750 and 799
https://bookinabox.com/

At Book In A Box, we’ve created a new process to turn your idea into a book. In short, we interview you in a systematic way that properly structures your ideas, and gets them out of you in words. Then we turn those words into a book—in your voice. All you need to do, as the author, is answer questions about what you already know. Everything else is handled by our team of experienced publishing professionals.

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

Publishing Concepts, Inc.

14109 Taylor Loop Rd, Little Rock, Arkansas, 72223, US
Last Update: 2025-11-26
Between 750 and 799
http://www.pcipublishing.com

Experience is the most powerful difference. Celebrating our 25th year in the custom magazine publishing business, Publishing Concepts, Inc. has developed award-winning corporate, association and board publications for well over 400 clients, of all types, nationwide. We’ve become the nation’s largest publisher of official State Boards of Nursing magazines as well as official State Academies of Family Physicians journals. Our Hospital Guides division is on the fast track to becoming an industry leader as well. Experience speaks volumes.

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

Compliance Badges Comparison

Security & Compliance Standards Overview

https://images.rankiteo.com/companyimages/book-in-a-box.jpeg
Book in a Box
—
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/pci-inc..jpeg
Publishing Concepts, Inc.
—
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
Book in a Box
100%
Compliance Rate
0/4 Standards Verified
Publishing Concepts, Inc.
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 Book in a Box in 2025.

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

No incidents recorded for Publishing Concepts, Inc. in 2025.

Incident History — Book in a Box (X = Date, Y = Severity)

Book in a Box cyber incidents detection timeline including parent company and subsidiaries

Incident History — Publishing Concepts, Inc. (X = Date, Y = Severity)

Publishing Concepts, Inc. cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/book-in-a-box.jpeg
Book in a Box
Incidents

No Incident

https://images.rankiteo.com/companyimages/pci-inc..jpeg
Publishing Concepts, Inc.
Incidents

No Incident

FAQ

Publishing Concepts, Inc. company demonstrates a stronger AI Cybersecurity Score compared to Book in a Box company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Historically, Publishing Concepts, Inc. company has disclosed a higher number of cyber incidents compared to Book in a Box company.

In the current year, Publishing Concepts, Inc. company and Book in a Box company have not reported any cyber incidents.

Neither Publishing Concepts, Inc. company nor Book in a Box company has reported experiencing a ransomware attack publicly.

Neither Publishing Concepts, Inc. company nor Book in a Box company has reported experiencing a data breach publicly.

Neither Publishing Concepts, Inc. company nor Book in a Box company has reported experiencing targeted cyberattacks publicly.

Neither Book in a Box company nor Publishing Concepts, Inc. company has reported experiencing or disclosing vulnerabilities publicly.

Neither Book in a Box nor Publishing Concepts, Inc. holds any compliance certifications.

Neither company holds any compliance certifications.

Publishing Concepts, Inc. company has more subsidiaries worldwide compared to Book in a Box company.

Book in a Box company employs more people globally than Publishing Concepts, Inc. company, reflecting its scale as a Book and Periodical Publishing.

Neither Book in a Box nor Publishing Concepts, Inc. holds SOC 2 Type 1 certification.

Neither Book in a Box nor Publishing Concepts, Inc. holds SOC 2 Type 2 certification.

Neither Book in a Box nor Publishing Concepts, Inc. holds ISO 27001 certification.

Neither Book in a Box nor Publishing Concepts, Inc. holds PCI DSS certification.

Neither Book in a Box nor Publishing Concepts, Inc. holds HIPAA certification.

Neither Book in a Box nor Publishing Concepts, Inc. 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