Comparison Overview

Chevron

VS

PT Pertamina (Persero)

Chevron

1400 Smith St, Houston, Texas, 77002, US
Last Update: 2025-12-02
Between 800 and 849

Our greatest resource is our people. Their ingenuity, creativity and collaboration have met the complex challenges of energy’s past. Together, we’ll take on the future. We support the LinkedIn Terms of Use (User Agreement), and we expect visitors to our page to do the same. We encourage open, lively conversation with a few simple rules: --We reserve the right to correct factual errors. --We will reply to comments when appropriate. --If we disagree with other opinions, we will do so respectfully. --You may not post anything that is spam or that is abusive, profane, or defamatory toward a person, entity, belief, or symbol. --We will delete any posts that contain personal information such as email addresses, phone numbers and physical addresses, and other third party intellectual property material, when that information does not belong to the author of the post. --You may not post job listings for non-Chevron positions. --While we support lively, open discussion, we reserve the right to delete comments.

NAICS: 211
NAICS Definition: Oil and Gas Extraction
Employees: 49,879
Subsidiaries: 10
12-month incidents
0
Known data breaches
0
Attack type number
0

PT Pertamina (Persero)

Jl. Medan Merdeka Timur No. 11-13, Jakarta Pusat, DKI Jakarta, ID, 10110
Last Update: 2025-12-01
Between 750 and 799

PT Pertamina (Persero) is an Indonesian state-owned enterprise, which is engaged in the integrated energy in Indonesia. Established on December 10, 1957, Pertamina had the experiences in upstream, midstream, downstream and renewable energy sectors for more than 50 years. This is the official LinkedIn Pertamina account and managed by Pertamina. Any other official social media account link in the corporate website Pertamina subsidiaries. Please kindly check the validity of the account. We support the LinkedIn Terms of Use (User Agreement) and encourage open, lively conversation with a few simple rules: -- We reserve the right to correct factual errors. -- We will reply to comments when appropriate. -- If we disagree with other opinions, we will do so respectfully. -- You may not post anything that is spam or that is abusive, profane, or defamatory toward a person, entity, belief, or symbol. More Information : Website www.pertamina.com Layanan E-PPID : http://ptm.id/ePPID_Pertamina Become a fan on Facebook.com/pertamina Check out YouTube.com/pertamina Follow us on Twitter.com/pertamina Likes us on Instagram.com/pertamina

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

Compliance Badges Comparison

Security & Compliance Standards Overview

https://images.rankiteo.com/companyimages/chevron.jpeg
Chevron
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/pertamina.jpeg
PT Pertamina (Persero)
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
Chevron
100%
Compliance Rate
0/4 Standards Verified
PT Pertamina (Persero)
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Oil and Gas Industry Average (This Year)

No incidents recorded for Chevron in 2025.

Incidents vs Oil and Gas Industry Average (This Year)

No incidents recorded for PT Pertamina (Persero) in 2025.

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

Chevron cyber incidents detection timeline including parent company and subsidiaries

Incident History — PT Pertamina (Persero) (X = Date, Y = Severity)

PT Pertamina (Persero) cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/chevron.jpeg
Chevron
Incidents

No Incident

https://images.rankiteo.com/companyimages/pertamina.jpeg
PT Pertamina (Persero)
Incidents

Date Detected: 12/2024
Type:Ransomware
Blog: Blog

FAQ

Chevron company demonstrates a stronger AI Cybersecurity Score compared to PT Pertamina (Persero) company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

PT Pertamina (Persero) company has historically faced a number of disclosed cyber incidents, whereas Chevron company has not reported any.

In the current year, PT Pertamina (Persero) company and Chevron company have not reported any cyber incidents.

PT Pertamina (Persero) company has confirmed experiencing a ransomware attack, while Chevron company has not reported such incidents publicly.

Neither PT Pertamina (Persero) company nor Chevron company has reported experiencing a data breach publicly.

Neither PT Pertamina (Persero) company nor Chevron company has reported experiencing targeted cyberattacks publicly.

Neither Chevron company nor PT Pertamina (Persero) company has reported experiencing or disclosing vulnerabilities publicly.

