Comparison Overview

Medline Industries, LP

VS

Olympus Corporation

Medline Industries, LP

Three Lakes Drive, Northfield, IL, 60093, US
Last Update: 2025-11-26
Between 750 and 799

Medline is the largest provider of medical-surgical products and supply chain solutions serving all points of care. Through its unique offering of world-class products, supply chain resilience and clinical practice expertise, Medline delivers improved clinical, financial and operational outcomes. Headquartered in Northfield, Illinois, the company employs 43,000 people worldwide and operates in over 100 countries and territories. To learn more about how Medline makes healthcare run better, visit www.medline.com.

NAICS: 3391
NAICS Definition: Medical Equipment and Supplies Manufacturing
Employees: 16,474
Subsidiaries: 10
12-month incidents
0
Known data breaches
0
Attack type number
0

Olympus Corporation

Nishi-shinjuku 2-3-1 Shinjuku Monolith, None, Shinjuku-ku, Tokyo, JP, None
Last Update: 2025-11-26

Olympus is passionate about creating customer-driven solutions for the medical industry. For more than 100 years, Olympus has focused on making people’s lives healthier, safer and more fulfilling by helping detect, prevent, and treat disease, furthering scientific research, and ensuring public safety. Olympus is headquartered in Tokyo, Japan, with more than 31,000 employees worldwide in nearly 40 countries and regions.

NAICS: 3391
NAICS Definition: Medical Equipment and Supplies Manufacturing
Employees: 10,074
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/medline-industries.jpeg
Medline Industries, LP
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/olympus-corp.jpeg
Olympus Corporation
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
Medline Industries, LP
100%
Compliance Rate
0/4 Standards Verified
Olympus Corporation
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Medical Equipment Manufacturing Industry Average (This Year)

No incidents recorded for Medline Industries, LP in 2025.

Incidents vs Medical Equipment Manufacturing Industry Average (This Year)

No incidents recorded for Olympus Corporation in 2025.

Incident History — Medline Industries, LP (X = Date, Y = Severity)

Medline Industries, LP cyber incidents detection timeline including parent company and subsidiaries

Incident History — Olympus Corporation (X = Date, Y = Severity)

Olympus Corporation cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/medline-industries.jpeg
Medline Industries, LP
Incidents

No Incident

https://images.rankiteo.com/companyimages/olympus-corp.jpeg
Olympus Corporation
Incidents

No Incident

FAQ

Medline Industries, LP company demonstrates a stronger AI Cybersecurity Score compared to Olympus Corporation company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Historically, Olympus Corporation company has disclosed a higher number of cyber incidents compared to Medline Industries, LP company.

In the current year, Olympus Corporation company and Medline Industries, LP company have not reported any cyber incidents.

Neither Olympus Corporation company nor Medline Industries, LP company has reported experiencing a ransomware attack publicly.

Neither Olympus Corporation company nor Medline Industries, LP company has reported experiencing a data breach publicly.

Neither Olympus Corporation company nor Medline Industries, LP company has reported experiencing targeted cyberattacks publicly.

Neither Medline Industries, LP company nor Olympus Corporation company has reported experiencing or disclosing vulnerabilities publicly.

Neither Medline Industries, LP nor Olympus Corporation holds any compliance certifications.

Neither company holds any compliance certifications.

Medline Industries, LP company has more subsidiaries worldwide compared to Olympus Corporation company.

Medline Industries, LP company employs more people globally than Olympus Corporation company, reflecting its scale as a Medical Equipment Manufacturing.

Neither Medline Industries, LP nor Olympus Corporation holds SOC 2 Type 1 certification.

Neither Medline Industries, LP nor Olympus Corporation holds SOC 2 Type 2 certification.

Neither Medline Industries, LP nor Olympus Corporation holds ISO 27001 certification.

Neither Medline Industries, LP nor Olympus Corporation holds PCI DSS certification.

Neither Medline Industries, LP nor Olympus Corporation holds HIPAA certification.

Neither Medline Industries, LP nor Olympus Corporation 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