Windows Event Log Detects Volume Shadow Copy Mounts (HarddiskVolumeShadowCopy, EventID 98)

Alerts when NTFS logs indicate a VSS (HarddiskVolumeShadowCopy) mount using EventID 98.

FreeReviewedSigma · Low · v2
Product
windows
Service
system
Author
Roberto Rodriguez @Cyb3rWard0g, Open Threat Research (OTR) (SigmaHQ), DRL 1.1
Published
2020-10-20
Updated
2026-07-31

ATT&CK techniques

Cred Access
  1. Recon

  2. Resource Dev

  3. Initial Access

  4. Execution

  5. Persistence

  6. Priv Esc

  7. Defense Evasion

  8. Discovery

  9. Lateral Movement

  10. Collection

  11. C2

  12. Exfiltration

  13. Impact

What it detects

This rule identifies attempts to mount a Volume Shadow Copy by matching Windows System events from the NTFS provider. The pattern looks specifically for device names containing HarddiskVolumeShadowCopy. Attackers may use Volume Shadow Copy mounting to access data from previous system states, making this telemetry useful for spotting potentially suspicious storage-based access.

Related detections9 linkedT1003.002 — drag to rearrange
Suspicious Registry Hive Dump via reg save to Disguised evt Files
Malicious NTDS Extraction from Volume Shadow Copy by RA World
Malicious Flax Typhoon SAM and SECURITY Registry Hive Dump via reg save (via process_creation)
Malicious Registry Hive Dump for Credential Access via reg save (via process_creation)
Suspicious Registry Hive Export of SAM and SECURITY for Credential Theft after FortiClient EMS Exploitation
Malicious Registry Hive Dump via reg save
Malicious SAM and SYSTEM Registry Hive Credential Dump via reg.exe (via process_creation)
Malicious Registry Hive Theft from Shadow Copy via Print LOLBIN
Malicious Volume Shadow Copy Access via Mklink to GLOBALROOT
Windows Event Log Detects Volume Shadow Copy Mounts (HarddiskVolumeShadowCopy, EventID 98)
Pivot detection · T1003.002 · 9 related

Changelog

v2
  1. v2
    Candidate ingested via manual entry.2026-07-31
  2. v1
    No changelog recorded for this version.2026-07-30

Detection content is published as a reviewed draft. Tune thresholds and exclusions against your own telemetry before enabling this rule for alerting.