Comparison Overview

BioGeneticsRx

VS

AbbVie

BioGeneticsRx

Tampa, US
Last Update: 2025-05-04 (UTC)
Between 800 and 849

At BioGeneticsRx we want positive outcomes for patients + physicians. Using state-of-the-art equipment, our laboratory can process more than 100,000 tests per month. To maximize efficiency, our laboratory is located in Memphis, Tennessee within close proximity to the FedEx hub. Furthermore, Memphis is in the Kahaba Medicare District, which provides favorable reimbursement of most of our PGx tests. State-of-the-art pharmacogeomics testing The ONLY lab with real time analysis tool – CQ Live Platinum quality lab with illumnia DNA testing at the molecular level CLIA and PTan certifications Fast turnaround time Patient receives a QR code card to gain access to CQ Live for PGx results updated real time for life Medicare and Medicaid Approved Most HMO's and PPO's Approved State-of-the-art Medication Reconciliation Tool The CQ Live Medication Reconciliation Tool is the first-ever interactive tool that incorporates drug-to-gene and drug-to-drug interaction. The tool allows physicians to provide personalized care through the CQLive Portal that enhances the existing genetic reports currently on the market. The live portal takes into consideration lifestyle factors, concomitant therapies and genetic markers to ensure patients have the best therapeutic outcome. Every Other PGx Lab only offers a one time Static report. Contact Us Today Toll Free 800-222-5676

NAICS: 3254
NAICS Definition: Pharmaceutical and Medicine Manufacturing
Employees: 51-200
Subsidiaries: 0
12-month incidents
0
Known data breaches
0
Attack type number
0

AbbVie

1 Waukegan Road, None, North Chicago, Illinois, US, 60064
Last Update: 2025-09-15 (UTC)
Between 800 and 849

AbbVie is a global biopharmaceutical company focused on creating medicines and solutions that put impact first — for patients, communities, and our world. We aim to address complex health issues and enhance people's lives through our core therapeutic areas: immunology, oncology, neuroscience, eye care, aesthetics and other areas of unmet need. Learn more about us at www.abbvie.com and review our community guidelines at https://www.abbvie.com/social-media-community-guidelines.html.

NAICS: 3254
NAICS Definition: Pharmaceutical and Medicine Manufacturing
Employees: 58,020
Subsidiaries: 15
12-month incidents
0
Known data breaches
1
Attack type number
1

Compliance Badges Comparison

Security & Compliance Standards Overview

https://images.rankiteo.com/companyimages/defaultcompany.jpeg
BioGeneticsRx
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/abbvie.jpeg
AbbVie
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
BioGeneticsRx
100%
Compliance Rate
0/4 Standards Verified
AbbVie
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Pharmaceutical Manufacturing Industry Average (This Year)

No incidents recorded for BioGeneticsRx in 2025.

Incidents vs Pharmaceutical Manufacturing Industry Average (This Year)

No incidents recorded for AbbVie in 2025.

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

BioGeneticsRx cyber incidents detection timeline including parent company and subsidiaries

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

AbbVie cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/defaultcompany.jpeg
BioGeneticsRx
Incidents

No Incident

https://images.rankiteo.com/companyimages/abbvie.jpeg
AbbVie
Incidents

Date Detected: 06/2023
Type:Breach
Attack Vector: Exploitation of Vulnerability
Motivation: Financial gain
Blog: Blog

FAQ

AbbVie company demonstrates a stronger AI Cybersecurity Score compared to BioGeneticsRx company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

AbbVie company has historically faced a number of disclosed cyber incidents, whereas BioGeneticsRx company has not reported any.

In the current year, AbbVie company and BioGeneticsRx company have not reported any cyber incidents.

Neither AbbVie company nor BioGeneticsRx company has reported experiencing a ransomware attack publicly.

AbbVie company has disclosed at least one data breach, while BioGeneticsRx company has not reported such incidents publicly.

Neither AbbVie company nor BioGeneticsRx company has reported experiencing targeted cyberattacks publicly.

Neither BioGeneticsRx company nor AbbVie company has reported experiencing or disclosing vulnerabilities publicly.

Neither BioGeneticsRx nor AbbVie holds any compliance certifications.

Neither company holds any compliance certifications.

AbbVie company has more subsidiaries worldwide compared to BioGeneticsRx company.

AbbVie company employs more people globally than BioGeneticsRx company, reflecting its scale as a Pharmaceutical Manufacturing.

Neither BioGeneticsRx nor AbbVie holds SOC 2 Type 1 certification.

Neither BioGeneticsRx nor AbbVie holds SOC 2 Type 2 certification.

Neither BioGeneticsRx nor AbbVie holds ISO 27001 certification.

Neither BioGeneticsRx nor AbbVie holds PCI DSS certification.

Neither BioGeneticsRx nor AbbVie holds HIPAA certification.

Neither BioGeneticsRx nor AbbVie holds GDPR certification.

Latest Global CVEs (Not Company-Specific)

Description

