Comparison Overview

Petrobras

VS

Suncor

Petrobras

Avenida República do Chile, n. 65, Centro, Rio de Janeiro, 20031-912, BR
Last Update: 2026-04-02
Between 750 and 799

Nosso propósito é prover energia que assegure prosperidade de forma ética, justa, segura e competitiva. Queremos ser a melhor empresa diversificada e integrada de energia na geração de valor, construindo um mundo mais sustentável, conciliando o foco em óleo e gás com a diversificação em negócios de baixo carbono (inclusive produtos petroquímicos e fertilizantes), sustentabilidade, segurança, respeito ao meio ambiente e atenção total às pessoas. Saiba mais em petrobras.com.br

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

Suncor

150 - 6 Avenue SW, Calgary, CA
Last Update: 2026-04-01
Between 800 and 849

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/petrobras.jpeg
Petrobras
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
Petrobras
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 Petrobras in 2026.

Incidents vs Oil and Gas Industry Average (This Year)

No incidents recorded for Suncor in 2026.

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

Petrobras 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/petrobras.jpeg
Petrobras
Incidents

Date Detected: 11/2025
Type:Ransomware
Motivation: financial gain, data exfiltration for competitive advantage
Blog: Blog
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 Petrobras company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Suncor company has faced a higher number of disclosed cyber incidents historically compared to Petrobras company.

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

Petrobras company has confirmed experiencing a ransomware attack, while Suncor company has not reported such incidents publicly.

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

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

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

Neither Petrobras nor Suncor holds any compliance certifications.

Neither company holds any compliance certifications.

Suncor company has more subsidiaries worldwide compared to Petrobras company.

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

Neither Petrobras nor Suncor holds SOC 2 Type 1 certification.

Neither Petrobras nor Suncor holds SOC 2 Type 2 certification.

Neither Petrobras nor Suncor holds ISO 27001 certification.

Neither Petrobras nor Suncor holds PCI DSS certification.

Neither Petrobras nor Suncor holds HIPAA certification.

Neither Petrobras 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.

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
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.

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
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.

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
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.

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
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.

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