Comparison Overview

1687, Inc

VS

Georgetown Palace Theatre

1687, Inc

PO Box 1000, New York, NY, 10014, US
Last Update: 2025-12-12
Between 750 and 799

Our mission is to support the work of Lenore Von Stein and Company in their efforts to create music and art that stretches the possibilities of expression and encourages creative thinking. We are also endeavoring to build an ethical, democratic organization in which artists are free to create and present work without interference or commercial compromises.

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

Georgetown Palace Theatre

810 S Austin Ave, Georgetown, TX 78626, US
Last Update: 2025-12-11

The Georgetown Palace Theatre celebrates the power of storytelling and our shared human experience with a commitment to artistic excellence, quality education, and community engagement and seeks to become the cultural destination for everyone. We are a nonprofit organization dedicated to enhancing the quality of life in Central Texas by providing a venue for quality and affordable entertainment and educational opportunities in the performing arts. We produce a diverse lineup of fully-staged plays and musicals throughout the season. We have an Adaptive Theatre for All Program as well as numerous summer camps and educational theatre classes. At the Palace, we strive to provide performance and education experiences for each and every community member. See you at the Palace!

NAICS: 711
NAICS Definition:
Employees: 47
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/1687-inc.jpeg
1687, Inc
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/georgetown-palace-theatre.jpeg
Georgetown Palace 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
1687, Inc
100%
Compliance Rate
0/4 Standards Verified
Georgetown Palace Theatre
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Performing Arts Industry Average (This Year)

No incidents recorded for 1687, Inc in 2025.

Incidents vs Performing Arts Industry Average (This Year)

No incidents recorded for Georgetown Palace Theatre in 2025.

Incident History — 1687, Inc (X = Date, Y = Severity)

1687, Inc cyber incidents detection timeline including parent company and subsidiaries

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

Georgetown Palace Theatre cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/1687-inc.jpeg
1687, Inc
Incidents

No Incident

https://images.rankiteo.com/companyimages/georgetown-palace-theatre.jpeg
Georgetown Palace Theatre
Incidents

No Incident

FAQ

1687, Inc company demonstrates a stronger AI Cybersecurity Score compared to Georgetown Palace Theatre company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Historically, Georgetown Palace Theatre company has disclosed a higher number of cyber incidents compared to 1687, Inc company.

In the current year, Georgetown Palace Theatre company and 1687, Inc company have not reported any cyber incidents.

Neither Georgetown Palace Theatre company nor 1687, Inc company has reported experiencing a ransomware attack publicly.

Neither Georgetown Palace Theatre company nor 1687, Inc company has reported experiencing a data breach publicly.

Neither Georgetown Palace Theatre company nor 1687, Inc company has reported experiencing targeted cyberattacks publicly.

Neither 1687, Inc company nor Georgetown Palace Theatre company has reported experiencing or disclosing vulnerabilities publicly.

Neither 1687, Inc nor Georgetown Palace Theatre holds any compliance certifications.

Neither company holds any compliance certifications.

Neither 1687, Inc company nor Georgetown Palace Theatre company has publicly disclosed detailed information about the number of their subsidiaries.

Georgetown Palace Theatre company employs more people globally than 1687, Inc company, reflecting its scale as a Performing Arts.

Neither 1687, Inc nor Georgetown Palace Theatre holds SOC 2 Type 1 certification.

Neither 1687, Inc nor Georgetown Palace Theatre holds SOC 2 Type 2 certification.

Neither 1687, Inc nor Georgetown Palace Theatre holds ISO 27001 certification.

Neither 1687, Inc nor Georgetown Palace Theatre holds PCI DSS certification.

Neither 1687, Inc nor Georgetown Palace Theatre holds HIPAA certification.

Neither 1687, Inc nor Georgetown Palace Theatre 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