Comparison Overview

Scuba.com

VS

3 Guys on Fire, Inc.

Scuba.com

50 W 17th St, New York, 10011, US
Last Update: 2026-04-04
View Profile
Between 750 and 799
http://scuba.com

Your one stop source for everything underwater. For over 30 years, Scuba.com is the number one destination for scuba diving and snorkeling gear from hundreds of brands. We offer a lowest price guarantee, plus free shipping on most items, and best-in-class customer service from diving experts. Shopping is available online at Scuba.com, via our phone team, or at our flagship dive shops in New York City and Southern California. Our NYC and Costa Mesa dive shops are PADI 5-Star Dive Centers, offering PADI certification classes for all experience levels and rental gear. Additionally, we are an authorized service center and fully equipped repair facility. Plus, join us on an upcoming curated dive trip!

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

3 Guys on Fire, Inc.

None
Last Update: 2026-03-29
Between 750 and 799
http://www.taildevil.com

3 Guys on Fire, Inc. launched a product called the Tail Devil at A.S.R. in January of 2004. Ever since the company has enjoyed phenomenal success in the skateboard industry, reaching into every market segment from in house skateboard brand development, private label OEM, licensing and wholesale distribution of other innovative products and ideas related to the extreme sports industry.

NAICS: None
NAICS Definition: Others
Employees: None
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/scuba.com.jpeg
Scuba.com
—
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/defaultcompany.jpeg
3 Guys on Fire, 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
Scuba.com
100%
Compliance Rate
0/4 Standards Verified
3 Guys on Fire, Inc.
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Sporting Goods Industry Average (This Year)

No incidents recorded for Scuba.com in 2026.

Incidents vs Sporting Goods Industry Average (This Year)

No incidents recorded for 3 Guys on Fire, Inc. in 2026.

Incident History — Scuba.com (X = Date, Y = Severity)

Scuba.com cyber incidents detection timeline including parent company and subsidiaries

Incident History — 3 Guys on Fire, Inc. (X = Date, Y = Severity)

3 Guys on Fire, Inc. cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/scuba.com.jpeg
Scuba.com
Incidents

No Incident

https://images.rankiteo.com/companyimages/defaultcompany.jpeg
3 Guys on Fire, Inc.
Incidents

No Incident

FAQ

3 Guys on Fire, Inc. company demonstrates a stronger AI Cybersecurity Score compared to Scuba.com company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Historically, 3 Guys on Fire, Inc. company has disclosed a higher number of cyber incidents compared to Scuba.com company.

In the current year, 3 Guys on Fire, Inc. company and Scuba.com company have not reported any cyber incidents.

Neither 3 Guys on Fire, Inc. company nor Scuba.com company has reported experiencing a ransomware attack publicly.

Neither 3 Guys on Fire, Inc. company nor Scuba.com company has reported experiencing a data breach publicly.

Neither 3 Guys on Fire, Inc. company nor Scuba.com company has reported experiencing targeted cyberattacks publicly.

Neither Scuba.com company nor 3 Guys on Fire, Inc. company has reported experiencing or disclosing vulnerabilities publicly.

Neither Scuba.com nor 3 Guys on Fire, Inc. holds any compliance certifications.

Neither company holds any compliance certifications.

Neither Scuba.com company nor 3 Guys on Fire, Inc. company has publicly disclosed detailed information about the number of their subsidiaries.

Scuba.com company employs more people globally than 3 Guys on Fire, Inc. company, reflecting its scale as a Sporting Goods.

Neither Scuba.com nor 3 Guys on Fire, Inc. holds SOC 2 Type 1 certification.

Neither Scuba.com nor 3 Guys on Fire, Inc. holds SOC 2 Type 2 certification.

Neither Scuba.com nor 3 Guys on Fire, Inc. holds ISO 27001 certification.

Neither Scuba.com nor 3 Guys on Fire, Inc. holds PCI DSS certification.

Neither Scuba.com nor 3 Guys on Fire, Inc. holds HIPAA certification.

Neither Scuba.com nor 3 Guys on Fire, Inc. 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