Comparison Overview

Oregon Symphony

VS

Houston Symphony

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

Houston Symphony

615 Louisiana Street, Houston, TX, 77002, US
Last Update: 2025-12-10

The Houston Symphony is at the forefront of a new era of growth and transformation. With an ambitious vision for the future, we are committed to being a world-class orchestra and a cultural leader in Houston, creating extraordinary musical experiences for all. Our outstanding orchestra, dedicated staff and Board, and dynamic Music Director Juraj Valčuha provide the foundation for our success. Together, we will create a new era of musical excellence and community engagement that will inspire and enrich the lives of all who experience the Houston Symphony.

NAICS: 7111
NAICS Definition: Performing Arts Companies
Employees: 213
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/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
https://images.rankiteo.com/companyimages/houston-symphony.jpeg
Houston 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
Oregon Symphony
100%
Compliance Rate
0/4 Standards Verified
Houston Symphony
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Performing Arts Industry Average (This Year)

No incidents recorded for Oregon Symphony in 2025.

Incidents vs Performing Arts Industry Average (This Year)

No incidents recorded for Houston Symphony in 2025.

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

Oregon Symphony cyber incidents detection timeline including parent company and subsidiaries

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

Houston Symphony cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

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

No Incident

https://images.rankiteo.com/companyimages/houston-symphony.jpeg
Houston Symphony
Incidents

No Incident

FAQ

Houston Symphony company demonstrates a stronger AI Cybersecurity Score compared to Oregon Symphony company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

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

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

Neither Houston Symphony company nor Oregon Symphony company has reported experiencing a ransomware attack publicly.

Neither Houston Symphony company nor Oregon Symphony company has reported experiencing a data breach publicly.

Neither Houston Symphony company nor Oregon Symphony company has reported experiencing targeted cyberattacks publicly.

Neither Oregon Symphony company nor Houston Symphony company has reported experiencing or disclosing vulnerabilities publicly.

Neither Oregon Symphony nor Houston Symphony holds any compliance certifications.

Neither company holds any compliance certifications.

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

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

Neither Oregon Symphony nor Houston Symphony holds SOC 2 Type 1 certification.

Neither Oregon Symphony nor Houston Symphony holds SOC 2 Type 2 certification.

Neither Oregon Symphony nor Houston Symphony holds ISO 27001 certification.

Neither Oregon Symphony nor Houston Symphony holds PCI DSS certification.

Neither Oregon Symphony nor Houston Symphony holds HIPAA certification.

Neither Oregon Symphony nor Houston Symphony holds GDPR certification.

Latest Global CVEs (Not Company-Specific)

Description

LibreChat is a ChatGPT clone with additional features. In versions 0.8.0 and below, there is no handler for JSON parsing errors; SyntaxError from express.json() includes user input in the error message, which gets reflected in responses. User input (including HTML/JavaScript) can be exposed in error responses, creating an XSS risk if Content-Type isn't strictly enforced. This issue does not have a fix at the time of publication.

Risk Information
cvss4
Base: 5.3
Severity: LOW
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/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

LibreChat is a ChatGPT clone with additional features. In versions 0.8.0 and below, when creating prompts, JSON requests are sent to define and modify the prompts via PATCH endpoint for prompt groups (/api/prompts/groups/:groupId). However, the request bodies are not sufficiently validated for proper input, enabling users to modify prompts in a way that was not intended as part of the front end system. The patchPromptGroup function passes req.body directly to updatePromptGroup() without filtering sensitive fields. This issue is fixed in version 0.8.1.

Risk Information
cvss4
Base: 5.3
Severity: LOW
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/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

LibreChat is a ChatGPT clone with additional features. In versions 0.8.0 and below, when a user posts a question, the iconURL parameter of the POST request can be modified by an attacker. The malicious code is then stored in the chat which can then be shared to other users. When sharing chats with a potentially malicious “tracker”, resources loaded can lead to loss of privacy for users who view the chat link that is sent to them. This issue is fixed in version 0.8.1.

Risk Information
cvss4
Base: 8.6
Severity: LOW
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:H/VI:H/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
Description

MaxKB is an open-source AI assistant for enterprise. Versions 2.3.1 and below have improper file permissions which allow attackers to overwrite the built-in dynamic linker and other critical files, potentially resulting in privilege escalation. This issue is fixed in version 2.4.0.

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

MaxKB is an open-source AI assistant for enterprise. In versions 2.3.1 and below, the tool module allows an attacker to escape the sandbox environment and escalate privileges under certain concurrent conditions. This issue is fixed in version 2.4.0.

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