Owens & Minor Company Cyber Security Posture

owens-minor.com

Owens & Minor, Inc. (NYSE: OMI) is a Fortune 500 global healthcare solutions company providing essential products and services that support care from the hospital to the home. For over 100 years, Owens & Minor and its affiliated brands, Apriaยฎ , Byramยฎ, and HALYARD*, have helped to make each day better for the patients, providers, and communities we serve. Powered by more than 20,000 teammates worldwide, Owens & Minor delivers comfort and confidence behind the scenes so healthcare stays at the forefront. Owens & Minor exists because every day, everywhere, Life Takes Careโ„ข.

O&M Company Details

Linkedin ID:

owens-minor

Employees number:

12607 employees

Number of followers:

136929.0

NAICS:

62

Industry Type:

Hospitals and Health Care

Homepage:

owens-minor.com

IP Addresses:

Scan still pending

Company ID:

OWE_3394818

Scan Status:

In-progress

AI scoreO&M Risk Score (AI oriented)

Between 800 and 900

This score is AI-generated and less favored by cyber insurers, who prefer the TPRM score.

Ailogo

Owens & Minor Company Scoring based on AI Models

Model NameDateDescriptionCurrent Score DifferenceScore
AVERAGE-Industry03-12-2025

This score represents the average cybersecurity rating of companies already scanned within the same industry. It provides a benchmark to compare an individual company's security posture against its industry peers.

N/A

Between 800 and 900

Owens & Minor Company Cyber Security News & History

Past Incidents
0
Attack Types
0
EntityTypeSeverityImpactSeenUrl IDDetailsView

Owens & Minor Company Subsidiaries

SubsidiaryImage

Owens & Minor, Inc. (NYSE: OMI) is a Fortune 500 global healthcare solutions company providing essential products and services that support care from the hospital to the home. For over 100 years, Owens & Minor and its affiliated brands, Apriaยฎ , Byramยฎ, and HALYARD*, have helped to make each day better for the patients, providers, and communities we serve. Powered by more than 20,000 teammates worldwide, Owens & Minor delivers comfort and confidence behind the scenes so healthcare stays at the forefront. Owens & Minor exists because every day, everywhere, Life Takes Careโ„ข.

Loading...

Access Data Using Our API

SubsidiaryImage

Get company history

curl -i -X GET 'https://api.rankiteo.com/underwriter-getcompany-history?linkedin_id=owens-minor' -H 'apikey: YOUR_API_KEY_HERE'
newsone

O&M Cyber Security News

2025-06-06T14:27:11.000Z
Owens & Minor spikes $1.36B Rotech buyout over regulatory barriers

Owens & Minor said Thursday it has terminated the planned $1.36 billion acquisition of home medical equipment company Rotech Healthcare Holdingsย ...

2025-06-05T17:38:57.000Z
Owens & Minor Cancels Rotech Buyout

Owens & Minor (NYSE:OMI) on Thursday announced an agreement to terminate its previously announced $1.36B acquisition of privately held homeย ...

2025-06-05T14:29:51.000Z
Owens & Minor Mutually Agrees With Rotech Healthcare to Terminate Takeover Deal

Owens & Minor said Thursday it has mutually decided with Rotech Healthcare to terminate the previously announced takeover of the latter.

2025-04-11T07:00:00.000Z
In brief: Owens & Minor invests in DT, Samsung partners with Stanford, Alabama fights PBMs

RICHMOND, Va. โ€“ Owens & Minor and Rotech Healthcare have mutually agreed to terminate their previously announced acquisition. Under the terms ofย ...

2024-09-24T07:00:00.000Z
Owens & Minor appoints interim CFO to permanent seat

Healthcare logistics company Owens & Minor appointed its interim CFO Jonathan Leon to the role of permanent finance chief and EVP effectiveย ...

2024-07-23T07:00:00.000Z
Owens & Minor to buy medical equipment firm Rotech for $1.36 bln

Medical supplies distributor Owens & Minor (OMI.N) said on Tuesday it has agreed to buy medical equipment firm Rotech Healthcare for $1.36 billion in cash.

2025-01-23T08:00:00.000Z
Solara Medical Supplies to pay $3M to settle cyber violations

INDIANAPOLIS โ€“ Apria Healthcare, now part of Owens & Minor, has agreed to pay more than $6.4 million to resolve a consolidated data breach classย ...

