Skip to main content
Skip to main content

McKesson HIPAA, Supply Chain Risk & Vendor Assessment

Before you share customer data with McKesson, your compliance team needs documented proof they can be trusted. ThirdProof investigated McKesson across 27 intelligence sources — here's what we found.

Risk Tier
Tier 2High Risk
SOC 2
— Not Found
FedRAMP
— Not Authorized
Last Assessed
Mar 23, 2026
🟡SSL/TLS: TLSv1.3🟢Domain Age: 31.4 years🟢Infrastructure: 873 open ports, 0 CVEs🟢Sanctions: Clear — 2 matches checked, none confirmed
SOC 2 Status
McKesson has not had a SOC 2 claim detected on their trust page.
Sanctions Screening
McKesson returned no matches in OFAC SDN, EU Consolidated, and UN sanctions screening.
Risk Tier
ThirdProof assigned McKesson a High Risk tier with 82% confidence across 27 intelligence sources.

24 sources queried. 90% confidence. Every McKesson investigation produces both a risk report and an auto-filled security questionnaire — no vendor follow-up required.

Get McKesson's Full Report Free →
5 free investigations|Risk report + auto-filled questionnaire|Avg. 7 minutes

Certification & Compliance Status

Need a complete vendor security questionnaire?

Run a full ThirdProof investigation to get 133 security questions auto-filled with source evidence — ready for your next audit or vendor onboarding review.

Get McKesson's Full Report Free →
27 data sources queried per assessment
Reports generated in an average of 7 minutes
SHA-256 verified for audit integrity
Deterministic risk scoring — no AI guesswork
2Tier

High Risk

McKesson

Vendor Risk Assessment

Confidence Score90%

Based on data availability and source coverage

24

Sources Queried

21

Sources With Data

March 23, 2026

Last Assessed

Executive Summary

AI-generated analysis for McKesson

McKesson (mckesson.com) is a major publicly traded healthcare and pharmaceutical distribution company assessed at Risk Tier 2 (High Risk) with 90% confidence. This assessment reflects specific infrastructure and governance gaps identified during independent investigation, not a reflection of the company's overall market standing or business reputation. McKesson presents several meaningful positive signals. The domain has been registered since 1994 and web-archived since 1996, reflecting over 30 years of established online presence. The domain is protected by enterprise-grade registrar controls (CSC Corporate Domains) with full transfer/deletion locks. TLS is current and strong, using TLS 1.3 with a valid GlobalSign certificate expiring August 2026. The CDN infrastructure (Cloudflare/Incapsula) shows a clean abuse score of 0% and a zero threat score on website scanning. Malware detection service returned no malware or phishing flags. The company appears in the ISO 9362 BIC registry confirming entity identity, no sanctions or watchlist matches were found, and no adverse media signals were detected across recent articles. Evidence suggests McKesson operates AI-driven oncology analytics through its Ontada division using OpenAI and Microsoft Azure AI, indicating active AI capability investment. Several gaps elevate the risk tier and require attention before this vendor can be approved for high data access workloads:

Key Findings

  • Five high-risk service ports (FTP/21, SMTP/25, MySQL/3306, RDP/3389, Elasticsearch/9200) are exposed on the infrastructure footprint. The IP resolves to Cloudflare/Incapsula CDN edge infrastructure, which may mean these ports are not directly connected to McKesson's backend systems — however, this cannot be confirmed without vendor clarification.
  • The marketing website (mckesson.com) received a C+ (60/100) grade from HTTP security header analysis, with missing Strict-Transport-Security, Content-Security-Policy, and X-Frame-Options headers. The application portal (my.mckesson.com) was detected but not separately scanned.
  • No public trust center, compliance page, or subprocessor list was found at any standard path. For a company of McKesson's scale, this represents a transparency gap for enterprise buyers conducting due diligence.
  • McKesson's AI data usage policy does not clearly specify whether customer data is used for model training, and no data retention period for AI processing is stated. With confirmed use of OpenAI and Microsoft Azure AI for oncology data analysis, this gap is material for buyers with sensitive data.
  • SOC 2 compliance is indirectly indicated (via a job posting for a SOC Compliance Senior Analyst) but no formal trust page or report has been published. ISO 27001 certification was not found in independent registry searches. Overall, McKesson is a well-established enterprise vendor with significant institutional credibility, but the combination of exposed high-risk ports, absent compliance transparency, and unclear AI data handling practices creates a documented risk that must be resolved before granting high data access. A conditional approval is warranted pending vendor-provided assurances on the specific items identified herein.

