Back to Intelligence

Medical Snooping Exposed: Detecting and Remediating Unauthorized Insider Access to EHR Systems

SA
Security Arsenal Team
November 16, 2026
13 min read

The UK Information Commissioner's Office (ICO) has received reports of over 300 cases of unauthorized insider access to medical records this year alone. These aren't external threat actors breaching perimeters — these are trusted insiders abusing legitimate access credentials to snoop on patient records. For healthcare security teams, this represents a critical blind spot: your monitoring is likely tuned for external threats while insiders with valid credentials quietly violate patient privacy and trigger regulatory violations.

Healthcare organizations face unique insider risk due to the sensitive nature of protected health information (PHI) combined with broad access requirements for clinical staff. A nurse might legitimately access thousands of patient records weekly, making it trivially easy to hide malicious snooping within normal workflows. Without behavioral analytics and access pattern monitoring, these violations go undetected until a patient complaint or audit exposes them.

Technical Analysis: The Insider Threat Vector

This threat does not involve a specific CVE or software vulnerability. Instead, it exploits the fundamental trust model of healthcare information systems. Electronic Health Record (EHR) platforms like Epic, Cerner, Allscripts, and Meditech are designed for rapid clinical access — a physician might need immediate access to any patient record during an emergency.

The attack chain is deceptively simple:

  1. Legitimate Authentication — Insider uses valid credentials to access the EHR system
  2. Unauthorized Query — Insider searches for or accesses patient records without a legitimate treatment relationship
  3. Data Exposure — PHI is viewed, potentially copied, photographed, or exfiltrated
  4. Detection Gap — Without access pattern monitoring, the activity appears as normal clinical workflow

Common insider snooping scenarios observed in healthcare breaches include:

  • Celebrity/VIP Snooping — Staff accessing records of public figures, executives, or high-profile patients
  • Personal Interest — Accessing records of family members, friends, neighbors, or romantic interests
  • Malicious Intent — Gathering information for stalking, harassment, identity theft, or extortion
  • Curiosity — Casual browsing of interesting cases without treatment justification
  • Financial Gain — Selling patient information or using it for insurance fraud

The regulatory exposure is severe. Under GDPR Article 32 and HIPAA Security Rule §164.312(b), organizations must implement audit controls and access monitoring. Failure to detect unauthorized access can result in regulatory fines, lawsuits from affected patients, and reputational damage. The UK's ICO can levy fines up to £17.5 million or 4% of annual global turnover under UK GDPR.

Detection & Response: Hunting for Medical Record Snooping

Detecting insider snooping requires a different approach than traditional security monitoring. You're not looking for exploit code or malware — you're looking for anomalies in legitimate user behavior.

Sigma Rules

The following Sigma rules target Windows Event Logs and Sysmon telemetry from EHR client workstations and application servers. These rules focus on access pattern anomalies rather than specific malicious binaries.

YAML
---
title: EHR Application Launch by Non-Clinical User
id: 8f4e2a91-7c3b-4d5e-9f1a-2b8c6d4e5a7f
status: experimental
description: Detects EHR application execution by users not assigned to clinical roles. Baseline your clinical staff groups before deployment.
references:
  - https://www.infosecurity-magazine.com/news/ico-300-reports-of-medical-snooping/
  - https://attack.mitre.org/techniques/T1078/
author: Security Arsenal
date: 2026/04/06
tags:
  - attack.privilege_escalation
  - attack.t1078
  - attack.collection
logsource:
  category: process_creation
  product: windows
detection:
  selection_ehr:
    Image|endswith:
      - '\Epic.exe'
      - '\Hyperspace.exe'
      - '\PowerChart.exe'
      - '\Cerner.exe'
      - '\Sunrise.exe'
      - '\Meditech.exe'
  selection_nonclinical:
    User|contains:
      - 'admin'
      - 'svc_'
      - 'helpdesk'
      - 'billing'
      - 'facilities'
  condition: selection_ehr and selection_nonclinical
falsepositives:
  - IT support staff troubleshooting EHR applications
  - Clinical informatics personnel
  - Application administrators performing maintenance
