Comparison Overview

repsol

VS

Suncor

repsol

Méndez Álvaro, 44, Madrid, Madrid, ES, 28045
Last Update: 2026-04-02
View Profile
Between 750 and 799
http://www.repsol.com

What do you do with the energy that drives you every day? We strive to turn it into something useful for you—your decisions and your next steps. We are a company that explores multi-energy solutions through innovation, technology, and the curiosity of our team. With over 25,000 colleagues and presence in 27 countries, we deliver real solutions to the challenges of mobility, home, and industry. And we do it the way we know best: #AllOurEnergy.

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

Suncor

150 - 6 Avenue SW, Calgary, CA
Last Update: 2026-04-01
Between 800 and 849
http://www.suncor.com

In 1967, we pioneered commercial development of Canada's oil sands – one of the largest petroleum resource basins in the world. Since then, Suncor has grown to become a globally competitive integrated energy company with a balanced portfolio of high-quality assets, a strong balance sheet and significant growth prospects. Suncor’s operations include oil sands development and upgrading, conventional and offshore oil and gas production, petroleum refining, and product marketing under the Petro-Canada brand. Our use of innovative technology has made us an industry leader in the energy business – and with a strong strategy for growth, Suncor offers a solid foundation for you to continue building your career. As an employer, Suncor is one of the best companies in Canada, providing tremendous future potential where talented people thrive and lead. As our business evolves, so do our employment opportunities. Our work culture includes a dynamic mix of newcomers and experienced professionals, with a diversity of skills and expertise from all parts of Canada.

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

Compliance Badges Comparison

Security & Compliance Standards Overview

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

Benchmark & Cyber Underwriting Signals

Incidents vs Oil and Gas Industry Average (This Year)

No incidents recorded for repsol in 2026.

Incidents vs Oil and Gas Industry Average (This Year)

No incidents recorded for Suncor in 2026.

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

repsol cyber incidents detection timeline including parent company and subsidiaries

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

Suncor cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

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

No Incident

https://images.rankiteo.com/companyimages/suncor.jpeg
Suncor
Incidents

Date Detected: 06/2023
Type:Cyber Attack
Blog: Blog

Date Detected: 06/2023
Type:Cyber Attack
Blog: Blog

FAQ

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

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

In the current year, Suncor company and repsol company have not reported any cyber incidents.

Neither Suncor company nor repsol company has reported experiencing a ransomware attack publicly.

Neither Suncor company nor repsol company has reported experiencing a data breach publicly.

Suncor company has reported targeted cyberattacks, while repsol company has not reported such incidents publicly.

Neither repsol company nor Suncor company has reported experiencing or disclosing vulnerabilities publicly.

Neither repsol nor Suncor holds any compliance certifications.

Neither company holds any compliance certifications.

repsol company has more subsidiaries worldwide compared to Suncor company.

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

Neither repsol nor Suncor holds SOC 2 Type 1 certification.

Neither repsol nor Suncor holds SOC 2 Type 2 certification.

Neither repsol nor Suncor holds ISO 27001 certification.

Neither repsol nor Suncor holds PCI DSS certification.

Neither repsol nor Suncor holds HIPAA certification.

Neither repsol nor Suncor 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