Comparison Overview

Gibney

VS

PlayWrite, Inc.

Gibney

280 Broadway, New York , New York , 10007, US
Last Update: 2025-12-09
Between 750 and 799

Gibney is a dance company, performing arts hub, and a social action incubator located in New York City. Since 1991, our mission has been to tap into the vast potential of movement, creativity, and performance to effect social change and personal transformation. Through the expansive programming housed at our beautiful 890 Broadway and 280 Broadway locations, we push boundaries, lift voices, and mobilize the power of movement to transform lives and change the world.

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

PlayWrite, Inc.

PO Box 13420, Portland, OR, 97213, US
Last Update: 2025-12-11
Between 750 and 799

PlayWrite, formed in 2003, works with youth 'at the edge’ to create original plays, powerful vehicles through which their voices are heard. PlayWrite coaches are drawn from the Oregon theater community, and are trained to work one-on-one with each young person. Within the intense structured activities of PlayWrite workshops, these young writers create original art. In the process, they learn to trust, manage, and heal their own emotional experiences; to work collaboratively; and to contribute positively to their communities. PlayWrite provides creative workshops for under-served youth on an ongoing basis throughout the year. The young participants collaborate with theatre professionals throughout the process of crafting a play, from character development to directing professional actors.

NAICS: 711
NAICS Definition:
Employees: 17
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/gibney-dance.jpeg
Gibney
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/playwrite-inc-.jpeg
PlayWrite, 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
Compliance Summary
Gibney
100%
Compliance Rate
0/4 Standards Verified
PlayWrite, Inc.
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Performing Arts Industry Average (This Year)

No incidents recorded for Gibney in 2025.

Incidents vs Performing Arts Industry Average (This Year)

No incidents recorded for PlayWrite, Inc. in 2025.

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

Gibney cyber incidents detection timeline including parent company and subsidiaries

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

PlayWrite, Inc. cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/gibney-dance.jpeg
Gibney
Incidents

No Incident

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

No Incident

FAQ

PlayWrite, Inc. company demonstrates a stronger AI Cybersecurity Score compared to Gibney company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Historically, PlayWrite, Inc. company has disclosed a higher number of cyber incidents compared to Gibney company.

In the current year, PlayWrite, Inc. company and Gibney company have not reported any cyber incidents.

Neither PlayWrite, Inc. company nor Gibney company has reported experiencing a ransomware attack publicly.

Neither PlayWrite, Inc. company nor Gibney company has reported experiencing a data breach publicly.

Neither PlayWrite, Inc. company nor Gibney company has reported experiencing targeted cyberattacks publicly.

Neither Gibney company nor PlayWrite, Inc. company has reported experiencing or disclosing vulnerabilities publicly.

Neither Gibney nor PlayWrite, Inc. holds any compliance certifications.

Neither company holds any compliance certifications.

Neither Gibney company nor PlayWrite, Inc. company has publicly disclosed detailed information about the number of their subsidiaries.

Gibney company employs more people globally than PlayWrite, Inc. company, reflecting its scale as a Performing Arts.

Neither Gibney nor PlayWrite, Inc. holds SOC 2 Type 1 certification.

Neither Gibney nor PlayWrite, Inc. holds SOC 2 Type 2 certification.

Neither Gibney nor PlayWrite, Inc. holds ISO 27001 certification.

Neither Gibney nor PlayWrite, Inc. holds PCI DSS certification.

Neither Gibney nor PlayWrite, Inc. holds HIPAA certification.

Neither Gibney nor PlayWrite, Inc. 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