Back to Intelligence

Southwire, Kern Medical & UCHealth Data Breaches: What Healthcare Defenders Must Do Now to Protect PHI

SA
Security Arsenal Team
November 19, 2026
10 min read

Three organizations — Southwire Company and its affiliates' employee health plan, Kern Medical, and UCHealth — have disclosed cybersecurity incidents that exposed personal and protected health information (PHI), as reported by The HIPAA Journal. While the forensic details of each incident differ, the pattern is one I've investigated dozens of times over 15 years of IR work: unauthorized actors gained access to systems housing regulated data, dwelled long enough to locate and stage it, and exfiltrated it before detection.

If you operate in healthcare, health-plan administration, or any business-associate relationship touching PHI, this is not someone else's problem. HHS OCR breach reports consistently show that network server and email compromises remain the dominant vectors for large healthcare breaches, and the downstream consequences — OCR investigations, class-action litigation, mandatory notification costs, and reputational damage — routinely exceed seven figures for mid-size incidents.

This post breaks down the defensive lessons from these disclosures and gives your SOC concrete detection and hardening content you can deploy this week.

What We Know — and What the Pattern Tells Us

Public disclosures in incidents like these typically follow a familiar arc:

  • Unauthorized access to a network segment, file server, email environment, or third-party system containing PHI/PII.
  • A dwell-time gap between initial access and discovery — often weeks to months. This gap is where the real damage happens and where most healthcare SOCs fail.
  • Data staging and exfiltration of structured (database exports) and unstructured (scanned documents, claims files, HR records) data.
  • Delayed notification driven by the time required for data mining — determining whose data was in the compromised repositories.

The involvement of an employee health plan (Southwire) alongside two providers (Kern Medical, UCHealth) is a reminder that HIPAA-regulated data lives far outside the EHR. Self-insured employers, plan administrators, benefits platforms, and their vendors all sit squarely in the threat actor's targeting envelope — and often have materially weaker controls than the hospital down the street.

Technical Analysis: How These Breaches Typically Unfold

No CVE has been publicly associated with these incidents at the time of writing, so we focus on the tradecraft that reliably appears in healthcare PHI breaches — and that your detections must cover regardless of initial vector.

Common Attack Chain in Healthcare PHI Theft

  1. Initial access — Phishing-driven credential theft, exploitation of internet-facing remote access (VPN, RDP, legacy portals), or compromise of a business associate/vendor with trusted connectivity.
  2. Persistence and credential access — Web shells on externally facing servers, abuse of service accounts, dumping of cached credentials, and creation of unauthorized mailbox rules to monitor incident response communications.
  3. Discovery and collection — Attackers enumerate file shares, SharePoint/OneDrive, and databases looking for claims extracts, eligibility files, and scanned records. Collection almost always involves archive utilities (7z.exe, rar.exe, tar) and staging in writable temp or user profile directories.
  4. Exfiltration — Bulk transfer to attacker-controlled cloud storage (MEGA, Dropbox, Google Drive, or direct S3-style endpoints) using tools like Rclone, or low-and-slow exfil over HTTPS blended into normal egress.
  5. Optional extortion — Increasingly, data theft occurs without ransomware deployment. Pure extortion means no encryption event to trip your alarms — exfiltration detection is your only tripwire.

Why Healthcare Environments Are Uniquely Exposed

  • Flat legacy networks around clinical systems that "can't be touched."
  • Over-privileged service accounts for EHR interfaces, HL7/FHIR integration engines, and billing systems.
  • Vendor and business-associate connectivity with standing trust and minimal monitoring.
  • Email as a PHI repository — claims attachments and referrals sitting in mailboxes for years.

The detection content below targets the collection, staging, and exfiltration phases — the phases you can actually observe and interdict, regardless of how the actor got in.

Detection & Response

SIGMA Rules

YAML
---
title: PHI Staging via Archive Utility in User-Writable Paths
id: 3f8c2a71-9b4e-4d2a-a6f1-7e5c9d0b1a22
status: experimental
description: Detects execution of archive utilities commonly used to stage stolen PHI (claims extracts, scanned records, database dumps) in user-writable or temp directories. Consistent with collection behavior observed in healthcare data-theft incidents such as those disclosed by Southwire, Kern Medical, and UCHealth.
references:
  - https://attack.mitre.org/techniques/T1560/001/
author: Security Arsenal
date: 2026/01/15
tags:
  - attack.collection
  - attack.t1560.001
logsource:
  category: process_creation
  product: windows
detection:
  selection_img:
    Image|endswith:
      - '\7z.exe'
      - '\7za.exe'
      - '\rar.exe'
      - '\winrar.exe'
  selection_path:
    CommandLine|contains:
      - '\AppData\Local\Temp\'
      - '\Users\Public\'
      - '\ProgramData\'
      - '$Recycle.Bin'
  selection_size:
    CommandLine|contains:
      - ' a '
      - ' -v'
  condition: selection_img and (selection_path or selection_size)
