Comparison Overview

Seattle Children's Museum

VS

Old Fort Niagara

Seattle Children's Museum

305 Harrison Street, None, Seattle, WA, US, 98109
Last Update: 2025-12-01

Our purpose is to encourage kids and adults alike to embrace active, lifelong learning. We create and maintain museum spaces, events and programs that are inclusive, engaging, playful and fun for ALL of the region’s kids and families. We envision a region where children, families, students and educators have a wide network of facilities to support them in learning, engagement, play and quality time together. We will do our part to be part of that network. Our goals are to: - Build relationships and interconnectedness with the early learning community Connect to Seattle’s varied and diverse neighborhoods; - Grow the DNA and lineage of multiculturalism into a new focus on exhibits that have equity, inclusion, diversity, visibility, access and anti-racism built in; - Set the stage for kids to build competency through engagement, opportunities, interactions, and hands-on experiences; - Renew a deep commitment to fostering literacy, language, numeracy and communication skills; - Focus on art, culture, creativity, literacy, innovation and self-actualization for kids.

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

Old Fort Niagara

Po Box 169, Youngstown, New York 14174-0169, US
Last Update: 2025-12-02

We feel that thorough preservation, authentic presentation, and high-quality programming future generations can discover their interest and appreciation for our past. Old Fort Niagara has been preserving and presenting the early history of the United States and Canada for over 90 years. Throughout that time we have updated and improved our programming in order to provide the most educational and entertaining experience to our visitors.

NAICS: 712
NAICS Definition: Museums, Historical Sites, and Similar Institutions
Employees: 15
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/seattle-children's-museum.jpeg
Seattle Children's 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/old-fort-niagara.jpeg
Old Fort Niagara
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
Seattle Children's Museum
100%
Compliance Rate
0/4 Standards Verified
Old Fort Niagara
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 Seattle Children's Museum in 2025.

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

No incidents recorded for Old Fort Niagara in 2025.

Incident History — Seattle Children's Museum (X = Date, Y = Severity)

Seattle Children's Museum cyber incidents detection timeline including parent company and subsidiaries

Incident History — Old Fort Niagara (X = Date, Y = Severity)

Old Fort Niagara cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/seattle-children's-museum.jpeg
Seattle Children's Museum
Incidents

No Incident

https://images.rankiteo.com/companyimages/old-fort-niagara.jpeg
Old Fort Niagara
Incidents

No Incident

FAQ

Old Fort Niagara company demonstrates a stronger AI Cybersecurity Score compared to Seattle Children's Museum company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Historically, Old Fort Niagara company has disclosed a higher number of cyber incidents compared to Seattle Children's Museum company.

In the current year, Old Fort Niagara company and Seattle Children's Museum company have not reported any cyber incidents.

Neither Old Fort Niagara company nor Seattle Children's Museum company has reported experiencing a ransomware attack publicly.

Neither Old Fort Niagara company nor Seattle Children's Museum company has reported experiencing a data breach publicly.

Neither Old Fort Niagara company nor Seattle Children's Museum company has reported experiencing targeted cyberattacks publicly.

Neither Seattle Children's Museum company nor Old Fort Niagara company has reported experiencing or disclosing vulnerabilities publicly.

Neither Seattle Children's Museum nor Old Fort Niagara holds any compliance certifications.

Neither company holds any compliance certifications.

Neither Seattle Children's Museum company nor Old Fort Niagara company has publicly disclosed detailed information about the number of their subsidiaries.

Seattle Children's Museum company employs more people globally than Old Fort Niagara company, reflecting its scale as a Museums, Historical Sites, and Zoos.

Neither Seattle Children's Museum nor Old Fort Niagara holds SOC 2 Type 1 certification.

Neither Seattle Children's Museum nor Old Fort Niagara holds SOC 2 Type 2 certification.

Neither Seattle Children's Museum nor Old Fort Niagara holds ISO 27001 certification.

Neither Seattle Children's Museum nor Old Fort Niagara holds PCI DSS certification.

Neither Seattle Children's Museum nor Old Fort Niagara holds HIPAA certification.

Neither Seattle Children's Museum nor Old Fort Niagara 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