Comparison Overview

SFO Museum

VS

Lyman Allyn Art Museum

SFO Museum

San Francisco International Airport, None, San Francisco, California, US, 94128
Last Update: 2025-12-01
View Profile
Between 750 and 799
http://sfomuseum.org

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
View Profile

Lyman Allyn Art Museum

625 Williams Street, New London, CT, 06320, US
Last Update: 2025-12-01
Between 750 and 799
http://www.lymanallyn.org

Located just off I-95, Exit 83, the Lyman Allyn Art Museum has enjoyed celebrating the arts with visitors for almost a century. The Museum presents a stimulating mix of changing exhibitions, in addition to our permanent installations that celebrate American art and history, and Louis Comfort Tiffany’s close connection to the area. In 2025 the Museum plans to open Lyman Allyn Park, an urban park that will serve as a cultural and educational resource for the City of New London and surrounding region.

NAICS: 712
NAICS Definition:
Employees: 29
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/lyman-allyn-art-museum.jpeg
Lyman Allyn Art 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
Lyman Allyn Art 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 2025.

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

No incidents recorded for Lyman Allyn Art Museum in 2025.

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

SFO Museum cyber incidents detection timeline including parent company and subsidiaries

Incident History — Lyman Allyn Art Museum (X = Date, Y = Severity)

Lyman Allyn Art 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/lyman-allyn-art-museum.jpeg
Lyman Allyn Art Museum
Incidents

No Incident

FAQ

Both SFO Museum company and Lyman Allyn Art Museum company demonstrate a comparable AI Cybersecurity Score, with strong governance and monitoring frameworks in place.

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

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

Neither Lyman Allyn Art Museum company nor SFO Museum company has reported experiencing a ransomware attack publicly.

Neither Lyman Allyn Art Museum company nor SFO Museum company has reported experiencing a data breach publicly.

Neither Lyman Allyn Art Museum company nor SFO Museum company has reported experiencing targeted cyberattacks publicly.

Neither SFO Museum company nor Lyman Allyn Art Museum company has reported experiencing or disclosing vulnerabilities publicly.

Neither SFO Museum nor Lyman Allyn Art Museum holds any compliance certifications.

Neither company holds any compliance certifications.

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

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

Neither SFO Museum nor Lyman Allyn Art Museum holds SOC 2 Type 1 certification.

Neither SFO Museum nor Lyman Allyn Art Museum holds SOC 2 Type 2 certification.

Neither SFO Museum nor Lyman Allyn Art Museum holds ISO 27001 certification.

Neither SFO Museum nor Lyman Allyn Art Museum holds PCI DSS certification.

Neither SFO Museum nor Lyman Allyn Art Museum holds HIPAA certification.

Neither SFO Museum nor Lyman Allyn Art Museum holds GDPR certification.

Latest Global CVEs (Not Company-Specific)

Description

ImageMagick is free and open-source software used for editing and manipulating digital images. Prior to 7.1.2-9 and 6.9.13-34, there is a vulnerability in ImageMagick’s Magick++ layer that manifests when Options::fontFamily is invoked with an empty string. Clearing a font family calls RelinquishMagickMemory on _drawInfo->font, freeing the font string but leaving _drawInfo->font pointing to freed memory while _drawInfo->family is set to that (now-invalid) pointer. Any later cleanup or reuse of _drawInfo->font re-frees or dereferences dangling memory. DestroyDrawInfo and other setters (Options::font, Image::font) assume _drawInfo->font remains valid, so destruction or subsequent updates trigger crashes or heap corruption. This vulnerability is fixed in 7.1.2-9 and 6.9.13-34.

Published
Date
2025-12-02
Updated
Date
2025-12-02
Risk Information
cvss3
Base: 4.9
Severity: HIGH
CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:L
References
Description

FeehiCMS version 2.1.1 has a Remote Code Execution via Unrestricted File Upload in Ad Management. FeehiCMS version 2.1.1 allows authenticated remote attackers to upload files that the server later executes (or stores in an executable location) without sufficient validation, sanitization, or execution restrictions. An authenticated remote attacker can upload a crafted PHP file and cause the application or web server to execute it, resulting in remote code execution (RCE).

Published
Date
2025-12-02
Updated
Date
2025-12-02
Risk Information
cvss3
Base: 6.5
Severity: LOW
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N
References
Description

PHPGurukul Billing System 1.0 is vulnerable to SQL Injection in the admin/index.php endpoint. Specifically, the username parameter accepts unvalidated user input, which is then concatenated directly into a backend SQL query.

Published
Date
2025-12-02
Updated
Date
2025-12-02
Risk Information
cvss3
Base: 6.5
Severity: LOW
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N
References
Description

NMIS/BioDose software V22.02 and previous versions contain executable binaries with plain text hard-coded passwords. These hard-coded passwords could allow unauthorized access to both the application and database.

Published
Date
2025-12-02
Updated
Date
2025-12-02
Risk Information
cvss3
Base: 7.3
Severity: LOW
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:L
cvss4
Base: 8.4
Severity: LOW
CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:L/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
References
Description

NMIS/BioDose V22.02 and previous versions' installation directory paths by default have insecure file permissions, which in certain deployment scenarios can enable users on client workstations to modify the program executables and libraries.

Published
Date
2025-12-02
Updated
Date
2025-12-02
Risk Information
cvss3
Base: 8.0
Severity: LOW
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:H
cvss4
Base: 7.1
Severity: LOW
CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:L/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
References