Comparison Overview

Museums of Old York

VS

Japan House London

Museums of Old York

3 Lindsay Road, York, ME, 03909, US
Last Update: 2025-12-03
Between 750 and 799

The Museums of Old York is the product of a merger of three historical organizations founded in York with histories dating back more than a hundred years. The Mission of the Museums of Old York is to preserve and promote the rich history of the York region through programs and educational experiences that enhance historical perspective and build on community pride. We have 8 different buildings highlighting various aspects of York life, decorative arts, contemporary art, and social history located throughout York Village.

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

Japan House London

101 Kensington High Street, London, England, GB
Last Update: 2025-12-01

Japan House is the London home for Japanese creativity and innovation. Spread over three floors, Japan House London offers a gallery, with a regular programme of exhibitions; a hall for talks, performances, workshops and events; innovative Japanese restaurant AKIRA; and The Shop, a cultural retail space introducing Japanese products: their provenance and the artisans and designers who make them.

NAICS: 712
NAICS Definition: Museums, Historical Sites, and Similar Institutions
Employees: 79
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/museums-of-old-york.jpeg
Museums of Old York
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/japan-house-london.jpeg
Japan House London
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
Museums of Old York
100%
Compliance Rate
0/4 Standards Verified
Japan House London
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 Museums of Old York in 2025.

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

No incidents recorded for Japan House London in 2025.

Incident History — Museums of Old York (X = Date, Y = Severity)

Museums of Old York cyber incidents detection timeline including parent company and subsidiaries

Incident History — Japan House London (X = Date, Y = Severity)

Japan House London cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/museums-of-old-york.jpeg
Museums of Old York
Incidents

No Incident

https://images.rankiteo.com/companyimages/japan-house-london.jpeg
Japan House London
Incidents

No Incident

FAQ

Japan House London company demonstrates a stronger AI Cybersecurity Score compared to Museums of Old York company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Historically, Japan House London company has disclosed a higher number of cyber incidents compared to Museums of Old York company.

In the current year, Japan House London company and Museums of Old York company have not reported any cyber incidents.

Neither Japan House London company nor Museums of Old York company has reported experiencing a ransomware attack publicly.

Neither Japan House London company nor Museums of Old York company has reported experiencing a data breach publicly.

Neither Japan House London company nor Museums of Old York company has reported experiencing targeted cyberattacks publicly.

Neither Museums of Old York company nor Japan House London company has reported experiencing or disclosing vulnerabilities publicly.

Neither Museums of Old York nor Japan House London holds any compliance certifications.

Neither company holds any compliance certifications.

Neither Museums of Old York company nor Japan House London company has publicly disclosed detailed information about the number of their subsidiaries.

Japan House London company employs more people globally than Museums of Old York company, reflecting its scale as a Museums, Historical Sites, and Zoos.

Neither Museums of Old York nor Japan House London holds SOC 2 Type 1 certification.

Neither Museums of Old York nor Japan House London holds SOC 2 Type 2 certification.

Neither Museums of Old York nor Japan House London holds ISO 27001 certification.

Neither Museums of Old York nor Japan House London holds PCI DSS certification.

Neither Museums of Old York nor Japan House London holds HIPAA certification.

Neither Museums of Old York nor Japan House London 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