Comparison Overview

Seattle Theatre Group

VS

Lamb's Players Theatre

Seattle Theatre Group

None, None, None, None, US, None
Last Update: 2025-12-18
Between 750 and 799

Seattle Theatre Group® is a 501(c)(3) non-profit arts organization. Mission: To create enriching experiences in the arts, engage diverse communities, and steward historic theatres. Vision: STG is the people’s theatre. All are welcomed and represented. Values Statement: We value Art: Art connects us. It allows us to explore all aspects of our humanity, to debate, to celebrate and to grow. We value Community: It is our role to advocate for greater participation in the arts, reduce barriers, and include diverse People, Cultures and Perspectives on our stages, in our audiences and within our staff, volunteers and board. We value Service: We are committed to caring relationships with patrons, partners, artists and staff. We value Learning for All: We deepen connection to art when we inspire the greater community through education, performance opportunities and healing. We value our Team: We believe in the power of passionate people who care for our mission and each other. We value Stewardship: We make the best use of our resources, effectively and sustainably serve our mission, and preserve our assets. STG presents an average of 700 events annually at The Paramount, The Moore, and The Neptune Theatres as well as at venues throughout the region. Broadway productions, concerts, dance, theatre, lectures, education, community, film, and other enrichment programs can be found in our venues. A multitude of artists and performers, partner organizations, donors and foundations, volunteers, and most of all – our patrons, make it possible for STG's mission to be fulfilled.

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

Lamb's Players Theatre

1126 Loma Avenue, Coronado, CA, 92118, US
Last Update: 2025-12-12
Between 750 and 799

Lamb’s Players Theatre is one of San Diego’s leading professional non-profit theatres, now in its 41st year. The company produces in two of the region’s premier locations: San Diego’s vibrant downtown Gaslamp Quarter, and the beautiful island community of Coronado. In the Gaslamp Quarter, Lamb’s Players produces longer-running productions at the Horton Grand Theatre, an intimate 250-seat proscenium theatre located steps away from dozens of restaurants and nightspots. In Coronado, the theatre presents a full subscription season in its gorgeous 350-seat theatre within walking distance of numerous restaurants and the historic Hotel del Coronado. San Diego’s third largest theatre company, Lamb’s Players Theatre is one of only a handful of artist-directed ensemble theatres in the nation. The theatre is committed to the tradition of “repertory” theatre, maintaining both a long-term ensemble of resident actors and a body of work to which they frequently return. In addition to producing classics and lesser-known gems of the theatre, Lamb’s Players is committed to the development of new work. The theatre also has a special interest in exploring spiritual issues for a diverse mainstream audience.

NAICS: 711
NAICS Definition:
Employees: 49
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/seattle-theatre-group.jpeg
Seattle Theatre Group
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/lamb's-players-theatre.jpeg
Lamb's Players 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
Compliance Summary
Seattle Theatre Group
100%
Compliance Rate
0/4 Standards Verified
Lamb's Players Theatre
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Performing Arts Industry Average (This Year)

No incidents recorded for Seattle Theatre Group in 2025.

Incidents vs Performing Arts Industry Average (This Year)

No incidents recorded for Lamb's Players Theatre in 2025.

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

Seattle Theatre Group cyber incidents detection timeline including parent company and subsidiaries

Incident History — Lamb's Players Theatre (X = Date, Y = Severity)

Lamb's Players Theatre cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/seattle-theatre-group.jpeg
Seattle Theatre Group
Incidents

No Incident

https://images.rankiteo.com/companyimages/lamb's-players-theatre.jpeg
Lamb's Players Theatre
Incidents

No Incident

FAQ

Seattle Theatre Group company demonstrates a stronger AI Cybersecurity Score compared to Lamb's Players Theatre company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Historically, Lamb's Players Theatre company has disclosed a higher number of cyber incidents compared to Seattle Theatre Group company.

In the current year, Lamb's Players Theatre company and Seattle Theatre Group company have not reported any cyber incidents.

Neither Lamb's Players Theatre company nor Seattle Theatre Group company has reported experiencing a ransomware attack publicly.

Neither Lamb's Players Theatre company nor Seattle Theatre Group company has reported experiencing a data breach publicly.

Neither Lamb's Players Theatre company nor Seattle Theatre Group company has reported experiencing targeted cyberattacks publicly.

Neither Seattle Theatre Group company nor Lamb's Players Theatre company has reported experiencing or disclosing vulnerabilities publicly.

Neither Seattle Theatre Group nor Lamb's Players Theatre holds any compliance certifications.

Neither company holds any compliance certifications.

Neither Seattle Theatre Group company nor Lamb's Players Theatre company has publicly disclosed detailed information about the number of their subsidiaries.

Seattle Theatre Group company employs more people globally than Lamb's Players Theatre company, reflecting its scale as a Performing Arts.

Neither Seattle Theatre Group nor Lamb's Players Theatre holds SOC 2 Type 1 certification.

Neither Seattle Theatre Group nor Lamb's Players Theatre holds SOC 2 Type 2 certification.

Neither Seattle Theatre Group nor Lamb's Players Theatre holds ISO 27001 certification.

Neither Seattle Theatre Group nor Lamb's Players Theatre holds PCI DSS certification.

