Comparison Overview

HBL

VS

KeyBank

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

KeyBank

127 Public Square, Cleveland , Ohio, US, 44114
Last Update: 2025-11-23
Between 0 and 549

At KeyBank we’ve made a promise to our clients that they will always have a champion in us. To deliver on our promise, we’re committed to building a team of engaged employees who do the right thing for our clients and shareholders, and help them achieve financial wellness each and every day. Headquartered in Cleveland, Ohio, KeyCorp is one of the nation’s largest financial services companies. Key Companies provide investment management, retail and commercial banking, consumer finance and investment banking products to individuals and companies throughout the United States and, for certain businesses, internationally. Follow along for business and industry insights, expert advice and more resources to help you achieve your financial goals. KeyCorp is an Equal Opportunity Employer committed to sustaining an inclusive culture. All qualified applicants will receive consideration for employment without regard to race, color, religion, sex, sexual orientation, gender identity, national origin, disability or veteran status. KeyBank is Member FDIC. Equal Housing Lender. Credit applications are subject to credit approval.

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

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/keybank.jpeg
KeyBank
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
KeyBank
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 KeyBank in 2025.

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

HBL cyber incidents detection timeline including parent company and subsidiaries

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

KeyBank 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/keybank.jpeg
KeyBank
Incidents

Date Detected: 12/2024
Type:Breach
Attack Vector: External System Breach (Hacking)
Blog: Blog

Date Detected: 5/2023
Type:Breach
Attack Vector: Unauthorized use of personal information
Blog: Blog

Date Detected: 5/2023
Type:Breach
Attack Vector: Insider Threat
Blog: Blog

FAQ

HBL company demonstrates a stronger AI Cybersecurity Score compared to KeyBank company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

KeyBank company has faced a higher number of disclosed cyber incidents historically compared to HBL company.

In the current year, KeyBank company and HBL company have not reported any cyber incidents.

Neither KeyBank company nor HBL company has reported experiencing a ransomware attack publicly.

Both KeyBank company and HBL company have disclosed experiencing at least one data breach.

Neither KeyBank company nor HBL company has reported experiencing targeted cyberattacks publicly.

Neither HBL company nor KeyBank company has reported experiencing or disclosing vulnerabilities publicly.

Neither HBL nor KeyBank holds any compliance certifications.

Neither company holds any compliance certifications.

Neither HBL company nor KeyBank company has publicly disclosed detailed information about the number of their subsidiaries.

HBL company employs more people globally than KeyBank company, reflecting its scale as a Banking.

Neither HBL nor KeyBank holds SOC 2 Type 1 certification.

Neither HBL nor KeyBank holds SOC 2 Type 2 certification.

Neither HBL nor KeyBank holds ISO 27001 certification.

Neither HBL nor KeyBank holds PCI DSS certification.

Neither HBL nor KeyBank holds HIPAA certification.

Neither HBL nor KeyBank 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