Central Bank of the Commonwealth
Last Update: 2025-11-24
Between 800 and 849
None
NAICS: 52211
NAICS Definition: Commercial Banking
Employees: 0
Subsidiaries: 0
12-month incidents
0
Known data breaches
0
Attack type number
0
Comparison Overview
Central Bank of the Commonwealth
VS
Federal Bank
Federal Bank
Last Update: 2025-11-23
Between 750 and 799
Federal Bank, one of the leading private sector banks with presence across the country, began its journey from humble backgrounds to reach the stature of an institution with national prominence & character. With a rich legacy of 7 decades, the Bank aspires to be the most admired Bank in the country and fueling its dreams are the 19 million and growing customer base who have always been loyal to the Bank as the Bank is to them. Headquartered in Aluva, Kerala, the Bank’s scrips are widely held and are listed in the Bombay Stock Exchange and National Stock Exchange in India. The Bank’s global depository receipts are listed on the London Stock Exchange. The Bank has built its empire on the twin values of ethics and excellence, and this has propelled the Bank throughout its journey. Over 1,588 branches, 2079+ ATMs/ Cash Recyclers and a committed, experienced & energetic workforce, Federal Bank now has its presence across the nation. To service the NRIs, who have been its pillars of strength, the Bank operates Representative Offices at Dubai and Abu Dhabi in the UAE. The Bank today handles one fifth of the total NR remittance to the country and this is testimony to its relationship with the NR diaspora. The Bank also has an IFSC Banking Unit (IBU) in Gujarat International Finance Tec-City (GIFT City). Transformation is inevitable and for Federal Bank it has been no different. The Bank believes in transforming itself, keeping its principles intact, to match the beats of the industry and the expectations of its stakeholders. Technology is the new buzzword, and it has left its indelible mark in the banking industry as well. Disclaimer: Federal Bank advices against sharing any confidential information on social media handles of the Bank
NAICS: 52211
NAICS Definition: Commercial Banking
Employees: 11,893
Subsidiaries: 1
12-month incidents
0
Known data breaches
0
Attack type number
0
Compliance Badges Comparison
Security & Compliance Standards Overview
Central Bank of the Commonwealth
ISO 27001
Not verified
SOC2 Type 1
Not verified
SOC2 Type 2
Not verified
GDPR
Not verified
PCI DSS
Not verified
HIPAA
Not verified
Federal Bank
ISO 27001
Not verified
SOC2 Type 1
Not verified
SOC2 Type 2
Not verified
GDPR
Not verified
PCI DSS
Not verified
HIPAA
Not verified
Compliance Summary
Central Bank of the Commonwealth
100%
Compliance Rate
0/4 Standards Verified
Federal Bank
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 the Commonwealth in 2025.
Incidents vs Banking Industry Average (This Year)
No incidents recorded for Federal Bank in 2025.
Incident History — Central Bank of the Commonwealth (X = Date, Y = Severity)
Central Bank of the Commonwealth cyber incidents detection timeline including parent company and subsidiaries
Incident History — Federal Bank (X = Date, Y = Severity)
Federal Bank cyber incidents detection timeline including parent company and subsidiaries
Notable Incidents
Last 3 Security & Risk Events by Company
Central Bank of the Commonwealth
Incidents
No Incident
Federal Bank
Incidents
No Incident
FAQ
Central Bank of the Commonwealth company demonstrates a stronger AI Cybersecurity Score compared to Federal Bank company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.
Historically, Federal Bank company has disclosed a higher number of cyber incidents compared to Central Bank of the Commonwealth company.
In the current year, Federal Bank company and Central Bank of the Commonwealth company have not reported any cyber incidents.
Neither Federal Bank company nor Central Bank of the Commonwealth company has reported experiencing a ransomware attack publicly.
Neither Federal Bank company nor Central Bank of the Commonwealth company has reported experiencing a data breach publicly.
Neither Federal Bank company nor Central Bank of the Commonwealth company has reported experiencing targeted cyberattacks publicly.
Neither Central Bank of the Commonwealth company nor Federal Bank company has reported experiencing or disclosing vulnerabilities publicly.
Neither Central Bank of the Commonwealth nor Federal Bank holds any compliance certifications.
Neither company holds any compliance certifications.
Federal Bank company has more subsidiaries worldwide compared to Central Bank of the Commonwealth company.
Federal Bank company employs more people globally than Central Bank of the Commonwealth company, reflecting its scale as a Banking.
Neither Central Bank of the Commonwealth nor Federal Bank holds SOC 2 Type 1 certification.
Neither Central Bank of the Commonwealth nor Federal Bank holds SOC 2 Type 2 certification.
Neither Central Bank of the Commonwealth nor Federal Bank holds ISO 27001 certification.
Neither Central Bank of the Commonwealth nor Federal Bank holds PCI DSS certification.
Neither Central Bank of the Commonwealth nor Federal Bank holds HIPAA certification.
Neither Central Bank of the Commonwealth nor Federal 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
References
- https://github.com/angular/angular/commit/0276479e7d0e280e0f8d26fa567d3b7aa97a516f
- https://github.com/angular/angular/commit/05fe6686a97fa0bcd3cf157805b3612033f975bc
- https://github.com/angular/angular/commit/3240d856d942727372a705252f7c8c115394a41e
- https://github.com/angular/angular/releases/tag/19.2.16
- https://github.com/angular/angular/releases/tag/20.3.14
- https://github.com/angular/angular/releases/tag/21.0.1
- https://github.com/angular/angular/security/advisories/GHSA-58c5-g7wp-6w37
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