level: medium
---
title: Mass Patient Record Export via Clipboard
id: 3c7f9a2b-1d4e-4f5a-8b9c-6e2a5d8f1b4c
status: experimental
description: Detects high-frequency clipboard activity on EHR workstations, potentially indicating mass copying of patient data. Tune threshold based on clinical workflow.
references:
  - https://www.infosecurity-magazine.com/news/ico-300-reports-of-medical-snooping/
  - https://attack.mitre.org/techniques/T1115/
author: Security Arsenal
date: 2026/04/06
tags:
  - attack.collection
  - attack.t1115
  - attack.exfiltration
logsource:
  category: process_creation
  product: windows
detection:
  selection:
    Image|endswith:
      - '\Epic.exe'
      - '\Hyperspace.exe'
      - '\PowerChart.exe'
    CommandLine|contains:
      - 'PrintScreen'
      - 'SnippingTool'
      - 'Snip & Sketch'
falsepositives:
  - Clinical staff capturing screenshots for documentation
  - IT creating training materials
level: low
---
title: After-Hours EHR Access
id: 5e9b3c1f-8a7d-4e2f-9c6b-1a4d7e5f8c2a
status: experimental
description: Detects EHR application access during non-clinical hours (before 6 AM or after 8 PM). Requires tuning for shift-based clinical staff.
references:
  - https://www.infosecurity-magazine.com/news/ico-300-reports-of-medical-snooping/
  - https://attack.mitre.org/techniques/T1078/
author: Security Arsenal
date: 2026/04/06
tags:
  - attack.persistence
  - attack.t1078
  - attack.collection
logsource:
  category: process_creation
  product: windows
detection:
  selection:
    Image|endswith:
      - '\Epic.exe'
      - '\Hyperspace.exe'
      - '\PowerChart.exe'
      - '\Cerner.exe'
  timeframe:
    start: '22:00'
    end: '06:00'
  condition: selection
falsepositives:
  - Night shift clinical staff
  - On-call physicians
  - Emergency department personnel
level: low

KQL Hunt Queries (Microsoft Sentinel / Defender)

The following KQL queries hunt for suspicious EHR access patterns using Windows Security Events, Defender for Endpoint process telemetry, and application-specific logging.

KQL — Microsoft Sentinel / Defender
// Hunt 1: Identify users accessing EHR systems from unusual workstations
// Baseline normal user-workstation pairs over 30 days, then alert on deviations
let BaselinePeriod = 30d;
let DetectionPeriod = 1d;
let EHRProcesses = dynamic(["Epic.exe", "Hyperspace.exe", "PowerChart.exe", "Cerner.exe", "Sunrise.exe", "Meditech.exe"]);
let Baseline = DeviceProcessEvents
    | where TimeGenerated >= ago(BaselinePeriod) and TimeGenerated < ago(DetectionPeriod)
    | where FileName in~ (EHRProcesses)
    | summarize by AccountName, DeviceName;
DeviceProcessEvents
| where TimeGenerated >= ago(DetectionPeriod)
| where FileName in~ (EHRProcesses)
| extend AccountName = tolower(AccountName), DeviceName = tolower(DeviceName)
| where AccountName !in~ (Baseline | project AccountName) or DeviceName !in~ (Baseline | project DeviceName)
| summarize FirstAccess = min(TimeGenerated), ProcessCount = count() by AccountName, DeviceName, FileName
| project AccountName, DeviceName, FileName, FirstAccess, ProcessCount
| order by FirstAccess desc;

// Hunt 2: Detect rapid patient record access (velocity check)
// Assumes EHR application logs are ingested via custom log table or Windows Event Forwarding
// Adjust threshold based on clinical specialty (ED physicians access more records than specialists)
SecurityEvent
| where TimeGenerated >= ago(24h)
| where EventID == 4663  // An attempt was made to access an object
| where ObjectName contains "\\Patient Records\\" or ObjectName contains "\\EHR\\"
| summarize AccessCount = count(), UniquePatients = dcount(ObjectName) by Account, Computer
| where AccessCount > 200 or UniquePatients > 50  // Tune these thresholds
| project Account, Computer, AccessCount, UniquePatients
| order by AccessCount desc;

