Comparison Overview

Exploratorium

VS

Oyster Bay Historical Society

Exploratorium

Pier 15 (Embarcadero & Green St), San Francisco, CA, 94111, US
Last Update: 2025-12-01
Between 750 and 799

The Exploratorium is a public learning laboratory where you can explore the world through science, art, and human perception. Our world-renowned science museum offers 700+ interactive exhibits designed to ignite curiosity and foster exploration. Founded in 1969 by Dr. Frank Oppenheimer, our mission is to create inquiry-based experiences that transform learning worldwide. We envision a world where people think for themselves and can confidently ask questions, question answers, and understand the world around them. Dedicated to education reform in and out of the classroom, the Exploratorium is a premier professional development center for educators and a creator of award-winning educational resources. The Exploratorium has influenced generations of entrepreneurs, artists, scientists, teachers, students, children, museum professionals, and everyday doers. We also collaborate globally, bringing our original, interactive exhibits to more than 1,000 science centers, museums, and public spaces around the world.

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

Oyster Bay Historical Society

None
Last Update: 2025-12-01

The Oyster Bay Historical Society maintains the18th-century Earle-Wightman House and garden, as well as the Angela Koenig Research and Exhibition Center. The Society is committed to preserving the history of Oyster Bay and making that history accessible to everyone through its permanent collections, rotating exhibitions, and educational programs.

NAICS: 712
NAICS Definition: Museums, Historical Sites, and Similar Institutions
Employees: 6
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/exploratorium.jpeg
Exploratorium
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
Oyster Bay Historical Society
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
Exploratorium
100%
Compliance Rate
0/4 Standards Verified
Oyster Bay Historical Society
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 Exploratorium in 2025.

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

No incidents recorded for Oyster Bay Historical Society in 2025.

Incident History — Exploratorium (X = Date, Y = Severity)

Exploratorium cyber incidents detection timeline including parent company and subsidiaries

Incident History — Oyster Bay Historical Society (X = Date, Y = Severity)

Oyster Bay Historical Society cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/exploratorium.jpeg
Exploratorium
Incidents

No Incident

https://images.rankiteo.com/companyimages/defaultcompany.jpeg
Oyster Bay Historical Society
Incidents

No Incident

FAQ

Exploratorium company demonstrates a stronger AI Cybersecurity Score compared to Oyster Bay Historical Society company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Historically, Oyster Bay Historical Society company has disclosed a higher number of cyber incidents compared to Exploratorium company.

In the current year, Oyster Bay Historical Society company and Exploratorium company have not reported any cyber incidents.

Neither Oyster Bay Historical Society company nor Exploratorium company has reported experiencing a ransomware attack publicly.

Neither Oyster Bay Historical Society company nor Exploratorium company has reported experiencing a data breach publicly.

Neither Oyster Bay Historical Society company nor Exploratorium company has reported experiencing targeted cyberattacks publicly.

Neither Exploratorium company nor Oyster Bay Historical Society company has reported experiencing or disclosing vulnerabilities publicly.

Neither Exploratorium nor Oyster Bay Historical Society holds any compliance certifications.

Neither company holds any compliance certifications.

Neither Exploratorium company nor Oyster Bay Historical Society company has publicly disclosed detailed information about the number of their subsidiaries.

Exploratorium company employs more people globally than Oyster Bay Historical Society company, reflecting its scale as a Museums, Historical Sites, and Zoos.

Neither Exploratorium nor Oyster Bay Historical Society holds SOC 2 Type 1 certification.

Neither Exploratorium nor Oyster Bay Historical Society holds SOC 2 Type 2 certification.

Neither Exploratorium nor Oyster Bay Historical Society holds ISO 27001 certification.

Neither Exploratorium nor Oyster Bay Historical Society holds PCI DSS certification.

Neither Exploratorium nor Oyster Bay Historical Society holds HIPAA certification.

Neither Exploratorium nor Oyster Bay Historical Society 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