Comparison Overview

Tempus AI

VS

Thermo Fisher Scientific

Tempus AI

600 West Chicago Avenue Suite 510 Chicago, IL 60654, US
Last Update: 2025-11-27
Between 750 and 799

Tempus is making precision medicine a reality by applying AI in healthcare, deriving insights from our expansive library of clinical data and molecular data. We enable physicians to make real-time, data-driven decisions to deliver personalized care and targeted therapies for patients through our analytical machine learning platform that uses the power of artificial intelligence in healthcare. We also work with partners to facilitate discovery, development, and delivery of optimized therapeutic options for patients through distinctive solution sets. Our mission is for each patient to benefit from the treatment of others who came before by providing the healthcare industry tools that learn as we gather more data. It’s About Time. For more information, visit tempus.com and follow us on Twitter (@TempusLabs).

NAICS: 541714
NAICS Definition: Research and Development in Biotechnology (except Nanobiotechnology)
Employees: 1,001-5,000
Subsidiaries: 0
12-month incidents
0
Known data breaches
0
Attack type number
0

Thermo Fisher Scientific

168 Third Avenue, Waltham, MA, undefined, US
Last Update: 2025-11-25
Between 800 and 849

About Thermo Fisher Scientific Thermo Fisher Scientific Inc. is the world leader in serving science, with annual revenue of approximately $40 billion. Our Mission is to enable our customers to make the world healthier, cleaner and safer. Whether our customers are accelerating life sciences research, solving complex analytical challenges, increasing productivity in their laboratories, improving patient health through diagnostics or the development and manufacture of life-changing therapies, we are here to support them. Our global team delivers an unrivaled combination of innovative technologies, purchasing convenience and pharmaceutical services through our industry-leading brands, including Thermo Scientific, Applied Biosystems, Invitrogen, Fisher Scientific, Unity Lab Services, Patheon and PPD. For more information, please visit www.thermofisher.com.

NAICS: 541714
NAICS Definition: Research and Development in Biotechnology (except Nanobiotechnology)
Employees: 97,914
Subsidiaries: 18
12-month incidents
0
Known data breaches
1
Attack type number
1

Compliance Badges Comparison

Security & Compliance Standards Overview

https://images.rankiteo.com/companyimages/tempusai.jpeg
Tempus AI
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/thermo-fisher-scientific.jpeg
Thermo Fisher Scientific
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
Tempus AI
100%
Compliance Rate
0/4 Standards Verified
Thermo Fisher Scientific
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Biotechnology Research Industry Average (This Year)

No incidents recorded for Tempus AI in 2025.

Incidents vs Biotechnology Research Industry Average (This Year)

No incidents recorded for Thermo Fisher Scientific in 2025.

Incident History — Tempus AI (X = Date, Y = Severity)

Tempus AI cyber incidents detection timeline including parent company and subsidiaries

Incident History — Thermo Fisher Scientific (X = Date, Y = Severity)

Thermo Fisher Scientific cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/tempusai.jpeg
Tempus AI
Incidents

No Incident

https://images.rankiteo.com/companyimages/thermo-fisher-scientific.jpeg
Thermo Fisher Scientific
Incidents

Date Detected: 7/2017
Type:Breach
Attack Vector: Email Compromise
Blog: Blog

FAQ

Thermo Fisher Scientific company demonstrates a stronger AI Cybersecurity Score compared to Tempus AI company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Thermo Fisher Scientific company has historically faced a number of disclosed cyber incidents, whereas Tempus AI company has not reported any.

In the current year, Thermo Fisher Scientific company and Tempus AI company have not reported any cyber incidents.

Neither Thermo Fisher Scientific company nor Tempus AI company has reported experiencing a ransomware attack publicly.

Thermo Fisher Scientific company has disclosed at least one data breach, while Tempus AI company has not reported such incidents publicly.

Neither Thermo Fisher Scientific company nor Tempus AI company has reported experiencing targeted cyberattacks publicly.

Neither Tempus AI company nor Thermo Fisher Scientific company has reported experiencing or disclosing vulnerabilities publicly.

Neither Tempus AI nor Thermo Fisher Scientific holds any compliance certifications.

Neither company holds any compliance certifications.

Thermo Fisher Scientific company has more subsidiaries worldwide compared to Tempus AI company.

Neither Tempus AI nor Thermo Fisher Scientific holds SOC 2 Type 1 certification.

Neither Tempus AI nor Thermo Fisher Scientific holds SOC 2 Type 2 certification.

Neither Tempus AI nor Thermo Fisher Scientific holds ISO 27001 certification.

Neither Tempus AI nor Thermo Fisher Scientific holds PCI DSS certification.

Neither Tempus AI nor Thermo Fisher Scientific holds HIPAA certification.

Neither Tempus AI nor Thermo Fisher Scientific 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