Comparison Overview

Queensbury Theatre

VS

TheaterWorks Hartford

Queensbury Theatre

None
Last Update: 2025-12-09
Between 750 and 799

After more than 55 years, The Country Playhouse is drawing back the curtain to present a new look and name — Queensbury Theatre. We are rolling out the red carpet to bring you the finest in classic and contemporary theatre with our new state-of-the-art 250-seat main stage and our innovative black box theater. Now is your chance to share in the excitement! Take a seat and get in on the ground floor to help grow our vision for Houston community theatre excellence. We’re giving the cue for a new beginning at Queensbury Theatre — where the stage awaits.

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

TheaterWorks Hartford

233 Pearl St, Hartford, CT, 06103, US
Last Update: 2025-12-11
Between 750 and 799

TheaterWorks Hartford (TWH), located in the heart of Connecticut's capital city, takes pride in its commitment to important storytelling. In a newly renovated space that we own, TWH produces 5-6 productions a season. Our 188-seat theater invites some of the most exciting plays, playwrights, and creative teams to share the intimacy of our modified thrust, which serves as a unique "hug" to the shared humanity on stage and in the audience.

NAICS: 711
NAICS Definition:
Employees: 26
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/queensbury-theatre.jpeg
Queensbury 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/theaterworks-hartford.jpeg
TheaterWorks Hartford
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
Queensbury Theatre
100%
Compliance Rate
0/4 Standards Verified
TheaterWorks Hartford
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Performing Arts Industry Average (This Year)

No incidents recorded for Queensbury Theatre in 2025.

Incidents vs Performing Arts Industry Average (This Year)

No incidents recorded for TheaterWorks Hartford in 2025.

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

Queensbury Theatre cyber incidents detection timeline including parent company and subsidiaries

Incident History — TheaterWorks Hartford (X = Date, Y = Severity)

TheaterWorks Hartford cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/queensbury-theatre.jpeg
Queensbury Theatre
Incidents

No Incident

https://images.rankiteo.com/companyimages/theaterworks-hartford.jpeg
TheaterWorks Hartford
Incidents

No Incident

FAQ

Queensbury Theatre company demonstrates a stronger AI Cybersecurity Score compared to TheaterWorks Hartford company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Historically, TheaterWorks Hartford company has disclosed a higher number of cyber incidents compared to Queensbury Theatre company.

In the current year, TheaterWorks Hartford company and Queensbury Theatre company have not reported any cyber incidents.

Neither TheaterWorks Hartford company nor Queensbury Theatre company has reported experiencing a ransomware attack publicly.

Neither TheaterWorks Hartford company nor Queensbury Theatre company has reported experiencing a data breach publicly.

Neither TheaterWorks Hartford company nor Queensbury Theatre company has reported experiencing targeted cyberattacks publicly.

Neither Queensbury Theatre company nor TheaterWorks Hartford company has reported experiencing or disclosing vulnerabilities publicly.

Neither Queensbury Theatre nor TheaterWorks Hartford holds any compliance certifications.

Neither company holds any compliance certifications.

Neither Queensbury Theatre company nor TheaterWorks Hartford company has publicly disclosed detailed information about the number of their subsidiaries.

TheaterWorks Hartford company employs more people globally than Queensbury Theatre company, reflecting its scale as a Performing Arts.

Neither Queensbury Theatre nor TheaterWorks Hartford holds SOC 2 Type 1 certification.

Neither Queensbury Theatre nor TheaterWorks Hartford holds SOC 2 Type 2 certification.

Neither Queensbury Theatre nor TheaterWorks Hartford holds ISO 27001 certification.

Neither Queensbury Theatre nor TheaterWorks Hartford holds PCI DSS certification.

Neither Queensbury Theatre nor TheaterWorks Hartford holds HIPAA certification.

Neither Queensbury Theatre nor TheaterWorks Hartford 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