Comparison Overview

ST Engineering, Aethon

VS

JFlow Controls

ST Engineering, Aethon

200 Business Center Dr, Pittsburgh, 15205, US
Last Update: 2025-11-20
Between 750 and 799

ST Engineering, Aethon provides mobile robotics solutions to the healthcare and hospitality markets. We engineer, sell and support solutions to automate the transportation of goods and supplies. Our products and designed and built in Pittsburgh, PA and our people are passionate about using robotic technology to automate material movement and delivery to improve efficiency, labor utilization and safety. With operations in the US and Asia, Aethon autonomous mobile robot makes over 5 million deliveries annually in customer facilities around the globe. We have been featured in Economist, The Wall Street Journal, Inc., CNBC, 60 Minutes and Fox News. Our parent company, ST Engineering, is based in Singapore.

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

JFlow Controls

4665 Interstate Drive, Cincinnati, OH 45246, US
Last Update: 2025-11-26
Between 750 and 799

JFlow Controls is headquartered in Cincinnati, Ohio with an extensive representative network throughout the U.S. and abroad. We offer a wide range of valves including: Standard two-piece ball valves and three-piece ball valves Customized 3-way ball valves and 4-way ball valves Top entry valves Trunnion Valves Floating flanged valves Tri-clamp sanitary cavity filled and non-cavity filled valves Specialized products including Alloy material three piece, flanged and three-way valves, steam rated ball valves, metal seated valves and control valves The J Flow Controls management team has over 20 years of experience in offering customized project packages in all ranges of the industrial PVF market. Our customers include firms within a wide range of industries including: Oil & Gas Chemical Power Generation Semiconductor Bio Fuel/Ethanol Water & Wastewater Food & Beverage Marine Pharmaceutical Heating, Ventilating & Air Conditioning J Flow Controls offers unique pattern designs with fully traceable raw materials; spectroscopic testing of castings and numerically controlled machining. All valve components are inspected to international standards after assembly. The valves are fully tested to API 598. The manufacturing process is committed to the ultimate in close tolerance production allowing us to guarantee high quality, high cycle and flexibility in materials to meet our customer’s demands.

NAICS: None
NAICS Definition:
Employees: 29
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/aethon.jpeg
ST Engineering, Aethon
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/j-flow-controls.jpeg
JFlow Controls
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
ST Engineering, Aethon
100%
Compliance Rate
0/4 Standards Verified
JFlow Controls
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Industrial Automation Industry Average (This Year)

No incidents recorded for ST Engineering, Aethon in 2025.

Incidents vs Industrial Automation Industry Average (This Year)

No incidents recorded for JFlow Controls in 2025.

Incident History — ST Engineering, Aethon (X = Date, Y = Severity)

ST Engineering, Aethon cyber incidents detection timeline including parent company and subsidiaries

Incident History — JFlow Controls (X = Date, Y = Severity)

JFlow Controls cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/aethon.jpeg
ST Engineering, Aethon
Incidents

No Incident

https://images.rankiteo.com/companyimages/j-flow-controls.jpeg
JFlow Controls
Incidents

No Incident

FAQ

Both ST Engineering, Aethon company and JFlow Controls company demonstrate a comparable AI Cybersecurity Score, with strong governance and monitoring frameworks in place.

Historically, JFlow Controls company has disclosed a higher number of cyber incidents compared to ST Engineering, Aethon company.

In the current year, JFlow Controls company and ST Engineering, Aethon company have not reported any cyber incidents.

Neither JFlow Controls company nor ST Engineering, Aethon company has reported experiencing a ransomware attack publicly.

Neither JFlow Controls company nor ST Engineering, Aethon company has reported experiencing a data breach publicly.

Neither JFlow Controls company nor ST Engineering, Aethon company has reported experiencing targeted cyberattacks publicly.

Neither ST Engineering, Aethon company nor JFlow Controls company has reported experiencing or disclosing vulnerabilities publicly.

Neither ST Engineering, Aethon nor JFlow Controls holds any compliance certifications.

Neither company holds any compliance certifications.

Neither ST Engineering, Aethon company nor JFlow Controls company has publicly disclosed detailed information about the number of their subsidiaries.

ST Engineering, Aethon company employs more people globally than JFlow Controls company, reflecting its scale as a Industrial Automation.

Neither ST Engineering, Aethon nor JFlow Controls holds SOC 2 Type 1 certification.

Neither ST Engineering, Aethon nor JFlow Controls holds SOC 2 Type 2 certification.

Neither ST Engineering, Aethon nor JFlow Controls holds ISO 27001 certification.

Neither ST Engineering, Aethon nor JFlow Controls holds PCI DSS certification.

Neither ST Engineering, Aethon nor JFlow Controls holds HIPAA certification.

Neither ST Engineering, Aethon nor JFlow Controls 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