Comparison Overview

bioMérieux

VS

ICON plc

bioMérieux

100, Allée Louis Pasteur, None, Marcy-l'Étoile, Auvergne-Rhône-Alpes, FR, 69280
Last Update: 2025-11-25
Between 750 and 799

A family-owned company, bioMérieux has grown to become a world leader in the field of in vitro diagnostics. Our entrepreneurial adventure, begun over a century ago, is driven by an unrelenting commitment to improve public health worldwide. Since 1963, we've been paving the way in the field of in vitro diagnostics and have contributed greatly to improving public health and making the world a healthier place. The solutions that our teams imagine, develop and manufacture are key to enable healthcare professionals and industry players to make confident decisions to improve patient outcome and ensure consumer safety.

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

ICON plc

ICON plc, Dublin, undefined, 18, IE
Last Update: 2025-11-20
Between 750 and 799

Since our foundation in Dublin, Ireland in 1990, our mission has been to help our clients to accelerate the development of drugs and devices that save lives and improve quality of life. We do this by delivering best in class information, solutions and performance, with an unyielding focus on quality at all times. We offer a full range of consulting, development and commercialisation services from a global network of offices in 53 countries. We focus our innovation on the factors that are critical to our clients – reducing time to market, reducing cost, and increasing quality – and our global team of experts has extensive experience in a broad range of therapeutic areas.

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

Compliance Badges Comparison

Security & Compliance Standards Overview

https://images.rankiteo.com/companyimages/biomerieux.jpeg
bioMérieux
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/icon-plc-2.jpeg
ICON plc
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
bioMérieux
100%
Compliance Rate
0/4 Standards Verified
ICON plc
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Biotechnology Research Industry Average (This Year)

No incidents recorded for bioMérieux in 2025.

Incidents vs Biotechnology Research Industry Average (This Year)

No incidents recorded for ICON plc in 2025.

Incident History — bioMérieux (X = Date, Y = Severity)

bioMérieux cyber incidents detection timeline including parent company and subsidiaries

Incident History — ICON plc (X = Date, Y = Severity)

ICON plc cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/biomerieux.jpeg
bioMérieux
Incidents

Date Detected: 6/2023
Type:Vulnerability
Attack Vector: Unauthorized Access
Blog: Blog
https://images.rankiteo.com/companyimages/icon-plc-2.jpeg
ICON plc
Incidents

No Incident

FAQ

ICON plc company demonstrates a stronger AI Cybersecurity Score compared to bioMérieux company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

bioMérieux company has historically faced a number of disclosed cyber incidents, whereas ICON plc company has not reported any.

In the current year, ICON plc company and bioMérieux company have not reported any cyber incidents.

Neither ICON plc company nor bioMérieux company has reported experiencing a ransomware attack publicly.

Neither ICON plc company nor bioMérieux company has reported experiencing a data breach publicly.

Neither ICON plc company nor bioMérieux company has reported experiencing targeted cyberattacks publicly.

bioMérieux company has disclosed at least one vulnerability, while ICON plc company has not reported such incidents publicly.

Neither bioMérieux nor ICON plc holds any compliance certifications.

Neither company holds any compliance certifications.

ICON plc company has more subsidiaries worldwide compared to bioMérieux company.

ICON plc company employs more people globally than bioMérieux company, reflecting its scale as a Biotechnology Research.

Neither bioMérieux nor ICON plc holds SOC 2 Type 1 certification.

Neither bioMérieux nor ICON plc holds SOC 2 Type 2 certification.

Neither bioMérieux nor ICON plc holds ISO 27001 certification.

Neither bioMérieux nor ICON plc holds PCI DSS certification.

Neither bioMérieux nor ICON plc holds HIPAA certification.

Neither bioMérieux nor ICON plc 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