Comparison Overview

Eli Lilly and Company

VS

Zydus Group

Eli Lilly and Company

Lilly Corporate Center, Indianapolis, Indiana, US, 46285
Last Update: 2025-12-09
Between 800 and 849

We're a medicine company turning science into healing to make life better for people around the world. It all started nearly 150 years ago with a clear vision from founder Colonel Eli Lilly: "Take what you find here and make it better and better." Harnessing the power of biotechnology, chemistry and genetic medicine, our scientists are urgently advancing science to solve some of the world's most significant health challenges. General Information and Guidelines: When you engage with us on LinkedIn, you're agreeing to these Community Guidelines: https://e.lilly/guidelines. If you have questions about a Lilly medicine, contact The Lilly Answers Center at 1-800-Lilly-Rx (1-800-545-5979) Monday through Friday, excluding company holidays.

NAICS: 3254
NAICS Definition: Pharmaceutical and Medicine Manufacturing
Employees: 49,376
Subsidiaries: 16
12-month incidents
0
Known data breaches
0
Attack type number
0

Zydus Group

Zydus Corporate Park, Ahmedabad, Gujarat, 382481, IN
Last Update: 2025-12-10
Between 750 and 799

The Zydus Group with an overarching purpose of empowering people with freedom to live healthier and more fulfilled lives, is an innovative, global life-sciences company that discovers, develops, manufactures, and markets a broad range of healthcare therapies. The group employs over 27000 people worldwide and is driven by its mission to unlock new possibilities in life-sciences through quality healthcare solutions that impact lives. The group aspires to transform lives through pathbreaking discoveries.

NAICS: 325
NAICS Definition:
Employees: 18,313
Subsidiaries: 2
12-month incidents
0
Known data breaches
0
Attack type number
0

Compliance Badges Comparison

Security & Compliance Standards Overview

https://images.rankiteo.com/companyimages/eli-lilly-and-company.jpeg
Eli Lilly and Company
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/zyduscadila.jpeg
Zydus Group
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
Eli Lilly and Company
100%
Compliance Rate
0/4 Standards Verified
Zydus Group
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Pharmaceutical Manufacturing Industry Average (This Year)

No incidents recorded for Eli Lilly and Company in 2025.

Incidents vs Pharmaceutical Manufacturing Industry Average (This Year)

No incidents recorded for Zydus Group in 2025.

Incident History — Eli Lilly and Company (X = Date, Y = Severity)

Eli Lilly and Company cyber incidents detection timeline including parent company and subsidiaries

Incident History — Zydus Group (X = Date, Y = Severity)

Zydus Group cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/eli-lilly-and-company.jpeg
Eli Lilly and Company
Incidents

No Incident

https://images.rankiteo.com/companyimages/zyduscadila.jpeg
Zydus Group
Incidents

No Incident

FAQ

Eli Lilly and Company company demonstrates a stronger AI Cybersecurity Score compared to Zydus Group company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Historically, Zydus Group company has disclosed a higher number of cyber incidents compared to Eli Lilly and Company company.

In the current year, Zydus Group company and Eli Lilly and Company company have not reported any cyber incidents.

Neither Zydus Group company nor Eli Lilly and Company company has reported experiencing a ransomware attack publicly.

Neither Zydus Group company nor Eli Lilly and Company company has reported experiencing a data breach publicly.

Neither Zydus Group company nor Eli Lilly and Company company has reported experiencing targeted cyberattacks publicly.

Neither Eli Lilly and Company company nor Zydus Group company has reported experiencing or disclosing vulnerabilities publicly.

Neither Eli Lilly and Company nor Zydus Group holds any compliance certifications.

Neither company holds any compliance certifications.

Eli Lilly and Company company has more subsidiaries worldwide compared to Zydus Group company.

Eli Lilly and Company company employs more people globally than Zydus Group company, reflecting its scale as a Pharmaceutical Manufacturing.

Neither Eli Lilly and Company nor Zydus Group holds SOC 2 Type 1 certification.

Neither Eli Lilly and Company nor Zydus Group holds SOC 2 Type 2 certification.

Neither Eli Lilly and Company nor Zydus Group holds ISO 27001 certification.

Neither Eli Lilly and Company nor Zydus Group holds PCI DSS certification.

Neither Eli Lilly and Company nor Zydus Group holds HIPAA certification.

Neither Eli Lilly and Company nor Zydus Group 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