Comparison Overview

OMSI

VS

Long Island Museum

OMSI

1945 SE Water Ave., None, Portland, Oregon, US, 97214
Last Update: 2025-12-01
Between 750 and 799

The Oregon Museum of Science and Industry (OMSI) is a nationally-renowned science center providing science learning to a range of audiences. Our programming is guided by OMSI’s long-term vision to promote a healthy, innovative, and sustainable society where everyone is prepared to participate in civic life. OMSI’s science, technology, engineering, art and mathematics (STEAM) programming helps visitors and program participants master 21st-century skills such as critical thinking, problem solving and collaboration. We achieve this vision through exhibits, classes, camps, traveling educators, and adult programs around the state, making OMSI a trusted educational resource to all Oregonians.

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

Long Island Museum

1200 Route 25A, Stony Brook, 11790, US
Last Update: 2025-12-01

Located at 1200 Route 25A in Stony Brook, the Long Island Museum is a Smithsonian Affiliate dedicated to enhancing the lives of adults and children with an understanding of Long Island's rich history and diverse cultures. The museum is open Thursday through Saturday from 10 a.m. to 5 p.m. and Sunday from noon to 5 p.m. Occupying nine landscaped acres in historic Stony Brook, the museum includes three exhibition buildings and five historic structures featuring permanent and changing exhibitions on American history and art as they relate to Long Island, as well as the finest collection of horse-drawn carriages in the United States. The museum is accredited by the American Alliance of Museums and in 2006, became a Smithsonian Affiliate.

NAICS: 712
NAICS Definition: Museums, Historical Sites, and Similar Institutions
Employees: 40
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/omsi.jpeg
OMSI
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/long-island-museum.jpeg
Long Island 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
OMSI
100%
Compliance Rate
0/4 Standards Verified
Long Island 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 OMSI in 2025.

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

No incidents recorded for Long Island Museum in 2025.

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

OMSI cyber incidents detection timeline including parent company and subsidiaries

Incident History — Long Island Museum (X = Date, Y = Severity)

Long Island Museum cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/omsi.jpeg
OMSI
Incidents

No Incident

https://images.rankiteo.com/companyimages/long-island-museum.jpeg
Long Island Museum
Incidents

No Incident

FAQ

OMSI company demonstrates a stronger AI Cybersecurity Score compared to Long Island Museum company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Historically, Long Island Museum company has disclosed a higher number of cyber incidents compared to OMSI company.

In the current year, Long Island Museum company and OMSI company have not reported any cyber incidents.

Neither Long Island Museum company nor OMSI company has reported experiencing a ransomware attack publicly.

Neither Long Island Museum company nor OMSI company has reported experiencing a data breach publicly.

Neither Long Island Museum company nor OMSI company has reported experiencing targeted cyberattacks publicly.

Neither OMSI company nor Long Island Museum company has reported experiencing or disclosing vulnerabilities publicly.

Neither OMSI nor Long Island Museum holds any compliance certifications.

Neither company holds any compliance certifications.

Neither OMSI company nor Long Island Museum company has publicly disclosed detailed information about the number of their subsidiaries.

OMSI company employs more people globally than Long Island Museum company, reflecting its scale as a Museums, Historical Sites, and Zoos.

Neither OMSI nor Long Island Museum holds SOC 2 Type 1 certification.

Neither OMSI nor Long Island Museum holds SOC 2 Type 2 certification.

Neither OMSI nor Long Island Museum holds ISO 27001 certification.

Neither OMSI nor Long Island Museum holds PCI DSS certification.

Neither OMSI nor Long Island Museum holds HIPAA certification.

Neither OMSI nor Long Island 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