Comparison Overview

AccuTherm

VS

Stork Turbo Blading

AccuTherm

None
Last Update: 2025-11-28
Between 750 and 799

At AccuTherm, we consider ourselves application experts in the process heating industry. We are flexible and willing to meet any application challenge in the market. This drive and determination ensures that we can meet the demands of a commercial OEM product just as easily as the intricate industrial process applications.

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

Stork Turbo Blading

Kamerlingh Onnesstraat 21, Sneek, undefined, 8606 JN, NL
Last Update: 2025-11-27

STORK TURBO BLADING, part of Bilfinger since April 2024, is the premier independent manufacturer of rotating and stationary components for steam & gas turbines, axial compressors, axial blowers, generator axial fans, hot gas expanders, ID & FD Fans, hydro turbines, impellers, diffusers, blisks and disks, and much more. contact Continental Europe: [email protected] contact United States of America: joe.walker @ usa.stork.com http://www.storkturboblading.com/ The Stork Turbo Blading group is the largest and oldest independent manufacturer of these components in the world, with manufacturing facilities in the USA and The Netherlands. Stork supplies OEM's, O&M/MRO facilities, and end-users in the power generation, oil & gas, petrochemical, aerospace and other industries. Our components are in use globally. Today, we are part of the STORK Group of companies, a world-class technical leader. STORK TURBO BLADING's core competency is rotating equipment components, done correctly, at speeds the others can not match.

NAICS: None
NAICS Definition:
Employees: 84
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/accutherm.jpeg
AccuTherm
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/stork-turbo-blading.jpeg
Stork Turbo Blading
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
AccuTherm
100%
Compliance Rate
0/4 Standards Verified
Stork Turbo Blading
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 AccuTherm in 2025.

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

No incidents recorded for Stork Turbo Blading in 2025.

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

AccuTherm cyber incidents detection timeline including parent company and subsidiaries

Incident History — Stork Turbo Blading (X = Date, Y = Severity)

Stork Turbo Blading cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/accutherm.jpeg
AccuTherm
Incidents

No Incident

https://images.rankiteo.com/companyimages/stork-turbo-blading.jpeg
Stork Turbo Blading
Incidents

No Incident

FAQ

AccuTherm company demonstrates a stronger AI Cybersecurity Score compared to Stork Turbo Blading company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Historically, Stork Turbo Blading company has disclosed a higher number of cyber incidents compared to AccuTherm company.

In the current year, Stork Turbo Blading company and AccuTherm company have not reported any cyber incidents.

Neither Stork Turbo Blading company nor AccuTherm company has reported experiencing a ransomware attack publicly.

Neither Stork Turbo Blading company nor AccuTherm company has reported experiencing a data breach publicly.

Neither Stork Turbo Blading company nor AccuTherm company has reported experiencing targeted cyberattacks publicly.

Neither AccuTherm company nor Stork Turbo Blading company has reported experiencing or disclosing vulnerabilities publicly.

Neither AccuTherm nor Stork Turbo Blading holds any compliance certifications.

Neither company holds any compliance certifications.

Neither AccuTherm company nor Stork Turbo Blading company has publicly disclosed detailed information about the number of their subsidiaries.

Stork Turbo Blading company employs more people globally than AccuTherm company, reflecting its scale as a Mechanical Or Industrial Engineering.

Neither AccuTherm nor Stork Turbo Blading holds SOC 2 Type 1 certification.

Neither AccuTherm nor Stork Turbo Blading holds SOC 2 Type 2 certification.

Neither AccuTherm nor Stork Turbo Blading holds ISO 27001 certification.

Neither AccuTherm nor Stork Turbo Blading holds PCI DSS certification.

Neither AccuTherm nor Stork Turbo Blading holds HIPAA certification.

Neither AccuTherm nor Stork Turbo Blading 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