Comparison Overview

Ohr-O'Keefe Museum of Art

VS

Museum of Boulder

Ohr-O'Keefe Museum of Art

386 BEACH BLVD, BILOXI, 39530, US
Last Update: 2025-12-03
Between 750 and 799

The mission of the Ohr-O’Keefe Museum of Art is to promote and preserve the unique legacy of Biloxi potter George E. Ohr and the diverse cultural heritage of the Mississippi Gulf Coast; and to exhibit works which exemplify the independent, innovative, and creative spirit of George Ohr, emancipated craftsman Pleasant Reed, and Ohr-O’Keefe Museum architect Frank Gehry. This mission is served through compelling exhibitions and educational experiences viewed from a fresh perspective relevant to our community, the region, and the nation with a strong focus on ceramic arts.

NAICS: 712
NAICS Definition: Museums, Historical Sites, and Similar Institutions
Employees: 10
Subsidiaries: 0
12-month incidents
0
Known data breaches
0
Attack type number
0

Museum of Boulder

1206 Euclid Ave, Boulder, Colorado 80302, US
Last Update: 2025-12-03

The Museum of Boulder is a cultural and arts institution that showcases the remarkable accomplishments of Boulder through innovative exhibits, programs and social engagement. The Museum collects, preserves and presents Boulder history in order to connect with the past, provide a context for the present and inspire a vision for the future.

NAICS: 712
NAICS Definition: Museums, Historical Sites, and Similar Institutions
Employees: 28
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/ohr-o'keefe-museum-of-art.jpeg
Ohr-O'Keefe 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
https://images.rankiteo.com/companyimages/boulder-history-museum.jpeg
Museum of Boulder
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
Ohr-O'Keefe Museum of Art
100%
Compliance Rate
0/4 Standards Verified
Museum of Boulder
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 Ohr-O'Keefe Museum of Art in 2025.

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

No incidents recorded for Museum of Boulder in 2025.

Incident History — Ohr-O'Keefe Museum of Art (X = Date, Y = Severity)

Ohr-O'Keefe Museum of Art cyber incidents detection timeline including parent company and subsidiaries

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

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

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/ohr-o'keefe-museum-of-art.jpeg
Ohr-O'Keefe Museum of Art
Incidents

No Incident

https://images.rankiteo.com/companyimages/boulder-history-museum.jpeg
Museum of Boulder
Incidents

No Incident

FAQ

Both Ohr-O'Keefe Museum of Art company and Museum of Boulder company demonstrate a comparable AI Cybersecurity Score, with strong governance and monitoring frameworks in place.

Historically, Museum of Boulder company has disclosed a higher number of cyber incidents compared to Ohr-O'Keefe Museum of Art company.

In the current year, Museum of Boulder company and Ohr-O'Keefe Museum of Art company have not reported any cyber incidents.

Neither Museum of Boulder company nor Ohr-O'Keefe Museum of Art company has reported experiencing a ransomware attack publicly.

Neither Museum of Boulder company nor Ohr-O'Keefe Museum of Art company has reported experiencing a data breach publicly.

Neither Museum of Boulder company nor Ohr-O'Keefe Museum of Art company has reported experiencing targeted cyberattacks publicly.

Neither Ohr-O'Keefe Museum of Art company nor Museum of Boulder company has reported experiencing or disclosing vulnerabilities publicly.

Neither Ohr-O'Keefe Museum of Art nor Museum of Boulder holds any compliance certifications.

Neither company holds any compliance certifications.

Neither Ohr-O'Keefe Museum of Art company nor Museum of Boulder company has publicly disclosed detailed information about the number of their subsidiaries.

Museum of Boulder company employs more people globally than Ohr-O'Keefe Museum of Art company, reflecting its scale as a Museums, Historical Sites, and Zoos.

Neither Ohr-O'Keefe Museum of Art nor Museum of Boulder holds SOC 2 Type 1 certification.

Neither Ohr-O'Keefe Museum of Art nor Museum of Boulder holds SOC 2 Type 2 certification.

Neither Ohr-O'Keefe Museum of Art nor Museum of Boulder holds ISO 27001 certification.

Neither Ohr-O'Keefe Museum of Art nor Museum of Boulder holds PCI DSS certification.

Neither Ohr-O'Keefe Museum of Art nor Museum of Boulder holds HIPAA certification.

Neither Ohr-O'Keefe Museum of Art nor Museum of Boulder 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