Cross-source coverage
T1578.001 / ATT&CK
Modify Cloud Compute Infrastructure: Create Snapshot
3 rules across 1 source.
From MITRE ATT&CK 20.1
An adversary may create a snapshot or data backup within a cloud account to evade defenses. A snapshot is a point-in-time copy of an existing cloud compute component such as a virtual machine (VM), virtual hard drive, or volume. An adversary may leverage permissions to create a snapshot in order to bypass restrictions that prevent access to existing compute service infrastructure, unlike in Revert Cloud Instance where an adversary may revert to a snapshot to evade detection and remove evidence of their presence.
An adversary may Create Cloud Instance, mount one or more created snapshots to that instance, and then apply a policy that allows the adversary access to the created instance, such as a firewall policy that allows them inbound and outbound SSH access.
- Tactics
- Defense Impairment
- Platforms
- IaaS
- Telemetry
-
AWS:CloudTrail
How MITRE says to detect it DET0423
Detection Strategy for Modify Cloud Compute Infrastructure: Create Snapshot
IaaS Analytic 1187
Detection focuses on correlating snapshot creation events with subsequent instance creation and mounting activities. From a defender perspective, suspicious sequences include snapshot creation by unexpected or newly created IAM users, snapshots created from sensitive volumes without preceding change-control activity, or snapshots immediately followed by mounting to unauthorized instances. Cross-referencing with user behavior, IP geolocation, and automation context helps distinguish benign backup operations from adversary-driven snapshot exploitation.
AWS:CloudTrailCreateSnapshotAWS:CloudTrailDescribeSnapshots
elastic/detection-rules
3 rules| Detection | Severity | Format |
|---|---|---|
| AWS EC2 EBS Snapshot Created by Rare User | Low | Elastic TOML |
| Azure Compute Snapshot Created by Unusual Source ASN | Low | Elastic TOML |
| GCP Compute Snapshot Created by Rare User | Low | Elastic TOML |