Comparison Overview

Process Engineering & Equipment Company (PECO)

VS

Hoyer

Process Engineering & Equipment Company (PECO)

1705 Northridge Drive NW, Grand Rapids, Michigan, 49544, US
Last Update: 2025-11-27
Between 750 and 799

Process Engineering & Equipment Company (PECO) was established in 1984, serving both the industrial and HVAC markets. As a manufacturers'​ representative, we specialize in the application and sales of high-quality fluid handling, filtration and heat transfer products, from chillers, boilers,b air handling equipment and cooling towers, to pumps, valves, controls, and heat transfer equipment. In addition to equipment sales, we provide turn-key design, engineering, and shop fabrication of process cooling, heating, and steam systems by packaging pumps, tanks, filters, boilers, heat exchangers, controls, etc., into a heat transfer system that is custom engineered to meet the exacting critical process heat transfer needs of our customers. Hundreds of these systems have been successfully installed and operated through the years in Michigan, across the US, and around the world. Some of the most common industries served include injection molding, plastics, anodizing, food processing, aluminum and zinc molding, and automotive industries.

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

Hoyer

Over Hadstenvej 42, Hadsten, DK, 8370
Last Update: 2025-11-27
Between 750 and 799

Hoyer is a global supplier of high-performance and energy-efficient electric motors, drives, and control systems. Since 1974, we have helped our customers operate more economically and environmentally sustainable businesses by providing solutions that are fit for purpose and support that goes all the way. Across a wide range of industries, our customers benefit from our customised solutions, ready-to-ship stock, and our fast, reliable delivery. Our advanced test centres and classification setup ensure that every solution meets the highest global standards for marine and industrial applications. With headquarters in Denmark and China and sales offices worldwide, we combine local presence and expertise with global reach.

NAICS: None
NAICS Definition: Others
Employees: 174
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/process-engineering-&-equipment-company-peco-.jpeg
Process Engineering & Equipment Company (PECO)
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/hoyer.jpeg
Hoyer
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
Process Engineering & Equipment Company (PECO)
100%
Compliance Rate
0/4 Standards Verified
Hoyer
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 Process Engineering & Equipment Company (PECO) in 2025.

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

No incidents recorded for Hoyer in 2025.

Incident History — Process Engineering & Equipment Company (PECO) (X = Date, Y = Severity)

Process Engineering & Equipment Company (PECO) cyber incidents detection timeline including parent company and subsidiaries

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

Hoyer cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/process-engineering-&-equipment-company-peco-.jpeg
Process Engineering & Equipment Company (PECO)
Incidents

No Incident

https://images.rankiteo.com/companyimages/hoyer.jpeg
Hoyer
Incidents

No Incident

FAQ

Both Process Engineering & Equipment Company (PECO) company and Hoyer company demonstrate a comparable AI Cybersecurity Score, with strong governance and monitoring frameworks in place.

Historically, Hoyer company has disclosed a higher number of cyber incidents compared to Process Engineering & Equipment Company (PECO) company.

In the current year, Hoyer company and Process Engineering & Equipment Company (PECO) company have not reported any cyber incidents.

Neither Hoyer company nor Process Engineering & Equipment Company (PECO) company has reported experiencing a ransomware attack publicly.

Neither Hoyer company nor Process Engineering & Equipment Company (PECO) company has reported experiencing a data breach publicly.

Neither Hoyer company nor Process Engineering & Equipment Company (PECO) company has reported experiencing targeted cyberattacks publicly.

Neither Process Engineering & Equipment Company (PECO) company nor Hoyer company has reported experiencing or disclosing vulnerabilities publicly.

Neither Process Engineering & Equipment Company (PECO) nor Hoyer holds any compliance certifications.

Neither company holds any compliance certifications.

Neither Process Engineering & Equipment Company (PECO) company nor Hoyer company has publicly disclosed detailed information about the number of their subsidiaries.

Hoyer company employs more people globally than Process Engineering & Equipment Company (PECO) company, reflecting its scale as a Mechanical Or Industrial Engineering.

Neither Process Engineering & Equipment Company (PECO) nor Hoyer holds SOC 2 Type 1 certification.

Neither Process Engineering & Equipment Company (PECO) nor Hoyer holds SOC 2 Type 2 certification.

Neither Process Engineering & Equipment Company (PECO) nor Hoyer holds ISO 27001 certification.

Neither Process Engineering & Equipment Company (PECO) nor Hoyer holds PCI DSS certification.

Neither Process Engineering & Equipment Company (PECO) nor Hoyer holds HIPAA certification.

Neither Process Engineering & Equipment Company (PECO) nor Hoyer 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