Comparison Overview

Thermo Fisher Scientific

VS

CSL

Thermo Fisher Scientific

168 Third Avenue, Waltham, MA, undefined, US
Last Update: 2025-12-18
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

CSL

655 Elizabeth St, Melbourne, 3000, AU
Last Update: 2025-12-17
Between 800 and 849

CSL is a leading global biopharma company with a dynamic portfolio of lifesaving medicines, including those that treat haemophilia and immune deficiencies, vaccines to prevent influenza, and therapies in iron deficiency, dialysis and nephrology. Since our start in 1916, we have been driven by our promise to save lives using the latest technologies. Today, CSL – including our businesses, CSL Behring, CSL Seqirus, and CSL Vifor – provides lifesaving products to patients in more than 100 countries and employs 29,000+ people. Our unique combination of commercial strength, R&D focus and operational excellence enables us to identify, develop and deliver innovations so our patients can live life to the fullest. See our community guidelines: https://bit.ly/3Bs17Ra

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

Compliance Badges Comparison

Security & Compliance Standards Overview

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
https://images.rankiteo.com/companyimages/csl.jpeg
CSL
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
Thermo Fisher Scientific
100%
Compliance Rate
0/4 Standards Verified
CSL
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Biotechnology Research Industry Average (This Year)

No incidents recorded for Thermo Fisher Scientific in 2025.

Incidents vs Biotechnology Research Industry Average (This Year)

No incidents recorded for CSL in 2025.

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

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

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

CSL cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

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
https://images.rankiteo.com/companyimages/csl.jpeg
CSL
Incidents

No Incident

FAQ

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

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

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

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

Thermo Fisher Scientific company has disclosed at least one data breach, while the other CSL company has not reported such incidents publicly.

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

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

Neither Thermo Fisher Scientific nor CSL holds any compliance certifications.

Neither company holds any compliance certifications.

Thermo Fisher Scientific company has more subsidiaries worldwide compared to CSL company.

Thermo Fisher Scientific company employs more people globally than CSL company, reflecting its scale as a Biotechnology Research.

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

Neither Thermo Fisher Scientific nor CSL holds SOC 2 Type 2 certification.

Neither Thermo Fisher Scientific nor CSL holds ISO 27001 certification.

Neither Thermo Fisher Scientific nor CSL holds PCI DSS certification.

Neither Thermo Fisher Scientific nor CSL holds HIPAA certification.

Neither Thermo Fisher Scientific nor CSL holds GDPR certification.

Latest Global CVEs (Not Company-Specific)

Description

n8n is an open source workflow automation platform. Versions starting with 0.211.0 and prior to 1.120.4, 1.121.1, and 1.122.0 contain a critical Remote Code Execution (RCE) vulnerability in their workflow expression evaluation system. Under certain conditions, expressions supplied by authenticated users during workflow configuration may be evaluated in an execution context that is not sufficiently isolated from the underlying runtime. An authenticated attacker could abuse this behavior to execute arbitrary code with the privileges of the n8n process. Successful exploitation may lead to full compromise of the affected instance, including unauthorized access to sensitive data, modification of workflows, and execution of system-level operations. This issue has been fixed in versions 1.120.4, 1.121.1, and 1.122.0. Users are strongly advised to upgrade to a patched version, which introduces additional safeguards to restrict expression evaluation. If upgrading is not immediately possible, administrators should consider the following temporary mitigations: Limit workflow creation and editing permissions to fully trusted users only; and/or deploy n8n in a hardened environment with restricted operating system privileges and network access to reduce the impact of potential exploitation. These workarounds do not fully eliminate the risk and should only be used as short-term measures.

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

FastAPI Users allows users to quickly add a registration and authentication system to their FastAPI project. Prior to version 15.0.2, the OAuth login state tokens are completely stateless and carry no per-request entropy or any data that could link them to the session that initiated the OAuth flow. `generate_state_token()` is always called with an empty `state_data` dict, so the resulting JWT only contains the fixed audience claim plus an expiration timestamp. On callback, the library merely checks that the JWT verifies under `state_secret` and is unexpired; there is no attempt to match the state value to the browser that initiated the OAuth request, no correlation cookie, and no server-side cache. Any attacker can hit `/authorize`, capture the server-generated state, finish the upstream OAuth flow with their own provider account, and then trick a victim into loading `.../callback?code=<attacker_code>&state=<attacker_state>`. Because the state JWT is valid for any client for \~1 hour, the victim’s browser will complete the flow. This leads to login CSRF. Depending on the app’s logic, the login CSRF can lead to an account takeover of the victim account or to the victim user getting logged in to the attacker's account. Version 15.0.2 contains a patch for the issue.

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

FileZilla Client 3.63.1 contains a DLL hijacking vulnerability that allows attackers to execute malicious code by placing a crafted TextShaping.dll in the application directory. Attackers can generate a reverse shell payload using msfvenom and replace the missing DLL to achieve remote code execution when the application launches.

Risk Information
cvss3
Base: 9.8
Severity: LOW
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
cvss4
Base: 8.5
Severity: LOW
CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/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

LDAP Tool Box Self Service Password 1.5.2 contains a password reset vulnerability that allows attackers to manipulate HTTP Host headers during token generation. Attackers can craft malicious password reset requests that generate tokens sent to a controlled server, enabling potential account takeover by intercepting and using stolen reset tokens.

Risk Information
cvss3
Base: 7.5
Severity: LOW
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
cvss4
Base: 8.6
Severity: LOW
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:H/VI:H/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

Kimai 1.30.10 contains a SameSite cookie vulnerability that allows attackers to steal user session cookies through malicious exploitation. Attackers can trick victims into executing a crafted PHP script that captures and writes session cookie information to a file, enabling potential session hijacking.

Risk Information
cvss3
Base: 9.8
Severity: LOW
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
cvss4
Base: 8.5
Severity: LOW
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:H/VI:H/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