Comparison Overview

Pretend City Children's Museum

VS

Tallahassee Museum

Pretend City Children's Museum

29 Hubble, Irvine, CA, 92618, US
Last Update: 2026-01-22
Between 750 and 799

Pretend City Children’s Museum features a small, interconnected city designed to “build better brains” through purposeful play, hands-on learning experiences, role playing, and educational programming. As a non-profit 501(c)(3) organization serving all children, it depends on community-based funding and guest support. Through 17 interactive exhibits and activities guided by a highly trained professional staff, children learn foundational math, reading and science skills, while fostering curiosity, creativity, critical thinking, problem solving, organization, teamwork, self-confidence and socialization. The museum is a unique community resource offering developmental screenings and tools for families, educators and community agencies working to ensure that each child gains the experiences needed to discover their potential and build toward a productive and fulfilling future.

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

Tallahassee Museum

3945 Museum Dr, Tallahassee, FL, 32310, US
Last Update: 2026-01-22

From its first temporary location to the nationally recognized, accredited, 52-acre institution it is today, the Museum's educational commitment to the region and active learning has strengthened and broadened. Now providing programs for children, schools, families and adults, it serves a population of over 435,000 people in a 13-county region, promoting knowledge and understanding of the region’s cultural history and natural environment, and inspiring people to enrich their lives and build a better community.

NAICS: 712
NAICS Definition:
Employees: 56
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/pretend-city-children's-museum.jpeg
Pretend City Children's 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/tallahassee-museum.jpeg
Tallahassee 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
Pretend City Children's Museum
100%
Compliance Rate
0/4 Standards Verified
Tallahassee 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 Pretend City Children's Museum in 2026.

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

No incidents recorded for Tallahassee Museum in 2026.

Incident History — Pretend City Children's Museum (X = Date, Y = Severity)

Pretend City Children's Museum cyber incidents detection timeline including parent company and subsidiaries

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

Tallahassee Museum cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/pretend-city-children's-museum.jpeg
Pretend City Children's Museum
Incidents

No Incident

https://images.rankiteo.com/companyimages/tallahassee-museum.jpeg
Tallahassee Museum
Incidents

No Incident

FAQ

Both Pretend City Children's Museum company and Tallahassee Museum company demonstrate a comparable AI Cybersecurity Score, with strong governance and monitoring frameworks in place.

Historically, Tallahassee Museum company has disclosed a higher number of cyber incidents compared to Pretend City Children's Museum company.

In the current year, Tallahassee Museum company and Pretend City Children's Museum company have not reported any cyber incidents.

Neither Tallahassee Museum company nor Pretend City Children's Museum company has reported experiencing a ransomware attack publicly.

Neither Tallahassee Museum company nor Pretend City Children's Museum company has reported experiencing a data breach publicly.

Neither Tallahassee Museum company nor Pretend City Children's Museum company has reported experiencing targeted cyberattacks publicly.

Neither Pretend City Children's Museum company nor Tallahassee Museum company has reported experiencing or disclosing vulnerabilities publicly.

Neither Pretend City Children's Museum nor Tallahassee Museum holds any compliance certifications.

Neither company holds any compliance certifications.

Neither Pretend City Children's Museum company nor Tallahassee Museum company has publicly disclosed detailed information about the number of their subsidiaries.

Tallahassee Museum company employs more people globally than Pretend City Children's Museum company, reflecting its scale as a Museums, Historical Sites, and Zoos.

Neither Pretend City Children's Museum nor Tallahassee Museum holds SOC 2 Type 1 certification.

Neither Pretend City Children's Museum nor Tallahassee Museum holds SOC 2 Type 2 certification.

Neither Pretend City Children's Museum nor Tallahassee Museum holds ISO 27001 certification.

Neither Pretend City Children's Museum nor Tallahassee Museum holds PCI DSS certification.

Neither Pretend City Children's Museum nor Tallahassee Museum holds HIPAA certification.

Neither Pretend City Children's Museum nor Tallahassee 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