Comparison Overview

SFO Museum

VS

Svalbard Museum

SFO Museum

San Francisco International Airport, None, San Francisco, California, US, 94128
Last Update: 2026-01-23
Between 750 and 799

Created in 1980, SFO Museum was the first cultural institution of its kind located in an international airport. An ever-changing schedule of exhibitions on a diverse range of subjects provides an educational and cultural experience for all visitors to the Airport. SFO Museum's mission is to delight, engage, and inspire a global audience with a broad range of programming; to collect, preserve, interpret, and share the history of commercial aviation; and to enrich the public experience at San Francisco International Airport.

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

Svalbard Museum

Vei 231-1, Longyearbyen, NO, 9170
Last Update: 2026-01-18
Between 750 and 799

Svalbard Museum shall collect, preserve, disseminate and research related to cultural and natural history, environmental information and cultural preservation on Svalbard. This is fulfilled by e.g.: - Permanent and temporary exhibitions that supports the purpose - Information - Research and publication - Education - Seminars The museum receives operational funding from the Norwegian Government. We are a member of the Norwegian Museums Association and ICOM.

NAICS: 712
NAICS Definition: Museums, Historical Sites, and Similar Institutions
Employees: 3
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/sfo-museum.jpeg
SFO 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/svalbard-museum.jpeg
Svalbard 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
SFO Museum
100%
Compliance Rate
0/4 Standards Verified
Svalbard 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 SFO Museum in 2026.

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

No incidents recorded for Svalbard Museum in 2026.

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

SFO Museum cyber incidents detection timeline including parent company and subsidiaries

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

Svalbard Museum cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/sfo-museum.jpeg
SFO Museum
Incidents

No Incident

https://images.rankiteo.com/companyimages/svalbard-museum.jpeg
Svalbard Museum
Incidents

No Incident

FAQ

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

Historically, Svalbard Museum company has disclosed a higher number of cyber incidents compared to SFO Museum company.

In the current year, Svalbard Museum company and SFO Museum company have not reported any cyber incidents.

Neither Svalbard Museum company nor SFO Museum company has reported experiencing a ransomware attack publicly.

Neither Svalbard Museum company nor SFO Museum company has reported experiencing a data breach publicly.

Neither Svalbard Museum company nor SFO Museum company has reported experiencing targeted cyberattacks publicly.

Neither SFO Museum company nor Svalbard Museum company has reported experiencing or disclosing vulnerabilities publicly.

Neither SFO Museum nor Svalbard Museum holds any compliance certifications.

Neither company holds any compliance certifications.

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

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

Neither SFO Museum nor Svalbard Museum holds SOC 2 Type 1 certification.

Neither SFO Museum nor Svalbard Museum holds SOC 2 Type 2 certification.

Neither SFO Museum nor Svalbard Museum holds ISO 27001 certification.

Neither SFO Museum nor Svalbard Museum holds PCI DSS certification.

Neither SFO Museum nor Svalbard Museum holds HIPAA certification.

Neither SFO Museum nor Svalbard Museum holds GDPR certification.

Latest Global CVEs (Not Company-Specific)

Description

Improper validation of specified type of input in M365 Copilot allows an unauthorized attacker to disclose information over a network.

Risk Information
cvss3
Base: 9.3
Severity: LOW
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:N
Description

Improper access control in Azure Front Door (AFD) allows an unauthorized attacker to elevate privileges over a network.

Risk Information
cvss3
Base: 9.8
Severity: LOW
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Description

Azure Entra ID Elevation of Privilege Vulnerability

Risk Information
cvss3
Base: 9.3
Severity: LOW
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:L/A:N
Description

Moonraker is a Python web server providing API access to Klipper 3D printing firmware. In versions 0.9.3 and below, instances configured with the "ldap" component enabled are vulnerable to LDAP search filter injection techniques via the login endpoint. The 401 error response message can be used to determine whether or not a search was successful, allowing for brute force methods to discover LDAP entries on the server such as user IDs and user attributes. This issue has been fixed in version 0.10.0.

Risk Information
cvss4
Base: 2.7
Severity: LOW
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:U/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

Runtipi is a Docker-based, personal homeserver orchestrator that facilitates multiple services on a single server. Versions 3.7.0 and above allow an authenticated user to execute arbitrary system commands on the host server by injecting shell metacharacters into backup filenames. The BackupManager fails to sanitize the filenames of uploaded backups. The system persists user-uploaded files directly to the host filesystem using the raw originalname provided in the request. This allows an attacker to stage a file containing shell metacharacters (e.g., $(id).tar.gz) at a predictable path, which is later referenced during the restore process. The successful storage of the file is what allows the subsequent restore command to reference and execute it. This issue has been fixed in version 4.7.0.

Risk Information
cvss3
Base: 8.0
Severity: HIGH
CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:H/I:H/A:H