Comparison Overview

API Heat Transfer

VS

Weld Class Engineering

API Heat Transfer

2777 Walden Avenue, Buffalo, NY, 14225, US
Last Update: 2025-11-27

API Heat Transfer has successfully established itself as the market leader in innovative and energy efficient equipment. Our 130-year heritage has been dedicated to designing and delivering world-class heat transfer products for almost every industry. Our reputation is bolstered by our worldwide network of manufacturing facilities and more than 1,600 employees who provide sales, service, and support. Our process is ingrained in our culture and has served customers around the world, including your country. Upon working with us, you’ll find our performance sets us apart. With a broad product portfolio and expertise that spans multiple heat transfer technologies, we deliver the most complete solution for virtually every application and industry. Our team of engineering experts have a thorough understanding of complex challenges with decades of real-world experience you can trust. You’ll feel as confident in your engineering partner as you do your product.

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

Weld Class Engineering

5 Pioneer Dr, Woonona, New South Wales, 2517, AU
Last Update: 2025-11-27

Weld Class Engineering was founded with the vision of bringing a new level of expectation to the manufacturing and services industry. It is our mission to over deliver in everything we do. Our customers know that we truly care about their business and will do everything in our power to help them grow. we specialise in Stainless steel tanks, pressure vessels, piping, polishing, and balustrades in various metals. We also have a large contractor base of >100 + contractors in which we labour hire to other fabricators and clients. Specialty experience in industries such as Pharmaceutical, food, beverage, nuclear medicine, mining, waste water and chemical.

NAICS: None
NAICS Definition:
Employees: 2
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/api-heat-transfer.jpeg
API Heat Transfer
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/weldclassengineering.jpeg
Weld Class Engineering
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
API Heat Transfer
100%
Compliance Rate
0/4 Standards Verified
Weld Class Engineering
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 API Heat Transfer in 2025.

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

No incidents recorded for Weld Class Engineering in 2025.

Incident History — API Heat Transfer (X = Date, Y = Severity)

API Heat Transfer cyber incidents detection timeline including parent company and subsidiaries

Incident History — Weld Class Engineering (X = Date, Y = Severity)

Weld Class Engineering cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/api-heat-transfer.jpeg
API Heat Transfer
Incidents

No Incident

https://images.rankiteo.com/companyimages/weldclassengineering.jpeg
Weld Class Engineering
Incidents

No Incident

FAQ

API Heat Transfer company demonstrates a stronger AI Cybersecurity Score compared to Weld Class Engineering company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Historically, Weld Class Engineering company has disclosed a higher number of cyber incidents compared to API Heat Transfer company.

In the current year, Weld Class Engineering company and API Heat Transfer company have not reported any cyber incidents.

Neither Weld Class Engineering company nor API Heat Transfer company has reported experiencing a ransomware attack publicly.

Neither Weld Class Engineering company nor API Heat Transfer company has reported experiencing a data breach publicly.

Neither Weld Class Engineering company nor API Heat Transfer company has reported experiencing targeted cyberattacks publicly.

Neither API Heat Transfer company nor Weld Class Engineering company has reported experiencing or disclosing vulnerabilities publicly.

Neither API Heat Transfer nor Weld Class Engineering holds any compliance certifications.

Neither company holds any compliance certifications.

Neither API Heat Transfer company nor Weld Class Engineering company has publicly disclosed detailed information about the number of their subsidiaries.

API Heat Transfer company employs more people globally than Weld Class Engineering company, reflecting its scale as a Mechanical Or Industrial Engineering.

Neither API Heat Transfer nor Weld Class Engineering holds SOC 2 Type 1 certification.

Neither API Heat Transfer nor Weld Class Engineering holds SOC 2 Type 2 certification.

Neither API Heat Transfer nor Weld Class Engineering holds ISO 27001 certification.

Neither API Heat Transfer nor Weld Class Engineering holds PCI DSS certification.

Neither API Heat Transfer nor Weld Class Engineering holds HIPAA certification.

Neither API Heat Transfer nor Weld Class Engineering 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