Comparison Overview

Comerica Bank

VS

HBL

Comerica Bank

1717 Main Street, Dallas, TX, US, 75201
Last Update: 2025-12-09
Between 750 and 799

Comerica Incorporated (NYSE: CMA) is a financial services company headquartered in Dallas, Texas, strategically aligned by the Business Bank, the Retail Bank, and Wealth Management. The Business Bank provides companies of all sizes with an array of credit and non-credit financial products and services. The Retail Bank delivers personalized financial products and services to consumers. Wealth Management serves the needs of high net worth clients and institutions. Comerica’s approximately 8,000 colleagues focus on relationships, and helping people and businesses be successful. Comerica operates in seven of the 10 largest U.S. cities, with more than 430 banking centers in its primary markets of Texas, Arizona, California, Florida and Michigan. Select businesses operate in several other states, as well as in Canada and Mexico. Comerica is among the 25 largest U.S. banking companies. Visit Comerica's Facebook page at facebook.com/Comerica or on Twitter at @ComericaBank for more information on how Comerica is making a positive difference in the communities it serves. To learn more about Comerica’s products, services and career opportunities, visit Comerica.com.

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

HBL

HBL Plaza, I I Chundigar Rd., Karachi, PK
Last Update: 2025-12-09
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

Compliance Badges Comparison

Security & Compliance Standards Overview

https://images.rankiteo.com/companyimages/comerica-bank.jpeg
Comerica Bank
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/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
Compliance Summary
Comerica Bank
100%
Compliance Rate
0/4 Standards Verified
HBL
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Banking Industry Average (This Year)

No incidents recorded for Comerica Bank in 2025.

Incidents vs Banking Industry Average (This Year)

No incidents recorded for HBL in 2025.

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

Comerica Bank cyber incidents detection timeline including parent company and subsidiaries

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

HBL cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/comerica-bank.jpeg
Comerica Bank
Incidents

No Incident

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

Date Detected: 12/2017
Type:Breach
Attack Vector: ATM Skimming
Motivation: Financial Gain
Blog: Blog

FAQ

Comerica Bank 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 Comerica Bank company has not reported any.

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

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

HBL company has disclosed at least one data breach, while Comerica Bank company has not reported such incidents publicly.

Neither HBL company nor Comerica Bank company has reported experiencing targeted cyberattacks publicly.

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

Neither Comerica Bank nor HBL holds any compliance certifications.

Neither company holds any compliance certifications.

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

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

Neither Comerica Bank nor HBL holds SOC 2 Type 1 certification.

Neither Comerica Bank nor HBL holds SOC 2 Type 2 certification.

Neither Comerica Bank nor HBL holds ISO 27001 certification.

Neither Comerica Bank nor HBL holds PCI DSS certification.

Neither Comerica Bank nor HBL holds HIPAA certification.

Neither Comerica Bank nor HBL holds GDPR certification.

Latest Global CVEs (Not Company-Specific)

Description

NXLog Agent before 6.11 can load a file specified by the OPENSSL_CONF environment variable.

Risk Information
cvss3
Base: 8.1
Severity: HIGH
CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H
Description

uriparser through 0.9.9 allows unbounded recursion and stack consumption, as demonstrated by ParseMustBeSegmentNzNc with large input containing many commas.

Risk Information
cvss3
Base: 2.9
Severity: HIGH
CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:L
Description

A vulnerability was detected in Mayan EDMS up to 4.10.1. The affected element is an unknown function of the file /authentication/. The manipulation results in cross site scripting. The attack may be performed from remote. The exploit is now public and may be used. Upgrading to version 4.10.2 is sufficient to fix this issue. You should upgrade the affected component. The vendor confirms that this is "[f]ixed in version 4.10.2". Furthermore, that "[b]ackports for older versions in process and will be out as soon as their respective CI pipelines complete."

Risk Information
cvss2
Base: 5.0
Severity: LOW
AV:N/AC:L/Au:N/C:N/I:P/A:N
cvss3
Base: 4.3
Severity: LOW
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N
cvss4
Base: 5.3
Severity: LOW
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:L/VA:N/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
Description

MJML through 4.18.0 allows mj-include directory traversal to test file existence and (in the type="css" case) read files. NOTE: this issue exists because of an incomplete fix for CVE-2020-12827.

Risk Information
cvss3
Base: 4.5
Severity: HIGH
CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:C/C:L/I:N/A:L
Description

A half-blind Server Side Request Forgery (SSRF) vulnerability exists in kube-controller-manager when using the in-tree Portworx StorageClass. This vulnerability allows authorized users to leak arbitrary information from unprotected endpoints in the control plane’s host network (including link-local or loopback services).

Risk Information
cvss3
Base: 5.8
Severity: HIGH
CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:H/I:N/A:N