Comparison Overview

Control Gaging, Inc.

VS

Prophecy IoT®

Control Gaging, Inc.

847 Avis Drive, Ann Arbor, MI, US, 48108
Last Update: 2025-11-27
Between 750 and 799

For over forty years Control Gaging has designed and manufactured in-process and post-process gage systems that provide closed-loop feedback to machine controls based on real-time part measurement. Gages are available for ID, OD, disc and centerless grinders, turning machines, polish/superfinishing machines and other machining processes where finished size is critical.

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

Prophecy IoT®

15399 Canal Rd, Clinton Township, 48038, US
Last Update: 2025-11-21
Between 750 and 799

Smart Factory powered by Prophecy IoT® gives you the ability to listen to your machines. For years, we have all been reading and learning about the next revolution within the industry. Industry 4.0 some call it. Industrial IoT. Smart Factories. What does all this mean? Well, with Prophecy, what it means to us is enabling you to have a smart factory, finally giving you the ability to listen to your machines. For quite some time, your machines have been talking or wanting to talk. Now, we finally have a tool in which you can listen to what they're telling you and give accurate real time information about machine health, manufacturing performance, scrap, downtime, and unplanned downtime. And finally, the ability to accurately calculate your OEE, all while integrating that back into your ERP system. Smart Factory with Prophecy IoT® enables the ability to connect to any number of machines or devices through our automation engine with metrics up to 10,000 measurements per second. Smart Factory Powered by Prophecy IoT® gives you the ability to listen to your machines and take action on what it is they are telling you.

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

Compliance Badges Comparison

Security & Compliance Standards Overview

https://images.rankiteo.com/companyimages/control-gaging-inc-.jpeg
Control Gaging, 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/prophecy-iot.jpeg
Prophecy IoT®
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
Control Gaging, Inc.
100%
Compliance Rate
0/4 Standards Verified
Prophecy IoT®
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Industrial Automation Industry Average (This Year)

No incidents recorded for Control Gaging, Inc. in 2025.

Incidents vs Industrial Automation Industry Average (This Year)

No incidents recorded for Prophecy IoT® in 2025.

Incident History — Control Gaging, Inc. (X = Date, Y = Severity)

Control Gaging, Inc. cyber incidents detection timeline including parent company and subsidiaries

Incident History — Prophecy IoT® (X = Date, Y = Severity)

Prophecy IoT® cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/control-gaging-inc-.jpeg
Control Gaging, Inc.
Incidents

No Incident

https://images.rankiteo.com/companyimages/prophecy-iot.jpeg
Prophecy IoT®
Incidents

No Incident

FAQ

Both Control Gaging, Inc. company and Prophecy IoT® company demonstrate a comparable AI Cybersecurity Score, with strong governance and monitoring frameworks in place.

Historically, Prophecy IoT® company has disclosed a higher number of cyber incidents compared to Control Gaging, Inc. company.

In the current year, Prophecy IoT® company and Control Gaging, Inc. company have not reported any cyber incidents.

Neither Prophecy IoT® company nor Control Gaging, Inc. company has reported experiencing a ransomware attack publicly.

Neither Prophecy IoT® company nor Control Gaging, Inc. company has reported experiencing a data breach publicly.

Neither Prophecy IoT® company nor Control Gaging, Inc. company has reported experiencing targeted cyberattacks publicly.

Neither Control Gaging, Inc. company nor Prophecy IoT® company has reported experiencing or disclosing vulnerabilities publicly.

Neither Control Gaging, Inc. nor Prophecy IoT® holds any compliance certifications.

Neither company holds any compliance certifications.

Prophecy IoT® company has more subsidiaries worldwide compared to Control Gaging, Inc. company.

Neither Control Gaging, Inc. nor Prophecy IoT® holds SOC 2 Type 1 certification.

Neither Control Gaging, Inc. nor Prophecy IoT® holds SOC 2 Type 2 certification.

Neither Control Gaging, Inc. nor Prophecy IoT® holds ISO 27001 certification.

Neither Control Gaging, Inc. nor Prophecy IoT® holds PCI DSS certification.

Neither Control Gaging, Inc. nor Prophecy IoT® holds HIPAA certification.

Neither Control Gaging, Inc. nor Prophecy IoT® 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