Comparison Overview

Molina Healthcare

VS

McKesson

Molina Healthcare

200 Oceangate, Long Beach, California, US, 90802
Last Update: 2025-11-27

Molina Healthcare is a FORTUNE 500 company that is focused exclusively on government-sponsored health care programs for families and individuals who qualify for government sponsored health care. Molina Healthcare contracts with state governments and serves as a health plan providing a wide range of quality health care services to families and individuals. Molina Healthcare offers health plans in Arizona, California, Florida, Idaho, Illinois, Kentucky, Massachusetts, Michigan, Mississippi, Nevada, New Mexico, New York, Ohio, South Carolina, Texas, Utah, Virginia, Washington and Wisconsin. Molina also offers a Medicare product and has been selected in several states to participate in duals demonstration projects to manage the care for those eligible for both Medicaid and Medicare.

NAICS: 62
NAICS Definition: Health Care and Social Assistance
Employees: 17,236
Subsidiaries: 3
12-month incidents
0
Known data breaches
2
Attack type number
2

McKesson

6555 State Highway 161, Irving, Texas, 75039, US
Last Update: 2025-11-26
Between 800 and 849

Welcome to the official LinkedIn page for McKesson Corporation. We're an impact-driven healthcare organization dedicated to “Advancing Health Outcomes For All.” As a global healthcare company, we touch virtually every aspect of health. Our leaders empower our people to lead with a growth mindset and deliver excellence for our customers, partners, and the wellbeing of people, everywhere. We work with biopharma companies, care providers, pharmacies, manufacturers, governments, and others to deliver insights, products and services that make quality care more accessible and affordable. Delivering better health outcomes for our employees, our communities, and our environment. Every day, we strive to inspire and enable people to reach their full potential. To learn more about how #TeamMckesson helps improve care in every setting, visit: https://bit.ly/3xadvB0

NAICS: 62
NAICS Definition: Health Care and Social Assistance
Employees: 22,564
Subsidiaries: 10
12-month incidents
0
Known data breaches
0
Attack type number
0

Compliance Badges Comparison

Security & Compliance Standards Overview

https://images.rankiteo.com/companyimages/molina-healthcare.jpeg
Molina Healthcare
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/mckesson.jpeg
McKesson
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
Molina Healthcare
100%
Compliance Rate
0/4 Standards Verified
McKesson
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Hospitals and Health Care Industry Average (This Year)

No incidents recorded for Molina Healthcare in 2025.

Incidents vs Hospitals and Health Care Industry Average (This Year)

No incidents recorded for McKesson in 2025.

Incident History — Molina Healthcare (X = Date, Y = Severity)

Molina Healthcare cyber incidents detection timeline including parent company and subsidiaries

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

McKesson cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/molina-healthcare.jpeg
Molina Healthcare
Incidents

Date Detected: 05/2017
Type:Vulnerability
Attack Vector: Exploitation of a Security Flaw
Blog: Blog

Date Detected: 05/2017
Type:Breach
Attack Vector: Exploitation of a hyperlink vulnerability
Blog: Blog

Date Detected: 3/2015
Type:Breach
Attack Vector: Insider Threat
Blog: Blog
https://images.rankiteo.com/companyimages/mckesson.jpeg
McKesson
Incidents

No Incident

FAQ

McKesson company demonstrates a stronger AI Cybersecurity Score compared to Molina Healthcare company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Molina Healthcare company has historically faced a number of disclosed cyber incidents, whereas McKesson company has not reported any.

In the current year, McKesson company and Molina Healthcare company have not reported any cyber incidents.

Neither McKesson company nor Molina Healthcare company has reported experiencing a ransomware attack publicly.

Molina Healthcare company has disclosed at least one data breach, while the other McKesson company has not reported such incidents publicly.

Neither McKesson company nor Molina Healthcare company has reported experiencing targeted cyberattacks publicly.

Molina Healthcare company has disclosed at least one vulnerability, while McKesson company has not reported such incidents publicly.

Neither Molina Healthcare nor McKesson holds any compliance certifications.

Neither company holds any compliance certifications.

McKesson company has more subsidiaries worldwide compared to Molina Healthcare company.

McKesson company employs more people globally than Molina Healthcare company, reflecting its scale as a Hospitals and Health Care.

Neither Molina Healthcare nor McKesson holds SOC 2 Type 1 certification.

Neither Molina Healthcare nor McKesson holds SOC 2 Type 2 certification.

Neither Molina Healthcare nor McKesson holds ISO 27001 certification.

Neither Molina Healthcare nor McKesson holds PCI DSS certification.

Neither Molina Healthcare nor McKesson holds HIPAA certification.

Neither Molina Healthcare nor McKesson 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