Comparison Overview

PacificBasin Communications

VS

HMSI Publishing LLC

PacificBasin Communications

1088 Bishop St, Honolulu, 96813, US
Last Update: 2025-11-21

Communications is the cornerstone of the aio family of companies. As a leader in Island media, we deliver unsurpassed print and online products that inform and inspire, educate and entertain. With a reputation for editorial excellence and creative marketing, aio media encompasses Hawaii's largest magazine group, best-selling books, quality printing services and a variety of custom publishing opportunities. Our Ohana of Publications include: Hawaii Business Hawaii Magazine Hawaii Buyer's Guide Hawaii Home + Remodeling Honolulu Magazine MANA Magazine PacificBasin Communications is apart of the aio Ohana of companies. http://www.aiohawaii.com/

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

HMSI Publishing LLC

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

"Connecting authors to Amazon!". As a result of 25 years experience in publishing and the launch of "The Twitter Workbook", we formed HMSI Publishing LLC in July 2009. The goal is to enable authors to publish books and make a profit! In Nov 2009, we have nine authors signed up, and five books on Amazon. Eight more at various stages of production, employing 23 contractors in four continents. If you are interested in having your work published, please contact us.

NAICS: 511
NAICS Definition:
Employees: 21
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/pacificbasin-communications.jpeg
PacificBasin Communications
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/hmsi-publishing-llc.jpeg
HMSI Publishing LLC
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
PacificBasin Communications
100%
Compliance Rate
0/4 Standards Verified
HMSI Publishing LLC
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 PacificBasin Communications in 2025.

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

No incidents recorded for HMSI Publishing LLC in 2025.

Incident History — PacificBasin Communications (X = Date, Y = Severity)

PacificBasin Communications cyber incidents detection timeline including parent company and subsidiaries

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

HMSI Publishing LLC cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/pacificbasin-communications.jpeg
PacificBasin Communications
Incidents

No Incident

https://images.rankiteo.com/companyimages/hmsi-publishing-llc.jpeg
HMSI Publishing LLC
Incidents

No Incident

FAQ

HMSI Publishing LLC company demonstrates a stronger AI Cybersecurity Score compared to PacificBasin Communications company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Historically, HMSI Publishing LLC company has disclosed a higher number of cyber incidents compared to PacificBasin Communications company.

In the current year, HMSI Publishing LLC company and PacificBasin Communications company have not reported any cyber incidents.

Neither HMSI Publishing LLC company nor PacificBasin Communications company has reported experiencing a ransomware attack publicly.

Neither HMSI Publishing LLC company nor PacificBasin Communications company has reported experiencing a data breach publicly.

Neither HMSI Publishing LLC company nor PacificBasin Communications company has reported experiencing targeted cyberattacks publicly.

Neither PacificBasin Communications company nor HMSI Publishing LLC company has reported experiencing or disclosing vulnerabilities publicly.

Neither PacificBasin Communications nor HMSI Publishing LLC holds any compliance certifications.

Neither company holds any compliance certifications.

Neither PacificBasin Communications company nor HMSI Publishing LLC company has publicly disclosed detailed information about the number of their subsidiaries.

HMSI Publishing LLC company employs more people globally than PacificBasin Communications company, reflecting its scale as a Book and Periodical Publishing.

Neither PacificBasin Communications nor HMSI Publishing LLC holds SOC 2 Type 1 certification.

Neither PacificBasin Communications nor HMSI Publishing LLC holds SOC 2 Type 2 certification.

Neither PacificBasin Communications nor HMSI Publishing LLC holds ISO 27001 certification.

Neither PacificBasin Communications nor HMSI Publishing LLC holds PCI DSS certification.

Neither PacificBasin Communications nor HMSI Publishing LLC holds HIPAA certification.

Neither PacificBasin Communications nor HMSI Publishing LLC 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.