Comparison Overview

NOV

VS

RussNeft

NOV

10353 Richmond Ave, Houston, Texas, US, 77042
Last Update: 2025-12-09
Between 750 and 799

NOV delivers technology-driven solutions to empower the global energy industry. For more than 150 years, NOV has pioneered innovations that enable its customers to safely produce abundant energy while minimizing environmental impact. The energy industry depends on NOV’s deep expertise and technology to continually improve oilfield operations and assist in efforts to advance the energy transition towards a more sustainable future. NOV powers the industry that powers the world.

NAICS: 211
NAICS Definition: Oil and Gas Extraction
Employees: 35,039
Subsidiaries: 20
12-month incidents
0
Known data breaches
0
Attack type number
0

RussNeft

69, Pyatnitskaya st Moscow, RU
Last Update: 2025-12-09
Between 750 and 799

ОАО Oil and Gas Company «RussNeft» came into existence in September 2002 . The structure of OAO NK “RussNeft” counts 24 upstream enterprises, 2 refineries, its own distribution net of gas filling stations. Geographic reach of “RussNeft” covers 12 regions of Russia and CIS: Khanty-Mansi Autonomous District, Yamalo-Nenets Autonomous District, Tomsk, Ulianovsk, Penza, Briansk, Saratov, Kirov and Orenburg regions, the Republics of Udmurtia and Belarus. The head office of the Company is in Moscow. The Company is developing 167 oil and gas fields. The net effective pay of the company exceeds 600 million tons. The total amount of oil produced by the enterprises of the company is 13 million tons. In accordance with the approved long-term strategy of development “RussNeft is going within a 7-year period to build up the volume of production by more than one third. The total throughput of the refineries is 5.134 million tons. Since 2011 engine fuels of the Company meet ecological class Euro 3 quality standard.

NAICS: 211
NAICS Definition: Oil and Gas Extraction
Employees: 10,001
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/novglobal.jpeg
NOV
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/russneft.jpeg
RussNeft
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
NOV
100%
Compliance Rate
0/4 Standards Verified
RussNeft
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Oil and Gas Industry Average (This Year)

No incidents recorded for NOV in 2025.

Incidents vs Oil and Gas Industry Average (This Year)

No incidents recorded for RussNeft in 2025.

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

NOV cyber incidents detection timeline including parent company and subsidiaries

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

RussNeft cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/novglobal.jpeg
NOV
Incidents

No Incident

https://images.rankiteo.com/companyimages/russneft.jpeg
RussNeft
Incidents

No Incident

FAQ

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

Historically, RussNeft company has disclosed a higher number of cyber incidents compared to NOV company.

In the current year, RussNeft company and NOV company have not reported any cyber incidents.

Neither RussNeft company nor NOV company has reported experiencing a ransomware attack publicly.

Neither RussNeft company nor NOV company has reported experiencing a data breach publicly.

Neither RussNeft company nor NOV company has reported experiencing targeted cyberattacks publicly.

Neither NOV company nor RussNeft company has reported experiencing or disclosing vulnerabilities publicly.

Neither NOV nor RussNeft holds any compliance certifications.

Neither company holds any compliance certifications.

NOV company has more subsidiaries worldwide compared to RussNeft company.

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

Neither NOV nor RussNeft holds SOC 2 Type 1 certification.

Neither NOV nor RussNeft holds SOC 2 Type 2 certification.

Neither NOV nor RussNeft holds ISO 27001 certification.

Neither NOV nor RussNeft holds PCI DSS certification.

Neither NOV nor RussNeft holds HIPAA certification.

Neither NOV nor RussNeft 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