Comparison Overview

U.S. Bank

VS

Bank of China

U.S. Bank

800 Nicollet Mall, None, Minneapolis, MN, US, 55402
Last Update: 2025-12-17

At U.S. Bank, we help millions of clients achieve their goals with a balance of best-in-class technology and human expertise tailored to individual needs. As the fifth-largest commercial bank in the United States, we’ve built a reputation for strength and stability across a diversified mix of businesses, including commercial and institutional banking, business banking, payments, wealth management and consumer banking. We’ve been named one of the World’s Most Ethical Companies® by the Ethisphere Institute and the most admired superregional bank by Fortune. In addition to thousands of branches serving consumers, U.S. Bank offers a complete suite of products, services and strategic partnerships for business. Within our Wealth, Corporate, Commercial and Institutional Banking division, we serve more than half a million clients across the country and around the world, ranging from wealthy individuals and families to the largest corporations, including 90% of Fortune 1000 companies. We’re also consistently recognized as a great place to work. We’re shaping our company culture with intention, focused on creating a workplace where it’s safe to speak up, share ideas and try new things. We’re proud to be recognized as a “Best for Vets” employer by the Military Times and included on Fair360’s (formerly DiversityInc.) list of Top 50 Companies for Diversity. U.S. Bank, NA. Member FDIC. Equal Housing Lender.

NAICS: 52211
NAICS Definition: Commercial Banking
Employees: 79,818
Subsidiaries: 4
12-month incidents
0
Known data breaches
2
Attack type number
2

Bank of China

Bank of China Head Office Building, Beijing, undefined, 100818, CN
Last Update: 2025-12-17
Between 800 and 849

Bank of China, include BOC Hong Kong, BOC International, BOCG Insurance and other financial institutions, providing a comprehensive range of high-quality financial services to individual and corporate customers as well as financial institutions worldwide. Over the past century, Bank of China played an important role in China’s financial history. It was established in 1912 pursuant to the approval of DR. Sun Yat-sen. In the following 37 years the Bank served as the central bank, international exchange bank and specialized foreign trade bank successively. In 1949, Bank of China became the state-designated specialized foreign exchange bank. In 2003, it was named by the State Council as one of the pilot banks for joint-stock reform of wholly state-owned commercial banks. On August 26, 2004, Bank of China Limited was formally incorporated in Beijing as a state-controlled joint stock commercial bank. Bank of China is the most internationalized commercial bank in China. BOC London Branch, the first overseas branch of the Chinese banks, was established in 1929. Currently, it had over 10000 domestic operations and over 600 overseas operations. In 1994 and 1995, Bank of China became the note issuing bank in Hong Kong and Macao respectively. The Bank prepared a new strategic development plan which was approved by the Board of Directors in March 2009. Strategic Positioning: To be a large multinational banking group based on a diversified and integrated cross-border business platform, with a core business of commercial banking. Strategic Goals: To be a leading international bank delivering growth and excellence.

NAICS: 52211
NAICS Definition: Commercial Banking
Employees: 22,584
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/us-bank.jpeg
U.S. 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/bank-of-china.jpeg
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
Compliance Summary
U.S. Bank
100%
Compliance Rate
0/4 Standards Verified
Bank of China
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Banking Industry Average (This Year)

No incidents recorded for U.S. Bank in 2025.

Incidents vs Banking Industry Average (This Year)

No incidents recorded for Bank of China in 2025.

Incident History — U.S. Bank (X = Date, Y = Severity)

U.S. Bank cyber incidents detection timeline including parent company and subsidiaries

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

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

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/us-bank.jpeg
U.S. Bank
Incidents

Date Detected: 9/2022
Type:Breach
Attack Vector: Inadvertent sharing of a file by a vendor
Blog: Blog

Date Detected: 3/2021
Type:Cyber Attack
Attack Vector: Credential Stuffing
Blog: Blog

Date Detected: 7/2020
Type:Breach
Attack Vector: Physical Theft
Blog: Blog
https://images.rankiteo.com/companyimages/bank-of-china.jpeg
Bank of China
Incidents

No Incident

FAQ

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

U.S. Bank company has historically faced a number of disclosed cyber incidents, whereas Bank of China company has not reported any.

In the current year, Bank of China company and U.S. Bank company have not reported any cyber incidents.

Neither Bank of China company nor U.S. Bank company has reported experiencing a ransomware attack publicly.

U.S. Bank company has disclosed at least one data breach, while the other Bank of China company has not reported such incidents publicly.

U.S. Bank company has reported targeted cyberattacks, while Bank of China company has not reported such incidents publicly.

Neither U.S. Bank company nor Bank of China company has reported experiencing or disclosing vulnerabilities publicly.

Neither U.S. Bank nor Bank of China holds any compliance certifications.

Neither company holds any compliance certifications.

U.S. Bank company has more subsidiaries worldwide compared to Bank of China company.

U.S. Bank company employs more people globally than Bank of China company, reflecting its scale as a Banking.

Neither U.S. Bank nor Bank of China holds SOC 2 Type 1 certification.

Neither U.S. Bank nor Bank of China holds SOC 2 Type 2 certification.

Neither U.S. Bank nor Bank of China holds ISO 27001 certification.

Neither U.S. Bank nor Bank of China holds PCI DSS certification.

Neither U.S. Bank nor Bank of China holds HIPAA certification.

Neither U.S. Bank nor Bank of China holds GDPR certification.

Latest Global CVEs (Not Company-Specific)

Description

Marshmallow is a lightweight library for converting complex objects to and from simple Python datatypes. In versions from 3.0.0rc1 to before 3.26.2 and from 4.0.0 to before 4.1.2, Schema.load(data, many=True) is vulnerable to denial of service attacks. A moderately sized request can consume a disproportionate amount of CPU time. This issue has been patched in version 3.26.2 and 4.1.2.

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

KEDA is a Kubernetes-based Event Driven Autoscaling component. Prior to versions 2.17.3 and 2.18.3, an Arbitrary File Read vulnerability has been identified in KEDA, potentially affecting any KEDA resource that uses TriggerAuthentication to configure HashiCorp Vault authentication. The vulnerability stems from an incorrect or insufficient path validation when loading the Service Account Token specified in spec.hashiCorpVault.credential.serviceAccount. An attacker with permissions to create or modify a TriggerAuthentication resource can exfiltrate the content of any file from the node's filesystem (where the KEDA pod resides) by directing the file's content to a server under their control, as part of the Vault authentication request. The potential impact includes the exfiltration of sensitive system information, such as secrets, keys, or the content of files like /etc/passwd. This issue has been patched in versions 2.17.3 and 2.18.3.

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

Fedify is a TypeScript library for building federated server apps powered by ActivityPub. Prior to versions 1.6.13, 1.7.14, 1.8.15, and 1.9.2, a Regular Expression Denial of Service (ReDoS) vulnerability exists in Fedify's document loader. The HTML parsing regex at packages/fedify/src/runtime/docloader.ts:259 contains nested quantifiers that cause catastrophic backtracking when processing maliciously crafted HTML responses. This issue has been patched in versions 1.6.13, 1.7.14, 1.8.15, and 1.9.2.

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

Authenticated Remote Code Execution (RCE) in PluXml CMS 5.8.22 allows an attacker with administrator panel access to inject a malicious PHP webshell into a theme file (e.g., home.php).

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

An issue was discovered in Xiongmai XM530 IP cameras on firmware V5.00.R02.000807D8.10010.346624.S.ONVIF 21.06. The GetStreamUri exposes RTSP URIs containing hardcoded credentials enabling direct unauthorized video stream access.

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