Comparison Overview

Bandhan Bank

VS

Maybank

Bandhan Bank

BN 5, Sector V, Salt Lake City Adventz Infinity@5 Kolkata, West Bengal 700091, IN
Last Update: 2026-01-17
View Profile
Between 750 and 799
http://www.bandhanbank.com

Started as a universal bank on August 23, 2015, Bandhan Bank is one of India’s fastest-growing private sector banks. Bandhan Bank has always been committed to financial inclusion and aims to serve the underserved. Guided by the principle of ‘Aapka Bhala, Sabki Bhalai,’ the Bank is dedicated not only to serving its customers but also to making a positive difference in people’s lives. They actively aim to bridge the gap for those who may not have had easy access to conventional banking services. Its focus is on providing a variety of world-class banking products and a comprehensive 360-degree service proposition, including loans, deposit accounts, internet and mobile banking, and ATM services, across India, primarily to semi-urban and rural customers. Presently, Bandhan Bank has nearly 6,300 banking outlets pan-India. The Bank has mobilised deposits of ₹1,41,002 crore and its total advances stand at ₹1,31,927 crore taking the total business to ₹2,72,929 crore as on December 31, 2024. The Bank has a team of 78,400 employees on roll. Bandhan Bank is driven by a constant desire to serve better.

NAICS: 52211
NAICS Definition: Commercial Banking
Employees: 10,001
Subsidiaries: 0
12-month incidents
0
Known data breaches
0
Attack type number
0
View Profile

Maybank

100 Jalan Tun Perak, Kuala Lumpur, Wilayah Persekutuan, MY, 50050
Last Update: 2026-01-19
Between 800 and 849
http://www.maybank.com

Maybank Group is the leading financial services provider in Malaysia catering to the needs of consumers, investors, entrepreneurs, non-profit organisations and corporations. The Group, which has expanded internationally, has the largest network among Malaysian banks of over 2,400 branches and offices in 20 countries, employing over 44,000 Maybankers and serving over 22 million customers. It is the only regional bank with a presence in all 10 ASEAN countries (as of November 2016). By strengthening our core business and franchise, we gain competitive advantage by achieving synergies across our diverse group. Domestically we aim to achieve leadership across key and profitable segments. Internationally we capture value from new investments and continue to pursue organic expansion by delivering innovation and superior customer value. We are a top recruiter of talent and view our leadership pool and talent pipeline as key to realising our aspirations. We constantly seek to enhance performance management and achieve cost optimisation by focusing on effective IT operations and enhancing employee productivity. Maybank & Maybank Islamic are members of PIDM in Malaysia.

NAICS: 52211
NAICS Definition: Commercial Banking
Employees: 26,305
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/bandhanbank.jpeg
Bandhan 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/maybank.jpeg
Maybank
—
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
Bandhan Bank
100%
Compliance Rate
0/4 Standards Verified
Maybank
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Banking Industry Average (This Year)

No incidents recorded for Bandhan Bank in 2026.

Incidents vs Banking Industry Average (This Year)

No incidents recorded for Maybank in 2026.

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

Bandhan Bank cyber incidents detection timeline including parent company and subsidiaries

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

Maybank cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/bandhanbank.jpeg
Bandhan Bank
Incidents

No Incident

https://images.rankiteo.com/companyimages/maybank.jpeg
Maybank
Incidents

No Incident

FAQ

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

Historically, Maybank company has disclosed a higher number of cyber incidents compared to Bandhan Bank company.

In the current year, Maybank company and Bandhan Bank company have not reported any cyber incidents.

Neither Maybank company nor Bandhan Bank company has reported experiencing a ransomware attack publicly.

Neither Maybank company nor Bandhan Bank company has reported experiencing a data breach publicly.

Neither Maybank company nor Bandhan Bank company has reported experiencing targeted cyberattacks publicly.

Neither Bandhan Bank company nor Maybank company has reported experiencing or disclosing vulnerabilities publicly.

Neither Bandhan Bank nor Maybank holds any compliance certifications.

Neither company holds any compliance certifications.

Neither Bandhan Bank company nor Maybank company has publicly disclosed detailed information about the number of their subsidiaries.

Maybank company employs more people globally than Bandhan Bank company, reflecting its scale as a Banking.

Neither Bandhan Bank nor Maybank holds SOC 2 Type 1 certification.

Neither Bandhan Bank nor Maybank holds SOC 2 Type 2 certification.

Neither Bandhan Bank nor Maybank holds ISO 27001 certification.

Neither Bandhan Bank nor Maybank holds PCI DSS certification.

Neither Bandhan Bank nor Maybank holds HIPAA certification.

