Comparison Overview

The Leonardo

VS

Historic Denver

The Leonardo

209 E. 500 South, Salt Lake City, UT, 84111, US
Last Update: 2025-12-01
Between 750 and 799

The Leonardo is a contemporary museum that explores the unexpected ways that science, technology, art, and creativity connect. Located in the heart of downtown Salt Lake City, The Leo is your place to see one-of-a-kind, interactive exhibits and participate in ever-changing programs, workshops, and classes. It is The Leonardo’s mission to fuse science, technology and art in experiences that inspire creativity and innovation in people of all ages and backgrounds. Once home to the Salt Lake City Public Library, The Leonardo’s building has been a center for learning, curiosity, and discovery for the people of the Wasatch Front for nearly 50 years. The Leo is tremendously proud to carry on that legacy, and invite you to become a part of this unique museum experience. The Leonardo is currently open Wednesday to Sunday from 12pm to 5pm.

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

Historic Denver

undefined, undefined, undefined, 80202, US
Last Update: 2025-12-01

Historic Denver, Inc. is one of the nation’s premier urban historic preservation organizations. Preserving Denver’s distinctive cultural and architectural heritage is our work and passion. Our responsibility as a nonprofit corporation is to be a catalyst for and advocate of ideas, programs, actions and plans which enable our community to respect and carry forward the preservation of this heritage. Our success is achieved with advocacy, technical services, educational programs, membership events, and through the direct stewardship of historic resources through our grant management program and through our flagship property, the Molly Brown House Museum.

NAICS: 712
NAICS Definition: Museums, Historical Sites, and Similar Institutions
Employees: 18
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/the-leonardo.jpeg
The Leonardo
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/historic-denver-inc..jpeg
Historic Denver
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
The Leonardo
100%
Compliance Rate
0/4 Standards Verified
Historic Denver
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 The Leonardo in 2025.

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

No incidents recorded for Historic Denver in 2025.

Incident History — The Leonardo (X = Date, Y = Severity)

The Leonardo cyber incidents detection timeline including parent company and subsidiaries

Incident History — Historic Denver (X = Date, Y = Severity)

Historic Denver cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/the-leonardo.jpeg
The Leonardo
Incidents

No Incident

https://images.rankiteo.com/companyimages/historic-denver-inc..jpeg
Historic Denver
Incidents

No Incident

FAQ

Both The Leonardo company and Historic Denver company demonstrate a comparable AI Cybersecurity Score, with strong governance and monitoring frameworks in place.

Historically, Historic Denver company has disclosed a higher number of cyber incidents compared to The Leonardo company.

In the current year, Historic Denver company and The Leonardo company have not reported any cyber incidents.

Neither Historic Denver company nor The Leonardo company has reported experiencing a ransomware attack publicly.

Neither Historic Denver company nor The Leonardo company has reported experiencing a data breach publicly.

Neither Historic Denver company nor The Leonardo company has reported experiencing targeted cyberattacks publicly.

Neither The Leonardo company nor Historic Denver company has reported experiencing or disclosing vulnerabilities publicly.

Neither The Leonardo nor Historic Denver holds any compliance certifications.

Neither company holds any compliance certifications.

Neither The Leonardo company nor Historic Denver company has publicly disclosed detailed information about the number of their subsidiaries.

The Leonardo company employs more people globally than Historic Denver company, reflecting its scale as a Museums, Historical Sites, and Zoos.

Neither The Leonardo nor Historic Denver holds SOC 2 Type 1 certification.

Neither The Leonardo nor Historic Denver holds SOC 2 Type 2 certification.

Neither The Leonardo nor Historic Denver holds ISO 27001 certification.

Neither The Leonardo nor Historic Denver holds PCI DSS certification.

Neither The Leonardo nor Historic Denver holds HIPAA certification.

Neither The Leonardo nor Historic Denver 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