Comparison Overview

LancasterHistory

VS

Logistics Museum

LancasterHistory

230 North President Avenue, Lancaster, PA, 17603, US
Last Update: 2025-12-03

LancasterHistory engages and educates the public about the people, places, and events that shaped Lancaster County within the broader context of the history of the Commonwealth of Pennsylvania and the United States of America. As custodians of a complex past, we collect, preserve, exhibit, and make accessible materials chronicling Lancaster County’s heritage as we seek to engage audiences in multi-layered stories of that past.

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

Logistics Museum

Косая линия, В.О., д. 15а, Санкт-Петербург, 199106, RU
Last Update: 2025-12-01

Logistics Museum — the first of its kind museum in Russia, covering the entire distribution chain from production to the end consumer. The museum gives you the opportunity to become familiar with various practical logistics spheres: production, storage, processing and cargo transport. By visiting the Logistics Museum, our visitors become acquainted with the present state of modern day logistic as well as its trends and prospects for future development.

NAICS: 712
NAICS Definition: Museums, Historical Sites, and Similar Institutions
Employees: 192
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/lancasterhistory.org.jpeg
LancasterHistory
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/logistics-museum.jpeg
Logistics 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
LancasterHistory
100%
Compliance Rate
0/4 Standards Verified
Logistics 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 LancasterHistory in 2025.

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

No incidents recorded for Logistics Museum in 2025.

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

LancasterHistory cyber incidents detection timeline including parent company and subsidiaries

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

Logistics Museum cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/lancasterhistory.org.jpeg
LancasterHistory
Incidents

No Incident

https://images.rankiteo.com/companyimages/logistics-museum.jpeg
Logistics Museum
Incidents

No Incident

FAQ

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

Historically, Logistics Museum company has disclosed a higher number of cyber incidents compared to LancasterHistory company.

In the current year, Logistics Museum company and LancasterHistory company have not reported any cyber incidents.

Neither Logistics Museum company nor LancasterHistory company has reported experiencing a ransomware attack publicly.

Neither Logistics Museum company nor LancasterHistory company has reported experiencing a data breach publicly.

Neither Logistics Museum company nor LancasterHistory company has reported experiencing targeted cyberattacks publicly.

Neither LancasterHistory company nor Logistics Museum company has reported experiencing or disclosing vulnerabilities publicly.

Neither LancasterHistory nor Logistics Museum holds any compliance certifications.

Neither company holds any compliance certifications.

Neither LancasterHistory company nor Logistics Museum company has publicly disclosed detailed information about the number of their subsidiaries.

Logistics Museum company employs more people globally than LancasterHistory company, reflecting its scale as a Museums, Historical Sites, and Zoos.

Neither LancasterHistory nor Logistics Museum holds SOC 2 Type 1 certification.

Neither LancasterHistory nor Logistics Museum holds SOC 2 Type 2 certification.

Neither LancasterHistory nor Logistics Museum holds ISO 27001 certification.

Neither LancasterHistory nor Logistics Museum holds PCI DSS certification.

Neither LancasterHistory nor Logistics Museum holds HIPAA certification.

Neither LancasterHistory nor Logistics 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