Comparison Overview

Iberdrola

VS

ENGIE

Iberdrola

Plaza Euskadi, 5, Bilbao, Biscay, 48009, ES
Last Update: 2025-11-26
Between 800 and 849

With more than 180 years of history, Iberdrola is today a global energy leader, the leading wind power producer and one of the largest electricity companies in the world in terms of stock market capitalisation. We have been committed to clean energy for more than 20 years with the objective of exceeding 52,000 MW of renewable capacity by 2025. The group supplies energy to nearly 100 million people in dozens of countries, has more than 600,000 shareholders, a workforce of more than 42,300 employees. We are leading the energy transition to a sustainable model through our investments in renewables, smart grids, large-scale energy storage and digital transformation to deliver the most advanced products and services to our customers. Find out more in 'Life at Iberdrola'

NAICS: 22113
NAICS Definition: Electric Power Generation
Employees: 25,882
Subsidiaries: 13
12-month incidents
0
Known data breaches
0
Attack type number
0

ENGIE

1 place Samuel de Champlain, None, Paris, La défense, None, FR, 92930
Last Update: 2025-11-26
Between 750 and 799

What if your next career adventure started with ENGIE? Joining ENGIE means being part of a company at the forefront of the energy transition, committed to accelerating the shift to a carbon-neutral economy. With 98,000 employees across 30 countries, ENGIE's operations cover the entire energy value chain, from production to infrastructures and sales. ENGIE works across a range of complementary areas: renewable electricity and green gas production, flexibility assets (notably batteries), gas and electricity transmission and distribution networks, local energy infrastructures (heating and cooling networks) and energy supply to individuals, local authorities and businesses. #WithENGIE

NAICS: 22113
NAICS Definition: Electric Power Generation
Employees: 43,989
Subsidiaries: 8
12-month incidents
0
Known data breaches
1
Attack type number
1

Compliance Badges Comparison

Security & Compliance Standards Overview

https://images.rankiteo.com/companyimages/iberdrola.jpeg
Iberdrola
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/engie.jpeg
ENGIE
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
Iberdrola
100%
Compliance Rate
0/4 Standards Verified
ENGIE
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Renewable Energy Power Generation Industry Average (This Year)

No incidents recorded for Iberdrola in 2025.

Incidents vs Renewable Energy Power Generation Industry Average (This Year)

No incidents recorded for ENGIE in 2025.

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

Iberdrola cyber incidents detection timeline including parent company and subsidiaries

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

ENGIE cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/iberdrola.jpeg
Iberdrola
Incidents

No Incident

https://images.rankiteo.com/companyimages/engie.jpeg
ENGIE
Incidents

Date Detected: 08/2023
Type:Breach
Blog: Blog

FAQ

Iberdrola company demonstrates a stronger AI Cybersecurity Score compared to ENGIE company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

ENGIE company has historically faced a number of disclosed cyber incidents, whereas Iberdrola company has not reported any.

In the current year, ENGIE company and Iberdrola company have not reported any cyber incidents.

Neither ENGIE company nor Iberdrola company has reported experiencing a ransomware attack publicly.

ENGIE company has disclosed at least one data breach, while Iberdrola company has not reported such incidents publicly.

Neither ENGIE company nor Iberdrola company has reported experiencing targeted cyberattacks publicly.

Neither Iberdrola company nor ENGIE company has reported experiencing or disclosing vulnerabilities publicly.

Neither Iberdrola nor ENGIE holds any compliance certifications.

Neither company holds any compliance certifications.

Iberdrola company has more subsidiaries worldwide compared to ENGIE company.

ENGIE company employs more people globally than Iberdrola company, reflecting its scale as a Renewable Energy Power Generation.

Neither Iberdrola nor ENGIE holds SOC 2 Type 1 certification.

Neither Iberdrola nor ENGIE holds SOC 2 Type 2 certification.

Neither Iberdrola nor ENGIE holds ISO 27001 certification.

Neither Iberdrola nor ENGIE holds PCI DSS certification.

Neither Iberdrola nor ENGIE holds HIPAA certification.

Neither Iberdrola nor ENGIE 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