Comparison Overview

Petro-Canada

VS

PETROVIETNAM

Petro-Canada

Calgary, CA
Last Update: 2025-11-24
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
2

PETROVIETNAM

18 Lang Ha Hanoi, 101000, VN
Last Update: 2025-11-24
Between 750 and 799

Petrovietnam’s business - Core business: + Exploration, Production, Refinery, Petrochemicals, Storage, Transportation and Service in Petroleum Field; + Importing and Exporting petroleum materials, equipment and productions; + Distributing oil and gas products and hydrocarbon materials; - Other fields: + Surveying, designing, constructing both petroleum and civil sites; + Consulting in construction and investment, designing the petroleum and civil projects, manufacturing and trading construction materials; + Investing in real estate; + Investing in power projects; + Operating in Finance, banking, insurance, securities fields; + Manpower training and supplying in petroleum fields and labour export; + Operating in Hotel, Travel, Office business;

NAICS: 211
NAICS Definition:
Employees: 10,001
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/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/petrovietnam-group.jpeg
PETROVIETNAM
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
PETROVIETNAM
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 2025.

Incidents vs Oil and Gas Industry Average (This Year)

No incidents recorded for PETROVIETNAM in 2025.

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

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

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

PETROVIETNAM 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

Date Detected: 06/2023
Type:Data Leak
Blog: Blog
https://images.rankiteo.com/companyimages/petrovietnam-group.jpeg
PETROVIETNAM
Incidents

No Incident

FAQ

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

Petro-Canada company has historically faced a number of disclosed cyber incidents, whereas PETROVIETNAM company has not reported any.

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

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

Neither PETROVIETNAM company nor Petro-Canada company has reported experiencing a data breach publicly.

Petro-Canada company has reported targeted cyberattacks, while PETROVIETNAM company has not reported such incidents publicly.

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

Neither Petro-Canada nor PETROVIETNAM holds any compliance certifications.

Neither company holds any compliance certifications.

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

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

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

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

Neither Petro-Canada nor PETROVIETNAM holds ISO 27001 certification.

Neither Petro-Canada nor PETROVIETNAM holds PCI DSS certification.

Neither Petro-Canada nor PETROVIETNAM holds HIPAA certification.

Neither Petro-Canada nor PETROVIETNAM 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