Comparison Overview
Eversource Energy

Eversource Energy
56 Prospect Street, Hartford, 06103, US
Last Update: 22/05/2026
Eversource Energy (NYSE:ES), a Fortune 500 and Standard & Poor’s 500 energy company based in Connecticut, Massachusetts and New Hampshire, operates New England’s largest energy delivery system. Eversource is committed to safety, reliability, environmental leadership and...

NTPC Limited
New Delhi, IN
Last Update: 14/09/2026
NTPC Limited is India’s largest power generation utility with roots planted way back in 1975 to accelerate power development in India. Since then it has established itself as the dominant power major with a presence in the entire value chain of the power generation busi...
Compliance Ranges Comparison

Eversource Energy







NTPC Limited






Benchmark & Cyber Underwriting Signals
Incidents vs Utilities Industry Avg (This Year)
Eversource Energy has 45.36% fewer incidents than the average of same-industry companies with at least one recorded incident.
Incidents vs Utilities Industry Avg (This Year)
No incidents recorded for NTPC Limited in 2026.
Incident History - Eversource Energy (X = Date, Y = Severity)
Eversource Energy cyber incidents detection timeline including parent company and subsidiaries.
Incident History - NTPC Limited (X = Date, Y = Severity)
NTPC Limited cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Eversource Energy

NTPC Limited
FAQ
Latest Global CVEs
HTTP/2 servers could end up crashing due to inadvertently modifying its HPACK encoder concurrently. This happens because the server modifies the HPACK encoder from two goroutines without synchronization: one uses the encoder to encode a HEADERS frame as part of a response sent to a client and the other modifies the encoder's table size when handling a SETTINGS frame containing SETTINGS_HEADER_TABLE_SIZE that a client sends. A malicious client can repeatedly send a request while changing the header table size to crash the server.
Multiple ECH outer extension references are not permitted under RFC 9849; previously, a client could send a well-crafted packet that could trigger memory exhaustion in the server process by specifying multiple references. We now reject these as malformed and curb the memory amplification vector as a result.
A trusted template author may have previously written a valid template wherein the use of the 'yield' keyword would not be correctly escaped. We now ensure that valid keyword uses are escaped and non-keyword uses are not escaped.
Improper certificate validation in Microsoft Partner Center allows an unauthorized attacker to elevate privileges over a network.
Authorization bypass through user-controlled key in Microsoft Bookings allows an unauthorized attacker to elevate privileges over a network.