Comparison Overview

D Commerce Bank

VS

OCBC

D Commerce Bank

8, General Totleben Blvd. Sofia, 1000, BG
Last Update: 2025-03-15 (UTC)
Between 900 and 1000
http://www.dbank.bg

Excellent

Small bulgarian bank with a focus on small and medium sized businesses. D Commerce Bank AD has been established as a commercial bank with a full banking license to conduct financial and banking business in this country and abroad. The bank provides all kind of banking and financial services and applies best international practices. Main priority of our bank is to support the export activities and to increase the trade turnover of Bulgaria with Turkey by financing local manufacturing, finding buyers and attracting investors for increasing the volumes and the quality of products. D Commerce Bank AD puts high priority on service, comfort and confidentiality. A wide range of products is offered to individuals and companies from a variety of sectors. The bank strives to improve customer satisfaction by providing fast and cost effective solutions in a reliable and flexible manner.

NAICS: 522
NAICS Definition:
Employees: 201-500
Subsidiaries: 0
12-month incidents
0
Known data breaches
0
Attack type number
0

OCBC

65 Chulia St, Singapore, Singapore, 049513, SG
Last Update: 2025-05-06 (UTC)

Strong

Between 800 and 900
http://www.ocbc.com

OCBC is the longest established Singapore bank, formed in 1932 from the merger of three local banks, the oldest of which was founded in 1912. It is now the second largest financial services group in Southeast Asia by assets and one of the world’s most highly-rated banks, with an Aa1 rating from Moody’s. Recognised for its financial strength and stability, OCBC is consistently ranked among the World’s Top 50 Safest Banks by Global Finance and has been named Best Managed Bank in Singapore by The Asian Banker. OCBC and its subsidiaries offer a broad array of commercial banking, specialist financial and wealth management services, ranging from consumer, corporate, investment, private and transaction banking to treasury, insurance, asset management and stockbroking services. OCBC’s key markets are Singapore, Malaysia, Indonesia and Greater China. It has more than 570 branches and representative offices in 19 countries and regions. These include about 300 branches and offices in Indonesia under subsidiary Bank OCBC NISP, and over 90 branches and offices in Mainland China, Hong Kong SAR and Macau SAR under OCBC Wing Hang. OCBC’s private banking services are provided by its wholly-owned subsidiary Bank of Singapore, which operates on a unique open-architecture product platform to source for the best-in-class products to meet its clients’ goals. OCBC's insurance subsidiary, Great Eastern Holdings, is the oldest and most established life insurance group in Singapore and Malaysia. Its asset management subsidiary, Lion Global Investors, is one of the largest private sector asset management companies in Southeast Asia.

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

Compliance Badges Comparison

Security & Compliance Standards Overview

https://images.rankiteo.com/companyimages/d-commerce-bank.jpeg
D Commerce Bank
—
ISO 27001
Not verified
—
SOC 2
Not verified
—
GDPR
No public badge
—
PCI DSS
No public badge
https://images.rankiteo.com/companyimages/ocbc-bank.jpeg
OCBC
—
ISO 27001
Not verified
—
SOC 2
Not verified
—
GDPR
No public badge
—
PCI DSS
No public badge
Compliance Summary
D Commerce Bank
100%
Compliance Rate
0/4 Standards Verified
OCBC
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Banking Industry Average (This Year)

No incidents recorded for D Commerce Bank in 2025.

Incidents vs Banking Industry Average (This Year)

No incidents recorded for OCBC in 2025.

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

D Commerce Bank cyber incidents detection timeline including parent company and subsidiaries

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

OCBC cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/d-commerce-bank.jpeg
D Commerce Bank
Incidents

No Incident

https://images.rankiteo.com/companyimages/ocbc-bank.jpeg
OCBC
Incidents

No Incident

FAQ

D Commerce Bank company company demonstrates a stronger AI risk posture compared to OCBC company company, reflecting its advanced AI governance and monitoring frameworks.

Historically, OCBC company has disclosed a higher number of cyber incidents compared to D Commerce Bank company.

In the current year, OCBC company and D Commerce Bank company have not reported any cyber incidents.

Neither OCBC company nor D Commerce Bank company has reported experiencing a ransomware attack publicly.

Neither OCBC company nor D Commerce Bank company has reported experiencing a data breach publicly.

Neither OCBC company nor D Commerce Bank company has reported experiencing targeted cyberattacks publicly.

Neither D Commerce Bank company nor OCBC company has reported experiencing or disclosing vulnerabilities publicly.

OCBC company has more subsidiaries worldwide compared to D Commerce Bank company.

OCBC company employs more people globally than D Commerce Bank company, reflecting its scale as a Banking.

Latest Global CVEs (Not Company-Specific)

Description

A vulnerability was found in LaChatterie Verger up to 1.2.10. This impacts the function redirectToAuthorization of the file /src/main/services/mcp/oauth/provider.ts. The manipulation of the argument URL results in deserialization. The attack can be executed remotely. The exploit has been made public and could be used. The vendor was contacted early about this disclosure but did not respond in any way.

Published
Date
2025-10-04
Updated
Date
2025-10-04
Risk Information
cvss2
Base: 6.5
Severity: LOW
AV:N/AC:L/Au:S/C:P/I:P/A:P
cvss3
Base: 6.3
Severity: LOW
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L
cvss4
Base: 5.3
Severity: LOW
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P/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
Description

