Comparison Overview

Agricultural Bank of China

VS

PT Bank Rakyat Indonesia (Persero) Tbk

Agricultural Bank of China

undefined, undefined, undefined, 100005, CN
Last Update: 2025-11-26
Between 800 and 849

wholly state-owned

NAICS: 52211
NAICS Definition: Commercial Banking
Employees: 14,747
Subsidiaries: 0
12-month incidents
0
Known data breaches
0
Attack type number
0

PT Bank Rakyat Indonesia (Persero) Tbk

Jalan Jenderal Sudirman No 44-46 Jakarta Pusat, DKI Jakarta 10210, ID
Last Update: 2025-11-22
Between 800 and 849

Bank Rakyat Indonesia (BRI) adalah salah satu bank milik pemerintah yang terbesar di Indonesia. BRI didirikan di Purwokerto, Jawa Tengah oleh Raden Bei Aria Wirjaatmadja pada 16 Desember 1895. Lebih dari 128 tahun memberi pelayanan terbaik bagi seluruh lapisan masyarakat, BRI turut andil dalam upaya membangun negeri dan Memberi Makna Indonesia. Didukung oleh 7.155 jaringan kantor, 686.000 lebih jaringan e-channel, 740.000 lebih Agen BRILink serta jaringan satelit BRIsat, membuat BRI terus berusaha menjadi yang pertama dalam mendukung perekonomian masyarakat. Melalui visi "The Most Valuable Banking Group in Southeast Asia” dan “Champion of Financial Inclusion" menjadikan BRI fokus pada pengembangan SDM unggul, berkarakter kuat, dan ber-AKHLAK. Sebagai bentuk komitmen BRI dalam memberikan economic value bagi Negara, sepanjang lima tahun terakhir mulai dari 2019 hingga 2023, BRI telah memberikan setoran Dividen dan Pajak ke Negara mencapai Rp149,2 Triliun. Kinerja BRI terus tumbuh dan berkelanjutan. Terbukti pada tahun 2023 BRI berhasil membukukan laba sebesar Rp60,4 Triliun dan menjadi Bank dengan laba terbesar di Indonesia. BRI tidak hanya tempat bekerja, tapi tempat kamu Belajar, Bertumbuh, dan Berkontribusi mengoptimalkan semua potensi terbaikmu untuk semua nasabah BRI. BRI dan Seluruh Insan BRILiaN, Siap Memberi Makna Indonesia.

NAICS: 52211
NAICS Definition: Commercial Banking
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/agricultural-bank-of-china.jpeg
Agricultural Bank of China
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/pt-bank-rakyat-indonesia-persero-tbk.jpeg
PT Bank Rakyat Indonesia (Persero) Tbk
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
Agricultural Bank of China
100%
Compliance Rate
0/4 Standards Verified
PT Bank Rakyat Indonesia (Persero) Tbk
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Banking Industry Average (This Year)

No incidents recorded for Agricultural Bank of China in 2025.

Incidents vs Banking Industry Average (This Year)

No incidents recorded for PT Bank Rakyat Indonesia (Persero) Tbk in 2025.

Incident History — Agricultural Bank of China (X = Date, Y = Severity)

Agricultural Bank of China cyber incidents detection timeline including parent company and subsidiaries

Incident History — PT Bank Rakyat Indonesia (Persero) Tbk (X = Date, Y = Severity)

PT Bank Rakyat Indonesia (Persero) Tbk cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/agricultural-bank-of-china.jpeg
Agricultural Bank of China
Incidents

No Incident

https://images.rankiteo.com/companyimages/pt-bank-rakyat-indonesia-persero-tbk.jpeg
PT Bank Rakyat Indonesia (Persero) Tbk
Incidents

No Incident

FAQ

Agricultural Bank of China company demonstrates a stronger AI Cybersecurity Score compared to PT Bank Rakyat Indonesia (Persero) Tbk company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Historically, PT Bank Rakyat Indonesia (Persero) Tbk company has disclosed a higher number of cyber incidents compared to Agricultural Bank of China company.

In the current year, PT Bank Rakyat Indonesia (Persero) Tbk company and Agricultural Bank of China company have not reported any cyber incidents.

Neither PT Bank Rakyat Indonesia (Persero) Tbk company nor Agricultural Bank of China company has reported experiencing a ransomware attack publicly.

Neither PT Bank Rakyat Indonesia (Persero) Tbk company nor Agricultural Bank of China company has reported experiencing a data breach publicly.

Neither PT Bank Rakyat Indonesia (Persero) Tbk company nor Agricultural Bank of China company has reported experiencing targeted cyberattacks publicly.

Neither Agricultural Bank of China company nor PT Bank Rakyat Indonesia (Persero) Tbk company has reported experiencing or disclosing vulnerabilities publicly.

Neither Agricultural Bank of China nor PT Bank Rakyat Indonesia (Persero) Tbk holds any compliance certifications.

Neither company holds any compliance certifications.

Neither Agricultural Bank of China company nor PT Bank Rakyat Indonesia (Persero) Tbk company has publicly disclosed detailed information about the number of their subsidiaries.

Agricultural Bank of China company employs more people globally than PT Bank Rakyat Indonesia (Persero) Tbk company, reflecting its scale as a Banking.

Neither Agricultural Bank of China nor PT Bank Rakyat Indonesia (Persero) Tbk holds SOC 2 Type 1 certification.

Neither Agricultural Bank of China nor PT Bank Rakyat Indonesia (Persero) Tbk holds SOC 2 Type 2 certification.

Neither Agricultural Bank of China nor PT Bank Rakyat Indonesia (Persero) Tbk holds ISO 27001 certification.

Neither Agricultural Bank of China nor PT Bank Rakyat Indonesia (Persero) Tbk holds PCI DSS certification.

Neither Agricultural Bank of China nor PT Bank Rakyat Indonesia (Persero) Tbk holds HIPAA certification.

Neither Agricultural Bank of China nor PT Bank Rakyat Indonesia (Persero) Tbk 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