Comparison Overview

Shell

VS

Oxy

Shell

York Road, London, SE1 7NA, GB
Last Update: 2026-04-02
View Profile
Between 800 and 849
http://www.shell.com

Shell is a global group of energy and petrochemical companies, employing 96,000 people across 70+ countries. We serve around 1 million commercial and industrial customers, and around 33 million customers daily at our Shell-branded retail service stations. Our purpose is to power progress together by working with each other, our customers and our partners. #PoweringProgress

NAICS: 211
NAICS Definition: Oil and Gas Extraction
Employees: 185,291
Subsidiaries: 12
12-month incidents
1
Known data breaches
0
Attack type number
1
View Profile

Oxy

Houston, 77046, US
Last Update: 2026-04-01
Between 800 and 849
http://www.oxy.com

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 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,360
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/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
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
Shell
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)

Shell has 56.33% fewer 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 Oxy in 2026.

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

Shell 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/shell.jpeg
Shell
Incidents

Date Detected: 3/2026
Type:Vulnerability
Attack Vector: Web Application Vulnerability
Blog: Blog
https://images.rankiteo.com/companyimages/oxy.jpeg
Oxy
Incidents

No Incident

FAQ

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

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

In the current year, Shell company has reported more cyber incidents than Oxy company.

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

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

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

Shell company has disclosed at least one vulnerability, while Oxy company has not reported such incidents publicly.

Neither Shell nor Oxy holds any compliance certifications.

Neither company holds any compliance certifications.

Shell company has more subsidiaries worldwide compared to Oxy company.

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

Neither Shell nor Oxy holds SOC 2 Type 1 certification.

Neither Shell nor Oxy holds SOC 2 Type 2 certification.

Neither Shell nor Oxy holds ISO 27001 certification.

Neither Shell nor Oxy holds PCI DSS certification.

Neither Shell nor Oxy holds HIPAA certification.

Neither Shell nor Oxy holds GDPR certification.

Latest Global CVEs (Not Company-Specific)

Description

nimiq/core-rs-albatross is a Rust implementation of the Nimiq Proof-of-Stake protocol based on the Albatross consensus algorithm. Prior to version 1.3.0, two peer-facing consensus request handlers assume that the history index is always available and call blockchain.history_store.history_index().unwrap() directly. That assumption is false by construction. HistoryStoreProxy::history_index() explicitly returns None for the valid HistoryStoreProxy::WithoutIndex state. when a full node is syncing or otherwise running without the history index, a remote peer can send RequestTransactionsProof or RequestTransactionReceiptsByAddress and trigger an Option::unwrap() panic on the request path. This issue has been patched in version 1.3.0.

Published
Date
2026-04-03
Updated
Date
2026-04-03
Risk Information
cvss3
Base: 5.3
Severity: LOW
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
References
Description

PraisonAI is a multi-agent teams system. Prior to version 1.5.95, FileTools.download_file() in praisonaiagents validates the destination path but performs no validation on the url parameter, passing it directly to httpx.stream() with follow_redirects=True. An attacker who controls the URL can reach any host accessible from the server including cloud metadata services and internal network services. This issue has been patched in version 1.5.95.

Published
Date
2026-04-03
Updated
Date
2026-04-03
Risk Information
cvss3
Base: 8.6
Severity: LOW
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N
References
Description

PraisonAI is a multi-agent teams system. Prior to version 4.5.97, OAuthManager.validate_token() returns True for any token not found in its internal store, which is empty by default. Any HTTP request to the MCP server with an arbitrary Bearer token is treated as authenticated, granting full access to all registered tools and agent capabilities. This issue has been patched in version 4.5.97.

Published
Date
2026-04-03
Updated
Date
2026-04-03
Risk Information
cvss3
Base: 9.1
Severity: LOW
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
References
Description

PraisonAI is a multi-agent teams system. Prior to version 4.5.97, the PraisonAI Gateway server accepts WebSocket connections at /ws and serves agent topology at /info with no authentication. Any network client can connect, enumerate registered agents, and send arbitrary messages to agents and their tool sets. This issue has been patched in version 4.5.97.

Published
Date
2026-04-03
Updated
Date
2026-04-03
Risk Information
cvss3
Base: 9.1
Severity: LOW
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
References
Description

PraisonAI is a multi-agent teams system. Prior to version 4.5.90, MCPToolIndex.search_tools() compiles a caller-supplied string directly as a Python regular expression with no validation, sanitization, or timeout. A crafted regex causes catastrophic backtracking in the re engine, blocking the Python thread for hundreds of seconds and causing a complete service outage. This issue has been patched in version 4.5.90.

Published
Date
2026-04-03
Updated
Date
2026-04-03
Risk Information
cvss3
Base: 6.5
Severity: LOW
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
References