Comparison Overview

The Field

VS

Omaha Community Playhouse

The Field

2​2​8 P​a​r​k A​v​e S, New York, NY, 10003, US
Last Update: 2025-12-15
Between 750 and 799

The Field envisions a world where artists are abundantly and holistically prosperous. We’re building a community that connects, empowers, and elevates creative practitioners of all kinds. Whether you’re a writer, dancer, filmmaker, musician, actor, or a creative individual, there’s a place for you at The Field. Founded by artists for artists, our organization has provided fiscal sponsorship and fundraising support to thousands of independent artists and small arts organizations nationwide to get their projects off the ground. Through hands-on fundraising assistance, entrepreneurial capacity-building, and skill-building workshops, we are removing barriers and working to ensure that artists can prosper in all areas of their lives.

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

Omaha Community Playhouse

6915 Cass St., Omaha, NE, 68132, US
Last Update: 2025-12-13

The Omaha Community Playhouse is a performing arts organization that enhances quality of life through live theatre, professional touring, and arts education. We are dedicated to enriching the lives of audiences and participants through entertainment, thought-provoking stories, and first-hand involvement. OCP is one of the largest non-profit community theatres in the nation and is a cornerstone of the Omaha arts community.

NAICS: 711
NAICS Definition:
Employees: 73
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/thefieldnyc.jpeg
The Field
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/omaha-community-playhouse.jpeg
Omaha Community 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
Compliance Summary
The Field
100%
Compliance Rate
0/4 Standards Verified
Omaha Community Playhouse
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Performing Arts Industry Average (This Year)

No incidents recorded for The Field in 2025.

Incidents vs Performing Arts Industry Average (This Year)

No incidents recorded for Omaha Community Playhouse in 2025.

Incident History — The Field (X = Date, Y = Severity)

The Field cyber incidents detection timeline including parent company and subsidiaries

Incident History — Omaha Community Playhouse (X = Date, Y = Severity)

Omaha Community Playhouse cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/thefieldnyc.jpeg
The Field
Incidents

No Incident

https://images.rankiteo.com/companyimages/omaha-community-playhouse.jpeg
Omaha Community Playhouse
Incidents

No Incident

FAQ

Both The Field company and Omaha Community Playhouse company demonstrate a comparable AI Cybersecurity Score, with strong governance and monitoring frameworks in place.

Historically, Omaha Community Playhouse company has disclosed a higher number of cyber incidents compared to The Field company.

In the current year, Omaha Community Playhouse company and The Field company have not reported any cyber incidents.

Neither Omaha Community Playhouse company nor The Field company has reported experiencing a ransomware attack publicly.

Neither Omaha Community Playhouse company nor The Field company has reported experiencing a data breach publicly.

Neither Omaha Community Playhouse company nor The Field company has reported experiencing targeted cyberattacks publicly.

Neither The Field company nor Omaha Community Playhouse company has reported experiencing or disclosing vulnerabilities publicly.

Neither The Field nor Omaha Community Playhouse holds any compliance certifications.

Neither company holds any compliance certifications.

Neither The Field company nor Omaha Community Playhouse company has publicly disclosed detailed information about the number of their subsidiaries.

Omaha Community Playhouse company employs more people globally than The Field company, reflecting its scale as a Performing Arts.

Neither The Field nor Omaha Community Playhouse holds SOC 2 Type 1 certification.

Neither The Field nor Omaha Community Playhouse holds SOC 2 Type 2 certification.

Neither The Field nor Omaha Community Playhouse holds ISO 27001 certification.

Neither The Field nor Omaha Community Playhouse holds PCI DSS certification.

Neither The Field nor Omaha Community Playhouse holds HIPAA certification.

Neither The Field nor Omaha Community Playhouse 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