Deck Mate 1 executes firmware directly from an external EEPROM without verifying authenticity or integrity. An attacker with physical access can replace or reflash the EEPROM to run arbitrary code that persists across reboots. Because this design predates modern secure-boot or signed-update mechanisms, affected systems should be physically protected or retired from service. The vendor has not indicated that firmware updates are available for this legacy model.

Risk Information
cvss4
Base: 7.0
Severity: LOW
CVSS:4.0/AV:P/AC:L/AT:N/PR:N/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

Deck Mate 2 lacks a verified secure-boot chain and runtime integrity validation for its controller and display modules. Without cryptographic boot verification, an attacker with physical access can modify or replace the bootloader, kernel, or filesystem and gain persistent code execution on reboot. This weakness allows long-term firmware tampering that survives power cycles. The vendor indicates that more recent firmware updates strengthen update-chain integrity and disable physical update ports to mitigate related attack avenues.

Risk Information
cvss4
Base: 7.0
Severity: LOW
CVSS:4.0/AV:P/AC:L/AT:N/PR:N/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

Deck Mate 2's firmware update mechanism accepts packages without cryptographic signature verification, encrypts them with a single hard-coded AES key shared across devices, and uses a truncated HMAC for integrity validation. Attackers with access to the update interface - typically via the unit's USB update port - can craft or modify firmware packages to execute arbitrary code as root, allowing persistent compromise of the device's integrity and deck randomization process. Physical or on-premises access remains the most likely attack path, though network-exposed or telemetry-enabled deployments could theoretically allow remote exploitation if misconfigured. The vendor confirmed that firmware updates have been issued to correct these update-chain weaknesses and that USB update access has been disabled on affected units.

Risk Information
cvss4
Base: 7.0
Severity: LOW
CVSS:4.0/AV:P/AC:L/AT:N/PR:N/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

Uncontrolled Resource Consumption vulnerability in Legion of the Bouncy Castle Inc. Bouncy Castle for Java FIPS bc-fips on All (API modules), Legion of the Bouncy Castle Inc. Bouncy Castle for Java LTS bcprov-lts8on on All (API modules) allows Excessive Allocation. This vulnerability is associated with program files core/src/main/jdk1.9/org/bouncycastle/crypto/fips/AESNativeCFB.Java, core/src/main/jdk1.9/org/bouncycastle/crypto/fips/AESNativeGCM.Java, core/src/main/jdk1.9/org/bouncycastle/crypto/fips/SHA256NativeDigest.Java, core/src/main/jdk1.9/org/bouncycastle/crypto/fips/AESNativeEngine.Java, core/src/main/jdk1.9/org/bouncycastle/crypto/fips/AESNativeCBC.Java, core/src/main/jdk1.9/org/bouncycastle/crypto/fips/AESNativeCTR.Java, core/src/main/jdk1.9/org/bouncycastle/crypto/engines/AESNativeCFB.Java, core/src/main/jdk1.9/org/bouncycastle/crypto/engines/AESNativeGCM.Java, core/src/main/jdk1.9/org/bouncycastle/crypto/engines/AESNativeEngine.Java, core/src/main/jdk1.9/org/bouncycastle/crypto/engines/AESNativeCBC.Java, core/src/main/jdk1.9/org/bouncycastle/crypto/engines/AESNativeGCMSIV.Java, core/src/main/jdk1.9/org/bouncycastle/crypto/engines/AESNativeCCM.Java, core/src/main/jdk1.9/org/bouncycastle/crypto/engines/AESNativeCTR.Java, core/src/main/jdk1.9/org/bouncycastle/crypto/digests/SHA256NativeDigest.Java, core/src/main/jdk1.9/org/bouncycastle/crypto/digests/SHA224NativeDigest.Java, core/src/main/jdk1.9/org/bouncycastle/crypto/digests/SHA3NativeDigest.Java, core/src/main/jdk1.9/org/bouncycastle/crypto/digests/SHAKENativeDigest.Java, core/src/main/jdk1.9/org/bouncycastle/crypto/digests/SHA512NativeDigest.Java, core/src/main/jdk1.9/org/bouncycastle/crypto/digests/SHA384NativeDigest.Java. This issue affects Bouncy Castle for Java FIPS: from 2.1.0 through 2.1.1; Bouncy Castle for Java LTS: from 2.73.0 through 2.73.7.

Risk Information
cvss4
Base: 5.9
Severity: LOW
CVSS:4.0/AV:L/AC:L/AT:P/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:P/AU:N/R:U/V:C/RE:M/U:Amber
Description

Wasmtime is a runtime for WebAssembly. In versions from 38.0.0 to before 38.0.3, the implementation of component-model related host-to-wasm trampolines in Wasmtime contained a bug where it's possible to carefully craft a component, which when called in a specific way, would crash the host with a segfault or assert failure. Wasmtime 38.0.3 has been released and is patched to fix this issue. There are no workarounds.

Risk Information
cvss4
Base: 2.1
Severity: HIGH
CVSS:4.0/AV:N/AC:H/AT:P/PR:L/UI:P/VC:N/VI:N/VA:L/SC:N/SI:N/SA:L/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