Comparison Overview
Personalis, Inc.

Personalis, Inc.
6600 Dumbarton Circle, Fremont, California, US, 94555
Last Update: 14/09/2026
At Personalis, we are transforming the active management of cancer through breakthrough personalized testing. We aim to drive a new paradigm for cancer management, guiding care from biopsy through the life of the patient. Our highly sensitive assays combine tumor-and-no...

Amgen
One Amgen Center Drive, Thousand Oaks, 91320, US
Last Update: 26/09/2026
Amgen harnesses the best of biology and technology to fight the world’s toughest diseases, and make people’s lives easier, fuller and longer. We helped establish the biotechnology industry, and we remain on the cutting-edge of innovation, using technology and human gene...
Compliance Ranges Comparison

Personalis, Inc.







Amgen






Benchmark & Cyber Underwriting Signals
Incidents vs Biotechnology Research Industry Avg (This Year)
Personalis, Inc. has 21.26% fewer incidents than the average of same-industry companies with at least one recorded incident.
Incidents vs Biotechnology Research Industry Avg (This Year)
Amgen has 1.96% fewer incidents than the average of all companies with at least one recorded incident.
Incident History - Personalis, Inc. (X = Date, Y = Severity)
Personalis, Inc. cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Amgen (X = Date, Y = Severity)
Amgen cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Personalis, Inc.

Amgen
FAQ
Latest Global CVEs
A vulnerability was detected in mathurvishal CloudClassroom-PHP-Project up to 5dadec098bfbbf3300d60c3494db3fb95b66e7be. This impacts an unknown function of the file viewresult.php. Performing a manipulation of the argument seno results in sql injection. Remote exploitation of the attack is possible. The exploit is now public and may be used. This product follows a rolling release approach for continuous delivery, so version details for affected or updated releases are not provided. The vendor was contacted early about this disclosure but did not respond in any way.
Uncontrolled Resource Consumption (CWE-400) in Elasticsearch can lead denial of service via Excessive Allocation (CAPEC-130)
Uncontrolled Resource Consumption (CWE-400) in Kibana can lead denial of service via Excessive Allocation (CAPEC-130)
Uncontrolled Resource Consumption (CWE-400) in Elasticsearch can lead denial of service via Excessive Allocation (CAPEC-130)
Uncontrolled Resource Consumption (CWE-400) in Elasticsearch can lead denial of service via Excessive Allocation (CAPEC-130)