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
State Bank of India
State Bank of India
Last Update: 2025-11-23
Between 800 and 849
We are the largest Indian Public Sector Banking & Financial Services Company. Headquartered in Mumbai, our national presence across the country with over 22,000 branches and globally across all time-zones at 227 locations in 30 countries, makes us the leader in the sector. Our legacy ranges back to the British era through the Imperial Bank of India, founded in 1806. Today, we are a conglomerate employing skilled professionals who are successfully taking the legacy forward through our specialized and customized financial services designed to cater the needs of Corporates, SMEs, NRIs & Retail customers. For more information about Career & Life at SBI, please visit : https://bank.sbi/web/careers Disclaimer: SBI shall bear no responsibility for confidentiality of information shared with SBI through LinkedIn.
NAICS: 52211
NAICS Definition: Commercial Banking
Employees: 119,767
Subsidiaries: 3
12-month incidents
1
Known data breaches
1
Attack type number
2
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
State Bank of India
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
State Bank of India
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)
State Bank of India has 12.36% more incidents than the average of same-industry companies with at least one recorded incident.
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 — State Bank of India (X = Date, Y = Severity)
State Bank of India 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
FAQ
Agricultural Bank of China company demonstrates a stronger AI Cybersecurity Score compared to State Bank of India company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.
State Bank of India company has historically faced a number of disclosed cyber incidents, whereas Agricultural Bank of China company has not reported any.
In the current year, State Bank of India company has reported more cyber incidents than Agricultural Bank of China company.
Neither State Bank of India company nor Agricultural Bank of China company has reported experiencing a ransomware attack publicly.
State Bank of India company has disclosed at least one data breach, while Agricultural Bank of China company has not reported such incidents publicly.
Neither State Bank of India company nor Agricultural Bank of China company has reported experiencing targeted cyberattacks publicly.
State Bank of India company has disclosed at least one vulnerability, while Agricultural Bank of China company has not reported such incidents publicly.
Neither Agricultural Bank of China nor State Bank of India holds any compliance certifications.
Neither company holds any compliance certifications.
State Bank of India company has more subsidiaries worldwide compared to Agricultural Bank of China company.
State Bank of India company employs more people globally than Agricultural Bank of China company, reflecting its scale as a Banking.
Neither Agricultural Bank of China nor State Bank of India holds SOC 2 Type 1 certification.
Neither Agricultural Bank of China nor State Bank of India holds SOC 2 Type 2 certification.
Neither Agricultural Bank of China nor State Bank of India holds ISO 27001 certification.
Neither Agricultural Bank of China nor State Bank of India holds PCI DSS certification.
Neither Agricultural Bank of China nor State Bank of India holds HIPAA certification.
Neither Agricultural Bank of China nor State Bank of India 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
