Comparison Overview

The Pen Museum

VS

Wing Luke Museum of the Asian Pacific American Experience

The Pen Museum

60 Frederick Street, Birmingham, England, undefined, GB
Last Update: 2026-01-22
Between 750 and 799

Making steel pen nibs in Birmingham during the Victorian era was a major industry with 129 companies employing circa 8,000 workers (mainly women). By visiting the Pen Museum, you will discover a wide range of fascinating objects and details that help tell the story of Birmingham’s pen trade and its important legacy including the link between a prominent pen manufacturer (Josiah Mason) and the establishment of the University of Birmingham. Throughout the Museum there are a range of activities for people of all ages to enjoy including writing with a quill and ink, using typewriters plus an exciting opportunity to make your own nib using the same machinery once operated by women workers in the 19th century. We still need your support. As a charity, we totally depend on our dedicated, experienced and loyal team of volunteers along with the generosity of donors and supporters. Our wonderful visitors also provide regular income to help keep this part of Birmingham’s important heritage alive. Being the world’s only museum dedicated to the history of Birmingham’s steel pen trade and its global impact, we narrate an important part of Birmingham’s industrial development. Birmingham dominated the world’s production of steel pens in the mid to late 19th century, which, had a significant impact on improving literacy on a global basis. It has been estimated that the City produced approximately three quarters of the world’s pens in the mid to late 19th century. But it is more than a museum, it’s also a place of discovery and inspiration through our displays, activities and events. Our aim is to engage and inspire visitors, provide outreach in terms of history, deliver writing skills workshops with a new focus on digitising part of our collection and archive to increase public engagement and accessibility to as wide an audience as possible.

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

Wing Luke Museum of the Asian Pacific American Experience

719 S King St, Seattle, WA, 98104, US
Last Update: 2026-01-22
Between 750 and 799

Step into a uniquely American story. The Wing Luke Museum of the Asian Pacific American Experience is dedicated to immersing people in uniquely-American stories of survival, success, struggle, conflict, compassion and hope. The Museum is in the heart of Seattle’s vibrant Chinatown-International District, and includes the very hotel where countless immigrants first found a home, a meal, and refuge. As our nation’s only museum devoted to the Asian Pacific American experience, it’s one of the few places that can truly give you a new perspective on what it means to be American. The Wing is a Smithsonian Affiliate, a partnership with the Smithsonian Institution.

NAICS: 712
NAICS Definition: Museums, Historical Sites, and Similar Institutions
Employees: 53
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-pen-museum.jpeg
The Pen 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/wing-luke-museum-of-the-asian-pacific-american-experience.jpeg
Wing Luke Museum of the Asian Pacific American Experience
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 Pen Museum
100%
Compliance Rate
0/4 Standards Verified
Wing Luke Museum of the Asian Pacific American Experience
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 Pen Museum in 2026.

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

No incidents recorded for Wing Luke Museum of the Asian Pacific American Experience in 2026.

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

The Pen Museum cyber incidents detection timeline including parent company and subsidiaries

Incident History — Wing Luke Museum of the Asian Pacific American Experience (X = Date, Y = Severity)

Wing Luke Museum of the Asian Pacific American Experience cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/the-pen-museum.jpeg
The Pen Museum
Incidents

No Incident

https://images.rankiteo.com/companyimages/wing-luke-museum-of-the-asian-pacific-american-experience.jpeg
Wing Luke Museum of the Asian Pacific American Experience
Incidents

No Incident

FAQ

Both The Pen Museum company and Wing Luke Museum of the Asian Pacific American Experience company demonstrate a comparable AI Cybersecurity Score, with strong governance and monitoring frameworks in place.

Historically, Wing Luke Museum of the Asian Pacific American Experience company has disclosed a higher number of cyber incidents compared to The Pen Museum company.

In the current year, Wing Luke Museum of the Asian Pacific American Experience company and The Pen Museum company have not reported any cyber incidents.

Neither Wing Luke Museum of the Asian Pacific American Experience company nor The Pen Museum company has reported experiencing a ransomware attack publicly.

Neither Wing Luke Museum of the Asian Pacific American Experience company nor The Pen Museum company has reported experiencing a data breach publicly.

Neither Wing Luke Museum of the Asian Pacific American Experience company nor The Pen Museum company has reported experiencing targeted cyberattacks publicly.

Neither The Pen Museum company nor Wing Luke Museum of the Asian Pacific American Experience company has reported experiencing or disclosing vulnerabilities publicly.

Neither The Pen Museum nor Wing Luke Museum of the Asian Pacific American Experience holds any compliance certifications.

Neither company holds any compliance certifications.

Neither The Pen Museum company nor Wing Luke Museum of the Asian Pacific American Experience company has publicly disclosed detailed information about the number of their subsidiaries.

Wing Luke Museum of the Asian Pacific American Experience company employs more people globally than The Pen Museum company, reflecting its scale as a Museums, Historical Sites, and Zoos.

Neither The Pen Museum nor Wing Luke Museum of the Asian Pacific American Experience holds SOC 2 Type 1 certification.

Neither The Pen Museum nor Wing Luke Museum of the Asian Pacific American Experience holds SOC 2 Type 2 certification.

Neither The Pen Museum nor Wing Luke Museum of the Asian Pacific American Experience holds ISO 27001 certification.

Neither The Pen Museum nor Wing Luke Museum of the Asian Pacific American Experience holds PCI DSS certification.

Neither The Pen Museum nor Wing Luke Museum of the Asian Pacific American Experience holds HIPAA certification.