// Hunt 3: Detect EHR access followed immediately by screenshot tools or USB device insertion
let TimeWindow = 5m;
let EHRProcesses = dynamic(["Epic.exe", "Hyperspace.exe", "PowerChart.exe"]);
let CaptureTools = dynamic(["SnippingTool.exe", "ScreenSketch.exe", "ShareX.exe", "Greenshot.exe", "Lightshot.exe"]);
let EHRActivity = DeviceProcessEvents
    | where TimeGenerated >= ago(24h)
    | where FileName in~ (EHRProcesses)
    | project EHRTime = TimeGenerated, AccountName, DeviceName;
let CaptureActivity = DeviceProcessEvents
    | where TimeGenerated >= ago(24h)
    | where FileName in~ (CaptureTools)
    | project CaptureTime = TimeGenerated, AccountName, DeviceName, CaptureTool = FileName;
EHRActivity
| join kind=inner CaptureActivity on AccountName, DeviceName
| where CaptureTime between (EHRTime .. datetime_add('minute', 5, EHRTime))
| project AccountName, DeviceName, EHRTime, CaptureTime, CaptureTool
| order by CaptureTime desc;

Velociraptor VQL Hunt

The following VQL artifact hunts for evidence of patient data exfiltration via USB devices and clipboard artifacts on Windows endpoints.

VQL — Velociraptor
-- Hunt for USB device connections on EHR workstations
-- Cross-reference with EHR application usage to identify potential data exfiltration

LET usb_devices = SELECT 
    Key.LastWriteTime AS ConnectionTime,
    Key.Name AS DeviceInstanceID,
    Key.Data AS DeviceDescription
FROM glob(
    globs='HKEY_LOCAL_MACHINE\\SYSTEM\\CurrentControlSet\\Enum\\USBSTOR\\*\\*',
    accessor='registry'
)

LET ehr_processes = SELECT 
    Pid, 
    Name, 
    Exe, 
    Username, 
    CreateTime,
    CommandLine
FROM pslist()
WHERE Exe =~ '(Epic|Hyperspace|PowerChart|Cerner|Sunrise|Meditech)'

SELECT 
    ehr_processes.Username AS User,
    ehr_processes.Name AS EHRApplication,
    ehr_processes.CreateTime AS EHRStartTime,
    usb_devices.ConnectionTime AS USBConnectionTime,
    usb_devices.DeviceDescription AS USBDevice,
    ehr_processes.Exe AS EHRPath
FROM ehr_processes
JOIN usb_devices ON 1=1
WHERE timestamp(usb_devices.ConnectionTime) > timestamp(ehr_processes.CreateTime)
  AND timestamp(usb_devices.ConnectionTime) < timestamp(ehr_processes.CreateTime) + 3600
ORDER BY User, EHRStartTime DESC

Remediation Script: Implement EHR Access Monitoring

The following PowerShell script implements continuous monitoring of EHR application access and generates alerts for anomalous behavior patterns.

PowerShell
#Requires -RunAsAdministrator
# EHR Insider Threat Monitoring Script
# Deploys continuous monitoring for unauthorized EHR access patterns

# Configuration
$EHRProcesses = @("Epic.exe", "Hyperspace.exe", "PowerChart.exe", "Cerner.exe", "Sunrise.exe", "Meditech.exe")
$LogPath = "C:\SecurityLogs\EHR_Monitoring"
$AlertThreshold = 50  # Alert if user accesses more than 50 unique patients in 1 hour
$BaselineFile = "$LogPath\EHR_Baseline.json"

# Create logging directory
if (-not (Test-Path $LogPath)) {
    New-Item -Path $LogPath -ItemType Directory -Force
}