A vulnerability has been found in SeriaWei ZKEACMS up to 4.3. This affects the function Delete of the file src/ZKEACMS.Redirection/Controllers/UrlRedirectionController.cs of the component POST Request Handler. The manipulation leads to improper authorization. Remote exploitation of the attack is possible. The exploit has been disclosed to the public and may be used. The vendor was contacted early about this disclosure but did not respond in any way.

Published
Date
2025-10-04
Updated
Date
2025-10-04
Risk Information
cvss2
Base: 5.5
Severity: LOW
AV:N/AC:L/Au:S/C:N/I:P/A:P
cvss3
Base: 5.4
Severity: LOW
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L
cvss4
Base: 5.3
Severity: LOW
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:L/SC:N/SI:N/SA:N/E:P/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
Description

In the Linux kernel, the following vulnerability has been resolved: jfs: fix invalid free of JFS_IP(ipimap)->i_imap in diUnmount syzbot found an invalid-free in diUnmount: BUG: KASAN: double-free in slab_free mm/slub.c:3661 [inline] BUG: KASAN: double-free in __kmem_cache_free+0x71/0x110 mm/slub.c:3674 Free of addr ffff88806f410000 by task syz-executor131/3632 CPU: 0 PID: 3632 Comm: syz-executor131 Not tainted 6.1.0-rc7-syzkaller-00012-gca57f02295f1 #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/26/2022 Call Trace: <TASK> __dump_stack lib/dump_stack.c:88 [inline] dump_stack_lvl+0x1b1/0x28e lib/dump_stack.c:106 print_address_description+0x74/0x340 mm/kasan/report.c:284 print_report+0x107/0x1f0 mm/kasan/report.c:395 kasan_report_invalid_free+0xac/0xd0 mm/kasan/report.c:460 ____kasan_slab_free+0xfb/0x120 kasan_slab_free include/linux/kasan.h:177 [inline] slab_free_hook mm/slub.c:1724 [inline] slab_free_freelist_hook+0x12e/0x1a0 mm/slub.c:1750 slab_free mm/slub.c:3661 [inline] __kmem_cache_free+0x71/0x110 mm/slub.c:3674 diUnmount+0xef/0x100 fs/jfs/jfs_imap.c:195 jfs_umount+0x108/0x370 fs/jfs/jfs_umount.c:63 jfs_put_super+0x86/0x190 fs/jfs/super.c:194 generic_shutdown_super+0x130/0x310 fs/super.c:492 kill_block_super+0x79/0xd0 fs/super.c:1428 deactivate_locked_super+0xa7/0xf0 fs/super.c:332 cleanup_mnt+0x494/0x520 fs/namespace.c:1186 task_work_run+0x243/0x300 kernel/task_work.c:179 exit_task_work include/linux/task_work.h:38 [inline] do_exit+0x664/0x2070 kernel/exit.c:820 do_group_exit+0x1fd/0x2b0 kernel/exit.c:950 __do_sys_exit_group kernel/exit.c:961 [inline] __se_sys_exit_group kernel/exit.c:959 [inline] __x64_sys_exit_group+0x3b/0x40 kernel/exit.c:959 do_syscall_x64 arch/x86/entry/common.c:50 [inline] do_syscall_64+0x3d/0xb0 arch/x86/entry/common.c:80 entry_SYSCALL_64_after_hwframe+0x63/0xcd [...] JFS_IP(ipimap)->i_imap is not setting to NULL after free in diUnmount. If jfs_remount() free JFS_IP(ipimap)->i_imap but then failed at diMount(). JFS_IP(ipimap)->i_imap will be freed once again. Fix this problem by setting JFS_IP(ipimap)->i_imap to NULL after free.

Published
Date
2025-10-04
Updated
Date
2025-10-04
References
Description

In the Linux kernel, the following vulnerability has been resolved: scsi: qla2xxx: Fix deletion race condition System crash when using debug kernel due to link list corruption. The cause of the link list corruption is due to session deletion was allowed to queue up twice. Here's the internal trace that show the same port was allowed to double queue for deletion on different cpu. 20808683956 015 qla2xxx [0000:13:00.1]-e801:4: Scheduling sess ffff93ebf9306800 for deletion 50:06:0e:80:12:48:ff:50 fc4_type 1 20808683957 027 qla2xxx [0000:13:00.1]-e801:4: Scheduling sess ffff93ebf9306800 for deletion 50:06:0e:80:12:48:ff:50 fc4_type 1 Move the clearing/setting of deleted flag lock.

Published
Date
2025-10-04
Updated
Date
2025-10-04
References
Description

In the Linux kernel, the following vulnerability has been resolved: mm/ksm: fix race with VMA iteration and mm_struct teardown exit_mmap() will tear down the VMAs and maple tree with the mmap_lock held in write mode. Ensure that the maple tree is still valid by checking ksm_test_exit() after taking the mmap_lock in read mode, but before the for_each_vma() iterator dereferences a destroyed maple tree. Since the maple tree is destroyed, the flags telling lockdep to check an external lock has been cleared. Skip the for_each_vma() iterator to avoid dereferencing a maple tree without the external lock flag, which would create a lockdep warning.

Published
Date
2025-10-04
Updated
Date
2025-10-04
References