Neither The Pen Museum nor Wing Luke Museum of the Asian Pacific American Experience holds GDPR certification.

Latest Global CVEs (Not Company-Specific)

Description

Backstage is an open framework for building developer portals, and @backstage/backend-defaults provides the default implementations and setup for a standard Backstage backend app. Prior to versions 0.12.2, 0.13.2, 0.14.1, and 0.15.0, the `FetchUrlReader` component, used by the catalog and other plugins to fetch content from URLs, followed HTTP redirects automatically. This allowed an attacker who controls a host listed in `backend.reading.allow` to redirect requests to internal or sensitive URLs that are not on the allowlist, bypassing the URL allowlist security control. This is a Server-Side Request Forgery (SSRF) vulnerability that could allow access to internal resources, but it does not allow attackers to include additional request headers. This vulnerability is fixed in `@backstage/backend-defaults` version 0.12.2, 0.13.2, 0.14.1, and 0.15.0. Users should upgrade to this version or later. Some workarounds are available. Restrict `backend.reading.allow` to only trusted hosts that you control and that do not issue redirects, ensure allowed hosts do not have open redirect vulnerabilities, and/or use network-level controls to block access from Backstage to sensitive internal endpoints.

Risk Information
cvss3
Base: 3.5
Severity: HIGH
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:L/I:N/A:N
Description

Backstage is an open framework for building developer portals, and @backstage/cli-common provides config loading functionality used by the backend and command line interface of Backstage. Prior to version 0.1.17, the `resolveSafeChildPath` utility function in `@backstage/backend-plugin-api`, which is used to prevent path traversal attacks, failed to properly validate symlink chains and dangling symlinks. An attacker could bypass the path validation via symlink chains (creating `link1 → link2 → /outside` where intermediate symlinks eventually resolve outside the allowed directory) and dangling symlinks (creating symlinks pointing to non-existent paths outside the base directory, which would later be created during file operations). This function is used by Scaffolder actions and other backend components to ensure file operations stay within designated directories. This vulnerability is fixed in `@backstage/backend-plugin-api` version 0.1.17. Users should upgrade to this version or later. Some workarounds are available. Run Backstage in a containerized environment with limited filesystem access and/or restrict template creation to trusted users.

Risk Information
cvss3
Base: 6.3
Severity: HIGH
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:N/A:N
Description

Backstage is an open framework for building developer portals. Multiple Scaffolder actions and archive extraction utilities were vulnerable to symlink-based path traversal attacks. An attacker with access to create and execute Scaffolder templates could exploit symlinks to read arbitrary files via the `debug:log` action by creating a symlink pointing to sensitive files (e.g., `/etc/passwd`, configuration files, secrets); delete arbitrary files via the `fs:delete` action by creating symlinks pointing outside the workspace, and write files outside the workspace via archive extraction (tar/zip) containing malicious symlinks. This affects any Backstage deployment where users can create or execute Scaffolder templates. This vulnerability is fixed in `@backstage/backend-defaults` versions 0.12.2, 0.13.2, 0.14.1, and 0.15.0; `@backstage/plugin-scaffolder-backend` versions 2.2.2, 3.0.2, and 3.1.1; and `@backstage/plugin-scaffolder-node` versions 0.11.2 and 0.12.3. Users should upgrade to these versions or later. Some workarounds are available. Follow the recommendation in the Backstage Threat Model to limit access to creating and updating templates, restrict who can create and execute Scaffolder templates using the permissions framework, audit existing templates for symlink usage, and/or run Backstage in a containerized environment with limited filesystem access.

Risk Information
cvss3
Base: 7.1
Severity: HIGH
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:N/A:L
Description

FastAPI Api Key provides a backend-agnostic library that provides an API key system. Version 1.1.0 has a timing side-channel vulnerability in verify_key(). The method applied a random delay only on verification failures, allowing an attacker to statistically distinguish valid from invalid API keys by measuring response latencies. With enough repeated requests, an adversary could infer whether a key_id corresponds to a valid key, potentially accelerating brute-force or enumeration attacks. All users relying on verify_key() for API key authentication prior to the fix are affected. Users should upgrade to version 1.1.0 to receive a patch. The patch applies a uniform random delay (min_delay to max_delay) to all responses regardless of outcome, eliminating the timing correlation. Some workarounds are available. Add an application-level fixed delay or random jitter to all authentication responses (success and failure) before the fix is applied and/or use rate limiting to reduce the feasibility of statistical timing attacks.

Risk Information
cvss3
Base: 3.7
Severity: HIGH
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N
Description

The Flux Operator is a Kubernetes CRD controller that manages the lifecycle of CNCF Flux CD and the ControlPlane enterprise distribution. Starting in version 0.36.0 and prior to version 0.40.0, a privilege escalation vulnerability exists in the Flux Operator Web UI authentication code that allows an attacker to bypass Kubernetes RBAC impersonation and execute API requests with the operator's service account privileges. In order to be vulnerable, cluster admins must configure the Flux Operator with an OIDC provider that issues tokens lacking the expected claims (e.g., `email`, `groups`), or configure custom CEL expressions that can evaluate to empty values. After OIDC token claims are processed through CEL expressions, there is no validation that the resulting `username` and `groups` values are non-empty. When both values are empty, the Kubernetes client-go library does not add impersonation headers to API requests, causing them to be executed with the flux-operator service account's credentials instead of the authenticated user's limited permissions. This can result in privilege escalation, data exposure, and/or information disclosure. Version 0.40.0 patches the issue.

Risk Information
cvss3
Base: 5.3
Severity: HIGH
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N