Comparison Overview

Oxy

VS

Repsol

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

Repsol

Méndez Álvaro, 44, Madrid, Madrid, 28045, ES
Last Update: 2025-12-09
Between 750 and 799

At Repsol, we are at the forefront of the energy sector to build the future of energy with innovation and sustainability. We are a strong multienergy company that creates value in an integrated, diversified, and sustainable way to promote progress in society. We leverage our past experience to be present in the future of energy. Our global presence ensures the diversity that characterizes us as seen in our multicultural and multidisciplinary team that as of today comprises more than 25,000 people representing 77 nationalities who work across 27 countries. If you would like to learn more about us and join the Repsol team, go to the “Life” section.

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

Compliance Badges Comparison

Security & Compliance Standards Overview

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
https://images.rankiteo.com/companyimages/repsol.jpeg
Repsol
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
Oxy
100%
Compliance Rate
0/4 Standards Verified
Repsol
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Oil and Gas Industry Average (This Year)

No incidents recorded for Oxy in 2025.

Incidents vs Oil and Gas Industry Average (This Year)

No incidents recorded for Repsol in 2025.

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

Oxy cyber incidents detection timeline including parent company and subsidiaries

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

Repsol cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

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

No Incident

https://images.rankiteo.com/companyimages/repsol.jpeg
Repsol
Incidents

No Incident

FAQ

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

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

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

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

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

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

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

Neither Oxy nor Repsol holds any compliance certifications.

Neither company holds any compliance certifications.

Repsol company has more subsidiaries worldwide compared to Oxy company.

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

Neither Oxy nor Repsol holds SOC 2 Type 1 certification.

Neither Oxy nor Repsol holds SOC 2 Type 2 certification.

Neither Oxy nor Repsol holds ISO 27001 certification.

Neither Oxy nor Repsol holds PCI DSS certification.

Neither Oxy nor Repsol holds HIPAA certification.

Neither Oxy nor Repsol 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