Comparison Overview

ExxonMobil

VS

Transocean

ExxonMobil

undefined, undefined, undefined, undefined, US
Last Update: 2025-12-10
View Profile
Between 800 and 849
http://www.exxonmobil.com

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 to achieve #netzero emissions from our operated assets by 2050 (for Scope 1 and 2 greenhouse gas emissions) and are taking a comprehensive approach to create emission-reduction roadmaps for major operated assets. Find us also on: YouTube.com/ExxonMobil Find our latest Privacy Policy at https://corporate.exxonmobil.com/Global-legal-pages/privacy-policy See our terms and conditions at https://corporate.exxonmobil.com/global-legal-pages/terms-and-conditions Find resources on our GHG emission reduction efforts here: https://corporate.exxonmobil.com/resources

NAICS: 211
NAICS Definition: Oil and Gas Extraction
Employees: 61,842
Subsidiaries: 37
12-month incidents
0
Known data breaches
1
Attack type number
1
View Profile

Transocean

Turmstrasse 30, Zug, CH, 0000
Last Update: 2025-12-09
Between 750 and 799
http://www.deepwater.com

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

Compliance Badges Comparison

Security & Compliance Standards Overview

https://images.rankiteo.com/companyimages/exxonmobil.jpeg
ExxonMobil
—
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/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
Compliance Summary
ExxonMobil
100%
Compliance Rate
0/4 Standards Verified
Transocean
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Oil and Gas Industry Average (This Year)

No incidents recorded for ExxonMobil in 2025.

Incidents vs Oil and Gas Industry Average (This Year)

No incidents recorded for Transocean in 2025.

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

ExxonMobil cyber incidents detection timeline including parent company and subsidiaries

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

Transocean cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/exxonmobil.jpeg
ExxonMobil
Incidents

Date Detected: 12/2024
Type:Breach
Motivation: To protect corporate interests amid environmental scrutiny
Blog: Blog
https://images.rankiteo.com/companyimages/transocean.jpeg
Transocean
Incidents

No Incident

FAQ

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

ExxonMobil company has historically faced a number of disclosed cyber incidents, whereas Transocean company has not reported any.

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

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

ExxonMobil company has disclosed at least one data breach, while the other Transocean company has not reported such incidents publicly.

Neither Transocean company nor ExxonMobil company has reported experiencing targeted cyberattacks publicly.

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

Neither ExxonMobil nor Transocean holds any compliance certifications.

Neither company holds any compliance certifications.

ExxonMobil company has more subsidiaries worldwide compared to Transocean company.

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

Neither ExxonMobil nor Transocean holds SOC 2 Type 1 certification.

Neither ExxonMobil nor Transocean holds SOC 2 Type 2 certification.

Neither ExxonMobil nor Transocean holds ISO 27001 certification.

Neither ExxonMobil nor Transocean holds PCI DSS certification.

Neither ExxonMobil nor Transocean holds HIPAA certification.

Neither ExxonMobil nor Transocean holds GDPR certification.

Latest Global CVEs (Not Company-Specific)

Description

NXLog Agent before 6.11 can load a file specified by the OPENSSL_CONF environment variable.

Published
Date
2025-12-14
Updated
Date
2025-12-14
Risk Information
cvss3
Base: 8.1
Severity: HIGH
CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H
References
Description

uriparser through 0.9.9 allows unbounded recursion and stack consumption, as demonstrated by ParseMustBeSegmentNzNc with large input containing many commas.

Published
Date
2025-12-14
Updated
Date
2025-12-14
Risk Information
cvss3
Base: 2.9
Severity: HIGH
CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:L
References
Description

A vulnerability was detected in Mayan EDMS up to 4.10.1. The affected element is an unknown function of the file /authentication/. The manipulation results in cross site scripting. The attack may be performed from remote. The exploit is now public and may be used. Upgrading to version 4.10.2 is sufficient to fix this issue. You should upgrade the affected component. The vendor confirms that this is "[f]ixed in version 4.10.2". Furthermore, that "[b]ackports for older versions in process and will be out as soon as their respective CI pipelines complete."

Published
Date
2025-12-14
Updated
Date
2025-12-14
Risk Information
cvss2
Base: 5.0
Severity: LOW
AV:N/AC:L/Au:N/C:N/I:P/A:N
cvss3
Base: 4.3
Severity: LOW
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N
cvss4
Base: 5.3
Severity: LOW
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:P/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
References
Description

MJML through 4.18.0 allows mj-include directory traversal to test file existence and (in the type="css" case) read files. NOTE: this issue exists because of an incomplete fix for CVE-2020-12827.

Published
Date
2025-12-14
Updated
Date
2025-12-14
Risk Information
cvss3
Base: 4.5
Severity: HIGH
CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:C/C:L/I:N/A:L
References
Description

A half-blind Server Side Request Forgery (SSRF) vulnerability exists in kube-controller-manager when using the in-tree Portworx StorageClass. This vulnerability allows authorized users to leak arbitrary information from unprotected endpoints in the control plane’s host network (including link-local or loopback services).

Published
Date
2025-12-14
Updated
Date
2025-12-14
Risk Information
cvss3
Base: 5.8
Severity: HIGH
CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:H/I:N/A:N
References