Comparison Overview

McKesson

VS

Johnson & Johnson

McKesson

6555 State Highway 161, Irving, Texas, 75039, US
Last Update: 2025-12-09
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

Johnson & Johnson

New Brunswick, NJ, US, 08903
Last Update: 2025-12-09
Between 750 and 799

At Johnson & Johnson, we believe health is everything. As a focused healthcare company, with expertise in Innovative Medicine and MedTech, we’re empowered to tackle the world’s toughest health challenges, innovate through science and technology, and transform patient care. ​ All of this is possible because of our people. We’re passionate innovators who put people first, and through our purpose-driven culture and talented workforce, we are stronger than ever. ​ Learn more at https://www.jnj.com. Community Guidelines: http://www.jnj.com/social-media-community-guidelines

NAICS: 62
NAICS Definition: Health Care and Social Assistance
Employees: 108,305
Subsidiaries: 8
12-month incidents
1
Known data breaches
4
Attack type number
1

Compliance Badges Comparison

Security & Compliance Standards Overview

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
https://images.rankiteo.com/companyimages/johnson-&-johnson.jpeg
Johnson & Johnson
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
McKesson
100%
Compliance Rate
0/4 Standards Verified
Johnson & Johnson
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 McKesson in 2025.

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

Johnson & Johnson has 20.48% more incidents than the average of same-industry companies with at least one recorded incident.

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

McKesson cyber incidents detection timeline including parent company and subsidiaries

Incident History — Johnson & Johnson (X = Date, Y = Severity)

Johnson & Johnson cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/mckesson.jpeg
McKesson
Incidents

No Incident

https://images.rankiteo.com/companyimages/johnson-&-johnson.jpeg
Johnson & Johnson
Incidents

Date Detected: 7/2025
Type:Breach
Motivation: Financial Gain
Blog: Blog

Date Detected: 8/2024
Type:Breach
Attack Vector: Hacking
Blog: Blog

Date Detected: 6/2023
Type:Breach
Motivation: Financial Gain (Plaintiffs), Corporate Accountability, Consumer Protection
Blog: Blog

FAQ

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

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

In the current year, Johnson & Johnson company has reported more cyber incidents than McKesson company.

Neither Johnson & Johnson company nor McKesson company has reported experiencing a ransomware attack publicly.

Johnson & Johnson company has disclosed at least one data breach, while McKesson company has not reported such incidents publicly.

Neither Johnson & Johnson company nor McKesson company has reported experiencing targeted cyberattacks publicly.

Neither McKesson company nor Johnson & Johnson company has reported experiencing or disclosing vulnerabilities publicly.

Neither McKesson nor Johnson & Johnson holds any compliance certifications.

Neither company holds any compliance certifications.

McKesson company has more subsidiaries worldwide compared to Johnson & Johnson company.

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

Neither McKesson nor Johnson & Johnson holds SOC 2 Type 1 certification.

Neither McKesson nor Johnson & Johnson holds SOC 2 Type 2 certification.

Neither McKesson nor Johnson & Johnson holds ISO 27001 certification.

Neither McKesson nor Johnson & Johnson holds PCI DSS certification.

Neither McKesson nor Johnson & Johnson holds HIPAA certification.

Neither McKesson nor Johnson & Johnson holds GDPR certification.

Latest Global CVEs (Not Company-Specific)

Description

FreePBX Endpoint Manager is a module for managing telephony endpoints in FreePBX systems. Versions prior to 16.0.96 and 17.0.1 through 17.0.9 have a weak default password. By default, this is a 6 digit numeric value which can be brute forced. (This is the app_password parameter). Depending on local configuration, this password could be the extension, voicemail, user manager, DPMA or EPM phone admin password. This issue is fixed in versions 16.0.96 and 17.0.10.

Risk Information
cvss4
Base: 6.9
Severity: LOW
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/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

Neuron is a PHP framework for creating and orchestrating AI Agents. In versions 2.8.11 and below, the MySQLWriteTool executes arbitrary SQL provided by the caller using PDO::prepare() + execute() without semantic restrictions. This is consistent with the name (“write tool”), but in an LLM/agent context it becomes a high-risk capability: prompt injection or indirect prompt manipulation can cause execution of destructive queries such as DROP TABLE, TRUNCATE, DELETE, ALTER, or privilege-related statements (subject to DB permissions). Deployments that expose an agent with MySQLWriteTool enabled to untrusted input and/or run the tool with a DB user that has broad privileges are impacted. This issue is fixed in version 2.8.12.

Risk Information
cvss3
Base: 9.4
Severity: LOW
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:H
Description

Neuron is a PHP framework for creating and orchestrating AI Agents. Versions 2.8.11 and below use MySQLSelectTool, which is vulnerable to Read-Only Bypass. MySQLSelectTool is intended to be a read-only SQL tool (e.g., for LLM agent querying, however, validation based on the first keyword (e.g., SELECT) and a forbidden-keyword list does not block file-writing constructs such as INTO OUTFILE / INTO DUMPFILE. As a result, an attacker who can influence the tool input (e.g., via prompt injection through a public agent endpoint) may write arbitrary files to the DB server if the MySQL/MariaDB account has the FILE privilege and server configuration permits writes to a useful location (e.g., a web-accessible directory). This issue is fixed in version 2.8.12.

Risk Information
cvss3
Base: 8.2
Severity: LOW
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:N
Description

Okta Java Management SDK facilitates interactions with the Okta management API. In versions 11.0.0 through 20.0.0, race conditions may arise from concurrent requests using the ApiClient class. This could cause a status code or response header from one request’s response to influence another request’s response. This issue is fixed in version 20.0.1.

Risk Information
cvss3
Base: 8.4
Severity: HIGH
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:L
Description

The Auth0 Next.js SDK is a library for implementing user authentication in Next.js applications. When using versions 4.11.0 through 4.11.2 and 4.12.0, simultaneous requests on the same client may result in improper lookups in the TokenRequestCache for the request results. This issue is fixed in versions 4.11.2 and 4.12.1.

Risk Information
cvss3
Base: 5.4
Severity: HIGH
CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:H/I:L/A:N