Comparison Overview

Agricultural Bank of China

VS

Bank of Communications Co., Ltd. London Branch

Agricultural Bank of China

undefined, undefined, undefined, 100005, CN
Last Update: 2025-12-10
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

Bank of Communications Co., Ltd. London Branch

undefined, undefined, undefined, undefined, CN
Last Update: 2025-12-09

Founded in 1908, Bank of Communications Co., Ltd. ("the Bank"​) is one of the oldest banks in China as well as one of the note-issuing banks in modern China. The Bank was listed on the Hong Kong Stock Exchange in June 2005 and on the Shanghai Stock Exchange in May 2007. The Bank currently has 182 domestic branches, comprising 30 provincial branches, 7 branches directly managed by the Head Office and 145 managed by provinces. It has also established 2,701 banking outlets in 202 cities and 144 counties nationwide. In addition, the Bank has set up 12 overseas institutions, comprising branches in Hong Kong, New York, San Francisco, Tokyo, Singapore, Seoul, Frankfurt, Sydney, Macau, Ho Chi Minh City, Taipei and Bank of Communications (UK) Co., Ltd. According to the "Top 1000 World Banks 2012"​ published by the British magazine "The Banker"​, the Bank was ranked number 30 in terms of its Tier 1 Capital, moving 5 positions forward as compared with the prior year, and was among the top 50 for the fourth consecutive year. The Bank is one of the major financial services providers in China. The Bank's business scope includes commercial banking, securities services, trust services, financial leasing, fund management, insurance and offshore financial services. Its wholly-owned subsidiaries include BOCOM International Holdings Company Limited, China BOCOM Insurance Co., Ltd and Bank of Communications Finance Leasing Co., Ltd. Subsidiaries controlled by the Bank include Bank of Communications Schroder Fund Management Co., Ltd, Bank of Communications International Trust Co., Ltd, BoCommLife Insurance Company Limited, Dayi Bocomm Xingmin Rural Bank, Zhejiang Anji BOCOM Rural Bank Ltd, Xinjiang Shihezi BOCOM Rural Bank and Qingdao Laoshan BOCOM Rural Bank. In addition, the Bank is the largest shareholder of Jiangsu Changshu Rural Commercial Bank Co., Ltd.

NAICS: 52211
NAICS Definition: Commercial Banking
Employees: 12,684
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/bank-of-communications-limited-london-branch.jpeg
Bank of Communications Co., Ltd. London Branch
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
Bank of Communications Co., Ltd. London Branch
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 Bank of Communications Co., Ltd. London Branch 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 — Bank of Communications Co., Ltd. London Branch (X = Date, Y = Severity)

Bank of Communications Co., Ltd. London Branch 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/bank-of-communications-limited-london-branch.jpeg
Bank of Communications Co., Ltd. London Branch
Incidents

No Incident

FAQ

Agricultural Bank of China company demonstrates a stronger AI Cybersecurity Score compared to Bank of Communications Co., Ltd. London Branch company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Historically, Bank of Communications Co., Ltd. London Branch company has disclosed a higher number of cyber incidents compared to Agricultural Bank of China company.

In the current year, Bank of Communications Co., Ltd. London Branch company and Agricultural Bank of China company have not reported any cyber incidents.

Neither Bank of Communications Co., Ltd. London Branch company nor Agricultural Bank of China company has reported experiencing a ransomware attack publicly.

Neither Bank of Communications Co., Ltd. London Branch company nor Agricultural Bank of China company has reported experiencing a data breach publicly.

Neither Bank of Communications Co., Ltd. London Branch company nor Agricultural Bank of China company has reported experiencing targeted cyberattacks publicly.

Neither Agricultural Bank of China company nor Bank of Communications Co., Ltd. London Branch company has reported experiencing or disclosing vulnerabilities publicly.

Neither Agricultural Bank of China nor Bank of Communications Co., Ltd. London Branch holds any compliance certifications.

Neither company holds any compliance certifications.

Neither Agricultural Bank of China company nor Bank of Communications Co., Ltd. London Branch company has publicly disclosed detailed information about the number of their subsidiaries.

Agricultural Bank of China company employs more people globally than Bank of Communications Co., Ltd. London Branch company, reflecting its scale as a Banking.

Neither Agricultural Bank of China nor Bank of Communications Co., Ltd. London Branch holds SOC 2 Type 1 certification.

Neither Agricultural Bank of China nor Bank of Communications Co., Ltd. London Branch holds SOC 2 Type 2 certification.

Neither Agricultural Bank of China nor Bank of Communications Co., Ltd. London Branch holds ISO 27001 certification.

Neither Agricultural Bank of China nor Bank of Communications Co., Ltd. London Branch holds PCI DSS certification.

Neither Agricultural Bank of China nor Bank of Communications Co., Ltd. London Branch holds HIPAA certification.

Neither Agricultural Bank of China nor Bank of Communications Co., Ltd. London Branch holds GDPR certification.

Latest Global CVEs (Not Company-Specific)

Description

FreePBX Endpoint Manager is a module for managing telephony endpoints in FreePBX systems. Versions prior to 16.0.96 and 17.0.1 through 17.0.9 have a weak default password. By default, this is a 6 digit numeric value which can be brute forced. (This is the app_password parameter). Depending on local configuration, this password could be the extension, voicemail, user manager, DPMA or EPM phone admin password. This issue is fixed in versions 16.0.96 and 17.0.10.

Risk Information
cvss4
Base: 6.9
Severity: LOW
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/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

Neuron is a PHP framework for creating and orchestrating AI Agents. In versions 2.8.11 and below, the MySQLWriteTool executes arbitrary SQL provided by the caller using PDO::prepare() + execute() without semantic restrictions. This is consistent with the name (“write tool”), but in an LLM/agent context it becomes a high-risk capability: prompt injection or indirect prompt manipulation can cause execution of destructive queries such as DROP TABLE, TRUNCATE, DELETE, ALTER, or privilege-related statements (subject to DB permissions). Deployments that expose an agent with MySQLWriteTool enabled to untrusted input and/or run the tool with a DB user that has broad privileges are impacted. This issue is fixed in version 2.8.12.

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

Neuron is a PHP framework for creating and orchestrating AI Agents. Versions 2.8.11 and below use MySQLSelectTool, which is vulnerable to Read-Only Bypass. MySQLSelectTool is intended to be a read-only SQL tool (e.g., for LLM agent querying, however, validation based on the first keyword (e.g., SELECT) and a forbidden-keyword list does not block file-writing constructs such as INTO OUTFILE / INTO DUMPFILE. As a result, an attacker who can influence the tool input (e.g., via prompt injection through a public agent endpoint) may write arbitrary files to the DB server if the MySQL/MariaDB account has the FILE privilege and server configuration permits writes to a useful location (e.g., a web-accessible directory). This issue is fixed in version 2.8.12.

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

Okta Java Management SDK facilitates interactions with the Okta management API. In versions 11.0.0 through 20.0.0, race conditions may arise from concurrent requests using the ApiClient class. This could cause a status code or response header from one request’s response to influence another request’s response. This issue is fixed in version 20.0.1.

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

The Auth0 Next.js SDK is a library for implementing user authentication in Next.js applications. When using versions 4.11.0 through 4.11.2 and 4.12.0, simultaneous requests on the same client may result in improper lookups in the TokenRequestCache for the request results. This issue is fixed in versions 4.11.2 and 4.12.1.

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