Comparison Overview
The Energy Authority

The Energy Authority
1301 Riverplace Blvd, Suite 2700, Jacksonville, Florida, US, 32207
Last Update: 02/04/2026
The Energy Authority (TEA®) is the strategic partner of choice in providing energy solutions to public power. We are wholly-owned and directed by our public power Members who participate in our organization's decision-making. Today, over 80 public power utilities acros...

Duke Energy Corporation
525 S Tryon St, Charlotte, 28202, US
Last Update: 07/10/2026
Duke Energy, a Fortune 150 company headquartered in Charlotte, N.C., is one of America’s largest energy holding companies. The company’s electric utilities serve 8.4 million customers in North Carolina, South Carolina, Florida, Indiana, Ohio and Kentucky, and collective...
Compliance Ranges Comparison

The Energy Authority







Duke Energy Corporation






Benchmark & Cyber Underwriting Signals
Incidents vs Utilities Industry Avg (This Year)
No incidents recorded for The Energy Authority in 2026.
Incidents vs Utilities Industry Avg (This Year)
No incidents recorded for Duke Energy Corporation in 2026.
Incident History - The Energy Authority (X = Date, Y = Severity)
The Energy Authority cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Duke Energy Corporation (X = Date, Y = Severity)
Duke Energy Corporation cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

The Energy Authority

Duke Energy Corporation
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.