Comparison Overview
Sequent Energy Management

Sequent Energy Management
1200 Smith St, Houston, Texas, 77002, US
Last Update: 01/04/2026
Williams completed its acquisition of Sequent Energy Management, L.P. and Sequent Energy Canada, Corp. from Southern Company Gas on July 1, 2021. The acquisition accelerates Williams’ natural gas pipeline and storage optimization and marketing growth and increases Will...

ExxonMobil
US
Last Update: 07/10/2026
The need for energy is universal. That's why ExxonMobil scientists and engineers are pioneering new research and pursuing new technologies to reduce emissions while creating more efficient fuels. We're committed to responsibly meeting the world's energy needs. We aim...
Compliance Ranges Comparison

Sequent Energy Management







ExxonMobil






Benchmark & Cyber Underwriting Signals
Incidents vs Oil and Gas Industry Avg (This Year)
No incidents recorded for Sequent Energy Management in 2026.
Incidents vs Oil and Gas Industry Avg (This Year)
No incidents recorded for ExxonMobil in 2026.
Incident History - Sequent Energy Management (X = Date, Y = Severity)
Sequent Energy Management cyber incidents detection timeline including parent company and subsidiaries.
Incident History - ExxonMobil (X = Date, Y = Severity)
ExxonMobil cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Sequent Energy Management

ExxonMobil
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.