Comparison Overview

PJSC "Rosseti"​

VS

Shell

PJSC "Rosseti"​

undefined, Moscow City, undefined, undefined, RU
Last Update: 2025-11-25
Between 700 and 749

Rosseti, Public Joint Stock Company (PJSC ROSSETI) – an operator of energy grids in Russia, is one of the largest electric companies in the world. The company maintains 2.30 million km of power transmission lines, 490,000 substations with transformer capacity of more than 761 GW. In 2015, net power supply to consumers amounted to 720,5 billion kWh. The number of employees of the Rosseti Group of Companies is 216,000 people. The asset portfolio of PJSC ROSSETI includes 37 subsidiaries and affiliates, including 14 interregional and a main network company. The controlling shareholder of the company is the state represented by the Federal Agency for State Property Management of the Russian Federation, which owns 87.9% of the share capital. PJSC ROSSETI is a leading company in the Russian market in introducing innovative technologies to the main and distribution grid complex. The company pays great attention to such issues as energy conservation, energy efficiency, international cooperation, environmental protection and occupational safety.

NAICS: 211
NAICS Definition: Oil and Gas Extraction
Employees: 126
Subsidiaries: 0
12-month incidents
1
Known data breaches
1
Attack type number
1

Shell

York Road, London, England, SE1 7NA, GB
Last Update: 2025-11-20
Between 800 and 849

Shell is a global group of energy and petrochemical companies, employing 103,000 people and with operations in more than 70 countries. We serve more than 1 million commercial and industrial customers, and around 33 million customers daily at more than 47,000 Shell-branded retail service stations. Our purpose is to power progress together by providing more and cleaner energy solutions. #PoweringProgress

NAICS: 211
NAICS Definition: Oil and Gas Extraction
Employees: 154,123
Subsidiaries: 11
12-month incidents
0
Known data breaches
0
Attack type number
0

Compliance Badges Comparison

Security & Compliance Standards Overview

https://images.rankiteo.com/companyimages/pjsc-rosseti-.jpeg
PJSC "Rosseti"​
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/shell.jpeg
Shell
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
PJSC "Rosseti"​
100%
Compliance Rate
0/4 Standards Verified
Shell
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Oil and Gas Industry Average (This Year)

PJSC "Rosseti"​ has 19.05% more incidents than the average of same-industry companies with at least one recorded incident.

Incidents vs Oil and Gas Industry Average (This Year)

No incidents recorded for Shell in 2025.

Incident History — PJSC "Rosseti"​ (X = Date, Y = Severity)

PJSC "Rosseti"​ cyber incidents detection timeline including parent company and subsidiaries

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

Shell cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/pjsc-rosseti-.jpeg
PJSC "Rosseti"​
Incidents

Date Detected: 3/2025
Type:Breach
Attack Vector: Android Banking Trojan
Motivation: Financial Gain
Blog: Blog
https://images.rankiteo.com/companyimages/shell.jpeg
Shell
Incidents

No Incident

FAQ

Shell company demonstrates a stronger AI Cybersecurity Score compared to PJSC "Rosseti"​ company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

PJSC "Rosseti"​ company has historically faced a number of disclosed cyber incidents, whereas Shell company has not reported any.

In the current year, PJSC "Rosseti"​ company has reported more cyber incidents than Shell company.

Neither Shell company nor PJSC "Rosseti"​ company has reported experiencing a ransomware attack publicly.

PJSC "Rosseti"​ company has disclosed at least one data breach, while the other Shell company has not reported such incidents publicly.

Neither Shell company nor PJSC "Rosseti"​ company has reported experiencing targeted cyberattacks publicly.

Neither PJSC "Rosseti"​ company nor Shell company has reported experiencing or disclosing vulnerabilities publicly.

Neither PJSC "Rosseti"​ nor Shell holds any compliance certifications.

Neither company holds any compliance certifications.

Shell company has more subsidiaries worldwide compared to PJSC "Rosseti"​ company.

Shell company employs more people globally than PJSC "Rosseti"​ company, reflecting its scale as a Oil and Gas.

Neither PJSC "Rosseti"​ nor Shell holds SOC 2 Type 1 certification.

Neither PJSC "Rosseti"​ nor Shell holds SOC 2 Type 2 certification.

Neither PJSC "Rosseti"​ nor Shell holds ISO 27001 certification.

Neither PJSC "Rosseti"​ nor Shell holds PCI DSS certification.

Neither PJSC "Rosseti"​ nor Shell holds HIPAA certification.

Neither PJSC "Rosseti"​ nor Shell 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