Comparison Overview

Washington Trust for Historic Preservation

VS

Ohio History Connection

Washington Trust for Historic Preservation

1204 Minor Ave, Seattle, WA, US, 98101
Last Update: 2025-12-03
Between 750 and 799

The Washington Trust for Historic Preservation is a nonprofit organization dedicated to saving the places that matter in Washington State and to promoting sustainable and economically viable communities through historic preservation. We are Washington’s only statewide nonprofit advocacy organization working to build a collective ethic that preserves historic places through education, collaboration, and stewardship.

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

Ohio History Connection

800 E 17th Ave, None, Columbus, OH, US, 43211
Last Update: 2025-12-02
Between 650 and 699

With over 200 staff members, hundreds of volunteers and thousands of partners in historical societies, local history groups and local and state government, Ohio History Connection champions all Ohio history. Mission Spark discovery of Ohio's stories. Embrace the present, share the past and transform the future Our work includes: * A network of 50+ historic sites and museums; one of the largest statewide networks in the U.S. * Maintain the State Archives which serves as the institutional memory of the state, from founding documents to the vital records. * Administer the state’s historical museum in the Ohio History Center and Ohio Village, located in Columbus, OH. * Promote and assist local historical societies through the Local History Alliance. * Provide online textbook with teaching tools to Ohio's 4th graders. * Protect and promote Ohio's historic places through the Ohio Historic Preservation Office. * Manage the statewide History Fund, to be used for making grants to local history-related projects. * Oversee the more than 1,400 historical markers program throughout Ohio. Visit ohiohistory.org for a complete list of historic sites and services, including admission and hours. Visit ohiohistory.org/jobs for the latest job postings and ohiohistory.org/volunteer to volunteer. Specialties Collections of Ohio History, Genealogy, Civil War History, Museums, Natural History of OH, Earthworks and moundbuilding, Archaeology, Teaching Ohio history to youth, Presidents from OH, Historic preservation in OH, National Register of Historic Places

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

Compliance Badges Comparison

Security & Compliance Standards Overview

https://images.rankiteo.com/companyimages/washington-trust-for-historic-preservation.jpeg
Washington Trust for Historic Preservation
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/ohiohistory.jpeg
Ohio History Connection
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
Washington Trust for Historic Preservation
100%
Compliance Rate
0/4 Standards Verified
Ohio History Connection
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 Washington Trust for Historic Preservation in 2025.

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

No incidents recorded for Ohio History Connection in 2025.

Incident History — Washington Trust for Historic Preservation (X = Date, Y = Severity)

Washington Trust for Historic Preservation cyber incidents detection timeline including parent company and subsidiaries

Incident History — Ohio History Connection (X = Date, Y = Severity)

Ohio History Connection cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/washington-trust-for-historic-preservation.jpeg
Washington Trust for Historic Preservation
Incidents

No Incident

https://images.rankiteo.com/companyimages/ohiohistory.jpeg
Ohio History Connection
Incidents

Date Detected: 7/2023
Type:Ransomware
Blog: Blog

Date Detected: 6/2009
Type:Ransomware
Motivation: Financial gain
Blog: Blog

FAQ

Washington Trust for Historic Preservation company demonstrates a stronger AI Cybersecurity Score compared to Ohio History Connection company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Ohio History Connection company has historically faced a number of disclosed cyber incidents, whereas Washington Trust for Historic Preservation company has not reported any.

In the current year, Ohio History Connection company and Washington Trust for Historic Preservation company have not reported any cyber incidents.

Ohio History Connection company has confirmed experiencing a ransomware attack, while Washington Trust for Historic Preservation company has not reported such incidents publicly.

Neither Ohio History Connection company nor Washington Trust for Historic Preservation company has reported experiencing a data breach publicly.

Neither Ohio History Connection company nor Washington Trust for Historic Preservation company has reported experiencing targeted cyberattacks publicly.

Neither Washington Trust for Historic Preservation company nor Ohio History Connection company has reported experiencing or disclosing vulnerabilities publicly.

Neither Washington Trust for Historic Preservation nor Ohio History Connection holds any compliance certifications.

Neither company holds any compliance certifications.

Neither Washington Trust for Historic Preservation company nor Ohio History Connection company has publicly disclosed detailed information about the number of their subsidiaries.

Ohio History Connection company employs more people globally than Washington Trust for Historic Preservation company, reflecting its scale as a Museums, Historical Sites, and Zoos.

Neither Washington Trust for Historic Preservation nor Ohio History Connection holds SOC 2 Type 1 certification.

Neither Washington Trust for Historic Preservation nor Ohio History Connection holds SOC 2 Type 2 certification.

Neither Washington Trust for Historic Preservation nor Ohio History Connection holds ISO 27001 certification.

Neither Washington Trust for Historic Preservation nor Ohio History Connection holds PCI DSS certification.

Neither Washington Trust for Historic Preservation nor Ohio History Connection holds HIPAA certification.

Neither Washington Trust for Historic Preservation nor Ohio History Connection 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