Comparison Overview

Camac Industries

VS

Hussey Seating Company

Camac Industries

14 Park Lake Road, Sparta, New Jersey, 07871-3439, US
Last Update: 2025-11-27

Camac Industries was founded in 1947 by two engineers who wanted to provide individualized, personal service and custom-made pumps and heat exchangers to people servicing the anodizing industry. Incorporated in 1962, Camac has expanded to now build and support quality products for the metal finishing, chemical, water and waste treatment, printed circuit and related industries, all with the same dedication to custom solutions to our clients'​ needs. We are a family-owned and operated corporation that continues this tradition of service and quality. Our manufacturing facility is located in Sparta, New Jersey, and all of our products are made with pride in the U.S.A.

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

Hussey Seating Company

38 Dyer Street Ext, North Berwick, undefined, 03906, US
Last Update: 2025-11-27
Between 750 and 799

Hussey Seating makes a full line of top quality spectator seating including fixed polymer and upholstered chairs, telescopic platforms and telescopic gym seats, portable folding chairs and fixed learning systems. You’ll find Hussey Seating solutions throughout the world – in stadiums, arenas, schools, universities, colleges, worship halls and anywhere people gather. Hussey Seating. Your partner for seating solutions.™

NAICS: None
NAICS Definition: Others
Employees: 237
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/camac-industries.jpeg
Camac Industries
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/hussey-seating-company.jpeg
Hussey Seating Company
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
Camac Industries
100%
Compliance Rate
0/4 Standards Verified
Hussey Seating Company
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Mechanical Or Industrial Engineering Industry Average (This Year)

No incidents recorded for Camac Industries in 2025.

Incidents vs Mechanical Or Industrial Engineering Industry Average (This Year)

No incidents recorded for Hussey Seating Company in 2025.

Incident History — Camac Industries (X = Date, Y = Severity)

Camac Industries cyber incidents detection timeline including parent company and subsidiaries

Incident History — Hussey Seating Company (X = Date, Y = Severity)

Hussey Seating Company cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/camac-industries.jpeg
Camac Industries
Incidents

No Incident

https://images.rankiteo.com/companyimages/hussey-seating-company.jpeg
Hussey Seating Company
Incidents

No Incident

FAQ

Camac Industries company demonstrates a stronger AI Cybersecurity Score compared to Hussey Seating Company company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Historically, Hussey Seating Company company has disclosed a higher number of cyber incidents compared to Camac Industries company.

In the current year, Hussey Seating Company company and Camac Industries company have not reported any cyber incidents.

Neither Hussey Seating Company company nor Camac Industries company has reported experiencing a ransomware attack publicly.

Neither Hussey Seating Company company nor Camac Industries company has reported experiencing a data breach publicly.

Neither Hussey Seating Company company nor Camac Industries company has reported experiencing targeted cyberattacks publicly.

Neither Camac Industries company nor Hussey Seating Company company has reported experiencing or disclosing vulnerabilities publicly.

Neither Camac Industries nor Hussey Seating Company holds any compliance certifications.

Neither company holds any compliance certifications.

Neither Camac Industries company nor Hussey Seating Company company has publicly disclosed detailed information about the number of their subsidiaries.

Hussey Seating Company company employs more people globally than Camac Industries company, reflecting its scale as a Mechanical Or Industrial Engineering.

Neither Camac Industries nor Hussey Seating Company holds SOC 2 Type 1 certification.

Neither Camac Industries nor Hussey Seating Company holds SOC 2 Type 2 certification.

Neither Camac Industries nor Hussey Seating Company holds ISO 27001 certification.

Neither Camac Industries nor Hussey Seating Company holds PCI DSS certification.

Neither Camac Industries nor Hussey Seating Company holds HIPAA certification.

Neither Camac Industries nor Hussey Seating Company holds GDPR certification.

Latest Global CVEs (Not Company-Specific)

Description

Angular is a development platform for building mobile and desktop web applications using TypeScript/JavaScript and other languages. Prior to versions 19.2.16, 20.3.14, and 21.0.1, there is a XSRF token leakage via protocol-relative URLs in angular HTTP clients. The vulnerability is a Credential Leak by App Logic that leads to the unauthorized disclosure of the Cross-Site Request Forgery (XSRF) token to an attacker-controlled domain. Angular's HttpClient has a built-in XSRF protection mechanism that works by checking if a request URL starts with a protocol (http:// or https://) to determine if it is cross-origin. If the URL starts with protocol-relative URL (//), it is incorrectly treated as a same-origin request, and the XSRF token is automatically added to the X-XSRF-TOKEN header. This issue has been patched in versions 19.2.16, 20.3.14, and 21.0.1. A workaround for this issue involves avoiding using protocol-relative URLs (URLs starting with //) in HttpClient requests. All backend communication URLs should be hardcoded as relative paths (starting with a single /) or fully qualified, trusted absolute URLs.

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

Forge (also called `node-forge`) is a native implementation of Transport Layer Security in JavaScript. An Uncontrolled Recursion vulnerability in node-forge versions 1.3.1 and below enables remote, unauthenticated attackers to craft deep ASN.1 structures that trigger unbounded recursive parsing. This leads to a Denial-of-Service (DoS) via stack exhaustion when parsing untrusted DER inputs. This issue has been patched in version 1.3.2.

Risk Information
cvss4
Base: 8.7
Severity: LOW
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/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

Forge (also called `node-forge`) is a native implementation of Transport Layer Security in JavaScript. An Integer Overflow vulnerability in node-forge versions 1.3.1 and below enables remote, unauthenticated attackers to craft ASN.1 structures containing OIDs with oversized arcs. These arcs may be decoded as smaller, trusted OIDs due to 32-bit bitwise truncation, enabling the bypass of downstream OID-based security decisions. This issue has been patched in version 1.3.2.

Risk Information
cvss4
Base: 6.3
Severity: LOW
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:L/VA:N/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

Suricata is a network IDS, IPS and NSM engine developed by the OISF (Open Information Security Foundation) and the Suricata community. Prior to versions 7.0.13 and 8.0.2, working with large buffers in Lua scripts can lead to a stack overflow. Users of Lua rules and output scripts may be affected when working with large buffers. This includes a rule passing a large buffer to a Lua script. This issue has been patched in versions 7.0.13 and 8.0.2. A workaround for this issue involves disabling Lua rules and output scripts, or making sure limits, such as stream.depth.reassembly and HTTP response body limits (response-body-limit), are set to less than half the stack size.

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

Suricata is a network IDS, IPS and NSM engine developed by the OISF (Open Information Security Foundation) and the Suricata community. In versions from 8.0.0 to before 8.0.2, a NULL dereference can occur when the entropy keyword is used in conjunction with base64_data. This issue has been patched in version 8.0.2. A workaround involves disabling rules that use entropy in conjunction with base64_data.

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