Neither Seattle Theatre Group nor Lamb's Players Theatre holds HIPAA certification.

Neither Seattle Theatre Group nor Lamb's Players Theatre holds GDPR certification.

Latest Global CVEs (Not Company-Specific)

Description

Zerobyte is a backup automation tool Zerobyte versions prior to 0.18.5 and 0.19.0 contain an authentication bypass vulnerability where authentication middleware is not properly applied to API endpoints. This results in certain API endpoints being accessible without valid session credentials. This is dangerous for those who have exposed Zerobyte to be used outside of their internal network. A fix has been applied in both version 0.19.0 and 0.18.5. If immediate upgrade is not possible, restrict network access to the Zerobyte instance to trusted networks only using firewall rules or network segmentation. This is only a temporary mitigation; upgrading is strongly recommended.

Risk Information
cvss3
Base: 9.1
Severity: LOW
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
Description

Open Source Point of Sale (opensourcepos) is a web based point of sale application written in PHP using CodeIgniter framework. Starting in version 3.4.0 and prior to version 3.4.2, a Cross-Site Request Forgery (CSRF) vulnerability exists in the application's filter configuration. The CSRF protection mechanism was **explicitly disabled**, allowing the application to process state-changing requests (POST) without verifying a valid CSRF token. An unauthenticated remote attacker can exploit this by hosting a malicious web page. If a logged-in administrator visits this page, their browser is forced to send unauthorized requests to the application. A successful exploit allows the attacker to silently create a new Administrator account with full privileges, leading to a complete takeover of the system and loss of confidentiality, integrity, and availability. The vulnerability has been patched in version 3.4.2. The fix re-enables the CSRF filter in `app/Config/Filters.php` and resolves associated AJAX race conditions by adjusting token regeneration settings. As a workaround, administrators can manually re-enable the CSRF filter in `app/Config/Filters.php` by uncommenting the protection line. However, this is not recommended without applying the full patch, as it may cause functionality breakage in the Sales module due to token synchronization issues.

Risk Information
cvss3
Base: 8.8
Severity: LOW
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Description

Zed, a code editor, has an aribtrary code execution vulnerability in versions prior to 0.218.2-pre. The Zed IDE loads Model Context Protocol (MCP) configurations from the `settings.json` file located within a project’s `.zed` subdirectory. A malicious MCP configuration can contain arbitrary shell commands that run on the host system with the privileges of the user running the IDE. This can be triggered automatically without any user interaction besides opening the project in the IDE. Version 0.218.2-pre fixes the issue by implementing worktree trust mechanism. As a workaround, users should carefully review the contents of project settings files (`./zed/settings.json`) before opening new projects in Zed.

Risk Information
cvss3
Base: 7.7
Severity: HIGH
CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H
Description

Zed, a code editor, has an aribtrary code execution vulnerability in versions prior to 0.218.2-pre. The Zed IDE loads Language Server Protocol (LSP) configurations from the `settings.json` file located within a project’s `.zed` subdirectory. A malicious LSP configuration can contain arbitrary shell commands that run on the host system with the privileges of the user running the IDE. This can be triggered when a user opens project file for which there is an LSP entry. A concerted effort by an attacker to seed a project settings file (`./zed/settings.json`) with malicious language server configurations could result in arbitrary code execution with the user's privileges if the user opens the project in Zed without reviewing the contents. Version 0.218.2-pre fixes the issue by implementing worktree trust mechanism. As a workaround, users should carefully review the contents of project settings files (`./zed/settings.json`) before opening new projects in Zed.

Risk Information
cvss3
Base: 7.7
Severity: HIGH
CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H
Description

Storybook is a frontend workshop for building user interface components and pages in isolation. A vulnerability present starting in versions 7.0.0 and prior to versions 7.6.21, 8.6.15, 9.1.17, and 10.1.10 relates to Storybook’s handling of environment variables defined in a `.env` file, which could, in specific circumstances, lead to those variables being unexpectedly bundled into the artifacts created by the `storybook build` command. When a built Storybook is published to the web, the bundle’s source is viewable, thus potentially exposing those variables to anyone with access. For a project to potentially be vulnerable to this issue, it must build the Storybook (i.e. run `storybook build` directly or indirectly) in a directory that contains a `.env` file (including variants like `.env.local`) and publish the built Storybook to the web. Storybooks built without a `.env` file at build time are not affected, including common CI-based builds where secrets are provided via platform environment variables rather than `.env` files. Storybook runtime environments (i.e. `storybook dev`) are not affected. Deployed applications that share a repo with your Storybook are not affected. Users should upgrade their Storybook—on both their local machines and CI environment—to version .6.21, 8.6.15, 9.1.17, or 10.1.10 as soon as possible. Maintainers additionally recommend that users audit for any sensitive secrets provided via `.env` files and rotate those keys. Some projects may have been relying on the undocumented behavior at the heart of this issue and will need to change how they reference environment variables after this update. If a project can no longer read necessary environmental variable values, either prefix the variables with `STORYBOOK_` or use the `env` property in Storybook’s configuration to manually specify values. In either case, do not include sensitive secrets as they will be included in the built bundle.

Risk Information
cvss3
Base: 7.3
Severity: LOW
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L