Comparison Overview

Gnarly Bay

VS

OConnor

Gnarly Bay

10 High Street, Westerly, RI, 02891, US
Last Update: 2025-12-21
Between 750 and 799

When this started, it was a seed planted. A magical glowing seed. gnarly bay is a team made up of multi-hat-wearing creative individuals. We believe in the power of a well-integrated team working towards a shared goal and treat every project as an opportunity to reaffirm our belief in the power of storytelling. Whether it’s a broadcast commercial, an independent documentary, or branded content, our mission has always been to elevate stories for a better tomorrow. We hope you’ll come along.

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

OConnor

2701 N Ontario St, Burbank, California, US
Last Update: 2025-12-18
Between 750 and 799

OConnor Engineering Laboratories was founded in 1949 by Chadwell O’Connor. Chad, once a designer and builder of steam power plants, always had a passion for steam locomotives. In the late 1940s, he decided to document them on film before they were all gone, but found it impossible to pan smoothly with his Bell & Howell camera. To solve this problem, Chad designed and built a Fluid Head camera support that would allow his lightweight camera to follow the moving trains without jumps, and distracting starts and stops. One day, in 1949 while he was filming the trains at Glendale Station, another steam train enthusiast noticed this unusual setup and stopped to ask a few questions. He liked the concept, and asked Chad to build a Fluid Head that would solve pan & tilt problems on his new film, ‘The Living Desert’. The man was Walt Disney. Today OConnor Engineering specializes in heavy-duty fluid heads, tripods and camera accessories. As a Vitec group brand, OConnor has a large dealer networking spanning the United States and in more than two dozen countries across six continents.

NAICS: None
NAICS Definition: Others
Employees: None
Subsidiaries: 8
12-month incidents
0
Known data breaches
0
Attack type number
0

Compliance Badges Comparison

Security & Compliance Standards Overview

https://images.rankiteo.com/companyimages/gnarly-bay.jpeg
Gnarly Bay
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/oconnor.jpeg
OConnor
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
Gnarly Bay
100%
Compliance Rate
0/4 Standards Verified
OConnor
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Movies, Videos, and Sound Industry Average (This Year)

No incidents recorded for Gnarly Bay in 2025.

Incidents vs Movies, Videos, and Sound Industry Average (This Year)

No incidents recorded for OConnor in 2025.

Incident History — Gnarly Bay (X = Date, Y = Severity)

Gnarly Bay cyber incidents detection timeline including parent company and subsidiaries

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

OConnor cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/gnarly-bay.jpeg
Gnarly Bay
Incidents

No Incident

https://images.rankiteo.com/companyimages/oconnor.jpeg
OConnor
Incidents

No Incident

FAQ

OConnor company demonstrates a stronger AI Cybersecurity Score compared to Gnarly Bay company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Historically, OConnor company has disclosed a higher number of cyber incidents compared to Gnarly Bay company.

In the current year, OConnor company and Gnarly Bay company have not reported any cyber incidents.

Neither OConnor company nor Gnarly Bay company has reported experiencing a ransomware attack publicly.

Neither OConnor company nor Gnarly Bay company has reported experiencing a data breach publicly.

Neither OConnor company nor Gnarly Bay company has reported experiencing targeted cyberattacks publicly.

Neither Gnarly Bay company nor OConnor company has reported experiencing or disclosing vulnerabilities publicly.

Neither Gnarly Bay nor OConnor holds any compliance certifications.

Neither company holds any compliance certifications.

OConnor company has more subsidiaries worldwide compared to Gnarly Bay company.

Neither Gnarly Bay nor OConnor holds SOC 2 Type 1 certification.

Neither Gnarly Bay nor OConnor holds SOC 2 Type 2 certification.

Neither Gnarly Bay nor OConnor holds ISO 27001 certification.

Neither Gnarly Bay nor OConnor holds PCI DSS certification.

Neither Gnarly Bay nor OConnor holds HIPAA certification.

Neither Gnarly Bay nor OConnor holds GDPR certification.

Latest Global CVEs (Not Company-Specific)

Description

Versa SASE Client for Windows versions released between 7.8.7 and 7.9.4 contain a local privilege escalation vulnerability in the audit log export functionality. The client communicates user-controlled file paths to a privileged service, which performs file system operations without impersonating the requesting user. Due to improper privilege handling and a time-of-check time-of-use race condition combined with symbolic link and mount point manipulation, a local authenticated attacker can coerce the service into deleting arbitrary directories with SYSTEM privileges. This can be exploited to delete protected system folders such as C:\\Config.msi and subsequently achieve execution as NT AUTHORITY\\SYSTEM via MSI rollback techniques.

Risk Information
cvss4
Base: 8.5
Severity: LOW
CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/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

The WP JobHunt plugin for WordPress, used by the JobCareer theme, is vulnerable to unauthorized modification of data due to a missing capability check on the 'cs_update_application_status_callback' function in all versions up to, and including, 7.7. This makes it possible for authenticated attackers, with Candidate-level access and above, to inject cross-site scripting into the 'status' parameter of applied jobs for any user.

Risk Information
cvss3
Base: 7.6
Severity: LOW
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:L
Description

The WP JobHunt plugin for WordPress, used by the JobCareer theme, is vulnerable to Insecure Direct Object Reference in all versions up to, and including, 7.7 via the 'cs_update_application_status_callback' due to missing validation on a user controlled key. This makes it possible for authenticated attackers, with Candidate-level access and above, to send a site-generated email with injected HTML to any user.

Risk Information
cvss3
Base: 4.3
Severity: LOW
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N
Description

The FiboSearch – Ajax Search for WooCommerce plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the plugin's `thegem_te_search` shortcode in all versions up to, and including, 1.32.0 due to insufficient input sanitization and output escaping on user supplied attributes. This makes it possible for authenticated attackers, with Contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. This vulnerability requires TheGem theme (premium) to be installed with Header Builder mode enabled, and the FiboSearch "Replace search bars" option enabled for TheGem integration.

Risk Information
cvss3
Base: 5.4
Severity: LOW
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N
Description

The Ultimate Member – User Profile, Registration, Login, Member Directory, Content Restriction & Membership Plugin plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 2.11.0 via the ajax_get_members function. This is due to the use of a predictable low-entropy token (5 hex characters derived from md5 of post ID) to identify member directories and insufficient authorization checks on the unauthenticated AJAX endpoint. This makes it possible for unauthenticated attackers to extract sensitive data including usernames, display names, user roles (including administrator accounts), profile URLs, and user IDs by enumerating predictable directory_id values or brute-forcing the small 16^5 token space.

Risk Information
cvss3
Base: 5.3
Severity: LOW
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N