# Function to get current EHR sessions
function Get-EHRSession {
    $sessions = @()
    foreach ($process in $EHRProcesses) {
        $procs = Get-Process -Name $process.Replace('.exe','') -ErrorAction SilentlyContinue
        if ($procs) {
            foreach ($proc in $procs) {
                $owner = (Get-WmiObject Win32_Process -Filter "ProcessId=$($proc.Id)").GetOwner()
                $sessions += [PSCustomObject]@{
                    Timestamp = Get-Date
                    Username = "$($owner.Domain)\$($owner.User)"
                    ProcessName = $proc.ProcessName
                    ProcessId = $proc.Id
                    ComputerName = $env:COMPUTERNAME
                }
            }
        }
    }
    return $sessions
}

# Function to log EHR access
function Write-EHRLog {
    param($SessionData)
    $logFile = "$LogPath\EHR_Access_$(Get-Date -Format 'yyyyMMdd').csv"
    $SessionData | Export-Csv -Path $logFile -Append -NoTypeInformation
}

# Function to detect anomalous access patterns
function Detect-AnomalousAccess {
    param($Username)
    
    # Query Windows Event Log for file access (requires audit policy)
    $events = Get-WinEvent -FilterHashtable @{
        LogName='Security'
        ID=4663
        StartTime=(Get-Date).AddHours(-1)
    } -ErrorAction SilentlyContinue | Where-Object {
        $_.Message -match $Username
    }
    
    if ($events.Count -gt $AlertThreshold) {
        $alert = @{
            Timestamp = Get-Date
            Username = $Username
            AccessCount = $events.Count
            Severity = "HIGH"
            Message = "User $Username accessed $($events.Count) files in the last hour (threshold: $AlertThreshold)"
        }
        
        # Log alert
        $alertFile = "$LogPath\EHR_Alerts_$(Get-Date -Format 'yyyyMMdd').json"
        $alert | ConvertTo-Json | Out-File -FilePath $alertFile -Append
        
        # Send to SIEM (configure for your environment)
        # Send-Alert -Data $alert
        
        Write-Warning "ALERT: $($alert.Message)"
    }
}

# Main monitoring loop
Write-Host "Starting EHR Insider Threat Monitor..." -ForegroundColor Green
Write-Host "Logging to: $LogPath" -ForegroundColor Cyan

# Enable required audit policies (run once)
auditpol /set /subcategory:"File System" /success:enable /failure:enable
auditpol /set /subcategory:"Process Creation" /success:enable

while ($true) {
    $sessions = Get-EHRSession
    
    if ($sessions.Count -gt 0) {
        Write-EHRLog -SessionData $sessions
        
        # Analyze each session
        $sessions | Group-Object Username | ForEach-Object {
            Detect-AnomalousAccess -Username $_.Name
        }
    }
    
    Start-Sleep -Seconds 300  # Check every 5 minutes
}

# Additional hardening: Implement Windows Event Forwarding to central SIEM
# wecutil qc /q
# Configure subscription for Security Event 4663 from EHR workstations

Remediation: Comprehensive Insider Threat Program

Defending against medical record snooping requires a multi-layered approach combining technical controls, policy enforcement, and organizational culture change.

Immediate Actions (0-30 Days)

  1. Enable Comprehensive Audit Logging

    • Activate audit trails in your EHR platform (Epic: Audit Trail Logging, Cerner: Millennium Auditing, Meditech: Audit Log)
    • Enable Windows Security Event 4663 (File System auditing) on EHR database servers
    • Configure EHR application logging to capture:
      • User ID and role
      • Patient ID accessed
      • Timestamp and duration
      • Workstation/device identifier
      • Actions performed (view, edit, print, export)
  2. Deploy User Behavior Analytics (UBA)

    • Implement a UEBA solution (Microsoft Defender for Identity, Varonis, Securonix, Exabeam)
    • Establish baselines for clinical roles (ED physician vs. radiologist vs. nurse)
    • Alert on:
      • Access to records outside normal specialty
      • Access to VIP/celebrity patients (flag high-profile patients)
      • Access velocity anomalies (too many records in short time)
      • Access from unusual workstations or locations
      • Access during non-shift hours
  3. Implement "Break the Glass" Controls

    • Require justification for accessing records outside treatment relationship
    • Implement dual-authorization for accessing flagged VIP patients
    • Log and review all break-glass access within 24 hours
  4. Data Loss Prevention (DLP)

    • Deploy DLP rules blocking:
      • Email transmission of patient lists or multiple records
      • USB copying of EHR databases or exports
      • Cloud upload of files containing PHI patterns
      • Print jobs exceeding normal clinical volume

