Comparison Overview

Central Bank of India

VS

Capitec

Central Bank of India

Chander Mukhi, Nariman Point Mumbai, Maharashtra 400021, IN
Last Update: 2025-11-22

Welcome to the official LinkedIn page of Central Bank of India. Central Bank of India offers a wide range of products and services for every segment. Please join us to know more about our best products & services, attractive offers and the latest updates. We invite & value your active participation, valuable comments and feedback. Established in 1911, Central Bank of India was the first Indian commercial bank, wholly-owned and managed by Indians. The establishment of the Bank was the ultimate realization of the dream of Sir Sorabji Pochkhanawala, founder of the Bank. Sir Pherozesha Mehta was the first Chairman of a truly 'Swadeshi Bank'. Central Bank of India is a pioneer in launching a number of innovative and unique banking activities. Among the Public Sector Banks, Central Bank of India can be described as a truly All India Bank, due to the distribution of its large network of branches throughout the length and breadth of the country. Central Bank of India holds a very prominent place among the Public Sector Banks on account of its network of more than 4700 Branches at various centers.

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

Capitec

5 Neutron Road, Stellenbosch, Western Cape, ZA, 7600
Last Update: 2025-11-27
Between 800 and 849

Imagine simple, affordable banking solutions that work for you – just like it does for over 25 million South Africans. They’re banking smart, paying less and getting more value every day with us. As the country’s leading digital bank, we’re proud to have been voted the Coolest Bank by the youth in the 2024 Sunday Times GenNext Awards. With 880 branches and a team of over 16,900, we’re here to grow with you.

NAICS: 52211
NAICS Definition: Commercial Banking
Employees: 21,561
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/centralbankofindia.jpeg
Central Bank of India
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/capitec-bank.jpeg
Capitec
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
Central Bank of India
100%
Compliance Rate
0/4 Standards Verified
Capitec
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Banking Industry Average (This Year)

No incidents recorded for Central Bank of India in 2025.

Incidents vs Banking Industry Average (This Year)

No incidents recorded for Capitec in 2025.

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

Central Bank of India cyber incidents detection timeline including parent company and subsidiaries

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

Capitec cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/centralbankofindia.jpeg
Central Bank of India
Incidents

No Incident

https://images.rankiteo.com/companyimages/capitec-bank.jpeg
Capitec
Incidents

No Incident

FAQ

Capitec company demonstrates a stronger AI Cybersecurity Score compared to Central Bank of India company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Historically, Capitec company has disclosed a higher number of cyber incidents compared to Central Bank of India company.

In the current year, Capitec company and Central Bank of India company have not reported any cyber incidents.

Neither Capitec company nor Central Bank of India company has reported experiencing a ransomware attack publicly.

Neither Capitec company nor Central Bank of India company has reported experiencing a data breach publicly.

Neither Capitec company nor Central Bank of India company has reported experiencing targeted cyberattacks publicly.

Neither Central Bank of India company nor Capitec company has reported experiencing or disclosing vulnerabilities publicly.

Neither Central Bank of India nor Capitec holds any compliance certifications.

Neither company holds any compliance certifications.

Neither Central Bank of India company nor Capitec company has publicly disclosed detailed information about the number of their subsidiaries.

Capitec company employs more people globally than Central Bank of India company, reflecting its scale as a Banking.

Neither Central Bank of India nor Capitec holds SOC 2 Type 1 certification.

Neither Central Bank of India nor Capitec holds SOC 2 Type 2 certification.

Neither Central Bank of India nor Capitec holds ISO 27001 certification.

Neither Central Bank of India nor Capitec holds PCI DSS certification.

Neither Central Bank of India nor Capitec holds HIPAA certification.

Neither Central Bank of India nor Capitec 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