Comparison Overview

China Merchants Bank

VS

SEB

China Merchants Bank

7088 Shennan Blvd., Shenzhen, Guangdong, 518040, CN
Last Update: 2025-11-22
Between 800 and 849

Established in 1987 in Shenzhen, the forefront of China’s reform and opening-up drive, China Merchants Bank ("CMB") has developed into the most influential commercial bank brand in China thanks to continuous financial innovation, quality customer service, prudent management and strong business performance. For many consecutive years, CMB has been ranked among China’s top commercial banks according to comprehensive assessment by CBRC. The bank has won a number of titles, including the Best Commercial Bank of China, the Best Retail Bank in China, the Best Private Bank in China, China’s Best Custody Specialist from the British Financial Times, Euromoney and The Asset. The Bank was shortlisted as a World-Class Chinese Brand and ranked No. 1 in the P/B list of the world’s top 50 banks with the largest market value by the British Financial Times. It was also listed No.60 among the world's Top 1,000 Banks by The Banker.

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

SEB

Kungsträdgårdsgatan 8, Stockholm, Stockholm, SE, 10640
Last Update: 2025-11-20
Between 800 and 849

SEB is a leading northern European financial services group with a strong belief that entrepreneurial minds and innovative companies are key in creating a better world. SEB takes a long-term perspective and supports its customers in good times and bad. In Sweden and the Baltic countries, SEB offers financial advice and a wide range of financial services. In Denmark, Finland, Norway and Germany the bank's operations have a strong focus on corporate and investment banking based on a full-service offering to corporate and institutional clients. The international nature of SEB's business is reflected in its presence in some 20 countries worldwide. Read more about SEB at www.sebgroup.com Privacy note about SEB’s processing of your personal data can be found at: www.sebgroup.com/legal-and-regulatory-information/privacy-at-seb-group Content shared on this page may contain commercial information from SEB.

NAICS: 52211
NAICS Definition: Commercial Banking
Employees: 14,737
Subsidiaries: 5
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-merchants-bank.jpeg
China Merchants Bank
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/seb.jpeg
SEB
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 Merchants Bank
100%
Compliance Rate
0/4 Standards Verified
SEB
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Banking Industry Average (This Year)

No incidents recorded for China Merchants Bank in 2025.

Incidents vs Banking Industry Average (This Year)

No incidents recorded for SEB in 2025.

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

China Merchants Bank cyber incidents detection timeline including parent company and subsidiaries

Incident History — SEB (X = Date, Y = Severity)

SEB cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/china-merchants-bank.jpeg
China Merchants Bank
Incidents

No Incident

https://images.rankiteo.com/companyimages/seb.jpeg
SEB
Incidents

No Incident

FAQ

China Merchants Bank company demonstrates a stronger AI Cybersecurity Score compared to SEB company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Historically, SEB company has disclosed a higher number of cyber incidents compared to China Merchants Bank company.

In the current year, SEB company and China Merchants Bank company have not reported any cyber incidents.

Neither SEB company nor China Merchants Bank company has reported experiencing a ransomware attack publicly.

Neither SEB company nor China Merchants Bank company has reported experiencing a data breach publicly.

Neither SEB company nor China Merchants Bank company has reported experiencing targeted cyberattacks publicly.

Neither China Merchants Bank company nor SEB company has reported experiencing or disclosing vulnerabilities publicly.

Neither China Merchants Bank nor SEB holds any compliance certifications.

Neither company holds any compliance certifications.

SEB company has more subsidiaries worldwide compared to China Merchants Bank company.

SEB company employs more people globally than China Merchants Bank company, reflecting its scale as a Banking.

Neither China Merchants Bank nor SEB holds SOC 2 Type 1 certification.

Neither China Merchants Bank nor SEB holds SOC 2 Type 2 certification.

Neither China Merchants Bank nor SEB holds ISO 27001 certification.

Neither China Merchants Bank nor SEB holds PCI DSS certification.

Neither China Merchants Bank nor SEB holds HIPAA certification.

Neither China Merchants Bank nor SEB 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
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