Short-Term Improvements (30-90 Days)

  1. Role-Based Access Control (RBAC) Refinement

    • Audit current access permissions — many organizations grant overly broad access
    • Implement minimum necessary access per HIPAA §164.502(b)
    • Segregate access by department, specialty, and treatment relationship
    • Remove access immediately upon role change or termination
  2. Automated Access Reviews

    • Quarterly review of all EHR access permissions
    • Semi-annual review of VIP patient access
    • Automated alerts when dormant accounts access EHR
  3. Privacy Monitoring Platform

    • Deploy dedicated healthcare privacy monitoring (Protenus, Imprivata FairWarning, Iatric Systems)
    • These platforms specialize in detecting anomalous EHR access patterns using ML
    • Integrate with HR systems to detect access to family members, coworkers

Long-Term Strategy (90+ Days)

  1. Insider Threat Program

    • Establish a formal insider threat program with HR, legal, compliance, and IT security
    • Develop clear policies defining unauthorized access and consequences
    • Conduct regular training emphasizing that all access is monitored
    • Implement mandatory reporting mechanisms for suspected snooping
  2. Continuous Monitoring and Analytics

    • Build SOC playbooks for investigating EHR access anomalies
    • Develop threat hunting queries specific to your EHR platform
    • Integrate EHR logs into SIEM for correlation with other security events
    • Establish KPIs: time-to-detect, false positive rate, investigation closure rate
  3. Culture and Deterrence

    • Publicize that all access is logged and audited (deterrent effect)
    • Conduct random audits and publicize findings (anonymized)
    • Implement progressive discipline for violations
    • Recognize that some "snooping" is legitimate (quality review, billing, research) — create clear approval workflows

Regulatory Compliance Considerations

HIPAA (US):

  • Security Rule §164.312(b) — Audit Controls (Required)
  • Security Rule §164.312(c) — Integrity controls
  • Security Rule §164.308(a)(1)(ii)(D) — Information system activity review
  • Breach Notification Rule §164.400-414 — Unauthorized access constitutes a breach

GDPR/UK GDPR:

  • Article 32 — Security of processing (appropriate technical measures)
  • Article 33 — Notification of personal data breach to supervisory authority (72 hours)
  • Article 34 — Communication of breach to data subject

State Laws (California, Texas, New York, etc.):

  • Many states have specific health data breach notification requirements
  • Some states (Texas Medical Records Privacy Act) are more stringent than HIPAA

Metrics and Reporting

Track the following metrics to measure program effectiveness:

  • Detection Rate: Number of unauthorized access incidents detected per quarter
  • Mean Time to Detect (MTTD): Hours from unauthorized access to detection
  • Mean Time to Respond (MTTR): Hours from detection to investigation closure
  • False Positive Rate: Percentage of alerts that are legitimate clinical access
  • Regulatory Incidents: Breaches requiring notification to HHS/ICO

Target benchmarks:

  • MTTD < 24 hours for high-risk access patterns
  • MTTR < 72 hours for investigation
  • False positive rate < 20% (higher rates indicate need for tuning)

Conclusion

The 300+ reports to the UK ICO represent only the tip of the iceberg — most insider snooping goes undetected or unreported. Healthcare organizations cannot rely solely on perimeter defenses when the threat actor has legitimate credentials and authorized access. The key to defense is behavioral analytics, comprehensive audit logging, and a culture of accountability.

Your EHR platform contains some of the most sensitive data in your organization. Implement the monitoring and detection controls outlined in this post, establish a formal insider threat program, and make it clear to all staff that access to patient records is logged, monitored, and audited. The privacy of your patients and the regulatory standing of your organization depend on it.

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.