Independence Statement

All evidence in this report was sourced independently from public registries, infrastructure scanning, threat intelligence feeds, and open-source data — McKesson was not contacted and did not participate in or influence this assessment.

Investigation Findings

6 findings identified for McKesson

5 medium1 low
medium

Missing Security Headers

mckesson.com is missing 3 recommended security headers: Strict-Transport-Security, Content-Security-Policy, X-Frame-Options.

medium

Ports Exposed on CDN Edge Server

7 potentially sensitive port(s) are publicly accessible on mckesson.com: 21 (FTP), 25 (SMTP), 110 (POP3), 143 (IMAP), 3306 (MySQL), 3389 (RDP), 9200 (Elasticsearch). However, this IP belongs to Cloudflare edge infrastructure. These ports are likely CDN management interfaces, not direct access to mckesson.com's backend services.

medium

HTTP Security Grade: C+

mckesson.com received a mediocre grade (C+). Some security headers are configured but improvements are needed. Note: This scan was performed on the marketing site (mckesson.com). The application endpoint (my.mckesson.com) may have different security headers. Verify the application domain separately.

medium

No Public Subprocessor Page Found

No accessible subprocessor page was found for mckesson.com. GDPR Article 28 requires data processors to maintain a list of subprocessors. Vendors with mature data governance typically publish this list.

medium

AI Training Data Practices Unclear

mckesson.com has an AI-related policy page but does not clearly state whether customer data is used for AI model training.

low

No Public Trust or Security Page Found

No accessible trust, security, or compliance page was found at common paths for mckesson.com. Vendors with mature security programs typically publish a trust center. Vendor should be asked to provide compliance documentation directly.

Security Strengths

22 positive signals verified

Legal Entity Actively Registered

Business Registration

[Filtered] LEI Registration Lapsed

Business Registration

Entity Found in Regulatory Database — MCKESSON CORPORATION

Sanctions & Watchlist Screening

No Adverse Media Signals

Adverse Media Scan (Fallback)

Firmographic Data Available

Company Intelligence

Valid SSL Certificate

Domain Analysis

Established Domain (31+ years)

Domain Registration

Threat Intelligence Partially Available

Threat Intelligence

No Hacker News Mentions

Tech Community Sentiment

Certificate Data from TLS Handshake

Certificate Transparency

Established Web Presence (29+ years)

Web Archive History

Domain in 4 Threat Intelligence Pulses

Threat Intelligence (OTX)

Clean IP Reputation

IP Reputation

Clean Safe Browsing Status

Malware & Phishing Check

Clean Website Security Scan

Website Security Scan

Not Found as FDIC-Insured Institution

FDIC Institution Check

No SEC Enforcement Filings Found

SEC Filing Search

Historical Media Search Unavailable

Historical Media Search

HITRUST Directory Match — Manual Verification Required

Certification Registry Verification

SOC 2 Compliance Claimed on Trust Page

Certification Registry Verification

Third-Party AI Providers Disclosed

AI Data Usage Policy

AI Data Retention Policy Not Specified

AI Data Usage Policy

Recommended Actions

