Comparison Overview

FERGUSON MEDICAL GROUP, LP

VS

Duke University Health System

FERGUSON MEDICAL GROUP, LP

1012 North Main Street, None, Sikeston, Missouri, US, 63801
Last Update: 2025-11-28

Ferguson Medical Group is a premier multi-specialty healthcare group dedicated to providing quality state-of-the-art medical services in a caring, compassionate and professional atmosphere. We are committed to services, innovation and quality care while serving the complete medical needs of the Southeastern Missouri area.

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

Duke University Health System

2301 Erwin Road, Durham, North Carolina, US, 27710
Last Update: 2025-11-21
Between 750 and 799

As a world-class academic and health care system, Duke Health strives to transform medicine and health locally and globally through innovative scientific research, rapid translation of breakthrough discoveries, educating future clinical and scientific leaders, advocating and practicing evidence-based medicine to improve community health, and leading efforts to eliminate health inequalities.

NAICS: 62
NAICS Definition: Health Care and Social Assistance
Employees: 11,647
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/ferguson-medical-group-lp.jpeg
FERGUSON MEDICAL GROUP, LP
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/duke-university-health-system.jpeg
Duke University Health System
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
FERGUSON MEDICAL GROUP, LP
100%
Compliance Rate
0/4 Standards Verified
Duke University Health System
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 FERGUSON MEDICAL GROUP, LP in 2025.

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

No incidents recorded for Duke University Health System in 2025.

Incident History — FERGUSON MEDICAL GROUP, LP (X = Date, Y = Severity)

FERGUSON MEDICAL GROUP, LP cyber incidents detection timeline including parent company and subsidiaries

Incident History — Duke University Health System (X = Date, Y = Severity)

Duke University Health System cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/ferguson-medical-group-lp.jpeg
FERGUSON MEDICAL GROUP, LP
Incidents

Date Detected: 9/2018
Type:Ransomware
Motivation: Monetary ransom
Blog: Blog
https://images.rankiteo.com/companyimages/duke-university-health-system.jpeg
Duke University Health System
Incidents

No Incident

FAQ

Duke University Health System company demonstrates a stronger AI Cybersecurity Score compared to FERGUSON MEDICAL GROUP, LP company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

FERGUSON MEDICAL GROUP, LP company has historically faced a number of disclosed cyber incidents, whereas Duke University Health System company has not reported any.

In the current year, Duke University Health System company and FERGUSON MEDICAL GROUP, LP company have not reported any cyber incidents.

FERGUSON MEDICAL GROUP, LP company has confirmed experiencing a ransomware attack, while Duke University Health System company has not reported such incidents publicly.

Neither Duke University Health System company nor FERGUSON MEDICAL GROUP, LP company has reported experiencing a data breach publicly.

Neither Duke University Health System company nor FERGUSON MEDICAL GROUP, LP company has reported experiencing targeted cyberattacks publicly.

Neither FERGUSON MEDICAL GROUP, LP company nor Duke University Health System company has reported experiencing or disclosing vulnerabilities publicly.

Neither FERGUSON MEDICAL GROUP, LP nor Duke University Health System holds any compliance certifications.

Neither company holds any compliance certifications.

Duke University Health System company has more subsidiaries worldwide compared to FERGUSON MEDICAL GROUP, LP company.

Duke University Health System company employs more people globally than FERGUSON MEDICAL GROUP, LP company, reflecting its scale as a Hospitals and Health Care.

Neither FERGUSON MEDICAL GROUP, LP nor Duke University Health System holds SOC 2 Type 1 certification.

Neither FERGUSON MEDICAL GROUP, LP nor Duke University Health System holds SOC 2 Type 2 certification.

Neither FERGUSON MEDICAL GROUP, LP nor Duke University Health System holds ISO 27001 certification.

Neither FERGUSON MEDICAL GROUP, LP nor Duke University Health System holds PCI DSS certification.

Neither FERGUSON MEDICAL GROUP, LP nor Duke University Health System holds HIPAA certification.

Neither FERGUSON MEDICAL GROUP, LP nor Duke University Health System 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.