Comparison Overview

San Pedro Playhouse

VS

SFJAZZ

San Pedro Playhouse

800 W. Ashby Pl, San Antonio, TX, 78212, US
Last Update: 2025-12-11

Established in 1912 as the San Antonio Dramatic Club and incorporated on April 6, 1927, as the San Antonio Little Theatre it is the most historic theater in South Texas. The company has had other brands such as The San Pedro Playhouse (1997), and The Playhouse San Antonio (2012). Its most recent brand, The Public Theater of San Antonio, was unveiled on January 7th, 2018 in an effort to align the organization’s new professional vision to the needs of the region. For over a century, The Public Theater has evolved to serve its community as a 501c3 non-profit organization.

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

SFJAZZ

201 Franklin St., None, San Francisco, CA, US, 94102
Last Update: 2025-12-10
Between 650 and 699

SFJAZZ is one of the world’s most popular and important presenters of jazz. The SFJAZZ Center is a beautiful and perfect stage for jazz artists and the community to celebrate the living American art form of jazz. The $64 million dollar Center launched in 2013 and the 32 year old non-profit organization now crafts distinguished Programming and Education services from the heart of the San Francisco arts district.

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

Compliance Badges Comparison

Security & Compliance Standards Overview

https://images.rankiteo.com/companyimages/the-playhouse.jpeg
San Pedro 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/sfjazz.jpeg
SFJAZZ
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
San Pedro Playhouse
100%
Compliance Rate
0/4 Standards Verified
SFJAZZ
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Performing Arts Industry Average (This Year)

No incidents recorded for San Pedro Playhouse in 2025.

Incidents vs Performing Arts Industry Average (This Year)

No incidents recorded for SFJAZZ in 2025.

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

San Pedro Playhouse cyber incidents detection timeline including parent company and subsidiaries

Incident History — SFJAZZ (X = Date, Y = Severity)

SFJAZZ cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/the-playhouse.jpeg
San Pedro Playhouse
Incidents

No Incident

https://images.rankiteo.com/companyimages/sfjazz.jpeg
SFJAZZ
Incidents

Date Detected: 5/2023
Type:Ransomware
Attack Vector: Ransomware
Blog: Blog

FAQ

San Pedro Playhouse company demonstrates a stronger AI Cybersecurity Score compared to SFJAZZ company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

SFJAZZ company has historically faced a number of disclosed cyber incidents, whereas San Pedro Playhouse company has not reported any.

In the current year, SFJAZZ company and San Pedro Playhouse company have not reported any cyber incidents.

SFJAZZ company has confirmed experiencing a ransomware attack, while San Pedro Playhouse company has not reported such incidents publicly.

Neither SFJAZZ company nor San Pedro Playhouse company has reported experiencing a data breach publicly.

Neither SFJAZZ company nor San Pedro Playhouse company has reported experiencing targeted cyberattacks publicly.

Neither San Pedro Playhouse company nor SFJAZZ company has reported experiencing or disclosing vulnerabilities publicly.

Neither San Pedro Playhouse nor SFJAZZ holds any compliance certifications.

Neither company holds any compliance certifications.

Neither San Pedro Playhouse company nor SFJAZZ company has publicly disclosed detailed information about the number of their subsidiaries.

SFJAZZ company employs more people globally than San Pedro Playhouse company, reflecting its scale as a Performing Arts.

Neither San Pedro Playhouse nor SFJAZZ holds SOC 2 Type 1 certification.

Neither San Pedro Playhouse nor SFJAZZ holds SOC 2 Type 2 certification.

Neither San Pedro Playhouse nor SFJAZZ holds ISO 27001 certification.

Neither San Pedro Playhouse nor SFJAZZ holds PCI DSS certification.

Neither San Pedro Playhouse nor SFJAZZ holds HIPAA certification.

Neither San Pedro Playhouse nor SFJAZZ 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