Comparison Overview

Bank Mega

VS

Bandhan Bank

Bank Mega

Menara Bank Mega, Jl. Kapt Tendean 12 - 14A, Jakarta, DKI Jakarta, ID, 12790
Last Update: 2025-11-26
Between 750 and 799

Perjalanan Bank Mega berawal pada tahun 1969, dengan nama PT Bank Karman di Surabaya. Kemudian bertransformasi menjadi Mega Bank pada tahun 1992, dan berpindah lokasi ke Jakarta. Pada tahun 1996, Chairul Tanjung dengan PARA GROUP, yang kini dikenal dengan CT Corpora, mengambil alih dan membuat gebrakan dengan menghadirkan logo baru untuk mengukuhkan Mega Bank sebagai lembaga keuangan kepercayaan masyarakat. Tahun 2000 menjadi tahun yang penting, kala Mega Bank mengganti nama menjadi PT Bank Mega Tbk dan melaksanakan Initial Public Offering dan pencatatan di BEJ dan BES. Hingga kini, PT Bank Mega Tbk berpegang pada azas profesionalisme, keterbukaan dan kehati-hatian dengan struktur permodalan yang kuat serta produk dan fasilitas perbankan terkini. Mengusung visi untuk menjadi Bank Kebanggaan Indonesia, Bank Mega berkomitmen dalam mewujudkan hubungan baik yang berkesinambungan dengan nasabah, melalui layanan perbankan inovatif dan sinergi dengan didukung oleh ekosistem yang terintegrasi, sumber daya manusia yang profesional serta kemampuan kinerja organisasi terbaik untuk memberikan nilai tambah yang tinggi bagi seluruh stakeholder. Bank Mega menjunjung tinggi Dynamics, Entrepreneurship, Trust, Ethics, Commitment, Synergy sebagai nilai dan budaya perusahaan yang dibangun dalam setiap lapis organisasi perusahaan sehingga tercipta lingkungan kerja yang harmonis, dinamis, dan nyaman. Pencapaian terbaru Bank Mega: - Investortrust The Best Bank 2024 - Kategori KBMI 3 - 2024 Stellar Workplace Recognition in Employee Commitment - 2024 Stellar Workplace Recognition in Employee Satisfaction - LPS Award 2023 - Bank Terbaik Versi Pelaporan SCV - CNBC Indonesia Awards 2022 - The Best Performing Big Bank - CNBC Indonesia - Best of The Best Awards 2022 - The Best 50 Public Listed Companies 2022 - Forbes Indonesia - Tempo Financial Award - The Best Bank in Financial Resilience Kategori Bank Umum Konvensional (KBMI 3 dan 4) dan masih banyak lagi pencapaian Bank Mega lainnya...

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

Bandhan Bank

BN 5, Sector V, Salt Lake City Adventz Infinity@5 Kolkata, West Bengal 700091, IN
Last Update: 2025-11-27
Between 750 and 799

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

Compliance Badges Comparison

Security & Compliance Standards Overview

https://images.rankiteo.com/companyimages/pt-bank-mega-tbk..jpeg
Bank Mega
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/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
Compliance Summary
Bank Mega
100%
Compliance Rate
0/4 Standards Verified
Bandhan Bank
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Banking Industry Average (This Year)

No incidents recorded for Bank Mega in 2025.

Incidents vs Banking Industry Average (This Year)

No incidents recorded for Bandhan Bank in 2025.

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

Bank Mega cyber incidents detection timeline including parent company and subsidiaries

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

Bandhan Bank cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/pt-bank-mega-tbk..jpeg
Bank Mega
Incidents

No Incident

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

No Incident

FAQ

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

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

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

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

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

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

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

Neither Bank Mega nor Bandhan Bank holds any compliance certifications.

Neither company holds any compliance certifications.

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

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

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

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

Neither Bank Mega nor Bandhan Bank holds ISO 27001 certification.

Neither Bank Mega nor Bandhan Bank holds PCI DSS certification.

Neither Bank Mega nor Bandhan Bank holds HIPAA certification.

Neither Bank Mega nor Bandhan Bank 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