Comparison Overview

Thrive MES

VS

Motor Power Company

Thrive MES

134 W South Boundary St, Perrysburg, OH, 43551, US
Last Update: 2025-11-22

Continuous improvement–it’s an integral part of lean manufacturing and so is Thrive’s Downtime Tracking System. Immediately begin tracking machine downtime and define a reason from nearly any device on the shop floor with our cloud-based, automated downtime tracking and analysis software. Our plug and play hardware monitors the heartbeat and output of manufacturing lines to provide real-time equipment performance tracking. We track your line’s efficiency, as well as the cause, length and frequency of downtime events. Use the built-in reports to see the biggest source of downtime, all in real time. Our hardware is: - Easy to Install - Operator Friendly - Budget Friendly - A Source for Advanced Data Seeing the cause of downtime events is just the first step. Thrive’s unique algorithm calculates the impact on uptime and production each downtime event would have if fixed. Prioritize equipment maintenance, equipment purchases and other action steps by the expected results. Thrive provides the insight you need to make true data-driven decisions. With Thrive, you are able to: - Measure Your Efficiency in Real Time - Know Your Biggest Source of Downtime Now - Identify Poor Performing Equipment - Print Your Performance Snapshot Anytime - Review Your Historical Performance - Planned Downtimes Know whether your lines are running, how efficiently they’re performing and exactly how to reduce production downtime.

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

Motor Power Company

Via Fratelli Guerra 23/A, Reggio nell'Emilia, 42124, IT
Last Update: 2025-11-26
Between 750 and 799

Motor Power Company specializes in motion control solutions such as direct drive torque motors, brushless motors or gearless motorollers. We provide mechanical integration for technological automation upgrades. Our approach is simple: we identify a need and implement a solution. Our long-term investments in the study of motion have created a deep well of knowledge in all aspects of motion technology. We care a lot about our people, our engineers and designers. We reward creativity, intellectual growth and continuing investment in knowledge. The result is an innate ability to come up with original ideas that allow the design and final performance of our products to stand out in the market. Do you have a project to develop? Let's talk about it.

NAICS: None
NAICS Definition: Others
Employees: 97
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/thrive-mes.jpeg
Thrive MES
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/motor-power-company.jpeg
Motor Power 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
Thrive MES
100%
Compliance Rate
0/4 Standards Verified
Motor Power Company
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Industrial Automation Industry Average (This Year)

No incidents recorded for Thrive MES in 2025.

Incidents vs Industrial Automation Industry Average (This Year)

No incidents recorded for Motor Power Company in 2025.

Incident History — Thrive MES (X = Date, Y = Severity)

Thrive MES cyber incidents detection timeline including parent company and subsidiaries

Incident History — Motor Power Company (X = Date, Y = Severity)

Motor Power Company cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/thrive-mes.jpeg
Thrive MES
Incidents

No Incident

https://images.rankiteo.com/companyimages/motor-power-company.jpeg
Motor Power Company
Incidents

No Incident

FAQ

Thrive MES company demonstrates a stronger AI Cybersecurity Score compared to Motor Power Company company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Historically, Motor Power Company company has disclosed a higher number of cyber incidents compared to Thrive MES company.

In the current year, Motor Power Company company and Thrive MES company have not reported any cyber incidents.

Neither Motor Power Company company nor Thrive MES company has reported experiencing a ransomware attack publicly.

Neither Motor Power Company company nor Thrive MES company has reported experiencing a data breach publicly.

Neither Motor Power Company company nor Thrive MES company has reported experiencing targeted cyberattacks publicly.

Neither Thrive MES company nor Motor Power Company company has reported experiencing or disclosing vulnerabilities publicly.

Neither Thrive MES nor Motor Power Company holds any compliance certifications.

Neither company holds any compliance certifications.

Neither Thrive MES company nor Motor Power Company company has publicly disclosed detailed information about the number of their subsidiaries.

Motor Power Company company employs more people globally than Thrive MES company, reflecting its scale as a Industrial Automation.

Neither Thrive MES nor Motor Power Company holds SOC 2 Type 1 certification.

Neither Thrive MES nor Motor Power Company holds SOC 2 Type 2 certification.

Neither Thrive MES nor Motor Power Company holds ISO 27001 certification.

Neither Thrive MES nor Motor Power Company holds PCI DSS certification.

Neither Thrive MES nor Motor Power Company holds HIPAA certification.

Neither Thrive MES nor Motor Power 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