Comparison Overview

Agricultural Bank of China

VS

Banco Bradesco

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

Banco Bradesco

Cidade de Deus, s/n, Osasco, São Paulo, BR, 06029-900
Last Update: 2025-12-09
Between 750 and 799

O Bradesco é um dos líderes do setor financeiro privado e um dos maiores empregadores na categoria. Além disso, apresenta o melhor índice de eficiência entre os bancos de varejo. Nossa missão é fornecer soluções, produtos e serviços financeiros e de seguros com agilidade e competência, principalmente por meio da inclusão bancária e da promoção da mobilidade social, contribuindo para o desenvolvimento sustentável e a construção de relacionamentos duradouros. Nós acreditamos nas pessoas. Desde o início de nossas atividades, reconhecemos no valor do desempenho e no potencial realizador das pessoas a base de sustentação dos negócios da Organização Bradesco. Nossa atuação está inserida e se expande continuamente, por todo o território nacional, ampliando o universo de clientes e parceiros, contemplando uma gama de diversidade que é a própria expressão da estrutura social brasileira. Acreditamos em nossa capacidade de promover crescimento sustentado, para as pessoas e por meio delas. Siga com a gente também aqui, no LinkedIn!

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

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/bradesco.jpeg
Banco Bradesco
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
Banco Bradesco
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 Banco Bradesco 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 — Banco Bradesco (X = Date, Y = Severity)

Banco Bradesco 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/bradesco.jpeg
Banco Bradesco
Incidents

Date Detected: 7/2023
Type:Breach
Blog: Blog

FAQ

Agricultural Bank of China company demonstrates a stronger AI Cybersecurity Score compared to Banco Bradesco company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Banco Bradesco company has historically faced a number of disclosed cyber incidents, whereas Agricultural Bank of China company has not reported any.

In the current year, Banco Bradesco company and Agricultural Bank of China company have not reported any cyber incidents.

Neither Banco Bradesco company nor Agricultural Bank of China company has reported experiencing a ransomware attack publicly.

Banco Bradesco company has disclosed at least one data breach, while Agricultural Bank of China company has not reported such incidents publicly.

Neither Banco Bradesco company nor Agricultural Bank of China company has reported experiencing targeted cyberattacks publicly.

Neither Agricultural Bank of China company nor Banco Bradesco company has reported experiencing or disclosing vulnerabilities publicly.

Neither Agricultural Bank of China nor Banco Bradesco holds any compliance certifications.

Neither company holds any compliance certifications.

Neither Agricultural Bank of China company nor Banco Bradesco company has publicly disclosed detailed information about the number of their subsidiaries.

Banco Bradesco company employs more people globally than Agricultural Bank of China company, reflecting its scale as a Banking.

Neither Agricultural Bank of China nor Banco Bradesco holds SOC 2 Type 1 certification.

Neither Agricultural Bank of China nor Banco Bradesco holds SOC 2 Type 2 certification.

Neither Agricultural Bank of China nor Banco Bradesco holds ISO 27001 certification.

Neither Agricultural Bank of China nor Banco Bradesco holds PCI DSS certification.

Neither Agricultural Bank of China nor Banco Bradesco holds HIPAA certification.

Neither Agricultural Bank of China nor Banco Bradesco holds GDPR certification.

Latest Global CVEs (Not Company-Specific)

Description

NXLog Agent before 6.11 can load a file specified by the OPENSSL_CONF environment variable.

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

uriparser through 0.9.9 allows unbounded recursion and stack consumption, as demonstrated by ParseMustBeSegmentNzNc with large input containing many commas.

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

A vulnerability was detected in Mayan EDMS up to 4.10.1. The affected element is an unknown function of the file /authentication/. The manipulation results in cross site scripting. The attack may be performed from remote. The exploit is now public and may be used. Upgrading to version 4.10.2 is sufficient to fix this issue. You should upgrade the affected component. The vendor confirms that this is "[f]ixed in version 4.10.2". Furthermore, that "[b]ackports for older versions in process and will be out as soon as their respective CI pipelines complete."

Risk Information
cvss2
Base: 5.0
Severity: LOW
AV:N/AC:L/Au:N/C:N/I:P/A:N
cvss3
Base: 4.3
Severity: LOW
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N
cvss4
Base: 5.3
Severity: LOW
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:L/VA:N/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

MJML through 4.18.0 allows mj-include directory traversal to test file existence and (in the type="css" case) read files. NOTE: this issue exists because of an incomplete fix for CVE-2020-12827.

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

A half-blind Server Side Request Forgery (SSRF) vulnerability exists in kube-controller-manager when using the in-tree Portworx StorageClass. This vulnerability allows authorized users to leak arbitrary information from unprotected endpoints in the control plane’s host network (including link-local or loopback services).

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