2024-07-25T07:00:00.000Z
Owens & Minor inks $1.36B takeover of Rotech

Owens & Minor on Tuesday agreed to buy home medical equipment company Rotech Healthcare Holdings for $1.36 billion. Orlando, Florida-basedย ...

2025-01-06T08:00:00.000Z
Tycon Medical reports cyber incident

Tycon Medical Systems, a HME provider and distributor based here, has filed a notice with the Attorney General of Massachusetts of a cybersecurity incident.

similarCompanies

O&M Similar Companies

Erasmus MC

We are Erasmus MC. Our roots lie in Rotterdam, a city and port of international standing. We are the most innovative university medical center in the Netherlands and one of the worldโ€™s leading centers of scientific research. We are committed to achieving a healthy population and pursuing excellence

Falck

We are a global market leader in emergency response and healthcare services. 25,000 skilled and experienced professionals work in 26 countries around the world. Characterised by a strong, diverse, and inclusive working environment, we go to work every day with the promise to be there when you need

Hospital for Special Surgery

HSS is a world leader in orthopedics, rheumatology and rehabilitation. At its core is Hospital for Special Surgery, the largest academic medical center specialized in musculoskeletal health founded in 1863. Ranked #1 in Orthopedics worldwide by Newsweek (3 consecutive years) and nationwide by US New

Providence

Every day, 119,000 compassionate caregivers serve patients and communities through Providence St. Joseph Health, a national, Catholic, not-for-profit health system, driven by a belief that health is a human right. Rooted in the founding missions of the Sisters of Providence and the Sisters of St.

Region Hovedstaden

Det handler om liv. Om at bringe liv til verden og skabe livskvalitet. Om at redde liv og forbedre liv. Som medarbejder i Region Hovedstaden trรฆder du ind i en verden af muligheder og mangfoldighed med plads til dine ambitioner. Du er en del af et stรฆrkt fagligt miljรธ, hvor vi har fingeren pรฅ pulsen

Grupo Angeles Servicios de Salud

Hospital Angeles Health System es una empresa 100% mexicana, lโˆšโ‰ der en el sector de la salud privada en Mโˆšยฉxico y Latinoamโˆšยฉrica, con mโˆšยฐs de 30 aโˆšยฑos de experiencia en la atenciโˆšโ‰ฅn mโˆšยฉdica y hospitalaria. Cuenta con 26 Hospitales Angeles en todo el paโˆšโ‰ s y un cuerpo mโˆšยฉdico de mโˆšยฐs de 15,000 especi

faq

Frequently Asked Questions (FAQ) on Cybersecurity Incidents

O&M CyberSecurity History Information

Total Incidents: According to Rankiteo, O&M has faced 0 incidents in the past.

Incident Types: As of the current reporting period, O&M has not encountered any cybersecurity incidents.

Total Financial Loss: The total financial loss from these incidents is estimated to be {total_financial_loss}.

Cybersecurity Posture: The company's overall cybersecurity posture is described as Owens & Minor, Inc. (NYSE: OMI) is a Fortune 500 global healthcare solutions company providing essential products and services that support care from the hospital to the home. For over 100 years, Owens & Minor and its affiliated brands, Apriaยฎ , Byramยฎ, and HALYARD*, have helped to make each day better for the patients, providers, and communities we serve. Powered by more than 20,000 teammates worldwide, Owens & Minor delivers comfort and confidence behind the scenes so healthcare stays at the forefront. Owens & Minor exists because every day, everywhere, Life Takes Careโ„ข..

Detection and Response: The company detects and responds to cybersecurity incidents through {description_of_detection_and_response_process}.

Incident Details

Incident 1: Ransomware Attack

Title: {Incident_Title}

Description: {Brief_description_of_the_incident}

Date Detected: {Detection_Date}

Date Publicly Disclosed: {Disclosure_Date}

Date Resolved: {Resolution_Date}

Type: {Type_of_Attack}

Attack Vector: {Attack_Vector}

Vulnerability Exploited: {Vulnerability}

Threat Actor: {Threat_Actor}

Motivation: {Motivation}

Incident 2: Data Breach

Title: {Incident_Title}

Description: {Brief_description_of_the_incident}

Date Detected: {Detection_Date}

Date Publicly Disclosed: {Disclosure_Date}

Date Resolved: {Resolution_Date}

Type: {Type_of_Attack}

Attack Vector: {Attack_Vector}

