Suspicious Azure Compute Snapshot Creation via Activity Log

PremiumReviewedSigma · Medium · v1
Product
azure
Service
activitylogs
Author
HuntRule
Published
2026-11-02
Updated
2026-11-02

ATT&CK techniques

Defense Evasion → Collection
  1. Recon

  2. Resource Dev

  3. Initial Access

  4. Execution

  5. Persistence

  6. Priv Esc

  7. Cred Access

  8. Discovery

  9. Lateral Movement

  10. C2

  11. Exfiltration

  12. Impact

What it detects

This rule detects creation of a Microsoft.Compute snapshot recorded in the Azure Activity Log. It corresponds to cloud disk theft where an attacker snapshots a virtual machine disk before copying and attaching it elsewhere for collection. Detecting snapshot writes helps surface control-plane data theft against VM storage.

Related detections9 linkedT1005 — drag to rearrange
Suspicious Azure CLI Disk Snapshot and Copy for Data Theft
Malicious Velvet Ant Linux Backdoor and Credential Harvesting Artifacts (via file_event)
Malicious Browser Credential Dump File Drop by Phantom Stealer via file_event
Suspicious Cryptocurrency Wallet File Access by Stealer (via process_creation)
Suspicious PAN-OS Running Config Staged as Web Content via CVE-2024-3400
Suspicious Infostealer Log Artifacts Written to Disk (via file_event)
Possible macOS TCC Bypass via mdimport Loading Custom Spotlight Importer
Suspicious sqlcipher Decryption of Signal Database by WAVESIGN (via process_creation)
Suspicious Termination of Telegram Desktop Prior to Session Theft
Suspicious Azure Compute Snapshot Creation via Activity Log
Pivot detection · T1005 · 9 related

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