Comparison Overview

20 Stories High

VS

Oregon Symphony

20 Stories High

Toxteth TV, Liverpool, undefined, L8 1XE, US
Last Update: 2025-12-09

20 Stories High make theatre with… young people from excluded communities, emerging & world-class artists to tell stories that are… contemporary, youthful, authentic, melodic, gritty, poetic, rebellious, cheeky original, visual, challenging, tender anarchic, diverse, eclectic, bass-heavy, political, funny, collaborative… and heart-felt. We bring young people into theatre venues and go out into their communities. We hail from Liverpool, but our reach is national We believe everybody’s got a story to tell...and their own way of telling it...

NAICS: 7111
NAICS Definition: Performing Arts Companies
Employees: 28
Subsidiaries: 0
12-month incidents
0
Known data breaches
0
Attack type number
0

Oregon Symphony

921 SW Washington St, Portland, Oregon, undefined, US
Last Update: 2025-12-13
Between 750 and 799

The Oregon Symphony is Portland’s largest performing arts organization and the oldest American orchestra west of the Mississippi. Led by Music Director David Danzmayr, it performs with many of the world’s top musicians and offers the best of orchestral music – classical to pops to cutting-edge contemporary – to growing audiences in Portland and across Oregon. The orchestra consists of 76 full-time musicians who perform more than 80 concerts each year in downtown Portland’s historic Arlene Schnitzer Concert Hall, to draw an enthusiastic audience of more than 225,000 people annually. Appointed in 2023, the Oregon Symphony's President and CEO is Isaac Thompson.

NAICS: 711
NAICS Definition:
Employees: 128
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/20-stories-high.jpeg
20 Stories High
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/oregon-symphony.jpeg
Oregon Symphony
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
20 Stories High
100%
Compliance Rate
0/4 Standards Verified
Oregon Symphony
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Performing Arts Industry Average (This Year)

No incidents recorded for 20 Stories High in 2025.

Incidents vs Performing Arts Industry Average (This Year)

No incidents recorded for Oregon Symphony in 2025.

Incident History — 20 Stories High (X = Date, Y = Severity)

20 Stories High cyber incidents detection timeline including parent company and subsidiaries

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

Oregon Symphony cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/20-stories-high.jpeg
20 Stories High
Incidents

No Incident

https://images.rankiteo.com/companyimages/oregon-symphony.jpeg
Oregon Symphony
Incidents

No Incident

FAQ

Both 20 Stories High company and Oregon Symphony company demonstrate a comparable AI Cybersecurity Score, with strong governance and monitoring frameworks in place.

Historically, Oregon Symphony company has disclosed a higher number of cyber incidents compared to 20 Stories High company.

In the current year, Oregon Symphony company and 20 Stories High company have not reported any cyber incidents.

Neither Oregon Symphony company nor 20 Stories High company has reported experiencing a ransomware attack publicly.

Neither Oregon Symphony company nor 20 Stories High company has reported experiencing a data breach publicly.

Neither Oregon Symphony company nor 20 Stories High company has reported experiencing targeted cyberattacks publicly.

Neither 20 Stories High company nor Oregon Symphony company has reported experiencing or disclosing vulnerabilities publicly.

Neither 20 Stories High nor Oregon Symphony holds any compliance certifications.

Neither company holds any compliance certifications.

Neither 20 Stories High company nor Oregon Symphony company has publicly disclosed detailed information about the number of their subsidiaries.

Oregon Symphony company employs more people globally than 20 Stories High company, reflecting its scale as a Performing Arts.

Neither 20 Stories High nor Oregon Symphony holds SOC 2 Type 1 certification.

Neither 20 Stories High nor Oregon Symphony holds SOC 2 Type 2 certification.

Neither 20 Stories High nor Oregon Symphony holds ISO 27001 certification.

Neither 20 Stories High nor Oregon Symphony holds PCI DSS certification.

Neither 20 Stories High nor Oregon Symphony holds HIPAA certification.

Neither 20 Stories High nor Oregon Symphony holds GDPR certification.

Latest Global CVEs (Not Company-Specific)

Description

NXLog Agent before 6.11 can load a file specified by the OPENSSL_CONF environment variable.

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

uriparser through 0.9.9 allows unbounded recursion and stack consumption, as demonstrated by ParseMustBeSegmentNzNc with large input containing many commas.

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

A vulnerability was detected in Mayan EDMS up to 4.10.1. The affected element is an unknown function of the file /authentication/. The manipulation results in cross site scripting. The attack may be performed from remote. The exploit is now public and may be used. Upgrading to version 4.10.2 is sufficient to fix this issue. You should upgrade the affected component. The vendor confirms that this is "[f]ixed in version 4.10.2". Furthermore, that "[b]ackports for older versions in process and will be out as soon as their respective CI pipelines complete."

Risk Information
cvss2
Base: 5.0
Severity: LOW
AV:N/AC:L/Au:N/C:N/I:P/A:N
cvss3
Base: 4.3
Severity: LOW
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N
cvss4
Base: 5.3
Severity: LOW
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:P/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

MJML through 4.18.0 allows mj-include directory traversal to test file existence and (in the type="css" case) read files. NOTE: this issue exists because of an incomplete fix for CVE-2020-12827.

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

A half-blind Server Side Request Forgery (SSRF) vulnerability exists in kube-controller-manager when using the in-tree Portworx StorageClass. This vulnerability allows authorized users to leak arbitrary information from unprotected endpoints in the control plane’s host network (including link-local or loopback services).

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