Comparison Overview

Punjab National Bank

VS

U.S. Bank

Punjab National Bank

Punjab National Bank, New Delhi, 110075, IN
Last Update: 2026-01-20
Between 750 and 799

“Fired by the spirit of nationalism and founded on the idea that Indians should have a national bank of their own, which would further the economic interest of the country, Punjab National Bank Ltd was the result of the efforts of far-sighted visionaries and patriots, among whom were persons like Lala Lajpat Rai, Mr. E C Jessawala, Babu Kali Prasono Roy, Lala Harkishan Lal and Sardar Dyal Singh Majithia. Incorporated under the Act VI of 1882, Indian Companies Act, the Bank commenced operations on April 12, 1895 from Lahore. Since inception, PNB has always been a "People's bank"​ serving millions of people throughout the country and also had the proud distinction of serving great national leaders like Sarvshri Jawahar Lal Nehru, Gobind Ballabh Pant, Lal Bahadur Shastri, Rafi Ahmed Kidwai, Smt. Indira Gandhi etc. amongst other who banked with us. Bank has spread its offerings and has grown as technology driven bank with products & services to meet the aspirations of every segment of customers. With more than 122 years of strong existence and a network of 6950 Domestic Branches, 10502 ATMs as on 31st March 2017, Punjab National Bank is serving more than 10 crore esteemed customers. PNB, being one of the largest Nationalised Bank, has continued to provide prudent and trustworthy banking services to its customers. The bank enjoys strong fundamentals, large franchise value and good brand image. With the mission of "Creating Value for all its customers, Investors and Employees for being the first choice for all stakeholders"​ its presence across India is a strong brand; “The name you can bank upon”. To download PNB One, click here: http://bit.ly/3WwQ4ig Share your feedback here: https://www.pnbindia.in/customers-survey.aspx

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

U.S. Bank

800 Nicollet Mall, Minneapolis, 55402, US
Last Update: 2026-01-17

At U.S. Bank, we help millions of clients achieve their goals with a balance of best-in-class technology and human expertise tailored to individual needs. As the fifth-largest commercial bank in the United States, we’ve built a reputation for strength and stability across a diversified mix of businesses, including commercial and institutional banking, business banking, payments, wealth management and consumer banking. We’ve been named one of the World’s Most Ethical Companies® by the Ethisphere Institute and the most admired superregional bank by Fortune. In addition to thousands of branches serving consumers, U.S. Bank offers a complete suite of products, services and strategic partnerships for business. Within our Wealth, Corporate, Commercial and Institutional Banking division, we serve more than half a million clients across the country and around the world, ranging from wealthy individuals and families to the largest corporations, including 90% of Fortune 1000 companies. We’re also consistently recognized as a great place to work. We’re shaping our company culture with intention, focused on creating a workplace where it’s safe to speak up, share ideas and try new things. We’re proud to be recognized as a “Best for Vets” employer by the Military Times and included on Fair360’s (formerly DiversityInc.) list of Top 50 Companies for Diversity. U.S. Bank, NA. Member FDIC. Equal Housing Lender.

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

Compliance Badges Comparison

Security & Compliance Standards Overview

https://images.rankiteo.com/companyimages/pnbindia.jpeg
Punjab National 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/us-bank.jpeg
U.S. 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
Compliance Summary
Punjab National Bank
100%
Compliance Rate
0/4 Standards Verified
U.S. Bank
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Banking Industry Average (This Year)

No incidents recorded for Punjab National Bank in 2026.

Incidents vs Banking Industry Average (This Year)

No incidents recorded for U.S. Bank in 2026.

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

Punjab National Bank cyber incidents detection timeline including parent company and subsidiaries

Incident History — U.S. Bank (X = Date, Y = Severity)

U.S. Bank cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/pnbindia.jpeg
Punjab National Bank
Incidents

Date Detected: 02/2018
Type:Data Leak
Motivation: Financial Gain
Blog: Blog
https://images.rankiteo.com/companyimages/us-bank.jpeg
U.S. Bank
Incidents

Date Detected: 9/2022
Type:Breach
Attack Vector: Inadvertent sharing of a file by a vendor
Blog: Blog

Date Detected: 3/2021
Type:Cyber Attack
Attack Vector: Credential Stuffing
Blog: Blog

Date Detected: 7/2020
Type:Breach
Attack Vector: Physical Theft
Blog: Blog

FAQ

U.S. Bank company demonstrates a stronger AI Cybersecurity Score compared to Punjab National Bank company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

U.S. Bank company has faced a higher number of disclosed cyber incidents historically compared to Punjab National Bank company.

In the current year, U.S. Bank company and Punjab National Bank company have not reported any cyber incidents.

Neither U.S. Bank company nor Punjab National Bank company has reported experiencing a ransomware attack publicly.

U.S. Bank company has disclosed at least one data breach, while Punjab National Bank company has not reported such incidents publicly.