Vulnerability Exploited: {Vulnerability}

Threat Actor: {Threat_Actor}

Motivation: {Motivation}

Common Attack Types: As of now, the company has not encountered any reported incidents involving common cyberattacks.

Identification of Attack Vectors: The company identifies the attack vectors used in incidents through {description_of_identification_process}.

Impact of the Incidents

Incident 1: Ransomware Attack

Financial Loss: {Financial_Loss}

Data Compromised: {Data_Compromised}

Systems Affected: {Systems_Affected}

Downtime: {Downtime}

Operational Impact: {Operational_Impact}

Conversion Rate Impact: {Conversion_Rate_Impact}

Revenue Loss: {Revenue_Loss}

Customer Complaints: {Customer_Complaints}

Brand Reputation Impact: {Brand_Reputation_Impact}

Legal Liabilities: {Legal_Liabilities}

Identity Theft Risk: {Identity_Theft_Risk}

Payment Information Risk: {Payment_Information_Risk}

Incident 2: Data Breach

Financial Loss: {Financial_Loss}

Data Compromised: {Data_Compromised}

Systems Affected: {Systems_Affected}

Downtime: {Downtime}

Operational Impact: {Operational_Impact}

Conversion Rate Impact: {Conversion_Rate_Impact}

Revenue Loss: {Revenue_Loss}

Customer Complaints: {Customer_Complaints}

Brand Reputation Impact: {Brand_Reputation_Impact}

Legal Liabilities: {Legal_Liabilities}

Identity Theft Risk: {Identity_Theft_Risk}

Payment Information Risk: {Payment_Information_Risk}

Average Financial Loss: The average financial loss per incident is {average_financial_loss}.

Commonly Compromised Data Types: The types of data most commonly compromised in incidents are {list_of_commonly_compromised_data_types}.

Incident 1: Ransomware Attack

Entity Name: {Entity_Name}

Entity Type: {Entity_Type}

Industry: {Industry}

Location: {Location}

Size: {Size}

Customers Affected: {Customers_Affected}

Incident 2: Data Breach

Entity Name: {Entity_Name}

Entity Type: {Entity_Type}

Industry: {Industry}

Location: {Location}

Size: {Size}

Customers Affected: {Customers_Affected}

Response to the Incidents

Incident 1: Ransomware Attack

Incident Response Plan Activated: {Yes/No}

Third Party Assistance: {Yes/No}

Law Enforcement Notified: {Yes/No}

Containment Measures: {Containment_Measures}

Remediation Measures: {Remediation_Measures}

Recovery Measures: {Recovery_Measures}

Communication Strategy: {Communication_Strategy}

Adaptive Behavioral WAF: {Adaptive_Behavioral_WAF}

On-Demand Scrubbing Services: {On_Demand_Scrubbing_Services}

Network Segmentation: {Network_Segmentation}

Enhanced Monitoring: {Enhanced_Monitoring}

Incident 2: Data Breach

Incident Response Plan Activated: {Yes/No}

Third Party Assistance: {Yes/No}

Law Enforcement Notified: {Yes/No}

Containment Measures: {Containment_Measures}

Remediation Measures: {Remediation_Measures}

Recovery Measures: {Recovery_Measures}

Communication Strategy: {Communication_Strategy}

Adaptive Behavioral WAF: {Adaptive_Behavioral_WAF}

On-Demand Scrubbing Services: {On_Demand_Scrubbing_Services}

Network Segmentation: {Network_Segmentation}

Enhanced Monitoring: {Enhanced_Monitoring}

Incident Response Plan: The company's incident response plan is described as {description_of_incident_response_plan}.

Third-Party Assistance: The company involves third-party assistance in incident response through {description_of_third_party_involvement}.

Data Breach Information

Incident 2: Data Breach

Type of Data Compromised: {Type_of_Data}

Number of Records Exposed: {Number_of_Records}

Sensitivity of Data: {Sensitivity_of_Data}

Data Exfiltration: {Yes/No}

Data Encryption: {Yes/No}

File Types Exposed: {File_Types}

Personally Identifiable Information: {Yes/No}

Prevention of Data Exfiltration: The company takes the following measures to prevent data exfiltration: {description_of_prevention_measures}.

Handling of PII Incidents: The company handles incidents involving personally identifiable information (PII) through {description_of_handling_process}.

Ransomware Information

Incident 1: Ransomware Attack

Ransom Demanded: {Ransom_Amount}

