Comparison Overview

Nordea

VS

Punjab National Bank

Nordea

Aleksanterinkatu 36 B, Helsinki, FI
Last Update: 2026-01-18
View Profile
Between 800 and 849
http://www.nordea.com

We are a universal bank with a 200-year history of supporting and growing the Nordic economies – enabling dreams and aspirations for a greater good. Every day, we work to support our customers’ financial development, delivering best-in-class omnichannel customer experiences and driving sustainable change. We are a full-service universal bank and the third largest corporation in the Nordic region and one of the top 10 financial services companies in Europe based on market capitalisation. We are present in 17 countries, including our four Nordic home markets which together constitute the 10th largest economy in the world. As demand for digital services increases, we're continuously working to become your future digital bank by improving the products and services we offer, such as new online banking platforms, mobile payments and analytics tools, to name a few. The Nordea share is listed on the Nasdaq Helsinki, Nasdaq Copenhagen and Nasdaq Stockholm exchanges. Read more about us at nordea.com. We value your opinions and welcome your comments and questions on our posts here on LinkedIn. Please note that we reply mainly during business hours, Monday-Friday. Please keep a polite, professional and constructive tone. We remove comments containing crude language and derogatory views of our staff and other people who comment on our posts. We do not allow content that is unrelated to the subject, and we remove discriminatory and racist comments as well as spam and advertising.

NAICS: 52211
NAICS Definition: Commercial Banking
Employees: 29,591
Subsidiaries: 1
12-month incidents
0
Known data breaches
0
Attack type number
0
View Profile

Punjab National Bank

Punjab National Bank, New Delhi, 110075, IN
Last Update: 2026-01-20
Between 750 and 799
http://pnb.bank.in

“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

Compliance Badges Comparison

Security & Compliance Standards Overview

https://images.rankiteo.com/companyimages/nordea.jpeg
Nordea
—
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/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
Compliance Summary
Nordea
100%
Compliance Rate
0/4 Standards Verified
Punjab National Bank
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Banking Industry Average (This Year)

No incidents recorded for Nordea in 2026.

Incidents vs Banking Industry Average (This Year)

No incidents recorded for Punjab National Bank in 2026.

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

Nordea cyber incidents detection timeline including parent company and subsidiaries

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

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

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/nordea.jpeg
Nordea
Incidents

No Incident

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

Date Detected: 02/2018
Type:Data Leak
Motivation: Financial Gain
Blog: Blog

FAQ

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

Punjab National Bank company has historically faced a number of disclosed cyber incidents, whereas Nordea company has not reported any.

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

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

Neither Punjab National Bank company nor Nordea company has reported experiencing a data breach publicly.

Neither Punjab National Bank company nor Nordea company has reported experiencing targeted cyberattacks publicly.

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

Neither Nordea nor Punjab National Bank holds any compliance certifications.

Neither company holds any compliance certifications.

Nordea company has more subsidiaries worldwide compared to Punjab National Bank company.

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

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

Neither Nordea nor Punjab National Bank holds SOC 2 Type 2 certification.

Neither Nordea nor Punjab National Bank holds ISO 27001 certification.

Neither Nordea nor Punjab National Bank holds PCI DSS certification.

Neither Nordea nor Punjab National Bank holds HIPAA certification.

Neither Nordea nor Punjab National 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.

Published
Date
2026-01-20
Updated
Date
2026-01-20
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
References
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).

Published
Date
2026-01-20
Updated
Date
2026-01-20
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
References
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).

Published
Date
2026-01-20
Updated
Date
2026-01-20
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
References
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).

Published
Date
2026-01-20
Updated
Date
2026-01-20
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
References
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).

Published
Date
2026-01-20
Updated
Date
2026-01-20
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
References