Comparison Overview

Ballet Arkansas

VS

Gimle

Ballet Arkansas

520 Main Street, Little Rock, AR, 72201, US
Last Update: 2025-12-09
View Profile
Between 750 and 799
http://www.balletarkansas.org

Ranked among the Top 100 Ballet Companies in America, Ballet Arkansas's world-class performances and education programs have touched the lives of more than HALF-A-MILLION Arkansans. The preeminent producer of dance programming in the region, Ballet Arkansas presents a vibrant repertory of the classics, masterworks of American dance, and premieres by the world's most daring dancemakers to an audience of more than 50K per year.

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

Gimle

Helligkorsvej 2, Roskilde, 4000, DK
Last Update: 2025-12-09
Between 750 and 799
https://gimle.dk

Gimle er Roskildes regionale spillested og ungdomskulturhus. Mere end 300 årlige kulturarrangementer afholdes både i og uden for huset. Kernen er koncertdrift med årlig præsentation af mere end 300 bands. Udover spillestedsdelen driver Gimle caféen, The Raven, der har åbent 6 dage om ugen, og en natcafé, der har åbent hver fredag og lørdag. Gimle er drevet på basis af 150 frivillige ildsjæle, 12 fastansatte (kontor, køkken og rengøring), og ca. 30 timeansatte (lyd, rengøring, køkken og natcafé). Læs mere om Gimles organisation på Gimle.dk

NAICS: 7111
NAICS Definition: Performing Arts Companies
Employees: 69
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/ballet-arkansas.jpeg
Ballet Arkansas
—
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/gimle.jpeg
Gimle
—
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
Ballet Arkansas
100%
Compliance Rate
0/4 Standards Verified
Gimle
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Performing Arts Industry Average (This Year)

No incidents recorded for Ballet Arkansas in 2025.

Incidents vs Performing Arts Industry Average (This Year)

No incidents recorded for Gimle in 2025.

Incident History — Ballet Arkansas (X = Date, Y = Severity)

Ballet Arkansas cyber incidents detection timeline including parent company and subsidiaries

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

Gimle cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/ballet-arkansas.jpeg
Ballet Arkansas
Incidents

No Incident

https://images.rankiteo.com/companyimages/gimle.jpeg
Gimle
Incidents

No Incident

FAQ

Both Ballet Arkansas company and Gimle company demonstrate a comparable AI Cybersecurity Score, with strong governance and monitoring frameworks in place.

Historically, Gimle company has disclosed a higher number of cyber incidents compared to Ballet Arkansas company.

In the current year, Gimle company and Ballet Arkansas company have not reported any cyber incidents.

Neither Gimle company nor Ballet Arkansas company has reported experiencing a ransomware attack publicly.

Neither Gimle company nor Ballet Arkansas company has reported experiencing a data breach publicly.

Neither Gimle company nor Ballet Arkansas company has reported experiencing targeted cyberattacks publicly.

Neither Ballet Arkansas company nor Gimle company has reported experiencing or disclosing vulnerabilities publicly.

Neither Ballet Arkansas nor Gimle holds any compliance certifications.

Neither company holds any compliance certifications.

Neither Ballet Arkansas company nor Gimle company has publicly disclosed detailed information about the number of their subsidiaries.

Gimle company employs more people globally than Ballet Arkansas company, reflecting its scale as a Performing Arts.

Neither Ballet Arkansas nor Gimle holds SOC 2 Type 1 certification.

Neither Ballet Arkansas nor Gimle holds SOC 2 Type 2 certification.

Neither Ballet Arkansas nor Gimle holds ISO 27001 certification.

Neither Ballet Arkansas nor Gimle holds PCI DSS certification.

Neither Ballet Arkansas nor Gimle holds HIPAA certification.

Neither Ballet Arkansas nor Gimle 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.

Published
Date
2025-12-14
Updated
Date
2025-12-14
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
References
Description

uriparser through 0.9.9 allows unbounded recursion and stack consumption, as demonstrated by ParseMustBeSegmentNzNc with large input containing many commas.

Published
Date
2025-12-14
Updated
Date
2025-12-14
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
References
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."

Published
Date
2025-12-14
Updated
Date
2025-12-14
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
References
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.

Published
Date
2025-12-14
Updated
Date
2025-12-14
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
References
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).

Published
Date
2025-12-14
Updated
Date
2025-12-14
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
References