Comparison Overview

Classic Controls, Inc.

VS

Hirata Corporation of America

Classic Controls, Inc.

5095 S Lakeland Dr, Lakeland, Florida 33813-2558, US
Last Update: 2025-11-26

Classic Controls is a total solutions, single-source provider of industrial process instruments, systems, valves and equipment. Along with representing “best-in-class” manufacturers, Classic Control's workforce is comprised of people driven by total customer satisfaction, who are technically strong and conscientious, and who can expertly apply, train, and support Classic Controls products. Classic Controls also offers complete services in both systems integration and valve & actuator repair. Headquartered conveniently in Lakeland Florida, Classic Controls maintains a spacious, modern facility with ample warehousing, machine shop, production area, and QC/testing capabilities.

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

Hirata Corporation of America

5625 Decatur Blvd., Indianapolis, IN, 46241, US
Last Update: 2025-11-27
Between 750 and 799

Hirata Corporation of America (HCA) is known throughtout the NAFTA region in many industries as the world's leader of production engineering systems. Hirata serves many diverse manufacturing industries, from semiconductors that demand a high degree of precision and cleanliness, to more conventional large scale manufacturing applications like engine / transmission assembly or tire production. The breadth of our experience is unmatched by others. We often leverage our know-how and technology learned in one industry and apply it to another seemingly dissimilar industry. We've demonstrated time and again our ability to raise our customers' productivity, lower cost, and improve return on investment with solutions that are both affordable and durable. Key Industries Served Powertrain / Vehicle Systems / Electronics / Alternate Energy / Solar / Battery Systems / General Consumer Goods / Food Service / Flat Panel / Aerospace / Medical Instruments / Pharmaceutical / Tire / Components

NAICS: None
NAICS Definition: Others
Employees: 108
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/classic-controls-inc.jpeg
Classic Controls, 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
https://images.rankiteo.com/companyimages/hirata-corporation-of-america.jpeg
Hirata Corporation of America
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
Classic Controls, Inc.
100%
Compliance Rate
0/4 Standards Verified
Hirata Corporation of America
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Industrial Automation Industry Average (This Year)

No incidents recorded for Classic Controls, Inc. in 2025.

Incidents vs Industrial Automation Industry Average (This Year)

No incidents recorded for Hirata Corporation of America in 2025.

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

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

Incident History — Hirata Corporation of America (X = Date, Y = Severity)

Hirata Corporation of America cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/classic-controls-inc.jpeg
Classic Controls, Inc.
Incidents

No Incident

https://images.rankiteo.com/companyimages/hirata-corporation-of-america.jpeg
Hirata Corporation of America
Incidents

No Incident

FAQ

Hirata Corporation of America company demonstrates a stronger AI Cybersecurity Score compared to Classic Controls, Inc. company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Historically, Hirata Corporation of America company has disclosed a higher number of cyber incidents compared to Classic Controls, Inc. company.

In the current year, Hirata Corporation of America company and Classic Controls, Inc. company have not reported any cyber incidents.

Neither Hirata Corporation of America company nor Classic Controls, Inc. company has reported experiencing a ransomware attack publicly.

Neither Hirata Corporation of America company nor Classic Controls, Inc. company has reported experiencing a data breach publicly.

Neither Hirata Corporation of America company nor Classic Controls, Inc. company has reported experiencing targeted cyberattacks publicly.

Neither Classic Controls, Inc. company nor Hirata Corporation of America company has reported experiencing or disclosing vulnerabilities publicly.

Neither Classic Controls, Inc. nor Hirata Corporation of America holds any compliance certifications.

Neither company holds any compliance certifications.

Neither Classic Controls, Inc. company nor Hirata Corporation of America company has publicly disclosed detailed information about the number of their subsidiaries.

Hirata Corporation of America company employs more people globally than Classic Controls, Inc. company, reflecting its scale as a Industrial Automation.

Neither Classic Controls, Inc. nor Hirata Corporation of America holds SOC 2 Type 1 certification.

Neither Classic Controls, Inc. nor Hirata Corporation of America holds SOC 2 Type 2 certification.

Neither Classic Controls, Inc. nor Hirata Corporation of America holds ISO 27001 certification.

Neither Classic Controls, Inc. nor Hirata Corporation of America holds PCI DSS certification.

Neither Classic Controls, Inc. nor Hirata Corporation of America holds HIPAA certification.

Neither Classic Controls, Inc. nor Hirata Corporation of America 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