Comparison Overview

Petro-Canada

VS

TotalEnergies

Petro-Canada

Calgary, CA
Last Update: 2026-01-20
Between 700 and 749

As a Suncor business, Petro-Canada is proudly Canadian, with a leading national network of retail stations, Petro-Pass cardlocks and bulk facilities. We know firsthand what it takes to run a business in Canada. It’s why we go beyond high-quality fuels and offer more ways to help you find efficiencies and get ahead. Through our commercial fuelling network we deliver bulk fuels, Diesel Exhaust Fluid and lubricants wherever and however you need them and our online fuel management tools help keep your fuel spend secure and in check. No matter your business, we are here to help keep you moving toward what matters most to you. When we put the leaf in our logo, we meant it. Because we share more than a country. We share a way to live. #LivebytheLeaf http://www.petro-canada.ca

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

TotalEnergies

2, place Jean Millier - La Défense 6, Paris La Défense Cedex, 92078, FR
Last Update: 2026-01-19
Between 750 and 799

Have you ever thought of offering your skills and expertise to a multinational company? Give your best to better energy and make the commitment with TotalEnergies. With over 500-plus professions in 130 countries, we offer high safety and environmental standards, strong ethical values, an innovation culture and wide-ranging career development. Be part of the global team whose mission is already shared by 105,000 employees : to be a world-class player in the energy transition

NAICS: 211
NAICS Definition: Oil and Gas Extraction
Employees: 82,218
Subsidiaries: 8
12-month incidents
0
Known data breaches
1
Attack type number
2

Compliance Badges Comparison

Security & Compliance Standards Overview

https://images.rankiteo.com/companyimages/petrocanada.jpeg
Petro-Canada
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/totalenergies.jpeg
TotalEnergies
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
Petro-Canada
100%
Compliance Rate
0/4 Standards Verified
TotalEnergies
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Oil and Gas Industry Average (This Year)

No incidents recorded for Petro-Canada in 2026.

Incidents vs Oil and Gas Industry Average (This Year)

No incidents recorded for TotalEnergies in 2026.

Incident History — Petro-Canada (X = Date, Y = Severity)

Petro-Canada cyber incidents detection timeline including parent company and subsidiaries

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

TotalEnergies cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/petrocanada.jpeg
Petro-Canada
Incidents

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

Date Detected: 06/2023
Type:Cyber Attack
Blog: Blog
https://images.rankiteo.com/companyimages/totalenergies.jpeg
TotalEnergies
Incidents

Date Detected: 8/2025
Type:Breach
Blog: Blog

Date Detected: 7/2024
Type:Cyber Attack
Blog: Blog

FAQ

TotalEnergies company demonstrates a stronger AI Cybersecurity Score compared to Petro-Canada company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Petro-Canada and TotalEnergies have experienced a similar number of publicly disclosed cyber incidents.

In the current year, TotalEnergies company and Petro-Canada company have not reported any cyber incidents.

Neither TotalEnergies company nor Petro-Canada company has reported experiencing a ransomware attack publicly.

TotalEnergies company has disclosed at least one data breach, while Petro-Canada company has not reported such incidents publicly.

Both TotalEnergies company and Petro-Canada company have reported experiencing targeted cyberattacks.

Neither Petro-Canada company nor TotalEnergies company has reported experiencing or disclosing vulnerabilities publicly.

Neither Petro-Canada nor TotalEnergies holds any compliance certifications.

Neither company holds any compliance certifications.

TotalEnergies company has more subsidiaries worldwide compared to Petro-Canada company.

TotalEnergies company employs more people globally than Petro-Canada company, reflecting its scale as a Oil and Gas.

Neither Petro-Canada nor TotalEnergies holds SOC 2 Type 1 certification.

Neither Petro-Canada nor TotalEnergies holds SOC 2 Type 2 certification.

Neither Petro-Canada nor TotalEnergies holds ISO 27001 certification.

Neither Petro-Canada nor TotalEnergies holds PCI DSS certification.

Neither Petro-Canada nor TotalEnergies holds HIPAA certification.

Neither Petro-Canada nor TotalEnergies holds GDPR certification.

Latest Global CVEs (Not Company-Specific)

Description

Typemill is a flat-file, Markdown-based CMS designed for informational documentation websites. A reflected Cross-Site Scripting (XSS) exists in the login error view template `login.twig` of versions 2.19.1 and below. The `username` value can be echoed back without proper contextual encoding when authentication fails. An attacker can execute script in the login page context. This issue has been fixed in version 2.19.2.

Risk Information
cvss3
Base: 5.4
Severity: LOW
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N
Description

A DOM-based Cross-Site Scripting (XSS) vulnerability exists in the DomainCheckerApp class within domain/script.js of Sourcecodester Domain Availability Checker v1.0. The vulnerability occurs because the application improperly handles user-supplied data in the createResultElement method by using the unsafe innerHTML property to render domain search results.

Description

A Remote Code Execution (RCE) vulnerability exists in Sourcecodester Modern Image Gallery App v1.0 within the gallery/upload.php component. The application fails to properly validate uploaded file contents. Additionally, the application preserves the user-supplied file extension during the save process. This allows an unauthenticated attacker to upload arbitrary PHP code by spoofing the MIME type as an image, leading to full system compromise.

Description

A UNIX symbolic link following issue in the jailer component in Firecracker version v1.13.1 and earlier and 1.14.0 on Linux may allow a local host user with write access to the pre-created jailer directories to overwrite arbitrary host files via a symlink attack during the initialization copy at jailer startup, if the jailer is executed with root privileges. To mitigate this issue, users should upgrade to version v1.13.2 or 1.14.1 or above.

Risk Information
cvss3
Base: 6.0
Severity: LOW
CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:N/I:H/A:H
cvss4
Base: 6.0
Severity: LOW
CVSS:4.0/AV:L/AC:L/AT:N/PR:H/UI:N/VC:N/VI:N/VA:N/SC:N/SI:H/SA:H/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

An information disclosure vulnerability exists in the /srvs/membersrv/getCashiers endpoint of the Aptsys gemscms backend platform thru 2025-05-28. This unauthenticated endpoint returns a list of cashier accounts, including names, email addresses, usernames, and passwords hashed using MD5. As MD5 is a broken cryptographic function, the hashes can be easily reversed using public tools, exposing user credentials in plaintext. This allows remote attackers to perform unauthorized logins and potentially gain access to sensitive POS operations or backend functions.