CNOOC
Last Update: 2025-11-26
Between 800 and 849
None
NAICS: 211
NAICS Definition: Oil and Gas Extraction
Employees: 3,848
Subsidiaries: 0
12-month incidents
0
Known data breaches
0
Attack type number
0
Comparison Overview
CNOOC
VS
Suncor
Suncor
Last Update: 2025-11-20
Between 750 and 799
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,321
Subsidiaries: 1
12-month incidents
0
Known data breaches
0
Attack type number
2
Compliance Badges Comparison
Security & Compliance Standards Overview
CNOOC
ISO 27001
Not verified
SOC2 Type 1
Not verified
SOC2 Type 2
Not verified
GDPR
Not verified
PCI DSS
Not verified
HIPAA
Not verified
Suncor
ISO 27001
Not verified
SOC2 Type 1
Not verified
SOC2 Type 2
Not verified
GDPR
Not verified
PCI DSS
Not verified
HIPAA
Not verified
Compliance Summary
CNOOC
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 CNOOC in 2025.
Incidents vs Oil and Gas Industry Average (This Year)
No incidents recorded for Suncor in 2025.
Incident History — CNOOC (X = Date, Y = Severity)
CNOOC 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
FAQ
CNOOC company demonstrates a stronger AI Cybersecurity Score compared to Suncor company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.
Suncor company has historically faced a number of disclosed cyber incidents, whereas CNOOC company has not reported any.
In the current year, Suncor company and CNOOC company have not reported any cyber incidents.
Neither Suncor company nor CNOOC company has reported experiencing a ransomware attack publicly.
Neither Suncor company nor CNOOC company has reported experiencing a data breach publicly.
Suncor company has reported targeted cyberattacks, while CNOOC company has not reported such incidents publicly.
Neither CNOOC company nor Suncor company has reported experiencing or disclosing vulnerabilities publicly.
Neither CNOOC nor Suncor holds any compliance certifications.
Neither company holds any compliance certifications.
Suncor company has more subsidiaries worldwide compared to CNOOC company.
Suncor company employs more people globally than CNOOC company, reflecting its scale as a Oil and Gas.
Neither CNOOC nor Suncor holds SOC 2 Type 1 certification.
Neither CNOOC nor Suncor holds SOC 2 Type 2 certification.
Neither CNOOC nor Suncor holds ISO 27001 certification.
Neither CNOOC nor Suncor holds PCI DSS certification.
Neither CNOOC nor Suncor holds HIPAA certification.
Neither CNOOC nor Suncor 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
References
- https://github.com/angular/angular/commit/0276479e7d0e280e0f8d26fa567d3b7aa97a516f
- https://github.com/angular/angular/commit/05fe6686a97fa0bcd3cf157805b3612033f975bc
- https://github.com/angular/angular/commit/3240d856d942727372a705252f7c8c115394a41e
- https://github.com/angular/angular/releases/tag/19.2.16
- https://github.com/angular/angular/releases/tag/20.3.14
- https://github.com/angular/angular/releases/tag/21.0.1
- https://github.com/angular/angular/security/advisories/GHSA-58c5-g7wp-6w37
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
