Comparison Overview

Danske Bank

VS

Bajaj Finserv

Danske Bank

Bernstorffsgade 40, Copenhagen, Capital Region of Denmark, DK, 1577
Last Update: 2026-01-17
View Profile
Between 800 and 849
http://www.danskebank.com

Danske Bank – A driver of growth and development For more than a 150 years, Danske Bank has strived to be a driver of growth and development in society. We have developed in tandem with the societies we are part of, and our advisory services, expertise and financial solutions have helped individuals, families, businesses and organisations to realise their ambitions and potential. With long-term sustainable development as our ambition, we will continue to work every day to be the best possible bank, for the benefit of our customers, employees, shareholders and the societies we are part of. Follow us for relevant content and insights You will receive the latest news, insights and information that can inspire and help you with your everyday financial needs. On our company page, you can also read more about life as an employee at Danske Bank and be sure to check our current job openings if you are interested in joining our international community of 22,000 people and help us build an even more innovative, agile and truly customer-centric culture.

NAICS: 52
NAICS Definition: Finance and Insurance
Employees: 18,488
Subsidiaries: 4
12-month incidents
0
Known data breaches
0
Attack type number
0
View Profile

Bajaj Finserv

Bajaj Finserv House, Sakore Nagar Rd, Viman Nagar, Pune, 411014, IN
Last Update: 2026-01-18
Between 800 and 849
http://www.bajajfinserv.in

Founded in April 2007, Bajaj Finserv is the financial arm of the Bajaj group. We believe in a simple philosophy to never settle for good and go for great. This reflects in our extensive product portfolio that spans across 3 broad categories- lending, insurance and wealth advisory. With 24 products spread across 12 product lines, we're one of the fastest growing and most diversified NBFCs in India. Our footprint spans the length and breadth of India.

NAICS: 52
NAICS Definition: Finance and Insurance
Employees: 68,272
Subsidiaries: 1
12-month incidents
0
Known data breaches
0
Attack type number
0

Compliance Badges Comparison

Security & Compliance Standards Overview

https://images.rankiteo.com/companyimages/danskebank.jpeg
Danske 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/bajaj-finserv-lending.jpeg
Bajaj Finserv
—
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
Danske Bank
100%
Compliance Rate
0/4 Standards Verified
Bajaj Finserv
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Financial Services Industry Average (This Year)

No incidents recorded for Danske Bank in 2026.

Incidents vs Financial Services Industry Average (This Year)

No incidents recorded for Bajaj Finserv in 2026.

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

Danske Bank cyber incidents detection timeline including parent company and subsidiaries

Incident History — Bajaj Finserv (X = Date, Y = Severity)

Bajaj Finserv cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/danskebank.jpeg
Danske Bank
Incidents

No Incident

https://images.rankiteo.com/companyimages/bajaj-finserv-lending.jpeg
Bajaj Finserv
Incidents

No Incident

FAQ

Bajaj Finserv company demonstrates a stronger AI Cybersecurity Score compared to Danske Bank company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Historically, Bajaj Finserv company has disclosed a higher number of cyber incidents compared to Danske Bank company.

In the current year, Bajaj Finserv company and Danske Bank company have not reported any cyber incidents.

Neither Bajaj Finserv company nor Danske Bank company has reported experiencing a ransomware attack publicly.

Neither Bajaj Finserv company nor Danske Bank company has reported experiencing a data breach publicly.

Neither Bajaj Finserv company nor Danske Bank company has reported experiencing targeted cyberattacks publicly.

Neither Danske Bank company nor Bajaj Finserv company has reported experiencing or disclosing vulnerabilities publicly.

Neither Danske Bank nor Bajaj Finserv holds any compliance certifications.

Neither company holds any compliance certifications.

Danske Bank company has more subsidiaries worldwide compared to Bajaj Finserv company.

Bajaj Finserv company employs more people globally than Danske Bank company, reflecting its scale as a Financial Services.

Neither Danske Bank nor Bajaj Finserv holds SOC 2 Type 1 certification.

Neither Danske Bank nor Bajaj Finserv holds SOC 2 Type 2 certification.

Neither Danske Bank nor Bajaj Finserv holds ISO 27001 certification.

Neither Danske Bank nor Bajaj Finserv holds PCI DSS certification.

Neither Danske Bank nor Bajaj Finserv holds HIPAA certification.

Neither Danske Bank nor Bajaj Finserv 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