Comparison Overview

Transocean

VS

Baker Hughes

Transocean

Turmstrasse 30, Zug, CH, 0000
Last Update: 2025-11-22
Between 750 and 799

Transocean is a leading international provider of offshore contract drilling services for oil and gas wells. The company specializes in technically demanding sectors of the global offshore drilling business, with a particular focus on ultra-deepwater and harsh environment drilling services and operates the highest specification floating offshore drilling fleet in the world. Transocean owns or has partial ownership interests in and operates a fleet of 27 mobile offshore drilling units, consisting of 20 ultra-deepwater floaters and seven harsh environment floaters.

NAICS: 211
NAICS Definition: Oil and Gas Extraction
Employees: 10,007
Subsidiaries: 0
12-month incidents
0
Known data breaches
0
Attack type number
0

Baker Hughes

17021 Aldine Westfield, Houston, Texas, 77073, US
Last Update: 2025-11-20
Between 800 and 849

Baker Hughes (NASDAQ: BKR) is an energy technology company that provides solutions for energy and industrial customers worldwide. Built on a century of experience and conducting business in over 120 countries, our innovative technologies and services are taking energy forward – making it safer, cleaner and more efficient for people and the planet. For more than a century, our inventions have revolutionized energy. We harness the power of engineering, data, and science to redefine what's possible. Our diverse portfolio of equipment and service capabilities span the energy and industrial value chain. Our two operating segments, Oilfield Services & Equipment (OFSE) and Industrial & Energy Technology (IET), are organized based on the nature of our markets and customers, and consist of similar products and services. Visit us at bakerhughes.com to learn more.

NAICS: 211
NAICS Definition: Oil and Gas Extraction
Employees: 65,278
Subsidiaries: 10
12-month incidents
0
Known data breaches
0
Attack type number
0

Compliance Badges Comparison

Security & Compliance Standards Overview

https://images.rankiteo.com/companyimages/transocean.jpeg
Transocean
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/bhge.jpeg
Baker Hughes
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
Transocean
100%
Compliance Rate
0/4 Standards Verified
Baker Hughes
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Oil and Gas Industry Average (This Year)

No incidents recorded for Transocean in 2025.

Incidents vs Oil and Gas Industry Average (This Year)

No incidents recorded for Baker Hughes in 2025.

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

Transocean cyber incidents detection timeline including parent company and subsidiaries

Incident History — Baker Hughes (X = Date, Y = Severity)

Baker Hughes cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/transocean.jpeg
Transocean
Incidents

No Incident

https://images.rankiteo.com/companyimages/bhge.jpeg
Baker Hughes
Incidents

No Incident

FAQ

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

Historically, Baker Hughes company has disclosed a higher number of cyber incidents compared to Transocean company.

In the current year, Baker Hughes company and Transocean company have not reported any cyber incidents.

Neither Baker Hughes company nor Transocean company has reported experiencing a ransomware attack publicly.

Neither Baker Hughes company nor Transocean company has reported experiencing a data breach publicly.

Neither Baker Hughes company nor Transocean company has reported experiencing targeted cyberattacks publicly.

Neither Transocean company nor Baker Hughes company has reported experiencing or disclosing vulnerabilities publicly.

Neither Transocean nor Baker Hughes holds any compliance certifications.

Neither company holds any compliance certifications.

Baker Hughes company has more subsidiaries worldwide compared to Transocean company.

Baker Hughes company employs more people globally than Transocean company, reflecting its scale as a Oil and Gas.

Neither Transocean nor Baker Hughes holds SOC 2 Type 1 certification.

Neither Transocean nor Baker Hughes holds SOC 2 Type 2 certification.

Neither Transocean nor Baker Hughes holds ISO 27001 certification.

Neither Transocean nor Baker Hughes holds PCI DSS certification.

Neither Transocean nor Baker Hughes holds HIPAA certification.

Neither Transocean nor Baker Hughes 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