Ransom Paid: {Ransom_Paid}

Ransomware Strain: {Ransomware_Strain}

Data Encryption: {Yes/No}

Data Exfiltration: {Yes/No}

Ransom Payment Policy: The company's policy on paying ransoms in ransomware incidents is described as {description_of_ransom_payment_policy}.

Data Recovery from Ransomware: The company recovers data encrypted by ransomware through {description_of_data_recovery_process}.

Regulatory Compliance

Ransomware Logo

Incident 1: Ransomware Attack

Regulations Violated: {Regulations_Violated}

Fines Imposed: {Fines_Imposed}

Legal Actions: {Legal_Actions}

Regulatory Notifications: {Regulatory_Notifications}

Data Breach Logo

Incident 2: Data Breach

Regulations Violated: {Regulations_Violated}

Fines Imposed: {Fines_Imposed}

Legal Actions: {Legal_Actions}

Regulatory Notifications: {Regulatory_Notifications}

Regulatory Frameworks: The company complies with the following regulatory frameworks regarding cybersecurity: {list_of_regulatory_frameworks}.

Ensuring Regulatory Compliance: The company ensures compliance with regulatory requirements through {description_of_compliance_measures}.

Lessons Learned and Recommendations

Incident 1: Ransomware Attack

Lessons Learned: {Lessons_Learned}

Incident 2: Data Breach

Lessons Learned: {Lessons_Learned}

Incident 1: Ransomware Attack

Recommendations: {Recommendations}

Incident 2: Data Breach

Recommendations: {Recommendations}

Key Lessons Learned: The key lessons learned from past incidents are {list_of_key_lessons_learned}.

Implemented Recommendations: The company has implemented the following recommendations to improve cybersecurity: {list_of_implemented_recommendations}.

References

Incident 1: Ransomware Attack

Source: {Source}

URL: {URL}

Date Accessed: {Date_Accessed}

Incident 2: Data Breach

Source: {Source}

URL: {URL}

Date Accessed: {Date_Accessed}

Additional Resources: Stakeholders can find additional resources on cybersecurity best practices at {list_of_additional_resources}.

Investigation Status

Incident 1: Ransomware Attack

Investigation Status: {Investigation_Status}

Incident 2: Data Breach

Investigation Status: {Investigation_Status}

Communication of Investigation Status: The company communicates the status of incident investigations to stakeholders through {description_of_communication_process}.

Stakeholder and Customer Advisories

Incident 1: Ransomware Attack

Stakeholder Advisories: {Stakeholder_Advisories}

Customer Advisories: {Customer_Advisories}


Incident 2: Data Breach

Stakeholder Advisories: {Stakeholder_Advisories}

Customer Advisories: {Customer_Advisories}

Advisories Provided: The company provides the following advisories to stakeholders and customers following an incident: {description_of_advisories_provided}.

Initial Access Broker

Incident 1: Ransomware Attack

Entry Point: {Entry_Point}

Reconnaissance Period: {Reconnaissance_Period}

Backdoors Established: {Backdoors_Established}

High Value Targets: {High_Value_Targets}

Data Sold on Dark Web: {Yes/No}

Incident 2: Data Breach

Entry Point: {Entry_Point}

Reconnaissance Period: {Reconnaissance_Period}

Backdoors Established: {Backdoors_Established}

High Value Targets: {High_Value_Targets}

Data Sold on Dark Web: {Yes/No}

Monitoring and Mitigation of Initial Access Brokers: The company monitors and mitigates the activities of initial access brokers through {description_of_monitoring_and_mitigation_measures}.

Post-Incident Analysis

Incident 1: Ransomware Attack

Root Causes: {Root_Causes}

Corrective Actions: {Corrective_Actions}

Incident 2: Data Breach

Root Causes: {Root_Causes}

Corrective Actions: {Corrective_Actions}

Post-Incident Analysis Process: The company's process for conducting post-incident analysis is described as {description_of_post_incident_analysis_process}.

Corrective Actions Taken: The company has taken the following corrective actions based on post-incident analysis: {list_of_corrective_actions_taken}.

Additional Questions

General Information

Ransom Payment History: The company has {paid/not_paid} ransoms in the past.

Last Ransom Demanded: The amount of the last ransom demanded was {last_ransom_amount}.

Last Attacking Group: The attacking group in the last incident was {last_attacking_group}.

Incident Details

