Comparison Overview

Transocean

VS

Valero

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

Valero

One Valero Way, San Antonio, TX, US, 78249
Last Update: 2025-11-26
Between 750 and 799

Valero is an international manufacturer and marketer of transportation fuels and petrochemical products. We are a Fortune 500 company based in San Antonio, Texas, fueled by nearly 10,000 employees and 15 petroleum refineries with a combined throughput capacity of approximately 3.2 million barrels per day. We also proudly operate 12 ethanol plants in the Mid-Continent of the U.S., with a combined production capacity of 1.6 billion gallons per year. Our petroleum refineries are located in the United States, Canada and the United Kingdom. Valero also is a joint venture partner in Diamond Green Diesel, which operates a renewable diesel plant in Norco, Louisiana. Diamond Green Diesel is North America’s largest biomass-based diesel plant. Valero sells its products in the wholesale rack or bulk markets in the U.S., Canada, the U.K., Ireland and Latin America. Approximately 7,000 outlets carry Valero’s brand names. Visit www.valero.com for more information, and click 'Careers' to explore opportunities!

NAICS: 211
NAICS Definition: Oil and Gas Extraction
Employees: 10,812
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/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/valero-energy.jpeg
Valero
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
Valero
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 Valero in 2025.

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

Transocean cyber incidents detection timeline including parent company and subsidiaries

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

Valero 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/valero-energy.jpeg
Valero
Incidents

No Incident

FAQ

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

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

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

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

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

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

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

Neither Transocean nor Valero holds any compliance certifications.

Neither company holds any compliance certifications.

Neither Transocean company nor Valero company has publicly disclosed detailed information about the number of their subsidiaries.

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

Neither Transocean nor Valero holds SOC 2 Type 1 certification.

Neither Transocean nor Valero holds SOC 2 Type 2 certification.

Neither Transocean nor Valero holds ISO 27001 certification.

Neither Transocean nor Valero holds PCI DSS certification.

Neither Transocean nor Valero holds HIPAA certification.

Neither Transocean nor Valero 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