Azure Compute Snapshot Created by Unusual Source ASN
Description
Identifies the creation of an Azure managed-disk snapshot ("Microsoft.Compute/snapshots/write"). Adversaries create snapshots of disks to stage data for exfiltration, copying or sharing the snapshot to an attacker-controlled scope without reading the source VM directly. This ES|QL rule normalizes the acting identity across user- and service-principal-initiated operations and excludes known cloud-provider egress networks.
Query · esql
FROM logs-azure.activitylogs-* METADATA _id, _version, _index
| WHERE event.dataset == "azure.activitylogs"
AND event.action == "MICROSOFT.COMPUTE/SNAPSHOTS/WRITE"
AND event.outcome == "success"
AND NOT COALESCE(source.as.organization.name, "none") IN
("Google LLC", "Amazon.com, Inc.", "Microsoft Corporation", "GOOGLE-CLOUD-PLATFORM",
"MICROSOFT-CORP-MSN-AS-BLOCK", "AMAZON-AES", "AMAZON-02")
| EVAL Esql.actor = COALESCE(user.name, azure.activitylogs.identity.authorization.evidence.principal_id)
| KEEP _id, _version, _index, @timestamp, Esql.actor, cloud.account.id, azure.resource.name, source.as.organization.name, event.action
Analyst notes
Disclaimer: This investigation guide was created using generative AI technology and has been reviewed to improve its accuracy and relevance. While every effort has been made to ensure its quality, we recommend validating the content and adapting it to suit your specific environment and operational needs.
Investigating Azure Compute Snapshot Created by Unusual Source ASN
Azure disk snapshots are point-in-time copies of managed disks. Adversaries create a snapshot of a target disk and then share or copy it to an attacker-controlled subscription or storage, enabling data theft without touching the source instance.
Possible investigation steps
- Identify the actor (
Esql.actor) and whether snapshot creation is expected for that principal. - Review the target disk/snapshot (
azure.resource.name) and whether it holds sensitive data. - Review
source.as.organization.nameand the source IP for the operation; confirm it aligns with normal egress. - Correlate with follow-on
Microsoft.Compute/snapshots/beginGetAccess/action(SAS export),CopySnapshot, or snapshot sharing in the same window.
False positive analysis
- Backup, disaster-recovery, and image-bake automation create snapshots routinely; baseline known automation identities and add exceptions.
Response and remediation
- If unexpected, revoke any snapshot SAS/export access, rotate the implicated principal's credentials, and tighten least privilege on
Microsoft.Compute/snapshots/*.