Comparison Overview

Portland Stage

VS

Houston Symphony

Portland Stage

25A Forest Ave, Portland, Maine, 04101, US
Last Update: 2025-12-09
Between 750 and 799

Our Mission Located in Portland, Maine, we are the leading professional theater in Northern New England. PORTLAND STAGE entertains, educates and engages its audiences by producing a wide range of artistic works and programs that explore basic human issues and concerns relevant to the communities served by the theater. Our guiding principle is to promote creativity and dialogue among artists, staff, board and audience.

NAICS: 711
NAICS Definition:
Employees: 65
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/portland-stage.jpeg
Portland Stage
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
Portland Stage
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 Portland Stage in 2025.

Incidents vs Performing Arts Industry Average (This Year)

No incidents recorded for Houston Symphony in 2025.

Incident History — Portland Stage (X = Date, Y = Severity)

Portland Stage 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/portland-stage.jpeg
Portland Stage
Incidents

No Incident

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

No Incident

FAQ

Both Portland Stage company and Houston Symphony company demonstrate a comparable AI Cybersecurity Score, with strong governance and monitoring frameworks in place.

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

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

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

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

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

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

Neither Portland Stage nor Houston Symphony holds any compliance certifications.

Neither company holds any compliance certifications.

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

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

Neither Portland Stage nor Houston Symphony holds SOC 2 Type 1 certification.

Neither Portland Stage nor Houston Symphony holds SOC 2 Type 2 certification.

Neither Portland Stage nor Houston Symphony holds ISO 27001 certification.

Neither Portland Stage nor Houston Symphony holds PCI DSS certification.

Neither Portland Stage nor Houston Symphony holds HIPAA certification.

Neither Portland Stage nor Houston 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