Comparison Overview

ExxonMobil

VS

Valero

ExxonMobil

undefined, undefined, undefined, undefined, US
Last Update: 2025-12-10
Between 800 and 849

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

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

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/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
ExxonMobil
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 ExxonMobil in 2025.

Incidents vs Oil and Gas Industry Average (This Year)

No incidents recorded for Valero in 2025.

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

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

No Incident

FAQ

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

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

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

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

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

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

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

Neither ExxonMobil nor Valero holds any compliance certifications.

Neither company holds any compliance certifications.

ExxonMobil company has more subsidiaries worldwide compared to Valero company.

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

Neither ExxonMobil nor Valero holds SOC 2 Type 1 certification.

Neither ExxonMobil nor Valero holds SOC 2 Type 2 certification.

Neither ExxonMobil nor Valero holds ISO 27001 certification.

Neither ExxonMobil nor Valero holds PCI DSS certification.

Neither ExxonMobil nor Valero holds HIPAA certification.

Neither ExxonMobil nor Valero holds GDPR certification.

Latest Global CVEs (Not Company-Specific)

Description

FreePBX Endpoint Manager is a module for managing telephony endpoints in FreePBX systems. Versions prior to 16.0.96 and 17.0.1 through 17.0.9 have a weak default password. By default, this is a 6 digit numeric value which can be brute forced. (This is the app_password parameter). Depending on local configuration, this password could be the extension, voicemail, user manager, DPMA or EPM phone admin password. This issue is fixed in versions 16.0.96 and 17.0.10.

Risk Information
cvss4
Base: 6.9
Severity: LOW
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/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

Neuron is a PHP framework for creating and orchestrating AI Agents. In versions 2.8.11 and below, the MySQLWriteTool executes arbitrary SQL provided by the caller using PDO::prepare() + execute() without semantic restrictions. This is consistent with the name (“write tool”), but in an LLM/agent context it becomes a high-risk capability: prompt injection or indirect prompt manipulation can cause execution of destructive queries such as DROP TABLE, TRUNCATE, DELETE, ALTER, or privilege-related statements (subject to DB permissions). Deployments that expose an agent with MySQLWriteTool enabled to untrusted input and/or run the tool with a DB user that has broad privileges are impacted. This issue is fixed in version 2.8.12.

Risk Information
cvss3
Base: 9.4
Severity: LOW
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:H
Description

Neuron is a PHP framework for creating and orchestrating AI Agents. Versions 2.8.11 and below use MySQLSelectTool, which is vulnerable to Read-Only Bypass. MySQLSelectTool is intended to be a read-only SQL tool (e.g., for LLM agent querying, however, validation based on the first keyword (e.g., SELECT) and a forbidden-keyword list does not block file-writing constructs such as INTO OUTFILE / INTO DUMPFILE. As a result, an attacker who can influence the tool input (e.g., via prompt injection through a public agent endpoint) may write arbitrary files to the DB server if the MySQL/MariaDB account has the FILE privilege and server configuration permits writes to a useful location (e.g., a web-accessible directory). This issue is fixed in version 2.8.12.

Risk Information
cvss3
Base: 8.2
Severity: LOW
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:N
Description

Okta Java Management SDK facilitates interactions with the Okta management API. In versions 11.0.0 through 20.0.0, race conditions may arise from concurrent requests using the ApiClient class. This could cause a status code or response header from one request’s response to influence another request’s response. This issue is fixed in version 20.0.1.

Risk Information
cvss3
Base: 8.4
Severity: HIGH
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:L
Description

The Auth0 Next.js SDK is a library for implementing user authentication in Next.js applications. When using versions 4.11.0 through 4.11.2 and 4.12.0, simultaneous requests on the same client may result in improper lookups in the TokenRequestCache for the request results. This issue is fixed in versions 4.11.2 and 4.12.1.

Risk Information
cvss3
Base: 5.4
Severity: HIGH
CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:H/I:L/A:N