Comparison Overview

Maybank

VS

Indian Bank

Maybank

100 Jalan Tun Perak, Kuala Lumpur, Wilayah Persekutuan, MY, 50050
Last Update: 2025-11-23
Between 800 and 849

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,164
Subsidiaries: 0
12-month incidents
0
Known data breaches
0
Attack type number
0

Indian Bank

254-260, Avvai Shanmugam Salai, Royapettah, Chennai, Tamil Nadu, IN, 600 014
Last Update: 2025-11-25
Between 750 and 799

Established in 1907, today, we are a family of over 141 million customers and 40000 staff members. With a 100% CBS network of 6000+ branches and 5400+ ATMs and BNAs, Indian Bank has a wide national footprint, besides foreign branches in Singapore and Colombo, along with arrangements with 640 Overseas Correspondent Banks present in 77 countries. We strive continuously to provide the best banking solutions to the people/units from all possible sectors including Corporate, Retail, Institutional, Agriculture, MSME, SHG, and NRIs. Choose from our wide range of products spanning Deposits, Loans, Cards, Wallets, Apps, Insurance, Mutual Funds, Remittances, Forex services and more. For information, visit https://indianbank.bank.in/ Further, you can send feedback at [email protected]

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

Compliance Badges Comparison

Security & Compliance Standards Overview

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
https://images.rankiteo.com/companyimages/indianbank.jpeg
Indian 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
Maybank
100%
Compliance Rate
0/4 Standards Verified
Indian Bank
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Banking Industry Average (This Year)

No incidents recorded for Maybank in 2025.

Incidents vs Banking Industry Average (This Year)

No incidents recorded for Indian Bank in 2025.

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

Maybank cyber incidents detection timeline including parent company and subsidiaries

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

Indian Bank cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

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

No Incident

https://images.rankiteo.com/companyimages/indianbank.jpeg
Indian Bank
Incidents

Date Detected: 08/2017
Type:Breach
Blog: Blog

FAQ

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

Indian Bank company has historically faced a number of disclosed cyber incidents, whereas Maybank company has not reported any.

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

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

Indian Bank company has disclosed at least one data breach, while Maybank company has not reported such incidents publicly.

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

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

Neither Maybank nor Indian Bank holds any compliance certifications.

Neither company holds any compliance certifications.

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

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

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

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

Neither Maybank nor Indian Bank holds ISO 27001 certification.

Neither Maybank nor Indian Bank holds PCI DSS certification.

Neither Maybank nor Indian Bank holds HIPAA certification.

Neither Maybank nor Indian 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