U.S. Bank company has reported targeted cyberattacks, while Punjab National Bank company has not reported such incidents publicly.

Neither Punjab National Bank company nor U.S. Bank company has reported experiencing or disclosing vulnerabilities publicly.

Neither Punjab National Bank nor U.S. Bank holds any compliance certifications.

Neither company holds any compliance certifications.

U.S. Bank company has more subsidiaries worldwide compared to Punjab National Bank company.

U.S. Bank company employs more people globally than Punjab National Bank company, reflecting its scale as a Banking.

Neither Punjab National Bank nor U.S. Bank holds SOC 2 Type 1 certification.

Neither Punjab National Bank nor U.S. Bank holds SOC 2 Type 2 certification.

Neither Punjab National Bank nor U.S. Bank holds ISO 27001 certification.

Neither Punjab National Bank nor U.S. Bank holds PCI DSS certification.

Neither Punjab National Bank nor U.S. Bank holds HIPAA certification.

Neither Punjab National Bank nor U.S. Bank holds GDPR certification.

Latest Global CVEs (Not Company-Specific)

Description

SummaryA command injection vulnerability (CWE-78) has been found to exist in the `wrangler pages deploy` command. The issue occurs because the `--commit-hash` parameter is passed directly to a shell command without proper validation or sanitization, allowing an attacker with control of `--commit-hash` to execute arbitrary commands on the system running Wrangler. Root causeThe commitHash variable, derived from user input via the --commit-hash CLI argument, is interpolated directly into a shell command using template literals (e.g.,  execSync(`git show -s --format=%B ${commitHash}`)). Shell metacharacters are interpreted by the shell, enabling command execution. ImpactThis vulnerability is generally hard to exploit, as it requires --commit-hash to be attacker controlled. The vulnerability primarily affects CI/CD environments where `wrangler pages deploy` is used in automated pipelines and the --commit-hash parameter is populated from external, potentially untrusted sources. An attacker could exploit this to: * Run any shell command. * Exfiltrate environment variables. * Compromise the CI runner to install backdoors or modify build artifacts. Credits Disclosed responsibly by kny4hacker. Mitigation * Wrangler v4 users are requested to upgrade to Wrangler v4.59.1 or higher. * Wrangler v3 users are requested to upgrade to Wrangler v3.114.17 or higher. * Users on Wrangler v2 (EOL) should upgrade to a supported major version.

Risk Information
cvss4
Base: 7.7
Severity: LOW
CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:H/SC:L/SI:L/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

Vulnerability in the Oracle VM VirtualBox product of Oracle Virtualization (component: Core). Supported versions that are affected are 7.1.14 and 7.2.4. Easily exploitable vulnerability allows high privileged attacker with logon to the infrastructure where Oracle VM VirtualBox executes to compromise Oracle VM VirtualBox. While the vulnerability is in Oracle VM VirtualBox, attacks may significantly impact additional products (scope change). Successful attacks of this vulnerability can result in takeover of Oracle VM VirtualBox. CVSS 3.1 Base Score 8.2 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H).

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

Vulnerability in the Oracle VM VirtualBox product of Oracle Virtualization (component: Core). Supported versions that are affected are 7.1.14 and 7.2.4. Easily exploitable vulnerability allows high privileged attacker with logon to the infrastructure where Oracle VM VirtualBox executes to compromise Oracle VM VirtualBox. While the vulnerability is in Oracle VM VirtualBox, attacks may significantly impact additional products (scope change). Successful attacks of this vulnerability can result in unauthorized creation, deletion or modification access to critical data or all Oracle VM VirtualBox accessible data as well as unauthorized access to critical data or complete access to all Oracle VM VirtualBox accessible data and unauthorized ability to cause a partial denial of service (partial DOS) of Oracle VM VirtualBox. CVSS 3.1 Base Score 8.1 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:L).

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

Vulnerability in the Oracle VM VirtualBox product of Oracle Virtualization (component: Core). Supported versions that are affected are 7.1.14 and 7.2.4. Easily exploitable vulnerability allows high privileged attacker with logon to the infrastructure where Oracle VM VirtualBox executes to compromise Oracle VM VirtualBox. While the vulnerability is in Oracle VM VirtualBox, attacks may significantly impact additional products (scope change). Successful attacks of this vulnerability can result in takeover of Oracle VM VirtualBox. CVSS 3.1 Base Score 8.2 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H).

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

Vulnerability in the Oracle VM VirtualBox product of Oracle Virtualization (component: Core). Supported versions that are affected are 7.1.14 and 7.2.4. Easily exploitable vulnerability allows high privileged attacker with logon to the infrastructure where Oracle VM VirtualBox executes to compromise Oracle VM VirtualBox. While the vulnerability is in Oracle VM VirtualBox, attacks may significantly impact additional products (scope change). Successful attacks of this vulnerability can result in takeover of Oracle VM VirtualBox. CVSS 3.1 Base Score 8.2 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H).

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