Comparison Overview

Detroit Medical Center

VS

Labcorp

Detroit Medical Center

3990 John R, Detroit, Michigan, US, 48201
Last Update: 2025-11-26
Between 750 and 799

The Detroit Medical Center’s (DMC) record of service has provided medical excellence throughout the history of the Metropolitan Detroit area. From the founding of Children’s Hospital in 1886, to the creation of the first mechanical heart at Harper Hospital 50 years ago, to our compassion for the underserved, our legacy of caring is unmatched. Our medical experts are nationally recognized and each year, hundreds of DMC doctors are included in the list of America’s Best Doctors™. A reputation for excellence draws patients to world-class programs in oncology, organ transplant, cardiology, women’s services, neurosciences, stroke treatment, optometry, orthopaedics, pediatrics and rehabilitation. We are the leading academically integrated system in metropolitan Detroit and the largest health care provider in southeast Michigan. The DMC has more than 2,000 licensed beds and 3,000 affiliated physicians. Detroit Medical Center facilities employ best practices and conduct business in an atmosphere of respect and professionalism. Our recognition of and attention to diversity in our business operations and healthcare services in unparalleled. Our volunteer efforts in health education and disease prevention represent an ongoing commitment to the health and well-being of the communities we serve. The DMC continues to meet the health care needs of a growing community, offering the best in medical research and development, advanced technology and optimum clinical services.

NAICS: 62
NAICS Definition: Health Care and Social Assistance
Employees: 8,626
Subsidiaries: 46
12-month incidents
0
Known data breaches
5
Attack type number
3

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/detroitmedicalcenter.jpeg
Detroit Medical Center
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
Detroit Medical Center
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)

No incidents recorded for Detroit Medical Center in 2025.

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

No incidents recorded for Labcorp in 2025.

Incident History — Detroit Medical Center (X = Date, Y = Severity)

Detroit Medical Center 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/detroitmedicalcenter.jpeg
Detroit Medical Center
Incidents

Date Detected: 08/2022
Type:Cyber Attack
Attack Vector: Email Account Compromise
Motivation: Data Theft
Blog: Blog

Date Detected: 08/2022
Type:Breach
Attack Vector: Email Account Compromise
Blog: Blog

Date Detected: 06/2022
Type:Breach
Attack Vector: Malicious Code Injection
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

Detroit Medical Center company demonstrates a stronger AI Cybersecurity Score compared to Labcorp company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Detroit Medical Center company has faced a higher number of disclosed cyber incidents historically compared to Labcorp company.

In the current year, Labcorp company and Detroit Medical Center company have not reported any cyber incidents.

Both Labcorp company and Detroit Medical Center company have confirmed experiencing at least one ransomware attack.

Both Labcorp company and Detroit Medical Center company have disclosed experiencing at least one data breach.

Detroit Medical Center company has reported targeted cyberattacks, while Labcorp company has not reported such incidents publicly.

Neither Detroit Medical Center company nor Labcorp company has reported experiencing or disclosing vulnerabilities publicly.

Neither Detroit Medical Center nor Labcorp holds any compliance certifications.

Neither company holds any compliance certifications.

Detroit Medical Center company has more subsidiaries worldwide compared to Labcorp company.

Labcorp company employs more people globally than Detroit Medical Center company, reflecting its scale as a Hospitals and Health Care.

Neither Detroit Medical Center nor Labcorp holds SOC 2 Type 1 certification.

Neither Detroit Medical Center nor Labcorp holds SOC 2 Type 2 certification.

Neither Detroit Medical Center nor Labcorp holds ISO 27001 certification.

Neither Detroit Medical Center nor Labcorp holds PCI DSS certification.

Neither Detroit Medical Center nor Labcorp holds HIPAA certification.

Neither Detroit Medical Center nor Labcorp 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