Comparison Overview

Bajaj Auto Ltd

VS

Dräger

Bajaj Auto Ltd

Bajaj Auto Ltd, Pune, Maharashtra, 411035, IN
Last Update: 2025-11-21
Between 800 and 849

A journey that began 75 years ago in a corner of India and has since traversed the world over. Uniting people from across countries, cultures, and customs over the years with a multitude of different dreams, there's power in an idea. An idea that gave rise to brands that stood the test of time, with partnerships it inspired, and the people who made it all happen. One idea that sparked a legacy - this is the story of Bajaj Auto. “Do what you think is best, but be the best in what you do.” - Kamalnayan Bajaj These words embody the spirit of Bajaj Auto. From 1945 to today, from “Hamara Bajaj” to “The World’s Favourite Indian”- the most loved motorcycle brand in almost 80 countries, Bajaj Auto carries its rich legacy and unconventional thinking, with a penchant for staunch differentiation. This philosophy has helped us be No.1 or No.2 in over 20 countries with industry-leading EBITDA of ~20%. Some statistics that reflect our strength: • A Zero Debt 5.5 Billion Dollar Company • World’s largest three-wheeler and third-largest two-wheeler manufacturer • India’s Number 1 motorcycle exporter – 2 out of every 3 motorcycles exported are Bajaj • The largest exporter of Branded Goods – exporting over half of India’s two and three-wheelers • Over 33% of revenue from International markets with 15+ million motorcycles sold With powerful brands, our spectrum ranges from Boxer in Africa to KTM in Europe, from Rouser in Latin America to Pulsar in India, our versatility is evident. International alliances with KTM, Husqvarna, and Triumph have ensured that our horizons are broadened. A pioneer in motorcycle technology, our R&D is world-class with talent from all corners of the globe with TPM being the prime mover of productivity for the last 25+ years. From lean manufacturing, we have now moved to lean engineering & lean marketing, which has led to globally competitive fixed costs. With ever-expanding plans to win over the world, the sun truly never sets on a Bajaj Motorcycle.

NAICS: 30
NAICS Definition: Manufacturing
Employees: 18,175
Subsidiaries: 2
12-month incidents
0
Known data breaches
0
Attack type number
0

Dräger

Moislinger Allee 53-55, Lübeck, 23552, DE
Last Update: 2025-11-21
Between 750 and 799

Dräger is an international leader in the fields of medical and safety technology. The family-owned company was founded in Lübeck, Germany, in 1889. The company’s long-term success is based on the four key strengths of its value-driven culture: customer intimacy, professional employees, continuous innovation and a commitment to outstanding quality. Dräger offers its customers anaesthesia workstations, medical ventilation, patient monitoring as well as neonatal care for premature babies and newborns. With ceiling supply units, IT solutions for the OR, and gas management systems the company is at the customer’s side throughout the entire hospital. Emergency response services, law and regulatory enforcement and the industry trust in Dräger’s integrated hazard management, in particular for personal protection and plant safety. This includes: respiratory protection equipment, stationary and portable gas detection systems, professional diving equipment and systems, as well as alcohol and drug impairment detection. In collaboration with its customers Dräger develops customized solutions, such as entire fire training systems, training concepts and workshops. Dräger has more than 13.700 employees worldwide and is currently present in more than 190 countries. The company has sales and service subsidiaries in over 40 countries. Its development and production facilities are based in Germany, Great Britain, Sweden, South Africa, the USA, Brazil, the Czech Republic and China. http://t4.life/dataprotection Drägerwerk AG & Co. KGaA Board of Managing Directors: Stefan Dräger (Chairman), Rainer Klug, Gert-Hartwig Lescow, Dr. Reiner Piske, Anton Schrofner Company registered at Lübeck Local Court Register of Companies Number: HRB 7903 HL Turnover tax identification number as per § 27a Turnover Tax Law: DE 135082211 General partner: Drägerwerk Verwaltungs AG Company registered at Lübeck Local Court Register of Companies Number: HRB 7395 HL

NAICS: 30
NAICS Definition: Manufacturing
Employees: 10,890
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-auto-ltd.jpeg
Bajaj Auto Ltd
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/draeger.jpeg
Dräger
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 Auto Ltd
100%
Compliance Rate
0/4 Standards Verified
Dräger
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Manufacturing Industry Average (This Year)

No incidents recorded for Bajaj Auto Ltd in 2025.

Incidents vs Manufacturing Industry Average (This Year)

No incidents recorded for Dräger in 2025.

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

Bajaj Auto Ltd cyber incidents detection timeline including parent company and subsidiaries

Incident History — Dräger (X = Date, Y = Severity)