Most Recent Incident Detected: The most recent incident detected was on {most_recent_incident_detected_date}.

Most Recent Incident Publicly Disclosed: The most recent incident publicly disclosed was on {most_recent_incident_publicly_disclosed_date}.

Most Recent Incident Resolved: The most recent incident resolved was on {most_recent_incident_resolved_date}.

Impact of the Incidents

Highest Financial Loss: The highest financial loss from an incident was {highest_financial_loss}.

Most Significant Data Compromised: The most significant data compromised in an incident was {most_significant_data_compromised}.

Most Significant System Affected: The most significant system affected in an incident was {most_significant_system_affected}.

Response to the Incidents

Third-Party Assistance in Most Recent Incident: The third-party assistance involved in the most recent incident was {third_party_assistance_in_most_recent_incident}.

Containment Measures in Most Recent Incident: The containment measures taken in the most recent incident were {containment_measures_in_most_recent_incident}.

Data Breach Information

Most Sensitive Data Compromised: The most sensitive data compromised in a breach was {most_sensitive_data_compromised}.

Number of Records Exposed: The number of records exposed in the most significant breach was {number_of_records_exposed}.

Ransomware Information

Highest Ransom Demanded: The highest ransom demanded in a ransomware incident was {highest_ransom_demanded}.

Highest Ransom Paid: The highest ransom paid in a ransomware incident was {highest_ransom_paid}.

Regulatory Compliance

Highest Fine Imposed: The highest fine imposed for a regulatory violation was {highest_fine_imposed}.

Most Significant Legal Action: The most significant legal action taken for a regulatory violation was {most_significant_legal_action}.

Lessons Learned and Recommendations

Most Significant Lesson Learned: The most significant lesson learned from past incidents was {most_significant_lesson_learned}.

Most Significant Recommendation Implemented: The most significant recommendation implemented to improve cybersecurity was {most_significant_recommendation_implemented}.

References

Most Recent Source: The most recent source of information about an incident is {most_recent_source}.

Most Recent URL for Additional Resources: The most recent URL for additional resources on cybersecurity best practices is {most_recent_url}.

Investigation Status

Current Status of Most Recent Investigation: The current status of the most recent investigation is {current_status_of_most_recent_investigation}.

Stakeholder and Customer Advisories

Most Recent Stakeholder Advisory: The most recent stakeholder advisory issued was {most_recent_stakeholder_advisory}.

Most Recent Customer Advisory: The most recent customer advisory issued was {most_recent_customer_advisory}.

Initial Access Broker

Most Recent Entry Point: The most recent entry point used by an initial access broker was {most_recent_entry_point}.

Most Recent Reconnaissance Period: The most recent reconnaissance period for an incident was {most_recent_reconnaissance_period}.

Post-Incident Analysis

Most Significant Root Cause: The most significant root cause identified in post-incident analysis was {most_significant_root_cause}.

Most Significant Corrective Action: The most significant corrective action taken based on post-incident analysis was {most_significant_corrective_action}.

What Do We Measure?

revertimgrevertimgrevertimgrevertimg
Incident
revertimgrevertimgrevertimgrevertimg
Finding
revertimgrevertimgrevertimgrevertimg
Grade
revertimgrevertimgrevertimgrevertimg
Digital Assets

Every week, Rankiteo analyzes billions of signals to give organizations a sharper, faster view of emerging risks. With deeper, more actionable intelligence at their fingertips, security teams can outpace threat actors, respond instantly to Zero-Day attacks, and dramatically shrink their risk exposure window.

These are some of the factors we use to calculate the overall score:

Network Security

Identify exposed access points, detect misconfigured SSL certificates, and uncover vulnerabilities across the network infrastructure.

SBOM (Software Bill of Materials)

Gain visibility into the software components used within an organization to detect vulnerabilities, manage risk, and ensure supply chain security.

CMDB (Configuration Management Database)

Monitor and manage all IT assets and their configurations to ensure accurate, real-time visibility across the company's technology environment.

Threat Intelligence

Leverage real-time insights on active threats, malware campaigns, and emerging vulnerabilities to proactively defend against evolving cyberattacks.

Top LeftTop RightBottom LeftBottom Right
Rankiteo is a unified scoring and risk platform that analyzes billions of signals weekly to help organizations gain faster, more actionable insights into emerging threats. Empowering teams to outpace adversaries and reduce exposure.
Users Love Us Badge