Comparison Overview

HBL

VS

PT. BANK NEGARA INDONESIA (Persero) Tbk.

HBL

HBL Plaza, I I Chundigar Rd., Karachi, PK
Last Update: 2025-11-27
Between 750 and 799

HBL, Pakistan’s leading Bank, was the first commercial Bank to be established in Pakistan in 1947. Over the years, HBL has grown its branch network and maintained its position as the largest private sector Bank in Pakistan with over 1,728+ branches and 2,300+ ATMs globally, serving 37million+ clients worldwide. HBL will never ask for customer's personal data on public platforms. Please avoid sharing such data via social media.

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

PT. BANK NEGARA INDONESIA (Persero) Tbk.

Jl. Jendral Sudirman Kav. 1, Jakarta, ID, 10220
Last Update: 2025-11-27
Between 750 and 799

Since its establishment in 1946, BNI has been part of the dynamic of national development in Indonesia. Now BNI has grown and developed into a solid national bank with a sustainable financial performance. ‘Serving the Country, Pride of the Nation”, BNI continues to increase its contribution for the progress of the nation and country, today and in the future. At the end of 2024, BNI employs more than 27,000 employees. To serve its customers, BNI leverages its wide ranging service network, comprising of 1,780 domestic outlets and 10 overseas branches in Singapore, Hong Kong, Tokyo, New York, London, Seoul, Osaka, Amsterdam & Sydney. With 13,388 proprietary ATMs, 208,981 Branchless Banking agents (BNI Agen46). BNI always strives to be the bank of choice by providing excellent service and value added solutions to all of its customers. BNI offers integrated financial services to its customers, supported by its subsidiaries: BNI Multi Finance, BNI Securities, BNI Life Insurance, BNI Remittance, BNI Asset Management, hiBank, and BNI Ventures

NAICS: 52211
NAICS Definition: Commercial Banking
Employees: 29,238
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/hblofficial.jpeg
HBL
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/pt-bank-negara-indonesia-persero-tbk-.jpeg
PT. BANK NEGARA INDONESIA (Persero) Tbk.
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
HBL
100%
Compliance Rate
0/4 Standards Verified
PT. BANK NEGARA INDONESIA (Persero) Tbk.
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Banking Industry Average (This Year)

No incidents recorded for HBL in 2025.

Incidents vs Banking Industry Average (This Year)

No incidents recorded for PT. BANK NEGARA INDONESIA (Persero) Tbk. in 2025.

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

HBL cyber incidents detection timeline including parent company and subsidiaries

Incident History — PT. BANK NEGARA INDONESIA (Persero) Tbk. (X = Date, Y = Severity)

PT. BANK NEGARA INDONESIA (Persero) Tbk. cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/hblofficial.jpeg
HBL
Incidents

Date Detected: 12/2017
Type:Breach
Attack Vector: ATM Skimming
Motivation: Financial Gain
Blog: Blog
https://images.rankiteo.com/companyimages/pt-bank-negara-indonesia-persero-tbk-.jpeg
PT. BANK NEGARA INDONESIA (Persero) Tbk.
Incidents

No Incident

FAQ

PT. BANK NEGARA INDONESIA (Persero) Tbk. company demonstrates a stronger AI Cybersecurity Score compared to HBL company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

HBL company has historically faced a number of disclosed cyber incidents, whereas PT. BANK NEGARA INDONESIA (Persero) Tbk. company has not reported any.

In the current year, PT. BANK NEGARA INDONESIA (Persero) Tbk. company and HBL company have not reported any cyber incidents.

Neither PT. BANK NEGARA INDONESIA (Persero) Tbk. company nor HBL company has reported experiencing a ransomware attack publicly.

HBL company has disclosed at least one data breach, while the other PT. BANK NEGARA INDONESIA (Persero) Tbk. company has not reported such incidents publicly.

Neither PT. BANK NEGARA INDONESIA (Persero) Tbk. company nor HBL company has reported experiencing targeted cyberattacks publicly.

Neither HBL company nor PT. BANK NEGARA INDONESIA (Persero) Tbk. company has reported experiencing or disclosing vulnerabilities publicly.

Neither HBL nor PT. BANK NEGARA INDONESIA (Persero) Tbk. holds any compliance certifications.

Neither company holds any compliance certifications.

Neither HBL company nor PT. BANK NEGARA INDONESIA (Persero) Tbk. company has publicly disclosed detailed information about the number of their subsidiaries.

PT. BANK NEGARA INDONESIA (Persero) Tbk. company employs more people globally than HBL company, reflecting its scale as a Banking.

Neither HBL nor PT. BANK NEGARA INDONESIA (Persero) Tbk. holds SOC 2 Type 1 certification.

Neither HBL nor PT. BANK NEGARA INDONESIA (Persero) Tbk. holds SOC 2 Type 2 certification.

Neither HBL nor PT. BANK NEGARA INDONESIA (Persero) Tbk. holds ISO 27001 certification.

Neither HBL nor PT. BANK NEGARA INDONESIA (Persero) Tbk. holds PCI DSS certification.

Neither HBL nor PT. BANK NEGARA INDONESIA (Persero) Tbk. holds HIPAA certification.

Neither HBL nor PT. BANK NEGARA INDONESIA (Persero) Tbk. 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