Steps to address findings for McKesson

  1. 1

    Resolve the infrastructure port exposure ambiguity within 30 days: contact McKesson's security team (security@mckesson.com or through their vendor portal) and request written confirmation on whether ports 3306 (MySQL), 3389 (RDP), and 9200 (Elasticsearch) belong to CDN edge infrastructure or McKesson-owned backend systems. Ask for a current penetration test executive summary or third-party attestation. Do not approve high data access workflows until this is answered.

  2. 2

    Request McKesson's SOC 2 Type II report directly — email their security or compliance team and ask for the most recent report (dated within the last 12 months) plus a bridge letter if the report period ended more than 6 months ago. Many enterprise vendors make this available via a signed NDA. Check whether McKesson maintains a trust center at trust.mckesson.com or security.mckesson.com, as these pages were not reachable at time of scan.

  3. 3

    Obtain McKesson's AI data processing addendum before connecting any sensitive data to their Ontada or AI-enabled products. Specifically require clarity on: (a) training data use, (b) retention periods for AI-processed data, (c) contractual flow-down terms with OpenAI and Microsoft Azure AI subprocessors. Attach this to your data processing agreement before go-live.

  4. 4

    Request McKesson's subprocessor list and establish a change notification mechanism. Send a formal written request to their DPO or privacy team asking for a complete Article 28-compliant subprocessor disclosure and requesting 30-day advance notice of material subprocessor additions. Document the request and any response in your vendor risk register.

  5. 5

    Independently verify HITRUST certification status by searching the HITRUST Alliance certified entity directory at directory.hitrustalliance.net and searching for 'McKesson'. If confirmed, this is a meaningful positive compliance signal for healthcare-adjacent workloads. If unconfirmed, note the gap in your vendor risk register.

  6. 6

    Separately scan the application domain (my.mckesson.com) using HTTP security scanner (observatory.mozilla.org) to assess security headers on the authenticated application environment, as the marketing site grade of C+ may not reflect the actual application security posture. Document findings alongside this report.

Intelligence Sources Queried

24 sources in this assessment

21of 24 sources returned data
IP Reputation
AI Data Usage Policy
Threat Intelligence (OTX)
Certification Registry Verification
Domain Analysis
FDIC Institution Check
Business Registration
Tech Community Sentiment
Company Intelligence
Adverse Media Scan (Fallback)
HTTP Security Scan
Sanctions & Watchlist Screening
Malware & Phishing Check
SEC Filing Search
Infrastructure Exposure
SSL/TLS Analysis
Supply Chain & Subprocessor Discovery
Trust & Compliance Page Scan
Website Security Scan
Web Archive History
Domain Registration
Certificate Transparency
Historical Media Search
Threat Intelligence

Data Coverage Notes

Some data sources may have had limited availability during this assessment. This does not reflect negatively on the vendor.

  • Certificate Transparency log data (Certificate Transparency service) was unavailable during this investigation; certificate information was obtained via direct TLS handshake only. A full subdomain enumeration from CT logs was not possible, which may limit visibility into McKesson's full infrastructure surface.
  • Historical media search (covering adverse events beyond the 12-month primary scan window) was unavailable during this investigation. McKesson has a documented history of regulatory settlements (notably the opioid-related national settlement) that falls outside the scope of currently available evidence but is publicly known context buyers should independently review.
  • External cyber risk scoring was not available for this investigation. Independent quantitative scoring of McKesson's overall security posture relative to industry benchmarks could not be completed.
  • The application portal (my.mckesson.com) was detected but was not independently scanned for security headers or TLS configuration. The C+ marketing site grade may not reflect the security posture of the authenticated application environment.
  • SOC 2 certification evidence consists of an indirect signal (a job posting for a SOC Compliance Senior Analyst) rather than a formal trust page or published report. No independent registry confirmation of SOC 2 Type II certification was available.
  • The HITRUST directory match for McKesson returned 90% name confidence but was flagged as requiring manual verification due to possible entity collision. HITRUST certification status cannot be confirmed or denied based on available evidence.
183+
Vendors assessed
98%
Average confidence
<2 min
Time to report
What a ThirdProof assessment covers

Sanctions Screening

Is McKesson on any OFAC, EU, or UN sanctions list? Are any officers or affiliates flagged?

Cyber Risk Assessment

What is McKesson's security posture? Threat intelligence scanning, known vulnerabilities, and security header analysis.

Business Registration

Is McKesson a legitimately registered business entity? Corporate status, jurisdiction, and officer verification.

Adverse Media Analysis

Has McKesson appeared in negative news coverage? Data breaches, lawsuits, regulatory actions, and complaints.

Domain & Infrastructure

Is McKesson's website secure? TLS configuration, DNS hygiene, security headers, and domain age analysis.

Company Intelligence

What are McKesson's firmographics? Employee count, industry classification, technology stack, and corporate structure.

Trust & Compliance Verification