Neither Chevron nor PT Pertamina (Persero) holds any compliance certifications.

Neither company holds any compliance certifications.

Chevron company has more subsidiaries worldwide compared to PT Pertamina (Persero) company.

PT Pertamina (Persero) company employs more people globally than Chevron company, reflecting its scale as a Oil and Gas.

Neither Chevron nor PT Pertamina (Persero) holds SOC 2 Type 1 certification.

Neither Chevron nor PT Pertamina (Persero) holds SOC 2 Type 2 certification.

Neither Chevron nor PT Pertamina (Persero) holds ISO 27001 certification.

Neither Chevron nor PT Pertamina (Persero) holds PCI DSS certification.

Neither Chevron nor PT Pertamina (Persero) holds HIPAA certification.

Neither Chevron nor PT Pertamina (Persero) holds GDPR certification.

Latest Global CVEs (Not Company-Specific)

Description

HedgeDoc is an open source, real-time, collaborative, markdown notes application. Prior to 1.10.4, some of HedgeDoc's OAuth2 endpoints for social login providers such as Google, GitHub, GitLab, Facebook or Dropbox lack CSRF protection, since they don't send a state parameter and verify the response using this parameter. This vulnerability is fixed in 1.10.4.

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

Langflow versions up to and including 1.6.9 contain a chained vulnerability that enables account takeover and remote code execution. An overly permissive CORS configuration (allow_origins='*' with allow_credentials=True) combined with a refresh token cookie configured as SameSite=None allows a malicious webpage to perform cross-origin requests that include credentials and successfully call the refresh endpoint. An attacker-controlled origin can therefore obtain fresh access_token / refresh_token pairs for a victim session. Obtained tokens permit access to authenticated endpoints — including built-in code-execution functionality — allowing the attacker to execute arbitrary code and achieve full system compromise.

Risk Information
cvss4
Base: 9.4
Severity: LOW
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:H/VI:H/VA:H/SC:H/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

A vulnerability was detected in xerrors Yuxi-Know up to 0.4.0. This vulnerability affects the function OtherEmbedding.aencode of the file /src/models/embed.py. Performing manipulation of the argument health_url results in server-side request forgery. The attack can be initiated remotely. The exploit is now public and may be used. The patch is named 0ff771dc1933d5a6b78f804115e78a7d8625c3f3. To fix this issue, it is recommended to deploy a patch. The vendor responded with a vulnerability confirmation and a list of security measures they have established already (e.g. disabled URL parsing, disabled URL upload mode, removed URL-to-markdown conversion).

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

A security vulnerability has been detected in Rarlab RAR App up to 7.11 Build 127 on Android. This affects an unknown part of the component com.rarlab.rar. Such manipulation leads to path traversal. It is possible to launch the attack remotely. Attacks of this nature are highly complex. It is indicated that the exploitability is difficult. The exploit has been disclosed publicly and may be used. Upgrading to version 7.20 build 128 is able to mitigate this issue. You should upgrade the affected component. The vendor responded very professional: "This is the real vulnerability affecting RAR for Android only. WinRAR and Unix RAR versions are not affected. We already fixed it in RAR for Android 7.20 build 128 and we publicly mentioned it in that version changelog. (...) To avoid confusion among users, it would be useful if such disclosure emphasizes that it is RAR for Android only issue and WinRAR isn't affected."

Risk Information
cvss2
Base: 5.1
Severity: HIGH
AV:N/AC:H/Au:N/C:P/I:P/A:P
cvss3
Base: 5.0
Severity: HIGH
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:L/A:L
cvss4
Base: 2.3
Severity: HIGH
CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:P/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P/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

A weakness has been identified in ZSPACE Q2C NAS up to 1.1.0210050. Affected by this issue is the function zfilev2_api.OpenSafe of the file /v2/file/safe/open of the component HTTP POST Request Handler. This manipulation of the argument safe_dir causes command injection. It is possible to initiate the attack remotely. The exploit has been made available to the public and could be exploited. The vendor was contacted early about this disclosure but did not respond in any way.

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