Comparison Overview

Berliner Ensemble

VS

Shakespeare & Company

Berliner Ensemble

1 Bertolt-Brecht-Platz, Berlin, 10117, DE
Last Update: 2025-12-09
Between 800 and 849

Das Berliner Ensemble zählt zu den renommiertesten und traditionsreichsten Bühnen Deutschlands. Das Theater am Schiffbauerdamm, seit 1954 benannt nach Bertolt Brechts weltberühmter Kompanie, hat als Berliner Ensemble Theatergeschichte geschrieben. In seiner über 130-jährigen Geschichte hat das Haus am Schiffbauerdamm sich stets mit aktuellen gesellschaftsrelevanten Fragen auseinandergesetzt und legt seit der Intendanz von Oliver Reese den Fokus wieder verstärkt auf zeitgenössische Texte und aktuelle Themen.

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

Shakespeare & Company

70 Kemble St, Lenox, MA, 01240, US
Last Update: 2025-12-09
Between 750 and 799

The mission of Shakespeare & Company is to deliver a sustainable and vital program of Performance, Training, and Education, integrated for the deepened experience of the artists, the audience, the Company, and the community. We embrace the core values of Shakespeare’s work: collaboration, commitment to language, visceral experience, and classical ideals, expressed with physical prowess and an embodied contemporary voice.

NAICS: 711
NAICS Definition:
Employees: 132
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/berliner-ensemble.jpeg
Berliner Ensemble
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/shakespeare-&-company.jpeg
Shakespeare & Company
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
Berliner Ensemble
100%
Compliance Rate
0/4 Standards Verified
Shakespeare & Company
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Performing Arts Industry Average (This Year)

No incidents recorded for Berliner Ensemble in 2025.

Incidents vs Performing Arts Industry Average (This Year)

No incidents recorded for Shakespeare & Company in 2025.

Incident History — Berliner Ensemble (X = Date, Y = Severity)

Berliner Ensemble cyber incidents detection timeline including parent company and subsidiaries

Incident History — Shakespeare & Company (X = Date, Y = Severity)

Shakespeare & Company cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/berliner-ensemble.jpeg
Berliner Ensemble
Incidents

Date Detected: 12/2023
Type:Cyber Attack
Motivation: Blackmail
Blog: Blog
https://images.rankiteo.com/companyimages/shakespeare-&-company.jpeg
Shakespeare & Company
Incidents

No Incident

FAQ

Berliner Ensemble company demonstrates a stronger AI Cybersecurity Score compared to Shakespeare & Company company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Berliner Ensemble company has historically faced a number of disclosed cyber incidents, whereas Shakespeare & Company company has not reported any.

In the current year, Shakespeare & Company company and Berliner Ensemble company have not reported any cyber incidents.

Neither Shakespeare & Company company nor Berliner Ensemble company has reported experiencing a ransomware attack publicly.

Neither Shakespeare & Company company nor Berliner Ensemble company has reported experiencing a data breach publicly.

Berliner Ensemble company has reported targeted cyberattacks, while Shakespeare & Company company has not reported such incidents publicly.

Neither Berliner Ensemble company nor Shakespeare & Company company has reported experiencing or disclosing vulnerabilities publicly.

Neither Berliner Ensemble nor Shakespeare & Company holds any compliance certifications.

Neither company holds any compliance certifications.

Neither Berliner Ensemble company nor Shakespeare & Company company has publicly disclosed detailed information about the number of their subsidiaries.

Shakespeare & Company company employs more people globally than Berliner Ensemble company, reflecting its scale as a Performing Arts.

Neither Berliner Ensemble nor Shakespeare & Company holds SOC 2 Type 1 certification.

Neither Berliner Ensemble nor Shakespeare & Company holds SOC 2 Type 2 certification.

Neither Berliner Ensemble nor Shakespeare & Company holds ISO 27001 certification.

Neither Berliner Ensemble nor Shakespeare & Company holds PCI DSS certification.

Neither Berliner Ensemble nor Shakespeare & Company holds HIPAA certification.

Neither Berliner Ensemble nor Shakespeare & Company 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