Does McKesson claim SOC 2, ISO 27001, HITRUST, or FedRAMP? ThirdProof scans trust pages for certification claims and cross-references the FedRAMP public registry for independent verification.

Supply Chain & Subprocessor Discovery

Who does McKesson depend on? ThirdProof discovers subprocessors from vendor-published pages and runs sanctions screening and safe browsing checks against each one.

Regulatory & Financial Filings

Has McKesson appeared in SEC enforcement filings? Is it associated with any FDIC bank failures? ThirdProof searches regulatory databases with entity verification to confirm attribution.

Full methodology, rule engine, and AI disclosure: /methodology

McKesson Healthcare Supply Chain Risk Context

McKesson Corporation (NYSE: MCK) is a Fortune 8 company operating as one of the largest pharmaceutical distributors and healthcare IT providers globally. McKesson's operations span pharmaceutical distribution, medical-surgical supplies, and healthcare technology solutions. The company's scale and position in the healthcare supply chain make it a critical vendor for hospitals, pharmacies, and healthcare systems. Organizations evaluating McKesson should assess HIPAA compliance, supply chain security, and the specific McKesson business unit providing services — each operates with distinct compliance profiles.

McKesson Security & Risk Posture

ThirdProof investigated McKesson across 27 intelligence sources and assigned a High Risk (Tier 2) rating with 90% confidence. Sanctions screening returned clear with no OFAC, EU, or UN matches. The High Risk tier reflects infrastructure exposure and supply chain transparency gaps rather than sanctions or regulatory enforcement concerns. As a publicly traded Fortune 8 company, McKesson provides financial transparency through SEC filings, but infrastructure security findings require documented risk acceptance in your vendor risk register.

Evaluate McKesson for Your Vendor Program

Your first 5 McKesson assessments are free — no credit card, no vendor participation required. ThirdProof queries 27 intelligence sources autonomously: OFAC SDN screening, business registration verification, adverse media analysis, infrastructure scanning, HIPAA-relevant security controls, and more. Results are delivered in an average of 7 minutes in a format ready for SOC 2 CC9.2, HIPAA, and healthcare vendor due diligence packages.

Seeing this in an audit? ThirdProof lets you investigate McKesson and every other vendor in your stack — average report time: 7 minutes. Get McKesson's Full Report Free →

Frequently asked about McKesson

