Comparison Overview

Portland Museum of Art

VS

Anchorage Museum

Portland Museum of Art

7 Congress Square, Portland, ME, 04101, US
Last Update: 2025-12-03
Between 750 and 799

With an extensive collection and nationally renowned exhibitions, the Portland Museum of Art is the cultural heart of Portland, Maine. The PMA boasts significant holdings of American, European, and contemporary art, as well as iconic works from Maine—highlighting the rich artistic tradition of the state and its artists. The museum brings it all to life with unparalleled programming. From special members events, Free School Tours, and a commitment to family activities to PMA Films, curator talks, and tours of the Winslow Homer Studio—it’s all happening at the PMA.

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

Anchorage Museum

625 C Street, Anchorage, Alaska, 99501, US
Last Update: 2025-12-01

The Anchorage Museum shares the art, history, culture, and stories of Alaska and the North from diverse perspectives through exhibitions, public programs, and community projects focused on people, place, planet and potential. Located in Anchorage, Alaska, the museum sits on the traditional homeland of the Dena’ina Eklutna. Learn more at www.anchoragemuseum.org. SUMMER HOURS May 1 through Sept. 30 10 a.m. to 6 p.m. every day WINTER HOURS Oct. 1 through April 30 10 a.m. to 6 p.m. Tuesday-Saturday Noon to 6 p.m. Sunday Closed Monday

NAICS: 712
NAICS Definition: Museums, Historical Sites, and Similar Institutions
Employees: 85
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/portland-museum-of-art.jpeg
Portland Museum of Art
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/anchorage-museum.jpeg
Anchorage 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
Portland Museum of Art
100%
Compliance Rate
0/4 Standards Verified
Anchorage 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 Portland Museum of Art in 2025.

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

No incidents recorded for Anchorage Museum in 2025.

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

Portland Museum of Art cyber incidents detection timeline including parent company and subsidiaries

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

Anchorage Museum cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/portland-museum-of-art.jpeg
Portland Museum of Art
Incidents

No Incident

https://images.rankiteo.com/companyimages/anchorage-museum.jpeg
Anchorage Museum
Incidents

No Incident

FAQ

Both Portland Museum of Art company and Anchorage Museum company demonstrate a comparable AI Cybersecurity Score, with strong governance and monitoring frameworks in place.

Historically, Anchorage Museum company has disclosed a higher number of cyber incidents compared to Portland Museum of Art company.

In the current year, Anchorage Museum company and Portland Museum of Art company have not reported any cyber incidents.

Neither Anchorage Museum company nor Portland Museum of Art company has reported experiencing a ransomware attack publicly.

Neither Anchorage Museum company nor Portland Museum of Art company has reported experiencing a data breach publicly.

Neither Anchorage Museum company nor Portland Museum of Art company has reported experiencing targeted cyberattacks publicly.

Neither Portland Museum of Art company nor Anchorage Museum company has reported experiencing or disclosing vulnerabilities publicly.

Neither Portland Museum of Art nor Anchorage Museum holds any compliance certifications.

Neither company holds any compliance certifications.

Neither Portland Museum of Art company nor Anchorage Museum company has publicly disclosed detailed information about the number of their subsidiaries.

Portland Museum of Art company employs more people globally than Anchorage Museum company, reflecting its scale as a Museums, Historical Sites, and Zoos.

Neither Portland Museum of Art nor Anchorage Museum holds SOC 2 Type 1 certification.

Neither Portland Museum of Art nor Anchorage Museum holds SOC 2 Type 2 certification.

Neither Portland Museum of Art nor Anchorage Museum holds ISO 27001 certification.

Neither Portland Museum of Art nor Anchorage Museum holds PCI DSS certification.

Neither Portland Museum of Art nor Anchorage Museum holds HIPAA certification.

Neither Portland Museum of Art nor Anchorage Museum 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