Comparison Overview

Valero

VS

Oxy

Valero

One Valero Way, San Antonio, TX, US, 78249
Last Update: 2025-12-10
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

Oxy

undefined, Houston, TX, 77046, US
Last Update: 2025-12-09
Between 800 and 849

Oxy is an international energy company with assets primarily in the United States, the Middle East and North Africa. We are one of the largest oil producers in the U.S., including a leading producer in the Permian and DJ basins, and offshore Gulf of Mexico. Our midstream and marketing segment provides flow assurance and maximizes the value of our oil and gas. Our chemical subsidiary OxyChem manufactures the building blocks for life-enhancing products. Our Oxy Low Carbon Ventures subsidiary is advancing leading-edge technologies and business solutions that economically grow our business while reducing emissions. We are committed to using our global leadership in carbon management to advance a lower-carbon world. Visit oxy.com for more information.

NAICS: 211
NAICS Definition: Oil and Gas Extraction
Employees: 16,183
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/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
https://images.rankiteo.com/companyimages/oxy.jpeg
Oxy
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
Valero
100%
Compliance Rate
0/4 Standards Verified
Oxy
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Oil and Gas Industry Average (This Year)

No incidents recorded for Valero in 2025.

Incidents vs Oil and Gas Industry Average (This Year)

No incidents recorded for Oxy in 2025.

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

Valero cyber incidents detection timeline including parent company and subsidiaries

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

Oxy cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/valero-energy.jpeg
Valero
Incidents

No Incident

https://images.rankiteo.com/companyimages/oxy.jpeg
Oxy
Incidents

No Incident

FAQ

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

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

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

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

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

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

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

Neither Valero nor Oxy holds any compliance certifications.

Neither company holds any compliance certifications.

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

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

Neither Valero nor Oxy holds SOC 2 Type 1 certification.

Neither Valero nor Oxy holds SOC 2 Type 2 certification.

Neither Valero nor Oxy holds ISO 27001 certification.

Neither Valero nor Oxy holds PCI DSS certification.

Neither Valero nor Oxy holds HIPAA certification.

Neither Valero nor Oxy 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.

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
Description

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

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

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

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

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