Comparison Overview

Tampa Bay History Center

VS

Santa Monica History Museum

Tampa Bay History Center

801 Water Street, Tampa, FL, 33602, US
Last Update: 2025-12-01

The Tampa Bay History Center takes you on a 12,000-year journey through the past, highlighting the people and stories of Florida's West Coast. With three floors of cutting-edge exhibits and theaters, the History Center offers a unique experience for visitors of all ages and provides a sense of place for long-time residents, newcomers and out-of-town guests.

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

Santa Monica History Museum

1350 7th St, Santa Monica, California, undefined, US
Last Update: 2025-12-03

The Santa Monica History Museum, a non-profit organization, was founded in 1975 by the Santa Monica Centennial Committee to collect and preserve the history, art and culture of the Santa Monica Bay Area and to be the guardian/caretaker of the history. Its mission is the advancement of historical information and education, and the collection, documentation and preservation of objects and memorabilia relating to the Santa Monica Bay Area; and to give residents, particularly children, a sense of roots, belonging, and a strong appreciation for the unique history and qualities of their own city, and pride in the diverse, multi-cultural past of Santa Monica. The museum’s goal is to provide public access to its extensive collection through interpretive exhibitions, on- and off-site programs, and through archival and research services for youth and adults.

NAICS: 712
NAICS Definition:
Employees: 7
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/tampa-bay-history-center.jpeg
Tampa Bay History Center
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/santa-monica-history-museum.jpeg
Santa Monica History 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
Compliance Summary
Tampa Bay History Center
100%
Compliance Rate
0/4 Standards Verified
Santa Monica History Museum
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 Tampa Bay History Center in 2025.

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

No incidents recorded for Santa Monica History Museum in 2025.

Incident History — Tampa Bay History Center (X = Date, Y = Severity)

Tampa Bay History Center cyber incidents detection timeline including parent company and subsidiaries

Incident History — Santa Monica History Museum (X = Date, Y = Severity)

Santa Monica History Museum cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/tampa-bay-history-center.jpeg
Tampa Bay History Center
Incidents

No Incident

https://images.rankiteo.com/companyimages/santa-monica-history-museum.jpeg
Santa Monica History Museum
Incidents

No Incident

FAQ

Santa Monica History Museum company demonstrates a stronger AI Cybersecurity Score compared to Tampa Bay History Center company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Historically, Santa Monica History Museum company has disclosed a higher number of cyber incidents compared to Tampa Bay History Center company.

In the current year, Santa Monica History Museum company and Tampa Bay History Center company have not reported any cyber incidents.

Neither Santa Monica History Museum company nor Tampa Bay History Center company has reported experiencing a ransomware attack publicly.

Neither Santa Monica History Museum company nor Tampa Bay History Center company has reported experiencing a data breach publicly.

Neither Santa Monica History Museum company nor Tampa Bay History Center company has reported experiencing targeted cyberattacks publicly.

Neither Tampa Bay History Center company nor Santa Monica History Museum company has reported experiencing or disclosing vulnerabilities publicly.

Neither Tampa Bay History Center nor Santa Monica History Museum holds any compliance certifications.

Neither company holds any compliance certifications.

Neither Tampa Bay History Center company nor Santa Monica History Museum company has publicly disclosed detailed information about the number of their subsidiaries.

Tampa Bay History Center company employs more people globally than Santa Monica History Museum company, reflecting its scale as a Museums, Historical Sites, and Zoos.

Neither Tampa Bay History Center nor Santa Monica History Museum holds SOC 2 Type 1 certification.

Neither Tampa Bay History Center nor Santa Monica History Museum holds SOC 2 Type 2 certification.

Neither Tampa Bay History Center nor Santa Monica History Museum holds ISO 27001 certification.

Neither Tampa Bay History Center nor Santa Monica History Museum holds PCI DSS certification.

Neither Tampa Bay History Center nor Santa Monica History Museum holds HIPAA certification.

Neither Tampa Bay History Center nor Santa Monica History Museum 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