Comparison Overview

Bajaj Finserv

VS

PING AN

Bajaj Finserv

Bajaj Finserv House, Sakore Nagar Rd, Viman Nagar, Pune, Maharashtra, IN, 411014
Last Update: 2025-12-09
Between 800 and 849

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: 64,942
Subsidiaries: 1
12-month incidents
0
Known data breaches
0
Attack type number
0

PING AN

No. 5033 Yitian Road, Futian District, Shenzhen, Guangdong, 518046, CN
Last Update: 2025-12-09
Between 800 and 849

This is the official Company Page of Ping An Insurance (Group) Company of China, Ltd. (HKEx: 2318; SSE: 601318; ADR: PNGAY). Ping An strives to become a world leading technology-powered financial services group. We believe the way people receive financial services and healthcare in the future will be through intelligent ecosystems enabled by technology. With over 220 million retail customers and nearly 611 million Internet users, Ping An is one of the largest financial services companies in the world. Technology has enabled us to bring changes to the landscape of retail finance and healthcare in China. Supported by the Group’s strong core financials, our continued investment in fintech and healthtech resulted in increasing revenue contributions from our tech units as well as several unicorns. Ping An ranked 6th in the Forbes Global 2000 list and 16th in the Fortune Global 500 list in 2021. Follow us for latest news, events and job opportunities.

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

Compliance Badges Comparison

Security & Compliance Standards Overview

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
https://images.rankiteo.com/companyimages/ping-an.jpeg
PING AN
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
Bajaj Finserv
100%
Compliance Rate
0/4 Standards Verified
PING AN
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Financial Services Industry Average (This Year)

No incidents recorded for Bajaj Finserv in 2025.

Incidents vs Financial Services Industry Average (This Year)

No incidents recorded for PING AN in 2025.

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

Bajaj Finserv cyber incidents detection timeline including parent company and subsidiaries

Incident History — PING AN (X = Date, Y = Severity)

PING AN cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

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

No Incident

https://images.rankiteo.com/companyimages/ping-an.jpeg
PING AN
Incidents

No Incident

FAQ

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

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

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

Neither PING AN company nor Bajaj Finserv company has reported experiencing a ransomware attack publicly.

Neither PING AN company nor Bajaj Finserv company has reported experiencing a data breach publicly.

Neither PING AN company nor Bajaj Finserv company has reported experiencing targeted cyberattacks publicly.

Neither Bajaj Finserv company nor PING AN company has reported experiencing or disclosing vulnerabilities publicly.

Neither Bajaj Finserv nor PING AN holds any compliance certifications.

Neither company holds any compliance certifications.

Bajaj Finserv company has more subsidiaries worldwide compared to PING AN company.

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

Neither Bajaj Finserv nor PING AN holds SOC 2 Type 1 certification.

Neither Bajaj Finserv nor PING AN holds SOC 2 Type 2 certification.

Neither Bajaj Finserv nor PING AN holds ISO 27001 certification.

Neither Bajaj Finserv nor PING AN holds PCI DSS certification.

Neither Bajaj Finserv nor PING AN holds HIPAA certification.

Neither Bajaj Finserv nor PING AN 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