Comparison Overview

Oxford Playhouse

VS

California Symphony

Oxford Playhouse

Beaumont Street, Oxford, England, OX1 2, GB
Last Update: 2025-12-10
View Profile
Between 750 and 799
http://oxfordplayhouse.com

Positioned at the cultural heart of Oxfordshire, Oxford Playhouse inspires, engages and entertains a wide-reaching and diverse audience. It presents, produces and tours the highest quality middle-scale, small-scale and off-site theatre; supports and nurtures artists to make work; creates imaginative and ambitious participation opportunities for children and young people and provides exceptional cultural experiences for all.

NAICS: 711
NAICS Definition:
Employees: 62
Subsidiaries: 0
12-month incidents
0
Known data breaches
0
Attack type number
0
View Profile

California Symphony

100 Pringle Ave, Walnut Creek, California, 94596, US
Last Update: 2025-12-14
Between 750 and 799
http://www.californiasymphony.org

California Symphony is distinguished by its position as "a model for regional orchestras" (Mercury News), its contribution to the classical music tradition through its innovative approach to concerts, its commitment to lifelong education for both the children and adults in its community, and its impact on the American classical music canon through the talent being fostered via California Symphony’s nationally recognized Young American Composer Residency.

NAICS: 711
NAICS Definition:
Employees: 59
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/oxford-playhouse.jpeg
Oxford Playhouse
—
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/the-california-symphony-orchestra.jpeg
California 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
Oxford Playhouse
100%
Compliance Rate
0/4 Standards Verified
California Symphony
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Performing Arts Industry Average (This Year)

No incidents recorded for Oxford Playhouse in 2025.

Incidents vs Performing Arts Industry Average (This Year)

No incidents recorded for California Symphony in 2025.

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

Oxford Playhouse cyber incidents detection timeline including parent company and subsidiaries

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

California Symphony cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/oxford-playhouse.jpeg
Oxford Playhouse
Incidents

No Incident

https://images.rankiteo.com/companyimages/the-california-symphony-orchestra.jpeg
California Symphony
Incidents

No Incident

FAQ

Both Oxford Playhouse company and California Symphony company demonstrate a comparable AI Cybersecurity Score, with strong governance and monitoring frameworks in place.

Historically, California Symphony company has disclosed a higher number of cyber incidents compared to Oxford Playhouse company.

In the current year, California Symphony company and Oxford Playhouse company have not reported any cyber incidents.

Neither California Symphony company nor Oxford Playhouse company has reported experiencing a ransomware attack publicly.

Neither California Symphony company nor Oxford Playhouse company has reported experiencing a data breach publicly.

Neither California Symphony company nor Oxford Playhouse company has reported experiencing targeted cyberattacks publicly.

Neither Oxford Playhouse company nor California Symphony company has reported experiencing or disclosing vulnerabilities publicly.

Neither Oxford Playhouse nor California Symphony holds any compliance certifications.

Neither company holds any compliance certifications.

Neither Oxford Playhouse company nor California Symphony company has publicly disclosed detailed information about the number of their subsidiaries.

Oxford Playhouse company employs more people globally than California Symphony company, reflecting its scale as a Performing Arts.

Neither Oxford Playhouse nor California Symphony holds SOC 2 Type 1 certification.

Neither Oxford Playhouse nor California Symphony holds SOC 2 Type 2 certification.

Neither Oxford Playhouse nor California Symphony holds ISO 27001 certification.

Neither Oxford Playhouse nor California Symphony holds PCI DSS certification.

Neither Oxford Playhouse nor California Symphony holds HIPAA certification.

Neither Oxford Playhouse nor California 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.

Published
Date
2025-12-14
Updated
Date
2025-12-14
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
References
Description

uriparser through 0.9.9 allows unbounded recursion and stack consumption, as demonstrated by ParseMustBeSegmentNzNc with large input containing many commas.

Published
Date
2025-12-14
Updated
Date
2025-12-14
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
References
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."

Published
Date
2025-12-14
Updated
Date
2025-12-14
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
References
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.

Published
Date
2025-12-14
Updated
Date
2025-12-14
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
References
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).

Published
Date
2025-12-14
Updated
Date
2025-12-14
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
References