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

FreePBX Endpoint Manager is a module for managing telephony endpoints in FreePBX systems. Versions prior to 16.0.96 and 17.0.1 through 17.0.9 have a weak default password. By default, this is a 6 digit numeric value which can be brute forced. (This is the app_password parameter). Depending on local configuration, this password could be the extension, voicemail, user manager, DPMA or EPM phone admin password. This issue is fixed in versions 16.0.96 and 17.0.10.

Risk Information
cvss4
Base: 6.9
Severity: LOW
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/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

Neuron is a PHP framework for creating and orchestrating AI Agents. In versions 2.8.11 and below, the MySQLWriteTool executes arbitrary SQL provided by the caller using PDO::prepare() + execute() without semantic restrictions. This is consistent with the name (“write tool”), but in an LLM/agent context it becomes a high-risk capability: prompt injection or indirect prompt manipulation can cause execution of destructive queries such as DROP TABLE, TRUNCATE, DELETE, ALTER, or privilege-related statements (subject to DB permissions). Deployments that expose an agent with MySQLWriteTool enabled to untrusted input and/or run the tool with a DB user that has broad privileges are impacted. This issue is fixed in version 2.8.12.

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

Neuron is a PHP framework for creating and orchestrating AI Agents. Versions 2.8.11 and below use MySQLSelectTool, which is vulnerable to Read-Only Bypass. MySQLSelectTool is intended to be a read-only SQL tool (e.g., for LLM agent querying, however, validation based on the first keyword (e.g., SELECT) and a forbidden-keyword list does not block file-writing constructs such as INTO OUTFILE / INTO DUMPFILE. As a result, an attacker who can influence the tool input (e.g., via prompt injection through a public agent endpoint) may write arbitrary files to the DB server if the MySQL/MariaDB account has the FILE privilege and server configuration permits writes to a useful location (e.g., a web-accessible directory). This issue is fixed in version 2.8.12.

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

Okta Java Management SDK facilitates interactions with the Okta management API. In versions 11.0.0 through 20.0.0, race conditions may arise from concurrent requests using the ApiClient class. This could cause a status code or response header from one request’s response to influence another request’s response. This issue is fixed in version 20.0.1.

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

The Auth0 Next.js SDK is a library for implementing user authentication in Next.js applications. When using versions 4.11.0 through 4.11.2 and 4.12.0, simultaneous requests on the same client may result in improper lookups in the TokenRequestCache for the request results. This issue is fixed in versions 4.11.2 and 4.12.1.

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