Comparison Overview

Oregon Zoo

VS

Canadian Museum of History

Oregon Zoo

4001 SW Canyon RD, None, Portland, OR, US, 97221
Last Update: 2026-01-23
View Profile
Between 700 and 749
http://www.oregonzoo.org

The Oregon Zoo connects communities to the wonder of wildlife to create a better future for all. We are a hub for science, conservation, education and animal well-being delivering the highest quality of care to 165 species and subspecies. Community supported since 1888, we are part of Metro, greater Portland’s regional government — inspiring and welcoming guests and community members of all ages, abilities and backgrounds.

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

Canadian Museum of History

100 Laurier Street, Gatineau, K1A 0W8, CA
Last Update: 2026-01-23
Between 750 and 799
https://www.historymuseum.ca

JOIN THE RENOWNED CANADIAN MUSEUM OF HISTORY YOUR COUNTRY. YOUR HISTORY. YOUR CAREER. The Museum is a place of endless discovery and thoughtful reflection about this country, its people and the world in which we live. We offer a remarkable range of career opportunities in the areas of research, collections management, project management, and creative development. As well, a variety of interesting career experiences, integral to the success of the Museum, employ people in a range of Museum-wide administrative, operational and service roles. Opportunities are found in finance, information technology, visitor and security services, corporate affairs, and human resources. The Museum is dedicated to preserving, promoting and exploring Canada’s rich history and cultural diversity, and strives to ensure a diverse, equitable and inclusive working environment.

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

Compliance Badges Comparison

Security & Compliance Standards Overview

https://images.rankiteo.com/companyimages/oregon-zoo.jpeg
Oregon Zoo
—
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/mch-cmh.jpeg
Canadian Museum of History
—
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
Oregon Zoo
100%
Compliance Rate
0/4 Standards Verified
Canadian Museum of History
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 Oregon Zoo in 2026.

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

No incidents recorded for Canadian Museum of History in 2026.

Incident History — Oregon Zoo (X = Date, Y = Severity)

Oregon Zoo cyber incidents detection timeline including parent company and subsidiaries

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

Canadian Museum of History cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/oregon-zoo.jpeg
Oregon Zoo
Incidents

Date Detected: 12/2023
Type:Breach
Attack Vector: Unauthorized Access
Blog: Blog
https://images.rankiteo.com/companyimages/mch-cmh.jpeg
Canadian Museum of History
Incidents

No Incident

FAQ

Canadian Museum of History company demonstrates a stronger AI Cybersecurity Score compared to Oregon Zoo company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Oregon Zoo company has historically faced a number of disclosed cyber incidents, whereas Canadian Museum of History company has not reported any.

In the current year, Canadian Museum of History company and Oregon Zoo company have not reported any cyber incidents.

Neither Canadian Museum of History company nor Oregon Zoo company has reported experiencing a ransomware attack publicly.

Oregon Zoo company has disclosed at least one data breach, while the other Canadian Museum of History company has not reported such incidents publicly.

Neither Canadian Museum of History company nor Oregon Zoo company has reported experiencing targeted cyberattacks publicly.

Neither Oregon Zoo company nor Canadian Museum of History company has reported experiencing or disclosing vulnerabilities publicly.

Neither Oregon Zoo nor Canadian Museum of History holds any compliance certifications.

Neither company holds any compliance certifications.

Canadian Museum of History company has more subsidiaries worldwide compared to Oregon Zoo company.

Canadian Museum of History company employs more people globally than Oregon Zoo company, reflecting its scale as a Museums, Historical Sites, and Zoos.

Neither Oregon Zoo nor Canadian Museum of History holds SOC 2 Type 1 certification.

Neither Oregon Zoo nor Canadian Museum of History holds SOC 2 Type 2 certification.

Neither Oregon Zoo nor Canadian Museum of History holds ISO 27001 certification.

Neither Oregon Zoo nor Canadian Museum of History holds PCI DSS certification.

Neither Oregon Zoo nor Canadian Museum of History holds HIPAA certification.

Neither Oregon Zoo nor Canadian Museum of History 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.

Published
Date
2026-01-22
Updated
Date
2026-01-22
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
References
Description

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

Published
Date
2026-01-22
Updated
Date
2026-01-22
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
References
Description

Azure Entra ID Elevation of Privilege Vulnerability

Published
Date
2026-01-22
Updated
Date
2026-01-22
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
References
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.

Published
Date
2026-01-22
Updated
Date
2026-01-22
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
References
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.

Published
Date
2026-01-22
Updated
Date
2026-01-22
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
References