Dräger cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/bajaj-auto-ltd.jpeg
Bajaj Auto Ltd
Incidents

No Incident

https://images.rankiteo.com/companyimages/draeger.jpeg
Dräger
Incidents

No Incident

FAQ

Bajaj Auto Ltd company demonstrates a stronger AI Cybersecurity Score compared to Dräger company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Historically, Dräger company has disclosed a higher number of cyber incidents compared to Bajaj Auto Ltd company.

In the current year, Dräger company and Bajaj Auto Ltd company have not reported any cyber incidents.

Neither Dräger company nor Bajaj Auto Ltd company has reported experiencing a ransomware attack publicly.

Neither Dräger company nor Bajaj Auto Ltd company has reported experiencing a data breach publicly.

Neither Dräger company nor Bajaj Auto Ltd company has reported experiencing targeted cyberattacks publicly.

Neither Bajaj Auto Ltd company nor Dräger company has reported experiencing or disclosing vulnerabilities publicly.

Neither Bajaj Auto Ltd nor Dräger holds any compliance certifications.

Neither company holds any compliance certifications.

Bajaj Auto Ltd company has more subsidiaries worldwide compared to Dräger company.

Bajaj Auto Ltd company employs more people globally than Dräger company, reflecting its scale as a Manufacturing.

Neither Bajaj Auto Ltd nor Dräger holds SOC 2 Type 1 certification.

Neither Bajaj Auto Ltd nor Dräger holds SOC 2 Type 2 certification.

Neither Bajaj Auto Ltd nor Dräger holds ISO 27001 certification.

Neither Bajaj Auto Ltd nor Dräger holds PCI DSS certification.

Neither Bajaj Auto Ltd nor Dräger holds HIPAA certification.

Neither Bajaj Auto Ltd nor Dräger holds GDPR certification.

Latest Global CVEs (Not Company-Specific)

Description

Angular is a development platform for building mobile and desktop web applications using TypeScript/JavaScript and other languages. Prior to versions 19.2.16, 20.3.14, and 21.0.1, there is a XSRF token leakage via protocol-relative URLs in angular HTTP clients. The vulnerability is a Credential Leak by App Logic that leads to the unauthorized disclosure of the Cross-Site Request Forgery (XSRF) token to an attacker-controlled domain. Angular's HttpClient has a built-in XSRF protection mechanism that works by checking if a request URL starts with a protocol (http:// or https://) to determine if it is cross-origin. If the URL starts with protocol-relative URL (//), it is incorrectly treated as a same-origin request, and the XSRF token is automatically added to the X-XSRF-TOKEN header. This issue has been patched in versions 19.2.16, 20.3.14, and 21.0.1. A workaround for this issue involves avoiding using protocol-relative URLs (URLs starting with //) in HttpClient requests. All backend communication URLs should be hardcoded as relative paths (starting with a single /) or fully qualified, trusted absolute URLs.

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

Forge (also called `node-forge`) is a native implementation of Transport Layer Security in JavaScript. An Uncontrolled Recursion vulnerability in node-forge versions 1.3.1 and below enables remote, unauthenticated attackers to craft deep ASN.1 structures that trigger unbounded recursive parsing. This leads to a Denial-of-Service (DoS) via stack exhaustion when parsing untrusted DER inputs. This issue has been patched in version 1.3.2.

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

Forge (also called `node-forge`) is a native implementation of Transport Layer Security in JavaScript. An Integer Overflow vulnerability in node-forge versions 1.3.1 and below enables remote, unauthenticated attackers to craft ASN.1 structures containing OIDs with oversized arcs. These arcs may be decoded as smaller, trusted OIDs due to 32-bit bitwise truncation, enabling the bypass of downstream OID-based security decisions. This issue has been patched in version 1.3.2.

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

Suricata is a network IDS, IPS and NSM engine developed by the OISF (Open Information Security Foundation) and the Suricata community. Prior to versions 7.0.13 and 8.0.2, working with large buffers in Lua scripts can lead to a stack overflow. Users of Lua rules and output scripts may be affected when working with large buffers. This includes a rule passing a large buffer to a Lua script. This issue has been patched in versions 7.0.13 and 8.0.2. A workaround for this issue involves disabling Lua rules and output scripts, or making sure limits, such as stream.depth.reassembly and HTTP response body limits (response-body-limit), are set to less than half the stack size.

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

Suricata is a network IDS, IPS and NSM engine developed by the OISF (Open Information Security Foundation) and the Suricata community. In versions from 8.0.0 to before 8.0.2, a NULL dereference can occur when the entropy keyword is used in conjunction with base64_data. This issue has been patched in version 8.0.2. A workaround involves disabling rules that use entropy in conjunction with base64_data.

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