Does McKesson have SOC 2 Type II?+
No SOC 2 found. McKesson rated High Risk — exposed services detected. See all 3 findings →
Is McKesson on the OFAC sanctions list?+
McKesson returned no matches in ThirdProof's OFAC SDN, EU Consolidated, and UN sanctions screening as of March 2026.
What is McKesson's vendor risk tier?+
ThirdProof assigned McKesson a risk tier of High Risk with 82% confidence based on assessment across 27 intelligence sources as of March 2026.
Why is McKesson rated High Risk?+
ThirdProof's assessment assigned McKesson a High Risk (Tier 2) rating with 90% confidence. The elevated risk rating reflects infrastructure exposure findings and supply chain transparency gaps — not sanctions or adverse media concerns. McKesson's scale as a Fortune 8 company and pharmaceutical distributor creates a large attack surface. Organizations should review the full assessment report for specific infrastructure findings and assess compensating controls.
Is McKesson HIPAA compliant?+
As a pharmaceutical distributor and healthcare IT provider processing PHI, McKesson is subject to HIPAA requirements. Organizations evaluating McKesson should request a Business Associate Agreement (BAA) and verify HIPAA compliance documentation for the specific McKesson products and services in use. ThirdProof's assessment evaluates McKesson's security posture across 27 intelligence sources as part of HIPAA vendor due diligence.
Does McKesson have SOC 2 certification?+
Organizations should request McKesson's current SOC 2 Type II report directly. Given McKesson's diverse product portfolio spanning pharmaceutical distribution and healthcare IT, verify that the SOC 2 scope covers the specific McKesson services your organization uses. SOC 2 reports are confidential and cannot be independently verified through a public registry.
Can I get an auto-filled security questionnaire for McKesson?+
Yes. Every ThirdProof investigation of McKesson produces two deliverables: an audit-ready risk report and a 133-question security questionnaire pre-filled with evidence from 27 independent sources. The questionnaire is mapped to SIG, SOC 2, HIPAA, PCI DSS and 9 other frameworks — answered without sending McKesson a single email or waiting for a vendor response.
Is McKesson safe to use as a vendor?+
McKesson is a healthcare IT vendor that handles protected health information (PHI). Safety depends on their current security posture, certification status, and how they handle your specific data. ThirdProof automates this evaluation across 27 intelligence sources — sanctions databases (OFAC, EU, UN), business registration verification, adverse media scanning, and cyber risk assessment — producing a deterministic risk tier with confidence score plus an auto-filled security questionnaire. Run a free investigation to see McKesson's full risk profile.
Does McKesson have SOC 2 certification?+
No SOC 2 found. McKesson rated High Risk — exposed services detected. See all 3 findings →
Is McKesson FedRAMP authorized?+
FedRAMP authorization is relevant for government contractors evaluating healthcare IT platforms. Based on ThirdProof's assessment, McKesson is not currently listed on the FedRAMP Marketplace. Organizations with federal compliance requirements should verify this directly and consider alternative vendors with FedRAMP authorization where required.
Has McKesson had any data breaches?+
Data breach history is an important signal for any vendor, particularly healthcare IT platforms like McKesson that handle protected health information (PHI). ThirdProof's adverse media analysis searches multiple news APIs and public records for data breaches, security incidents, lawsuits, regulatory enforcement actions, and financial distress signals. Each finding is linked to its original source with severity classification.
Is McKesson on any sanctions lists?+
Sanctions screening is standard due diligence for healthcare IT vendors. ThirdProof screens McKesson against OFAC SDN, consolidated international sanctions lists, and PEP databases. The screening uses entity name verification to reduce false positives. If McKesson or any associated officers appear on a sanctions list, this triggers automatic escalation to the highest risk tier.
How do I assess McKesson for vendor risk?+
Assessing McKesson as a healthcare IT vendor involves verifying HIPAA, SOC 2, and HITRUST compliance, reviewing their subprocessor chain, and checking sanctions exposure. ThirdProof automates this across 27 intelligence sources in an average of 7 minutes — no questionnaires or vendor participation required. Your first 5 investigations are free.
How long does a ThirdProof assessment take?+
A ThirdProof assessment completes in an average of 7 minutes. 27 intelligence sources are queried in parallel — sanctions databases, business registries, threat intelligence feeds, certificate transparency logs, and more. The result is a deterministic risk tier with confidence score and audit-ready PDF report.
Is ThirdProof free?+
ThirdProof offers 5 free vendor assessments with no credit card required. Each assessment includes the full report — risk tier, confidence score, individual findings, executive summary, and PDF export. Paid plans start at $399/month for teams that need ongoing vendor monitoring.
Can I use a ThirdProof report as SOC 2 audit evidence?+
Yes. ThirdProof reports are designed to satisfy SOC 2 CC9.2 (vendor risk management) requirements. Each report includes SHA-256 integrity verification, methodology disclosure, source attribution for every finding, and AI content labeling. Auditors can independently verify the report's authenticity and trace each finding to its original source.
How is ThirdProof different from a security questionnaire?+
Security questionnaires require vendor participation, take weeks, and produce self-reported answers. ThirdProof queries 27 independent intelligence sources — no vendor involvement needed. Risk tiers are assigned by a deterministic rules engine (not AI opinion), and every finding links to its original source. You get an audit-ready report in an average of 7 minutes instead of waiting weeks for a questionnaire response.

McKesson is in your vendor stack. Can you prove you assessed them?

SOC 2 CC9.2, HIPAA, PCI-DSS, and CMMC all require documented vendor due diligence — not just knowing the answer, but having audit-ready evidence you verified it. Most compliance teams can't produce that documentation on demand.

ThirdProof investigates McKesson across 27 intelligence sources in an average of 7 minutes — sanctions screening, cyber posture, SOC 2 verification, FedRAMP status, and more. Every investigation produces two deliverables: an audit-ready risk report and an auto-filled security questionnaire your prospects and auditors expect to see.

✓ 5 free investigations✓ Risk report + auto-filled questionnaire✓ No credit card required✓ Average report time: 7 minutes

Replaces $600–$900 in manual compliance consulting time per vendor assessed.