Agricultural Bank of China
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
Comparison Overview
Agricultural Bank of China
VS
PT. BANK NEGARA INDONESIA (Persero) Tbk.
PT. BANK NEGARA INDONESIA (Persero) Tbk.
Last Update: 2025-11-27
Between 750 and 799
Since its establishment in 1946, BNI has been part of the dynamic of national development in Indonesia. Now BNI has grown and developed into a solid national bank with a sustainable financial performance. ‘Serving the Country, Pride of the Nation”, BNI continues to increase its contribution for the progress of the nation and country, today and in the future. At the end of 2024, BNI employs more than 27,000 employees. To serve its customers, BNI leverages its wide ranging service network, comprising of 1,780 domestic outlets and 10 overseas branches in Singapore, Hong Kong, Tokyo, New York, London, Seoul, Osaka, Amsterdam & Sydney. With 13,388 proprietary ATMs, 208,981 Branchless Banking agents (BNI Agen46). BNI always strives to be the bank of choice by providing excellent service and value added solutions to all of its customers. BNI offers integrated financial services to its customers, supported by its subsidiaries: BNI Multi Finance, BNI Securities, BNI Life Insurance, BNI Remittance, BNI Asset Management, hiBank, and BNI Ventures
NAICS: 52211
NAICS Definition: Commercial Banking
Employees: 29,238
Subsidiaries: 0
12-month incidents
0
Known data breaches
0
Attack type number
0
Compliance Badges Comparison
Security & Compliance Standards Overview
Agricultural Bank of China
ISO 27001
Not verified
SOC2 Type 1
Not verified
SOC2 Type 2
Not verified
GDPR
Not verified
PCI DSS
Not verified
HIPAA
Not verified
PT. BANK NEGARA INDONESIA (Persero) Tbk.
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
Agricultural Bank of China
100%
Compliance Rate
0/4 Standards Verified
PT. BANK NEGARA 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 NEGARA 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 NEGARA INDONESIA (Persero) Tbk. (X = Date, Y = Severity)
PT. BANK NEGARA INDONESIA (Persero) Tbk. cyber incidents detection timeline including parent company and subsidiaries
Notable Incidents
Last 3 Security & Risk Events by Company
Agricultural Bank of China
Incidents
No Incident
PT. BANK NEGARA INDONESIA (Persero) Tbk.
Incidents
No Incident
FAQ
Agricultural Bank of China company demonstrates a stronger AI Cybersecurity Score compared to PT. BANK NEGARA INDONESIA (Persero) Tbk. company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.
Historically, PT. BANK NEGARA 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 NEGARA INDONESIA (Persero) Tbk. company and Agricultural Bank of China company have not reported any cyber incidents.
Neither PT. BANK NEGARA INDONESIA (Persero) Tbk. company nor Agricultural Bank of China company has reported experiencing a ransomware attack publicly.
Neither PT. BANK NEGARA INDONESIA (Persero) Tbk. company nor Agricultural Bank of China company has reported experiencing a data breach publicly.
Neither PT. BANK NEGARA 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 NEGARA INDONESIA (Persero) Tbk. company has reported experiencing or disclosing vulnerabilities publicly.
Neither Agricultural Bank of China nor PT. BANK NEGARA INDONESIA (Persero) Tbk. holds any compliance certifications.
Neither company holds any compliance certifications.
Neither Agricultural Bank of China company nor PT. BANK NEGARA INDONESIA (Persero) Tbk. company has publicly disclosed detailed information about the number of their subsidiaries.
PT. BANK NEGARA INDONESIA (Persero) Tbk. company employs more people globally than Agricultural Bank of China company, reflecting its scale as a Banking.
Neither Agricultural Bank of China nor PT. BANK NEGARA INDONESIA (Persero) Tbk. holds SOC 2 Type 1 certification.
Neither Agricultural Bank of China nor PT. BANK NEGARA INDONESIA (Persero) Tbk. holds SOC 2 Type 2 certification.
Neither Agricultural Bank of China nor PT. BANK NEGARA INDONESIA (Persero) Tbk. holds ISO 27001 certification.
Neither Agricultural Bank of China nor PT. BANK NEGARA INDONESIA (Persero) Tbk. holds PCI DSS certification.
Neither Agricultural Bank of China nor PT. BANK NEGARA INDONESIA (Persero) Tbk. holds HIPAA certification.
Neither Agricultural Bank of China nor PT. BANK NEGARA 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
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
