Comparison Overview

Coastal Discovery Museum

VS

Tucson Museum Of Art

Coastal Discovery Museum

70 HONEY HORN DR, Hilton Head Island, South Carolina, 29926, US
Last Update: 2025-12-01

The Coastal Discovery Museum, an Smithsonian Affiliate, is known for its beautiful setting on Hilton Head Island's 70-acre Honey Horn property and for year-round programs, walks, talks, tours and events that explore Lowcountry wildlife, history, art and culture. with a mission. With a mission is to provide experiences that inspire people to care for the Lowcountry, the Museum serves more than 100,000 local area residents, educators and school groups, and tourists annually.

NAICS: 712
NAICS Definition:
Employees: 13
Subsidiaries: 0
12-month incidents
0
Known data breaches
0
Attack type number
0

Tucson Museum Of Art

140 N Main Ave, Tucson, Arizona 85701-8290, US
Last Update: 2025-12-03

The Tucson Museum of Art and Historic Block encompasses an entire city block in historic downtown, and features original and traveling exhibitions focusing on Art of Latin America, Art of the American West, Modern and Contemporary Art and Asian Art as well as tours, education programs, studio art classes, and a Museum Store aimed at delighting and educating visitors. The Tucson Museum of Art serves the city and surrounding regions and is committed to broadening public access to the arts and enriching daily life.

NAICS: 712
NAICS Definition: Museums, Historical Sites, and Similar Institutions
Employees: 45
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/coastal-discovery-museum.jpeg
Coastal Discovery Museum
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/tucson-museum-of-art.jpeg
Tucson Museum Of Art
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
Coastal Discovery Museum
100%
Compliance Rate
0/4 Standards Verified
Tucson Museum Of Art
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Museums, Historical Sites, and Zoos Industry Average (This Year)

No incidents recorded for Coastal Discovery Museum in 2025.

Incidents vs Museums, Historical Sites, and Zoos Industry Average (This Year)

No incidents recorded for Tucson Museum Of Art in 2025.

Incident History — Coastal Discovery Museum (X = Date, Y = Severity)

Coastal Discovery Museum cyber incidents detection timeline including parent company and subsidiaries

Incident History — Tucson Museum Of Art (X = Date, Y = Severity)

Tucson Museum Of Art cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/coastal-discovery-museum.jpeg
Coastal Discovery Museum
Incidents

No Incident

https://images.rankiteo.com/companyimages/tucson-museum-of-art.jpeg
Tucson Museum Of Art
Incidents

No Incident

FAQ

Both Coastal Discovery Museum company and Tucson Museum Of Art company demonstrate a comparable AI Cybersecurity Score, with strong governance and monitoring frameworks in place.

Historically, Tucson Museum Of Art company has disclosed a higher number of cyber incidents compared to Coastal Discovery Museum company.

In the current year, Tucson Museum Of Art company and Coastal Discovery Museum company have not reported any cyber incidents.

Neither Tucson Museum Of Art company nor Coastal Discovery Museum company has reported experiencing a ransomware attack publicly.

Neither Tucson Museum Of Art company nor Coastal Discovery Museum company has reported experiencing a data breach publicly.

Neither Tucson Museum Of Art company nor Coastal Discovery Museum company has reported experiencing targeted cyberattacks publicly.

Neither Coastal Discovery Museum company nor Tucson Museum Of Art company has reported experiencing or disclosing vulnerabilities publicly.

Neither Coastal Discovery Museum nor Tucson Museum Of Art holds any compliance certifications.

Neither company holds any compliance certifications.

Neither Coastal Discovery Museum company nor Tucson Museum Of Art company has publicly disclosed detailed information about the number of their subsidiaries.

Tucson Museum Of Art company employs more people globally than Coastal Discovery Museum company, reflecting its scale as a Museums, Historical Sites, and Zoos.

Neither Coastal Discovery Museum nor Tucson Museum Of Art holds SOC 2 Type 1 certification.

Neither Coastal Discovery Museum nor Tucson Museum Of Art holds SOC 2 Type 2 certification.

Neither Coastal Discovery Museum nor Tucson Museum Of Art holds ISO 27001 certification.

Neither Coastal Discovery Museum nor Tucson Museum Of Art holds PCI DSS certification.

Neither Coastal Discovery Museum nor Tucson Museum Of Art holds HIPAA certification.

Neither Coastal Discovery Museum nor Tucson Museum Of Art holds GDPR certification.

Latest Global CVEs (Not Company-Specific)

Description

vLLM is an inference and serving engine for large language models (LLMs). Prior to 0.11.1, vllm has a critical remote code execution vector in a config class named Nemotron_Nano_VL_Config. When vllm loads a model config that contains an auto_map entry, the config class resolves that mapping with get_class_from_dynamic_module(...) and immediately instantiates the returned class. This fetches and executes Python from the remote repository referenced in the auto_map string. Crucially, this happens even when the caller explicitly sets trust_remote_code=False in vllm.transformers_utils.config.get_config. In practice, an attacker can publish a benign-looking frontend repo whose config.json points via auto_map to a separate malicious backend repo; loading the frontend will silently run the backend’s code on the victim host. This vulnerability is fixed in 0.11.1.

Risk Information
cvss3
Base: 7.1
Severity: HIGH
CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:H/I:H/A:H
Description

fastify-reply-from is a Fastify plugin to forward the current HTTP request to another server. Prior to 12.5.0, by crafting a malicious URL, an attacker could access routes that are not allowed, even though the reply.from is defined for specific routes in @fastify/reply-from. This vulnerability is fixed in 12.5.0.

Risk Information
cvss4
Base: 6.9
Severity: LOW
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/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

Angular is a development platform for building mobile and desktop web applications using TypeScript/JavaScript and other languages. Prior to 21.0.2, 20.3.15, and 19.2.17, A Stored Cross-Site Scripting (XSS) vulnerability has been identified in the Angular Template Compiler. It occurs because the compiler's internal security schema is incomplete, allowing attackers to bypass Angular's built-in security sanitization. Specifically, the schema fails to classify certain URL-holding attributes (e.g., those that could contain javascript: URLs) as requiring strict URL security, enabling the injection of malicious scripts. This vulnerability is fixed in 21.0.2, 20.3.15, and 19.2.17.

Risk Information
cvss4
Base: 8.5
Severity: LOW
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:A/VC:H/VI:H/VA:H/SC:N/SI:N/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

Gin-vue-admin is a backstage management system based on vue and gin. In 2.8.6 and earlier, attackers can delete any file on the server at will, causing damage or unavailability of server resources. Attackers can control the 'FileMd5' parameter to delete any file and folder.

Risk Information
cvss4
Base: 8.7
Severity: LOW
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/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

Portkey.ai Gateway is a blazing fast AI Gateway with integrated guardrails. Prior to 1.14.0, the gateway determined the destination baseURL by prioritizing the value in the x-portkey-custom-host request header. The proxy route then appends the client-specified path to perform an external fetch. This can be maliciously used by users for SSRF attacks. This vulnerability is fixed in 1.14.0.

Risk Information
cvss4
Base: 6.9
Severity: LOW
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:N/SC:L/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