Comparison Overview

Wärtsilä

VS

Metso

Wärtsilä

Hiililaiturinkuja 2, Helsinki, Southern Finland, FI, 00180
Last Update: 2025-11-23
Between 750 and 799

We enable sustainable societies through innovation in technology and services together with all our stakeholders – today and tomorrow. We emphasise innovation in sustainable technology and services to help our customers continuously improve environmental and economic performance. We work together with our strong ecosystem of partners every day, providing a wide portfolio of leading technologies and innovative solutions that offer our customers superior uptime, reliability and foreseeable lifecycle costs across their operations. Our global passionate team of 17,500 energy and maritime experts in 200 locations in more than 70 countries is committed to shaping decarbonisation transformation of our industries across the globe.

NAICS: 3332
NAICS Definition: Industrial Machinery Manufacturing
Employees: 13,330
Subsidiaries: 4
12-month incidents
0
Known data breaches
0
Attack type number
0

Metso

Rauhalanpuisto 9, Espoo, 02230, FI
Last Update: 2025-11-23
Between 750 and 799

Metso is a frontrunner in sustainable technologies, end-to-end solutions and services for the aggregates, minerals processing and metals refining industries globally. By improving our customers’ energy and water efficiency, increasing their productivity, and reducing environmental risks with our product and process expertise, we are the partner for positive change. Metso is committed to limiting global warming to 1.5°C with Science Based Targets.

NAICS: 3332
NAICS Definition: Industrial Machinery Manufacturing
Employees: 20,150
Subsidiaries: 4
12-month incidents
0
Known data breaches
0
Attack type number
0

Compliance Badges Comparison

Security & Compliance Standards Overview

https://images.rankiteo.com/companyimages/wartsila.jpeg
Wärtsilä
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/metsoofficial.jpeg
Metso
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
Wärtsilä
100%
Compliance Rate
0/4 Standards Verified
Metso
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Industrial Machinery Manufacturing Industry Average (This Year)

No incidents recorded for Wärtsilä in 2025.

Incidents vs Industrial Machinery Manufacturing Industry Average (This Year)

No incidents recorded for Metso in 2025.

Incident History — Wärtsilä (X = Date, Y = Severity)

Wärtsilä cyber incidents detection timeline including parent company and subsidiaries

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

Metso cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/wartsila.jpeg
Wärtsilä
Incidents

No Incident

https://images.rankiteo.com/companyimages/metsoofficial.jpeg
Metso
Incidents

No Incident

FAQ

Wärtsilä company demonstrates a stronger AI Cybersecurity Score compared to Metso company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Historically, Metso company has disclosed a higher number of cyber incidents compared to Wärtsilä company.

In the current year, Metso company and Wärtsilä company have not reported any cyber incidents.

Neither Metso company nor Wärtsilä company has reported experiencing a ransomware attack publicly.

Neither Metso company nor Wärtsilä company has reported experiencing a data breach publicly.

Neither Metso company nor Wärtsilä company has reported experiencing targeted cyberattacks publicly.

Neither Wärtsilä company nor Metso company has reported experiencing or disclosing vulnerabilities publicly.

Neither Wärtsilä nor Metso holds any compliance certifications.

Neither company holds any compliance certifications.

Both Metso company and Wärtsilä company have a similar number of subsidiaries worldwide.

Metso company employs more people globally than Wärtsilä company, reflecting its scale as a Industrial Machinery Manufacturing.

Neither Wärtsilä nor Metso holds SOC 2 Type 1 certification.

Neither Wärtsilä nor Metso holds SOC 2 Type 2 certification.

Neither Wärtsilä nor Metso holds ISO 27001 certification.

Neither Wärtsilä nor Metso holds PCI DSS certification.

Neither Wärtsilä nor Metso holds HIPAA certification.

Neither Wärtsilä nor Metso 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