Comparison Overview
Johnson & Johnson Medical

Johnson & Johnson Medical
US
Last Update: 06/12/2025
Structuring and implementing international guidelines on corporate communications

Optum
11000 Optum Circle, Eden Prairie , 55344, US
Last Update: 03/09/2026
We’re evolving health care so everyone can have the opportunity to live their healthiest life. It’s why we put your unique needs at the heart of everything we do, making it easy and affordable to manage health and well-being. We are delivering the right care how and whe...
Compliance Ranges Comparison

Johnson & Johnson Medical







Optum






Benchmark & Cyber Underwriting Signals
Incidents vs Hospitals and Health Care Industry Avg (This Year)
No incidents recorded for Johnson & Johnson Medical in 2026.
Incidents vs Hospitals and Health Care Industry Avg (This Year)
No incidents recorded for Optum in 2026.
Incident History - Johnson & Johnson Medical (X = Date, Y = Severity)
Johnson & Johnson Medical cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Optum (X = Date, Y = Severity)
Optum cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Johnson & Johnson Medical

Optum
FAQ
Latest Global CVEs
Netskope was notified about a potential gap in Netskope Endpoint DLP (EPDLP) running on Windows systems. Successful exploitation of the gap could potentially allow a privileged user to send a crafted message to the EPDLP process port to trigger an integer overflow, leading to memory corruption. Successful exploitation would require the EPDLP module to be enabled in the client configuration, and that Memory Integrity is disabled. A successful exploit could potentially result in a denial-of-service, arbitrary code execution, or privilege escalation on the local machine.
Netskope was notified of an out-of-bounds heap read affecting the Endpoint DLP (EPDLP) service of the Netskope Client. A local standard user could potentially send a specially crafted message that is not properly validated with a bounds check, likely crashing the kernel driver handler. Successful exploitation could potentially crash the EPDLP service, temporarily interrupting DLP enforcement. A successful exploit could potentially also reveal per-boot memory layout information to unauthorized users.
IBM Db2 11.5.0 through 11.5.9, and 12.1.0 through 12.1.5 is vulnerable to a denial of service where a specific functionality on a Db2 server can be disabled by a privileged user under certain conditions.
IBM Db2 11.5.0 through 11.5.9, and 12.1.0 through 12.1.5 could allow an attacker with the ability to control or impersonate a DRDA server endpoint to execute arbitrary commands on Db2 clients due to a stack-based buffer overflow that improperly copies user-controlled data into a fixed-size stack buffer without bounds checking.
IBM Db2 11.5.0 through 11.5.9, and 12.1.0 through 12.1.5 could allow an authenticated user to send a specially crafted request to write arbitrary files on the system.