Comparison Overview

Playhouse on Park

VS

Theatre Bristol

Playhouse on Park

244 Park Rd, West Hartford, Connecticut, 06119, US
Last Update: 2025-12-12

Playhouse on Park, in West Hartford, CT, is managed under the direction of Playhouse Theatre Group, Inc. and has 163 seats surrounding a 3/4 thrust stage, offering audiences of all ages an intimate theatre experience. A year-round performance schedule is produced and/or presented by Playhouse Theatre Group, Inc. and includes: professional and community theatre; theatre for young audiences; new works and play readings; comedy and improvisation; cabarets and concerts; dance; educational opportunities led by resident and visiting artists; corporate events, special events and more!

NAICS: 711
NAICS Definition:
Employees: 26
Subsidiaries: 1
12-month incidents
0
Known data breaches
0
Attack type number
0

Theatre Bristol

82-84 York Road, Bristol, BS3 4AL, GB
Last Update: 2025-12-14
Between 750 and 799

We exist to support and improve live performance, to make it fairer, more equal and inclusive. We believe in the power of connecting people, sharing knowledge and resources, brokering relationships and advocating for best practice. Through this work we play a vital role in developing the live performance ecology of Bristol and the wider South West. Our vision is for live performance and performance makers to thrive; to be valued, resilient, and deeply connected to more people’s lives. We are here to up theatre’s game.

NAICS: 7111
NAICS Definition: Performing Arts Companies
Employees: 2
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/playhouse-on-park.jpeg
Playhouse on Park
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/theatre-bristol.jpeg
Theatre Bristol
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
Playhouse on Park
100%
Compliance Rate
0/4 Standards Verified
Theatre Bristol
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Performing Arts Industry Average (This Year)

No incidents recorded for Playhouse on Park in 2025.

Incidents vs Performing Arts Industry Average (This Year)

No incidents recorded for Theatre Bristol in 2025.

Incident History — Playhouse on Park (X = Date, Y = Severity)

Playhouse on Park cyber incidents detection timeline including parent company and subsidiaries

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

Theatre Bristol cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/playhouse-on-park.jpeg
Playhouse on Park
Incidents

No Incident

https://images.rankiteo.com/companyimages/theatre-bristol.jpeg
Theatre Bristol
Incidents

No Incident

FAQ

Playhouse on Park company demonstrates a stronger AI Cybersecurity Score compared to Theatre Bristol company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Historically, Theatre Bristol company has disclosed a higher number of cyber incidents compared to Playhouse on Park company.

In the current year, Theatre Bristol company and Playhouse on Park company have not reported any cyber incidents.

Neither Theatre Bristol company nor Playhouse on Park company has reported experiencing a ransomware attack publicly.

Neither Theatre Bristol company nor Playhouse on Park company has reported experiencing a data breach publicly.

Neither Theatre Bristol company nor Playhouse on Park company has reported experiencing targeted cyberattacks publicly.

Neither Playhouse on Park company nor Theatre Bristol company has reported experiencing or disclosing vulnerabilities publicly.

Neither Playhouse on Park nor Theatre Bristol holds any compliance certifications.

Neither company holds any compliance certifications.

Playhouse on Park company has more subsidiaries worldwide compared to Theatre Bristol company.

Playhouse on Park company employs more people globally than Theatre Bristol company, reflecting its scale as a Performing Arts.

Neither Playhouse on Park nor Theatre Bristol holds SOC 2 Type 1 certification.

Neither Playhouse on Park nor Theatre Bristol holds SOC 2 Type 2 certification.

Neither Playhouse on Park nor Theatre Bristol holds ISO 27001 certification.

Neither Playhouse on Park nor Theatre Bristol holds PCI DSS certification.

Neither Playhouse on Park nor Theatre Bristol holds HIPAA certification.

Neither Playhouse on Park nor Theatre Bristol 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