Comparison Overview

MSD

VS

Eli Lilly and Company

MSD

90 E Scott Ave, Rahway, New Jersey, US, 07065
Last Update: 2026-04-01
View Profile
Between 750 and 799
http://www.msd.com

At MSD, known as Merck & Co., Inc., Rahway, NJ, USA in the United States and Canada, we are unified around our purpose: We use the power of leading-edge science to save and improve lives around the world. For more than 130 years, we have brought hope to humanity through the development of important medicines and vaccines. We aspire to be the premier research-intensive biopharmaceutical company in the world – and today, we are at the forefront of research to deliver innovative health solutions that advance the prevention and treatment of diseases in people and animals. We foster a diverse and inclusive global workforce and operate responsibly every day to enable a safe, sustainable and healthy future for all people and communities. For more information, visit www.msd.com and connect with us on Facebook, Instagram, Twitter, and YouTube.

NAICS: 3254
NAICS Definition: Pharmaceutical and Medicine Manufacturing
Employees: 40,830
Subsidiaries: 39
12-month incidents
0
Known data breaches
1
Attack type number
1
View Profile

Eli Lilly and Company

Lilly Corporate Center, Indianapolis, Indiana, US, 46285
Last Update: 2026-04-01
Between 800 and 849
http://www.lilly.com/

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: 53,748
Subsidiaries: 16
12-month incidents
0
Known data breaches
0
Attack type number
0

Compliance Badges Comparison

Security & Compliance Standards Overview

https://images.rankiteo.com/companyimages/msd-global.jpeg
MSD
—
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/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
Compliance Summary
MSD
100%
Compliance Rate
0/4 Standards Verified
Eli Lilly and Company
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Pharmaceutical Manufacturing Industry Average (This Year)

No incidents recorded for MSD in 2026.

Incidents vs Pharmaceutical Manufacturing Industry Average (This Year)

No incidents recorded for Eli Lilly and Company in 2026.

Incident History — MSD (X = Date, Y = Severity)

MSD cyber incidents detection timeline including parent company and subsidiaries

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

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

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/msd-global.jpeg
MSD
Incidents

Date Detected: 9/2025
Type:Breach
Attack Vector: unauthorized access, supply chain compromise
Blog: Blog
https://images.rankiteo.com/companyimages/eli-lilly-and-company.jpeg
Eli Lilly and Company
Incidents

No Incident

FAQ

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

MSD company has historically faced a number of disclosed cyber incidents, whereas Eli Lilly and Company company has not reported any.

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

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

MSD company has disclosed at least one data breach, while the other Eli Lilly and Company company has not reported such incidents publicly.

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

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

Neither MSD nor Eli Lilly and Company holds any compliance certifications.

Neither company holds any compliance certifications.

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

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

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

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

Neither MSD nor Eli Lilly and Company holds ISO 27001 certification.

Neither MSD nor Eli Lilly and Company holds PCI DSS certification.

Neither MSD nor Eli Lilly and Company holds HIPAA certification.

Neither MSD nor Eli Lilly and Company holds GDPR certification.

Latest Global CVEs (Not Company-Specific)

Description

nimiq/core-rs-albatross is a Rust implementation of the Nimiq Proof-of-Stake protocol based on the Albatross consensus algorithm. Prior to version 1.3.0, two peer-facing consensus request handlers assume that the history index is always available and call blockchain.history_store.history_index().unwrap() directly. That assumption is false by construction. HistoryStoreProxy::history_index() explicitly returns None for the valid HistoryStoreProxy::WithoutIndex state. when a full node is syncing or otherwise running without the history index, a remote peer can send RequestTransactionsProof or RequestTransactionReceiptsByAddress and trigger an Option::unwrap() panic on the request path. This issue has been patched in version 1.3.0.

Published
Date
2026-04-03
Updated
Date
2026-04-03
Risk Information
cvss3
Base: 5.3
Severity: LOW
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
References
Description

PraisonAI is a multi-agent teams system. Prior to version 1.5.95, FileTools.download_file() in praisonaiagents validates the destination path but performs no validation on the url parameter, passing it directly to httpx.stream() with follow_redirects=True. An attacker who controls the URL can reach any host accessible from the server including cloud metadata services and internal network services. This issue has been patched in version 1.5.95.

Published
Date
2026-04-03
Updated
Date
2026-04-03
Risk Information
cvss3
Base: 8.6
Severity: LOW
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N
References
Description

PraisonAI is a multi-agent teams system. Prior to version 4.5.97, OAuthManager.validate_token() returns True for any token not found in its internal store, which is empty by default. Any HTTP request to the MCP server with an arbitrary Bearer token is treated as authenticated, granting full access to all registered tools and agent capabilities. This issue has been patched in version 4.5.97.

Published
Date
2026-04-03
Updated
Date
2026-04-03
Risk Information
cvss3
Base: 9.1
Severity: LOW
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
References
Description

PraisonAI is a multi-agent teams system. Prior to version 4.5.97, the PraisonAI Gateway server accepts WebSocket connections at /ws and serves agent topology at /info with no authentication. Any network client can connect, enumerate registered agents, and send arbitrary messages to agents and their tool sets. This issue has been patched in version 4.5.97.

Published
Date
2026-04-03
Updated
Date
2026-04-03
Risk Information
cvss3
Base: 9.1
Severity: LOW
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
References
Description

PraisonAI is a multi-agent teams system. Prior to version 4.5.90, MCPToolIndex.search_tools() compiles a caller-supplied string directly as a Python regular expression with no validation, sanitization, or timeout. A crafted regex causes catastrophic backtracking in the re engine, blocking the Python thread for hundreds of seconds and causing a complete service outage. This issue has been patched in version 4.5.90.

Published
Date
2026-04-03
Updated
Date
2026-04-03
Risk Information
cvss3
Base: 6.5
Severity: LOW
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
References