Comparison Overview

BayMark Health Services

VS

Labcorp

BayMark Health Services

1720 Lakepointe Drive, Suite 117, Lewisville, TX, US, 75057
Last Update: 2025-11-28
Between 600 and 649

BayMark Health Services is North America’s largest provider of medication-assisted treatment (MAT) for substance use disorders, helping thousands of individuals on their path to recovery every day. Our service offerings include opioid treatment programs (OTP), office-based opioid treatment (OBOT) practices, outpatient and inpatient detox services, residential treatment centers and behavioral health services. Our aim is to help as many individuals as we can in need of substance use and mental health disorders.

NAICS: 62
NAICS Definition: Health Care and Social Assistance
Employees: 393
Subsidiaries: 0
12-month incidents
1
Known data breaches
1
Attack type number
2

Labcorp

531 South Spring Street, Burlington, North Carolina, US, 27215
Last Update: 2025-11-27
Between 750 and 799

Clear and confident health care decisions begin with questions. At Labcorp, we’re constantly in pursuit of answers. As a global leader of innovative and comprehensive laboratory services, we help doctors, hospitals, pharmaceutical companies, researchers and patients make clear and confident decisions. We provide insights and advance science to improve health and improve lives through our unparalleled diagnostics and drug development laboratory capabilities. Our more than 60,000 employees serve clients in over 100 countries, worked on over 80% of the new drugs approved by the FDA in 2022 and performed more than 600 million tests for patients around the world. Learn more about Labcorp (NYSE: LH) at www.labcorp.com.

NAICS: 62
NAICS Definition: Health Care and Social Assistance
Employees: 40,562
Subsidiaries: 1
12-month incidents
0
Known data breaches
3
Attack type number
2

Compliance Badges Comparison

Security & Compliance Standards Overview

https://images.rankiteo.com/companyimages/baymark-health-services.jpeg
BayMark Health Services
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/labcorp.jpeg
Labcorp
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
BayMark Health Services
100%
Compliance Rate
0/4 Standards Verified
Labcorp
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Hospitals and Health Care Industry Average (This Year)

BayMark Health Services has 33.33% more incidents than the average of same-industry companies with at least one recorded incident.

Incidents vs Hospitals and Health Care Industry Average (This Year)

No incidents recorded for Labcorp in 2025.

Incident History — BayMark Health Services (X = Date, Y = Severity)

BayMark Health Services cyber incidents detection timeline including parent company and subsidiaries

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

Labcorp cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/baymark-health-services.jpeg
BayMark Health Services
Incidents

Date Detected: 3/2025
Type:Ransomware
Motivation: Financial Gain
Blog: Blog

Date Detected: 9/2024
Type:Breach
Blog: Blog
https://images.rankiteo.com/companyimages/labcorp.jpeg
Labcorp
Incidents

Date Detected: 8/2018
Type:Breach
Attack Vector: Unauthorized Access
Blog: Blog

Date Detected: 8/2018
Type:Breach
Blog: Blog

Date Detected: 07/2018
Type:Breach
Motivation: Data Access
Blog: Blog

FAQ

Labcorp company demonstrates a stronger AI Cybersecurity Score compared to BayMark Health Services company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Labcorp company has faced a higher number of disclosed cyber incidents historically compared to BayMark Health Services company.

In the current year, BayMark Health Services company has reported more cyber incidents than Labcorp company.

Both Labcorp company and BayMark Health Services company have confirmed experiencing at least one ransomware attack.

Both Labcorp company and BayMark Health Services company have disclosed experiencing at least one data breach.

Neither Labcorp company nor BayMark Health Services company has reported experiencing targeted cyberattacks publicly.

Neither BayMark Health Services company nor Labcorp company has reported experiencing or disclosing vulnerabilities publicly.

Neither BayMark Health Services nor Labcorp holds any compliance certifications.

Neither company holds any compliance certifications.

Labcorp company has more subsidiaries worldwide compared to BayMark Health Services company.

Labcorp company employs more people globally than BayMark Health Services company, reflecting its scale as a Hospitals and Health Care.

Neither BayMark Health Services nor Labcorp holds SOC 2 Type 1 certification.

Neither BayMark Health Services nor Labcorp holds SOC 2 Type 2 certification.

Neither BayMark Health Services nor Labcorp holds ISO 27001 certification.

Neither BayMark Health Services nor Labcorp holds PCI DSS certification.

Neither BayMark Health Services nor Labcorp holds HIPAA certification.

Neither BayMark Health Services nor Labcorp holds GDPR certification.

Latest Global CVEs (Not Company-Specific)

Description

ThingsBoard in versions prior to v4.2.1 allows an authenticated user to upload malicious SVG images via the "Image Gallery", leading to a Stored Cross-Site Scripting (XSS) vulnerability. The exploit can be triggered when any user accesses the public API endpoint of the malicious SVG images, or if the malicious images are embedded in an `iframe` element, during a widget creation, deployed to any page of the platform (e.g., dashboards), and accessed during normal operations. The vulnerability resides in the `ImageController`, which fails to restrict the execution of JavaScript code when an image is loaded by the user's browser. This vulnerability can lead to the execution of malicious code in the context of other users' sessions, potentially compromising their accounts and allowing unauthorized actions.

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

Mattermost versions 11.0.x <= 11.0.2, 10.12.x <= 10.12.1, 10.11.x <= 10.11.4, 10.5.x <= 10.5.12 fail to to verify that the token used during the code exchange originates from the same authentication flow, which allows an authenticated user to perform account takeover via a specially crafted email address used when switching authentication methods and sending a request to the /users/login/sso/code-exchange endpoint. The vulnerability requires ExperimentalEnableAuthenticationTransfer to be enabled (default: enabled) and RequireEmailVerification to be disabled (default: disabled).

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

Mattermost versions 11.0.x <= 11.0.2, 10.12.x <= 10.12.1, 10.11.x <= 10.11.4, 10.5.x <= 10.5.12 fail to sanitize team email addresses to be visible only to Team Admins, which allows any authenticated user to view team email addresses via the GET /api/v4/channels/{channel_id}/common_teams endpoint

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

Exposure of email service credentials to users without administrative rights in Devolutions Server.This issue affects Devolutions Server: before 2025.2.21, before 2025.3.9.

Description

Exposure of credentials in unintended requests in Devolutions Server.This issue affects Server: through 2025.2.20, through 2025.3.8.