Comparison Overview

PBRack Clothing

VS

Hollis

PBRack Clothing

None
Last Update: 2026-04-04
View Profile
Between 750 and 799
http://pbrack.com

Lorem ipsum dolor sit amet, consectetur adipiscing elit. Pellentesque ut nunc imperdiet, iaculis risus at, vulputate orci. Nam nec mi non lacus mollis ultricies. Quisque eget augue sed orci commodo egestas quis vel velit. Class aptent taciti sociosqu ad litora torquent per conubia nostra, per inceptos himenaeos. Donec enim purus, finibus ut augue eleifend, commodo pharetra nunc. Nulla sit amet felis aliquet, dapibus metus ac, aliquet odio. Nam laoreet metus consectetur ex suscipit, eu convallis dolor commodo. Vestibulum condimentum nunc eu dolor sodales, eu lobortis erat cursus. Nam gravida accumsan orci, nec vestibulum ex congue non. Cras ut tellus molestie, iaculis augue vitae, vehicula ante. In non dui sit amet quam bibendum eleifend. Duis viverra enim risus. Curabitur pellentesque risus egestas erat rhoncus cursus. Ut nec dui id odio viverra tristique id eget nibh. Donec finibus malesuada vehicula. Maecenas lacinia ex quam, sit amet laoreet purus vehicula ac.

NAICS: None
NAICS Definition: Others
Employees: 3
Subsidiaries: 0
12-month incidents
0
Known data breaches
0
Attack type number
0
View Profile

Hollis

None
Last Update: 2026-04-01
Between 750 and 799
http://www.Hollis.com

Hollis represents the technical arm of the American Underwater Products family of companies, and brings innovation and engineering experience to the dive industry by designing the highest quality and most innovative equipment available. Based in San Leandro California, we manufacture and distribute to over 400 dealers worldwide in over 50 different countries.

NAICS: None
NAICS Definition: Others
Employees: 25
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/pbrack-clothing.jpeg
PBRack Clothing
—
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/hollis-gear.jpeg
Hollis
—
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
PBRack Clothing
100%
Compliance Rate
0/4 Standards Verified
Hollis
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Sporting Goods Industry Average (This Year)

No incidents recorded for PBRack Clothing in 2026.

Incidents vs Sporting Goods Industry Average (This Year)

No incidents recorded for Hollis in 2026.

Incident History — PBRack Clothing (X = Date, Y = Severity)

PBRack Clothing cyber incidents detection timeline including parent company and subsidiaries

Incident History — Hollis (X = Date, Y = Severity)

Hollis cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/pbrack-clothing.jpeg
PBRack Clothing
Incidents

No Incident

https://images.rankiteo.com/companyimages/hollis-gear.jpeg
Hollis
Incidents

No Incident

FAQ

PBRack Clothing company demonstrates a stronger AI Cybersecurity Score compared to Hollis company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Historically, Hollis company has disclosed a higher number of cyber incidents compared to PBRack Clothing company.

In the current year, Hollis company and PBRack Clothing company have not reported any cyber incidents.

Neither Hollis company nor PBRack Clothing company has reported experiencing a ransomware attack publicly.

Neither Hollis company nor PBRack Clothing company has reported experiencing a data breach publicly.

Neither Hollis company nor PBRack Clothing company has reported experiencing targeted cyberattacks publicly.

Neither PBRack Clothing company nor Hollis company has reported experiencing or disclosing vulnerabilities publicly.

Neither PBRack Clothing nor Hollis holds any compliance certifications.

Neither company holds any compliance certifications.

Neither PBRack Clothing company nor Hollis company has publicly disclosed detailed information about the number of their subsidiaries.

Hollis company employs more people globally than PBRack Clothing company, reflecting its scale as a Sporting Goods.

Neither PBRack Clothing nor Hollis holds SOC 2 Type 1 certification.

Neither PBRack Clothing nor Hollis holds SOC 2 Type 2 certification.

Neither PBRack Clothing nor Hollis holds ISO 27001 certification.

Neither PBRack Clothing nor Hollis holds PCI DSS certification.

Neither PBRack Clothing nor Hollis holds HIPAA certification.

Neither PBRack Clothing nor Hollis holds GDPR certification.

Latest Global CVEs (Not Company-Specific)

Description

nimiq/core-rs-albatross is a Rust implementation of the Nimiq Proof-of-Stake protocol based on the Albatross consensus algorithm. Prior to version 1.3.0, two peer-facing consensus request handlers assume that the history index is always available and call blockchain.history_store.history_index().unwrap() directly. That assumption is false by construction. HistoryStoreProxy::history_index() explicitly returns None for the valid HistoryStoreProxy::WithoutIndex state. when a full node is syncing or otherwise running without the history index, a remote peer can send RequestTransactionsProof or RequestTransactionReceiptsByAddress and trigger an Option::unwrap() panic on the request path. This issue has been patched in version 1.3.0.

Published
Date
2026-04-03
Updated
Date
2026-04-03
Risk Information
cvss3
Base: 5.3
Severity: LOW
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
References
Description

PraisonAI is a multi-agent teams system. Prior to version 1.5.95, FileTools.download_file() in praisonaiagents validates the destination path but performs no validation on the url parameter, passing it directly to httpx.stream() with follow_redirects=True. An attacker who controls the URL can reach any host accessible from the server including cloud metadata services and internal network services. This issue has been patched in version 1.5.95.

Published
Date
2026-04-03
Updated
Date
2026-04-03
Risk Information
cvss3
Base: 8.6
Severity: LOW
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N
References
Description

PraisonAI is a multi-agent teams system. Prior to version 4.5.97, OAuthManager.validate_token() returns True for any token not found in its internal store, which is empty by default. Any HTTP request to the MCP server with an arbitrary Bearer token is treated as authenticated, granting full access to all registered tools and agent capabilities. This issue has been patched in version 4.5.97.

Published
Date
2026-04-03
Updated
Date
2026-04-03
Risk Information
cvss3
Base: 9.1
Severity: LOW
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
References
Description

PraisonAI is a multi-agent teams system. Prior to version 4.5.97, the PraisonAI Gateway server accepts WebSocket connections at /ws and serves agent topology at /info with no authentication. Any network client can connect, enumerate registered agents, and send arbitrary messages to agents and their tool sets. This issue has been patched in version 4.5.97.

Published
Date
2026-04-03
Updated
Date
2026-04-03
Risk Information
cvss3
Base: 9.1
Severity: LOW
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
References
Description

PraisonAI is a multi-agent teams system. Prior to version 4.5.90, MCPToolIndex.search_tools() compiles a caller-supplied string directly as a Python regular expression with no validation, sanitization, or timeout. A crafted regex causes catastrophic backtracking in the re engine, blocking the Python thread for hundreds of seconds and causing a complete service outage. This issue has been patched in version 4.5.90.

Published
Date
2026-04-03
Updated
Date
2026-04-03
Risk Information
cvss3
Base: 6.5
Severity: LOW
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
References