Comparison Overview

New Line Theatre

VS

Oregon Repertory Singers

New Line Theatre

3802-A Keokuk Street, Saint Louis, MO, 63116, US
Last Update: 2025-12-09

New Line Theatre, "The bad boy of musical theatre," was created in 1991 to involve the people of the St. Louis region in the creation and exploration of provocative, alternative, politically and socially relevant works of musical theatre – daring, muscular, intelligent theatre about politics, race, violence, drugs, sexuality, religion, art, obscenity, the media, and other contemporary issues. And a lot of four-letter words. And every now and then, a little nudity. And lots of rock and roll.

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

Oregon Repertory Singers

1730 SW Skyline Blvd, Portland, Oregon, 97221, US
Last Update: 2025-12-10
Between 750 and 799

Oregon Repertory Singers performs world-class music accessible to all. Our professional-caliber adult choir of over 90 members was recently lauded as “the city’s finest large choir.” Our education- and performance-based youth choir serving children ages 4-18 is one-of-a-kind in the Portland area. We are committed to nurturing the singers, listeners, and supporters of this generation and the next!

NAICS: 711
NAICS Definition:
Employees: 11
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/new-line-theatre.jpeg
New Line Theatre
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-repertory-singers.jpeg
Oregon Repertory Singers
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
New Line Theatre
100%
Compliance Rate
0/4 Standards Verified
Oregon Repertory Singers
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Performing Arts Industry Average (This Year)

No incidents recorded for New Line Theatre in 2025.

Incidents vs Performing Arts Industry Average (This Year)

No incidents recorded for Oregon Repertory Singers in 2025.

Incident History — New Line Theatre (X = Date, Y = Severity)

New Line Theatre cyber incidents detection timeline including parent company and subsidiaries

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

Oregon Repertory Singers cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/new-line-theatre.jpeg
New Line Theatre
Incidents

No Incident

https://images.rankiteo.com/companyimages/oregon-repertory-singers.jpeg
Oregon Repertory Singers
Incidents

No Incident

FAQ

Both New Line Theatre company and Oregon Repertory Singers company demonstrate a comparable AI Cybersecurity Score, with strong governance and monitoring frameworks in place.

Historically, Oregon Repertory Singers company has disclosed a higher number of cyber incidents compared to New Line Theatre company.

In the current year, Oregon Repertory Singers company and New Line Theatre company have not reported any cyber incidents.

Neither Oregon Repertory Singers company nor New Line Theatre company has reported experiencing a ransomware attack publicly.

Neither Oregon Repertory Singers company nor New Line Theatre company has reported experiencing a data breach publicly.

Neither Oregon Repertory Singers company nor New Line Theatre company has reported experiencing targeted cyberattacks publicly.

Neither New Line Theatre company nor Oregon Repertory Singers company has reported experiencing or disclosing vulnerabilities publicly.

Neither New Line Theatre nor Oregon Repertory Singers holds any compliance certifications.

Neither company holds any compliance certifications.

Neither New Line Theatre company nor Oregon Repertory Singers company has publicly disclosed detailed information about the number of their subsidiaries.

New Line Theatre company employs more people globally than Oregon Repertory Singers company, reflecting its scale as a Performing Arts.

Neither New Line Theatre nor Oregon Repertory Singers holds SOC 2 Type 1 certification.

Neither New Line Theatre nor Oregon Repertory Singers holds SOC 2 Type 2 certification.

Neither New Line Theatre nor Oregon Repertory Singers holds ISO 27001 certification.

Neither New Line Theatre nor Oregon Repertory Singers holds PCI DSS certification.

Neither New Line Theatre nor Oregon Repertory Singers holds HIPAA certification.

Neither New Line Theatre nor Oregon Repertory Singers 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