Comparison Overview

St. Petersburg Museum of History

VS

Museum of Us

St. Petersburg Museum of History

335 2nd Ave NE, St Petersburg, Florida, 33701, US
Last Update: 2025-12-03

For over a century, the St. Petersburg Museum of History has shared stories of the Sunshine City. Our galleries offer visitors a look at Florida's rich history with a focus on St. Petersburg and Pinellas County. From the birth of commercial aviation and spring training here in the Sunshine City to the vast accomplishments of early Pinellas Pioneers, the St. Petersburg Museum of History offers something for everyone. Come check out our two-headed calf, our 3,000-year-old Egyptian mummy, our working replica of the Benoist XIV airboat, and the world's largest collection of autographed baseballs - and learn all about St. Pete's history!

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

Museum of Us

1350 El Prado, Balboa Park, San Diego, CA, 92101, US
Last Update: 2025-12-01
Between 750 and 799

Formerly known as the San Diego Museum of Man, the Museum of Us is an anthropology museum with a mission to inspire human connections by exploring the human experience. Centered on core anthropological values such as compassion, sitting in generosity rather than judgment, and love for all humanity, the Museum of Us takes a different approach from the traditional authoritative “museum voice." The 501(c)(3) non-profit was founded in Balboa Park in 1915 and is located in the iconic California Building and Tower. Through original, interactive exhibits visitors discover what it means to be human - whether it's exploring how beer shaped civilizations, connecting with strangers over shared secrets, or discovering who cannibals really are (could you be one?).

NAICS: 712
NAICS Definition: Museums, Historical Sites, and Similar Institutions
Employees: 56
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/st-petersburg-historical-society-inc-.jpeg
St. Petersburg Museum of History
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/san-diego-museum-of-man.jpeg
Museum of Us
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
St. Petersburg Museum of History
100%
Compliance Rate
0/4 Standards Verified
Museum of Us
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 St. Petersburg Museum of History in 2025.

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

No incidents recorded for Museum of Us in 2025.

Incident History — St. Petersburg Museum of History (X = Date, Y = Severity)

St. Petersburg Museum of History cyber incidents detection timeline including parent company and subsidiaries

Incident History — Museum of Us (X = Date, Y = Severity)

Museum of Us cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/st-petersburg-historical-society-inc-.jpeg
St. Petersburg Museum of History
Incidents

No Incident

https://images.rankiteo.com/companyimages/san-diego-museum-of-man.jpeg
Museum of Us
Incidents

No Incident

FAQ

Both St. Petersburg Museum of History company and Museum of Us company demonstrate a comparable AI Cybersecurity Score, with strong governance and monitoring frameworks in place.

Historically, Museum of Us company has disclosed a higher number of cyber incidents compared to St. Petersburg Museum of History company.

In the current year, Museum of Us company and St. Petersburg Museum of History company have not reported any cyber incidents.

Neither Museum of Us company nor St. Petersburg Museum of History company has reported experiencing a ransomware attack publicly.

Neither Museum of Us company nor St. Petersburg Museum of History company has reported experiencing a data breach publicly.

Neither Museum of Us company nor St. Petersburg Museum of History company has reported experiencing targeted cyberattacks publicly.

Neither St. Petersburg Museum of History company nor Museum of Us company has reported experiencing or disclosing vulnerabilities publicly.

Neither St. Petersburg Museum of History nor Museum of Us holds any compliance certifications.

Neither company holds any compliance certifications.

Neither St. Petersburg Museum of History company nor Museum of Us company has publicly disclosed detailed information about the number of their subsidiaries.

Museum of Us company employs more people globally than St. Petersburg Museum of History company, reflecting its scale as a Museums, Historical Sites, and Zoos.

Neither St. Petersburg Museum of History nor Museum of Us holds SOC 2 Type 1 certification.

Neither St. Petersburg Museum of History nor Museum of Us holds SOC 2 Type 2 certification.

Neither St. Petersburg Museum of History nor Museum of Us holds ISO 27001 certification.

Neither St. Petersburg Museum of History nor Museum of Us holds PCI DSS certification.

Neither St. Petersburg Museum of History nor Museum of Us holds HIPAA certification.

Neither St. Petersburg Museum of History nor Museum of Us 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