Can create snapshots of EBS volumes and RDS instances.1
Create Snapshot T1578.001
- Tactic
- Defense Impairment
- Platform
- IaaS
- Version
- 2.0
- Created
- 09 June 2020
- Last modified
- 12 May 2026
- Contributor
- Praetorian
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.
Create Snapshot MITRE reference T1578.001
1 software entry is documented implementing this technique. MITRE files each as a tool or as malware; newest first, then by how many groups carry them.
All 1 software entries for this technique
Offense vs defense T1578.001
Is defensive coverage keeping up with adversary use? Eight counts, each ranked against all 697 ATT&CK techniques. Attack sits left, defense right, so a shape leaning left means adversaries are better documented here than defenders are equipped. Hover any spoke for its percentile and the share of techniques that have more. The timeline below shows when each side arrived.
Create Snapshot detection strategy DET0423
MITRE names one behaviour worth catching for this technique and breaks it into 1 analytic, one per platform. Each carries the log sources it needs and the fields you tune per environment.
Detection Strategy for Modify Cloud Compute Infrastructure: Create Snapshot
AN1187 · IaaS
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.
Log sources
The data this analytic draws on. You do not need every component — each one you already collect covers part of it. Each links to its ATT&CK record.
| Data component | Name | Channel |
|---|---|---|
| Snapshot CreationDC0057 | AWS:CloudTrail | CreateSnapshot |
| Snapshot MetadataDC0062 | AWS:CloudTrail | DescribeSnapshots |
Tunable fields
MITRE calls these the analytic’s mutable elements: the thresholds and filters you set for your own environment.
| Field | What you tune |
|---|---|
| UserContext | IAM user, service account, or role performing snapshot creation. Tuned to allowlist known backup automation services. |
| TimeWindow | Frequency of snapshot creation in a defined period. Adjusted for environments with frequent automated backups. |
| GeoLocation | Unusual regions or IPs from which snapshot creation API calls originate. Helps identify cross-region snapshot abuse. |
| VolumeSensitivity | Tagging or classification of volumes being snapshotted. Tuned to prioritize alerts when sensitive volumes are copied. |
Routinely check user permissions to ensure only the expected users have the capability to create snapshots and backups.
Limit permissions for creating snapshots or backups in accordance with least privilege. Organizations should limit the number of users within the organization with an IAM role that has administrative privileges, strive to reduce all permanent privileged role assignments, and conduct periodic entitlement reviews on IAM users, roles and policies.
Tests from Atomic Red Team (MIT licence) · technique definition