Comparison Overview

Meezan Bank Limited

VS

Bank of China

Meezan Bank Limited

Meezan House, C-25, Estate Avenue, SITE, Karachi, Karachi, Sindh, 75500, PK
Last Update: 2025-11-22
Between 750 and 799

Meezan Bank, Pakistan's first and largest Islamic bank, is one of the fastest growing financial institutions in the banking sector of the country. With its Vision of establishing ‘Islamic banking as banking of first choice’ – the Bank commenced operations in 2002, after being issued the first-ever Islamic commercial banking license by the State Bank of Pakistan. Meezan Bank has an impressive growth rate, excellent credit rating and a strong Shariah Advisory board including reputed scholars from around the world.

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

Bank of China

Bank of China Head Office Building, Beijing, undefined, 100818, CN
Last Update: 2025-11-21
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/meezan-bank-ltd.jpeg
Meezan Bank Limited
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
Meezan Bank Limited
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 Meezan Bank Limited in 2025.

Incidents vs Banking Industry Average (This Year)

No incidents recorded for Bank of China in 2025.

Incident History — Meezan Bank Limited (X = Date, Y = Severity)

Meezan Bank Limited 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/meezan-bank-ltd.jpeg
Meezan Bank Limited
Incidents

No Incident

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 Meezan Bank Limited company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

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

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

Neither Bank of China company nor Meezan Bank Limited company has reported experiencing a ransomware attack publicly.

Neither Bank of China company nor Meezan Bank Limited company has reported experiencing a data breach publicly.

Neither Bank of China company nor Meezan Bank Limited company has reported experiencing targeted cyberattacks publicly.

Neither Meezan Bank Limited company nor Bank of China company has reported experiencing or disclosing vulnerabilities publicly.

Neither Meezan Bank Limited nor Bank of China holds any compliance certifications.

Neither company holds any compliance certifications.

Neither Meezan Bank Limited company nor Bank of China company has publicly disclosed detailed information about the number of their subsidiaries.

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

Neither Meezan Bank Limited nor Bank of China holds SOC 2 Type 1 certification.

Neither Meezan Bank Limited nor Bank of China holds SOC 2 Type 2 certification.

Neither Meezan Bank Limited nor Bank of China holds ISO 27001 certification.

Neither Meezan Bank Limited nor Bank of China holds PCI DSS certification.

Neither Meezan Bank Limited nor Bank of China holds HIPAA certification.

Neither Meezan Bank Limited nor Bank of China 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