Neither Bandhan Bank nor Maybank holds GDPR certification.

Latest Global CVEs (Not Company-Specific)

Description

SummaryA command injection vulnerability (CWE-78) has been found to exist in the `wrangler pages deploy` command. The issue occurs because the `--commit-hash` parameter is passed directly to a shell command without proper validation or sanitization, allowing an attacker with control of `--commit-hash` to execute arbitrary commands on the system running Wrangler. Root causeThe commitHash variable, derived from user input via the --commit-hash CLI argument, is interpolated directly into a shell command using template literals (e.g.,  execSync(`git show -s --format=%B ${commitHash}`)). Shell metacharacters are interpreted by the shell, enabling command execution. ImpactThis vulnerability is generally hard to exploit, as it requires --commit-hash to be attacker controlled. The vulnerability primarily affects CI/CD environments where `wrangler pages deploy` is used in automated pipelines and the --commit-hash parameter is populated from external, potentially untrusted sources. An attacker could exploit this to: * Run any shell command. * Exfiltrate environment variables. * Compromise the CI runner to install backdoors or modify build artifacts. Credits Disclosed responsibly by kny4hacker. Mitigation * Wrangler v4 users are requested to upgrade to Wrangler v4.59.1 or higher. * Wrangler v3 users are requested to upgrade to Wrangler v3.114.17 or higher. * Users on Wrangler v2 (EOL) should upgrade to a supported major version.

Published
Date
2026-01-20
Updated
Date
2026-01-20
Risk Information
cvss4
Base: 7.7
Severity: LOW
CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:H/SC:L/SI:L/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
References
Description

Vulnerability in the Oracle VM VirtualBox product of Oracle Virtualization (component: Core). Supported versions that are affected are 7.1.14 and 7.2.4. Easily exploitable vulnerability allows high privileged attacker with logon to the infrastructure where Oracle VM VirtualBox executes to compromise Oracle VM VirtualBox. While the vulnerability is in Oracle VM VirtualBox, attacks may significantly impact additional products (scope change). Successful attacks of this vulnerability can result in takeover of Oracle VM VirtualBox. CVSS 3.1 Base Score 8.2 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H).

Published
Date
2026-01-20
Updated
Date
2026-01-20
Risk Information
cvss3
Base: 8.2
Severity: LOW
CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H
References
Description

Vulnerability in the Oracle VM VirtualBox product of Oracle Virtualization (component: Core). Supported versions that are affected are 7.1.14 and 7.2.4. Easily exploitable vulnerability allows high privileged attacker with logon to the infrastructure where Oracle VM VirtualBox executes to compromise Oracle VM VirtualBox. While the vulnerability is in Oracle VM VirtualBox, attacks may significantly impact additional products (scope change). Successful attacks of this vulnerability can result in unauthorized creation, deletion or modification access to critical data or all Oracle VM VirtualBox accessible data as well as unauthorized access to critical data or complete access to all Oracle VM VirtualBox accessible data and unauthorized ability to cause a partial denial of service (partial DOS) of Oracle VM VirtualBox. CVSS 3.1 Base Score 8.1 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:L).

Published
Date
2026-01-20
Updated
Date
2026-01-20
Risk Information
cvss3
Base: 8.1
Severity: LOW
CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:L
References
Description

Vulnerability in the Oracle VM VirtualBox product of Oracle Virtualization (component: Core). Supported versions that are affected are 7.1.14 and 7.2.4. Easily exploitable vulnerability allows high privileged attacker with logon to the infrastructure where Oracle VM VirtualBox executes to compromise Oracle VM VirtualBox. While the vulnerability is in Oracle VM VirtualBox, attacks may significantly impact additional products (scope change). Successful attacks of this vulnerability can result in takeover of Oracle VM VirtualBox. CVSS 3.1 Base Score 8.2 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H).

Published
Date
2026-01-20
Updated
Date
2026-01-20
Risk Information
cvss3
Base: 8.2
Severity: LOW
CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H
References
Description

Vulnerability in the Oracle VM VirtualBox product of Oracle Virtualization (component: Core). Supported versions that are affected are 7.1.14 and 7.2.4. Easily exploitable vulnerability allows high privileged attacker with logon to the infrastructure where Oracle VM VirtualBox executes to compromise Oracle VM VirtualBox. While the vulnerability is in Oracle VM VirtualBox, attacks may significantly impact additional products (scope change). Successful attacks of this vulnerability can result in takeover of Oracle VM VirtualBox. CVSS 3.1 Base Score 8.2 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H).

Published
Date
2026-01-20
Updated
Date
2026-01-20
Risk Information
cvss3
Base: 8.2
Severity: LOW
CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H
References