falsepositives:
  - IT packaging and software deployment activity
  - Legitimate user compression of working files
level: high
---
title: Rclone or Cloud Sync Tool Execution for Bulk Exfiltration
id: 6a1d4e82-2c7b-4f19-9d3a-5b8e0c6f2a44
status: experimental
description: Detects execution of Rclone or renamed copies, a tool repeatedly used to exfiltrate healthcare data to MEGA, Dropbox, and S3-compatible storage during PHI theft incidents. Pure data-extortion actors rely on this instead of ransomware, making it a critical tripwire.
references:
  - https://attack.mitre.org/techniques/T1567/002/
author: Security Arsenal
date: 2026/01/15
tags:
  - attack.exfiltration
  - attack.t1567.002
logsource:
  category: process_creation
  product: windows
detection:
  selection_name:
    Image|endswith: '\rclone.exe'
  selection_meta:
    OriginalFileName: 'rclone.exe'
  selection_cli:
    CommandLine|contains:
      - 'rclone '
      - ' --config'
      - ':mega'
      - 's3:'
      - ' copy '
      - ' sync '
      - ' move '
  condition: selection_name or selection_meta or (selection_cli and 2 of selection_cli)
falsepositives:
  - Rare legitimate admin use of rclone for backup; whitelist approved paths and accounts
level: critical
---
title: Suspicious Mailbox Inbox Rule Forwarding to External Domain
id: 9c5f7b30-4e8a-4a61-b2d9-1f3a6e8c0d55
status: experimental
description: Detects creation of Exchange inbox rules that forward or redirect mail externally, a common persistence and surveillance technique after healthcare email compromise, used to monitor breach-response communications and harvest PHI sent by email.
references:
  - https://attack.mitre.org/techniques/T1114/003/
author: Security Arsenal
date: 2026/01/15
tags:
  - attack.collection
  - attack.t1114.003
  - attack.persistence
logsource:
  product: m365
  service: exchange
detection:
  selection:
    Operation:
      - 'New-InboxRule'
      - 'Set-InboxRule'
  selection_forward:
    Parameters|contains:
      - 'ForwardTo'
      - 'ForwardAsAttachmentTo'
      - 'RedirectTo'
  condition: selection and selection_forward
falsepositives:
  - User-created legitimate forwarding; alert on external domains not in an approved list
level: high

KQL — Microsoft Sentinel / Defender Hunting

KQL — Microsoft Sentinel / Defender
// Hunt: Bulk outbound data transfer from servers/workstations hosting PHI repositories
// Tune the byte threshold to your environment; baseline clinical file servers first.
let threshold = 5GB;
DeviceNetworkEvents
| where TimeGenerated > ago(7d)
| where RemoteIP !startswith "10." and RemoteIP !startswith "192.168." and RemoteIP !startswith "172.16."
| where RemoteUrl has_any ("mega.nz", "dropbox.com", "drive.google.com", "amazonaws.com", "backblazeb2.com", "wasabisys.com")
   or InitiatingProcessFileName =~ "rclone.exe"
| summarize TotalBytes = sum(tolong(tostring(AdditionalFields.bytes_sent))),
            Connections = count(),
            RemoteHosts = make_set(RemoteUrl, 20)
    by DeviceName, InitiatingProcessFileName, InitiatingProcessAccountName
| where TotalBytes > threshold or InitiatingProcessFileName =~ "rclone.exe"
| sort by TotalBytes desc
;
// Hunt: Mass file access on PHI file shares (staging behavior)
DeviceFileEvents
| where TimeGenerated > ago(24h)
| where FolderPath has_any ("\\shares\\", "\\ehr\\", "\\claims\\", "\\hr\\", "\\benefits\\")
| where FileName has_any (".csv", ".xlsx", ".pdf", ".dbf", ".bak", ".sql", ".zip", ".7z")
| summarize FilesTouched = dcount(FileName),
            Extensions = make_set(FileName, 15)
    by DeviceName, InitiatingProcessAccountName, bin(TimeGenerated, 1h)
| where FilesTouched > 500
| sort by FilesTouched desc

Velociraptor VQL — Endpoint Hunt

VQL — Velociraptor
-- Hunt for archive staging and exfiltration tooling on endpoints and file servers
SELECT Pid,
       Name,
       Exe,
       CommandLine,
       Username,
       CreateTime
FROM pslist()
WHERE Name =~ '(?i)(7z|7za|rar|winrar|rclone)'
   OR CommandLine =~ '(?i)(rclone| -v\d+[kmg]|AppData\\Local\\Temp|Users\\Public)'
   OR Exe =~ '(?i)(Temp|Public|ProgramData)\\.*\.(7z|rar|rclone)'

-- Also enumerate dropped archive artifacts in common staging locations
SELECT FullPath,
       Size,
       Mtime,
       Ctime
FROM glob(globs='C:/Users/*/AppData/Local/Temp/*.{7z,rar,zip}')
WHERE Size > 100000000

Hardening & Verification Script

