Comparison Overview
RWE
RWE
RWE Platz 1, Essen, North Rhine-Westphalia, DE, 45141
Last Update: 09/10/2026
RWE is leading the way to a modern energy world. With its investment and growth strategy, RWE is contributing significantly to the success of the energy transition and the decarbonisation of the energy system. Around 20,000 employees work for the company in over 20 coun...
Southern Company
30 Ivan Allen Jr Blvd, Atlanta, GA, US, 30308
Last Update: 05/10/2026
Together with our subsidiaries, we deliver clean, safe, reliable and affordable energy to our 9 million customers. Our focus is doing so with service excellence. That means we are leaders who take action to meet our customers’ and communities’ needs while advancing ou...
Compliance Ranges Comparison
RWE
Southern Company
Benchmark & Cyber Underwriting Signals
Incidents vs Utilities Industry Avg (This Year)
No incidents recorded for RWE in 2026.
Incidents vs Utilities Industry Avg (This Year)
Southern Company has 0.99% fewer incidents than the average of all companies with at least one recorded incident.
Incident History - RWE (X = Date, Y = Severity)
RWE cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Southern Company (X = Date, Y = Severity)
Southern Company cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
RWE
Southern Company
FAQ
Latest Global CVEs
IBM TRIRIGA Application Platform 5.0.0 through 5.0.8 could allow a remote authenticated attacker to obtain sensitive information due to exposure of session tokens in the HTML response.
IBM TRIRIGA Application Platform 5.0.0 through 5.0.8 could allow a remote authenticated attacker to obtain sensitive information due to an XML external entity (XXE) injection flaw.
IBM Aspera Enterprise WebApps 1.0.0 through 1.0.6 could allow a local attacker to obtain sensitive information due to cleartext transmission of sensitive information.
IBM Planning Analytics 2.0, and 2.1 could allow a remote authenticated attacker to execute arbitrary code due to a stack-based buffer overflow.
IBM DataStage on Cloud Pak for Data 5.4.0.0 can allow a man-in-the-middle attacker to present a forged TLS certificate, intercept the connection, and capture the IAM bearer Authorization header automatically attached by the session adapter. The captured token grants full platform-scope tenant API access, enabling the attacker to read and manipulate the victim's DataStage projects, flows, assets, and pipeline definitions. This is client-side SDK code running on the user's own machine, so exploitation requires an external network interceptor rather than a co-tenant in the shared cluster.