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
VakıfBank
VakıfBank
Last Update: 2025-11-23
Between 750 and 799
1954 yılında, vakıf kaynaklarını ekonomik kalkınmanın gereksinimleri doğrultusunda en iyi biçimde değerlendirmek amacıyla kurulan VakıfBank, o günden bu yana çağdaş bankacılık yöntemleri ve uygulamalarıyla Türkiye’nin tasarruf düzeyinin gelişim sürecine katkıda bulunmaktadır. VakıfBank; bölgesinin en iyi, en çok tercih edilen ve değer yaratan bankası olma vizyonu doğrultusunda, vakıf kültüründen aldığı güçle, kendisine emanet edilen varlık ve değerleri etkin ve verimli yöneterek müşteriler, çalışanlar, hissedarlar ve topluma kattığı değerleri sürekli artırma misyonuyla hareket etmektedir. Kurumsal, ticari ve küçük işletme bankacılığının yanı sıra bireysel ve özel bankacılık alanlarında da çağdaş bankacılık ürün ve hizmetleri sunan VakıfBank, özellikle bir alanda değil, tüm finansal alanlarda uzmanlaşmış, Türkiye’nin önde gelen bankalarından biridir. Temel bankacılık ürün ve hizmetlerine ek olarak yatırım bankacılığı ve sermaye piyasası faaliyetlerinde de bulunan VakıfBank, iç ve dış ticaretin finansmanında öncü bir rol üstlenmektedir. Ayrıca, finansal iştirakleri aracılığıyla sigortacılıktan finansal kiralama ve factoring hizmetlerine kadar geniş bir yelpazede yer alan finansal ürünleri çağın gerektirdiği yüksek teknolojilerle müşterilerine sunmaktadır. VakıfBank’ın ABD New York, Kuzey Irak Erbil, Katar Doha şubelerinin yanı sıra Bahreyn’de kıyı bankacılığı şubesi bulunmaktadır. Ayrıca, Avusturya’da VakıfBank International AG (Viyana Şubesi ve Almanya’da Köln Şubesi), KKTC’de Tasfiye Halinde World Vakıf UBB. Ltd. ve Kıbrıs Vakıflar Bank. Ltd. olmak üzere yurt dışında üç bankada da iştiraki bulunmaktadır. VakıfBank’ın diğer iştirakleri arasında; Vakıf Faktoring A.Ş., Vakıf Finansal Kiralama A.Ş., Vakıf Gayrimenkul Yatırım Ortaklığı A.Ş., Vakıf Menkul Kıymet Yat. Ort. A.Ş., Vakıf Yatırım Menkul Değerler A.Ş. Vakıf Pazarlama San. ve Ticaret A.Ş., Taksim Otelcilik A.Ş., Vakıf Enerji ve Madencilik A.Ş., Vakıf Gayrimenkul Değerleme A.Ş. bulunmaktadır.
NAICS: 52211
NAICS Definition: Commercial Banking
Employees: 11,273
Subsidiaries: 0
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
VakıfBank
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
VakıfBank
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 VakıfBank 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 — VakıfBank (X = Date, Y = Severity)
VakıfBank 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
VakıfBank
Incidents
No Incident
FAQ
Central Bank of the Commonwealth company demonstrates a stronger AI Cybersecurity Score compared to VakıfBank company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.
Historically, VakıfBank company has disclosed a higher number of cyber incidents compared to Central Bank of the Commonwealth company.
In the current year, VakıfBank company and Central Bank of the Commonwealth company have not reported any cyber incidents.
Neither VakıfBank company nor Central Bank of the Commonwealth company has reported experiencing a ransomware attack publicly.
Neither VakıfBank company nor Central Bank of the Commonwealth company has reported experiencing a data breach publicly.
Neither VakıfBank company nor Central Bank of the Commonwealth company has reported experiencing targeted cyberattacks publicly.
Neither Central Bank of the Commonwealth company nor VakıfBank company has reported experiencing or disclosing vulnerabilities publicly.
Neither Central Bank of the Commonwealth nor VakıfBank holds any compliance certifications.
Neither company holds any compliance certifications.
Neither Central Bank of the Commonwealth company nor VakıfBank company has publicly disclosed detailed information about the number of their subsidiaries.
VakıfBank 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 VakıfBank holds SOC 2 Type 1 certification.
Neither Central Bank of the Commonwealth nor VakıfBank holds SOC 2 Type 2 certification.
Neither Central Bank of the Commonwealth nor VakıfBank holds ISO 27001 certification.
Neither Central Bank of the Commonwealth nor VakıfBank holds PCI DSS certification.
Neither Central Bank of the Commonwealth nor VakıfBank holds HIPAA certification.
Neither Central Bank of the Commonwealth nor VakıfBank 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