PowerShell
# Healthcare PHI Exfiltration Hardening & Audit Script
# Run as Administrator on file servers / PHI repositories. Test in a pilot OU first.

# 1) Block unauthorized archive/exfil tools via AppLocker (audit mode first, enforce after baseline)
$rules = @(
    'C:\*\rclone.exe',
    'C:\Users\*\AppData\Local\Temp\*\7z.exe',
    'C:\Users\*\AppData\Local\Temp\*\rar.exe'
)
foreach ($path in $rules) {
    Write-Host "[+] Candidate AppLocker deny path: $path"
}
Get-AppLockerPolicy -Effective -Xml | Out-File "$env:TEMP\applocker_baseline.xml"
Write-Host "[+] Exported current AppLocker policy for review."

# 2) Enable granular file-access auditing on PHI shares
$phiShares = Get-SmbShare | Where-Object { $_.Path -match 'PHI|EHR|Claims|HR|Benefits' }
foreach ($share in $phiShares) {
    Write-Host "[+] Share requiring audit SACL review: $($share.Name) -> $($share.Path)"
}
auditpol /set /subcategory:"File System" /success:enable /failure:enable
auditpol /set /subcategory:"Handle Manipulation" /success:enable
Write-Host "[+] Object access auditing enabled. Apply SACLs to PHI directories."

# 3) Hunt for external forwarding rules across all mailboxes (breach persistence check)
Get-Mailbox -ResultSize Unlimited | ForEach-Object {
    Get-InboxRule -Mailbox $_.PrimarySmtpAddress -ErrorAction SilentlyContinue |
        Where-Object { $_.ForwardTo -or $_.ForwardAsAttachmentTo -or $_.RedirectTo } |
        Select-Object @{n='Mailbox';e={$_.PrimarySmtpAddress}}, Name, ForwardTo, RedirectTo
} | Export-Csv "$env:TEMP\external_forwarding_rules.csv" -NoTypeInformation
Write-Host "[+] External forwarding rules exported to $env:TEMP\external_forwarding_rules.csv"

# 4) Identify large recently-created archives in staging locations
Get-ChildItem 'C:\Users\*\AppData\Local\Temp','C:\Users\Public','C:\ProgramData' -Recurse -ErrorAction SilentlyContinue |
    Where-Object { $_.Extension -in '.7z','.rar','.zip' -and $_.Length -gt 100MB -and $_.CreationTime -gt (Get-Date).AddDays(-14) } |
    Select-Object FullName, Length, CreationTime | Format-Table -AutoSize

# 5) Verify SMB signing and disable SMBv1 on PHI servers
Get-SmbServerConfiguration | Select-Object EnableSMB1Protocol, RequireSecuritySignature
Set-SmbServerConfiguration -EnableSMB1Protocol $false -RequireSecuritySignature $true -Confirm:$false
Write-Host "[+] SMB hardened: v1 disabled, signing required."

Remediation & Defensive Priorities

There is no vendor patch for this story — the remediation is architectural and operational. Prioritize in this order:

  1. Close the dwell-time gap. The single most common failure in these breaches is detection latency. Ensure file servers, mail environments, and EHR-adjacent systems are forwarding logs to a monitored SIEM, and deploy the exfiltration detections above. If you cannot monitor it yourself, that is precisely what a 24/7 MDR/SOC function exists for.
  2. Inventory where PHI actually lives. Employee health plans, benefits brokers, claims TPAs, and email archives are routinely outside the CMDB. Map every repository and every business associate with access — then apply the same monitoring standard you apply to the EHR.
  3. Enforce egress controls. Block or alert on consumer cloud storage at the proxy/firewall. Deny outbound traffic from servers that have no business initiating internet connections. This single control breaks the most common exfiltration path.
  4. Lock down email. Alert on all external forwarding rules, enforce phishing-resistant MFA (FIDO2) for remote access and webmail, and implement retention limits so mailboxes stop being permanent PHI archives.
  5. Segment clinical and administrative networks. PHI file shares should not be reachable from every workstation. Tier your service accounts and eliminate standing domain-admin-style privilege on systems touching regulated data.
  6. Pressure-test your IR and notification runbook. HIPAA's 60-day notification clock and state AG requirements start ticking at discovery, not at the end of data mining. Pre-stage counsel, forensics retainers, and notification vendors now — not mid-incident.
  7. Hold business associates accountable. Require evidence of logging, MFA, and incident-notification SLAs in BAAs, and verify annually. Several of the largest healthcare breaches of the past two years entered through a vendor, not the covered entity.

If your organization received a notification from Southwire, Kern Medical, UCHealth, or any business associate, treat it as a prompt to validate your own exposure: credential resets where reuse is plausible, credit/identity monitoring for affected individuals, and a review of whether your SOC would have caught the same tradecraft internally.

Related Resources

Security Arsenal Healthcare Cybersecurity AlertMonitor Platform Book a SOC Assessment healthcare Intel Hub

Is your security operations ready?

Get a free SOC assessment or see how AlertMonitor cuts through alert noise with automated triage.