Comparison Overview

China UnionPay

VS

BBVA en México

China UnionPay

undefined, undefined, undefined, undefined, CN
Last Update: 2025-12-17
Between 750 and 799

中国银联是中国银行卡联合组织,通过银联跨行交易清算系统,实现商业银行系统间的互联互通和资源共享,保证银行卡跨行、跨地区和跨境的使用。中国银联已与境内外数百家机构展开广泛合作,银联网络遍布中国城乡,并已延伸至亚洲、欧洲、美洲、大洋洲、非洲等境外150多个国家和地区。 中国银联大力推进各类基于银行卡的综合支付服务。持卡人不仅可以在ATM自动取款机、商户POS刷卡终端等使用银行卡,还可以通过互联网、手机、固定电话、自助终端、智能电视终端等各类新兴渠道实现公用事业缴费、机票和酒店预订、信用卡还款、自助转账 等多种支付。围绕着满足多元化用卡需求,在中国银联和商业银行等相关机构的共同努力下,一个范围更广、领域更多、渠道更丰富的银行卡受理环境正在逐步形成。 中国银联正携手境内外合作伙伴,进一步推动我国银行卡产业又好又快发展,为人民群众提供优质、安全、高效的银行卡综合支付服务,把中国银联建设成为在国内具有权威性和公信力,在国际具有竞争力和影响力的国际性银行卡组织,把银联品牌建设成为具有全球影响力的国际主要银行卡品牌,实现网络全球化、品牌国际化的发展愿景。

NAICS: 52
NAICS Definition:
Employees: 1,923
Subsidiaries: 0
12-month incidents
0
Known data breaches
0
Attack type number
0

BBVA en México

Av. Paseo de la Reforma 510, Juárez, Cuauhtémoc, Ciudad de México, undefined, 06600, MX
Last Update: 2025-12-17
Between 750 and 799

Bienvenido a la página oficial del Banco BBVA Bancomer. Institución financiera de México desde 1932. Es una empresa filial de Banco Bilbao Vizcaya Argentaria (BBVA), uno de los grupos financieros líderes en Europa y considerado entre uno de los más grandes de la Zona Euro. El Grupo trabaja por un futuro mejor para las personas, al ofrecer a su clientela una relación de beneficio mutuo, servicio proactivo, asesoramiento y soluciones integrales con una amplia variedad de productos y servicios financieros.

NAICS: 52
NAICS Definition: Finance and Insurance
Employees: 19,743
Subsidiaries: 23
12-month incidents
0
Known data breaches
0
Attack type number
0

Compliance Badges Comparison

Security & Compliance Standards Overview

https://images.rankiteo.com/companyimages/china-unionpay.jpeg
China UnionPay
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/bbva-mexico.jpeg
BBVA en México
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
China UnionPay
100%
Compliance Rate
0/4 Standards Verified
BBVA en México
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Financial Services Industry Average (This Year)

No incidents recorded for China UnionPay in 2025.

Incidents vs Financial Services Industry Average (This Year)

No incidents recorded for BBVA en México in 2025.

Incident History — China UnionPay (X = Date, Y = Severity)

China UnionPay cyber incidents detection timeline including parent company and subsidiaries

Incident History — BBVA en México (X = Date, Y = Severity)

BBVA en México cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/china-unionpay.jpeg
China UnionPay
Incidents

No Incident

https://images.rankiteo.com/companyimages/bbva-mexico.jpeg
BBVA en México
Incidents

No Incident

FAQ

BBVA en México company demonstrates a stronger AI Cybersecurity Score compared to China UnionPay company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Historically, BBVA en México company has disclosed a higher number of cyber incidents compared to China UnionPay company.

In the current year, BBVA en México company and China UnionPay company have not reported any cyber incidents.

Neither BBVA en México company nor China UnionPay company has reported experiencing a ransomware attack publicly.

Neither BBVA en México company nor China UnionPay company has reported experiencing a data breach publicly.

Neither BBVA en México company nor China UnionPay company has reported experiencing targeted cyberattacks publicly.

Neither China UnionPay company nor BBVA en México company has reported experiencing or disclosing vulnerabilities publicly.

Neither China UnionPay nor BBVA en México holds any compliance certifications.

Neither company holds any compliance certifications.

BBVA en México company has more subsidiaries worldwide compared to China UnionPay company.

BBVA en México company employs more people globally than China UnionPay company, reflecting its scale as a Financial Services.

Neither China UnionPay nor BBVA en México holds SOC 2 Type 1 certification.

Neither China UnionPay nor BBVA en México holds SOC 2 Type 2 certification.

Neither China UnionPay nor BBVA en México holds ISO 27001 certification.

Neither China UnionPay nor BBVA en México holds PCI DSS certification.

Neither China UnionPay nor BBVA en México holds HIPAA certification.

Neither China UnionPay nor BBVA en México holds GDPR certification.

Latest Global CVEs (Not Company-Specific)

Description

httparty is an API tool. In versions 0.23.2 and prior, httparty is vulnerable to SSRF. This issue can pose a risk of leaking API keys, and it can also allow third parties to issue requests to internal servers. This issue has been patched via commit 0529bcd.

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

5ire is a cross-platform desktop artificial intelligence assistant and model context protocol client. In versions 0.15.2 and prior, an RCE vulnerability exists in useMarkdown.ts, where the markdown-it-mermaid plugin is initialized with securityLevel: 'loose'. This configuration explicitly permits the rendering of HTML tags within Mermaid diagram nodes. This issue has not been patched at time of publication.

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

continuwuity is a Matrix homeserver written in Rust. Prior to version 0.5.0, this vulnerability allows a remote, unauthenticated attacker to force the target server to cryptographically sign arbitrary membership events. The flaw exists because the server fails to validate the origin of a signing request, provided the event's state_key is a valid user ID belonging to the target server. This issue has been patched in version 0.5.0. A workaround for this issue involves blocking access to the PUT /_matrix/federation/v2/invite/{roomId}/{eventId} endpoint using the reverse proxy.

Risk Information
cvss4
Base: 9.9
Severity: LOW
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:L/SA:L/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

LangChain is a framework for building LLM-powered applications. Prior to @langchain/core versions 0.3.80 and 1.1.8, and prior to langchain versions 0.3.37 and 1.2.3, a serialization injection vulnerability exists in LangChain JS's toJSON() method (and subsequently when string-ifying objects using JSON.stringify(). The method did not escape objects with 'lc' keys when serializing free-form data in kwargs. The 'lc' key is used internally by LangChain to mark serialized objects. When user-controlled data contains this key structure, it is treated as a legitimate LangChain object during deserialization rather than plain user data. This issue has been patched in @langchain/core versions 0.3.80 and 1.1.8, and langchain versions 0.3.37 and 1.2.3

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

LangChain is a framework for building agents and LLM-powered applications. Prior to versions 0.3.81 and 1.2.5, a serialization injection vulnerability exists in LangChain's dumps() and dumpd() functions. The functions do not escape dictionaries with 'lc' keys when serializing free-form dictionaries. The 'lc' key is used internally by LangChain to mark serialized objects. When user-controlled data contains this key structure, it is treated as a legitimate LangChain object during deserialization rather than plain user data. This issue has been patched in versions 0.3.81 and 1.2.5.

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