AWS EC2 EBS Snapshot Created by Rare User
Identifies the first time, within a lookback window, an identity creates an EBS volume snapshot via the EC2 "CreateSnapshot" or "CreateSnapshots" APIs. Adversaries abuse snapshots to stage data for exfiltration (snapshot one or more volumes, then share or copy them to an attacker-controlled account) or to capture sensitive data from a compromised environment. This is a New Terms rule detecting a rare occurrence of the "cloud.account.id", "user.name", and "source.as.organization.name" tuple for this action.
Elastic rule (View on GitHub)
1[metadata]
2creation_date = "2026/11/11"
3integration = ["aws"]
4maturity = "production"
5updated_date = "2026/11/11"
6
7[rule]
8author = ["Elastic"]
9description = """
10Identifies the first time, within a lookback window, an identity creates an EBS volume snapshot via the EC2
11"CreateSnapshot" or "CreateSnapshots" APIs. Adversaries abuse snapshots to stage data for exfiltration (snapshot one or
12more volumes, then share or copy them to an attacker-controlled account) or to capture sensitive data from a compromised
13environment. This is a New Terms rule detecting a rare occurrence of the "cloud.account.id", "user.name", and
14"source.as.organization.name" tuple for this action.
15"""
16false_positives = [
17 """
18 Backup, disaster-recovery, and data-lifecycle automation routinely creates snapshots. Service-invoked calls (AWS
19 Backup, Data Lifecycle Manager) are excluded, but custom backup tooling or administrators taking ad hoc snapshots
20 may generate first-seen matches that warrant review.
21 """,
22]
23from = "now-6m"
24index = ["logs-aws.cloudtrail-*"]
25language = "kuery"
26license = "Elastic License v2"
27name = "AWS EC2 EBS Snapshot Created by Rare User"
28note = """## Triage and analysis
29
30> **Disclaimer**:
31> 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.
32
33### Investigating AWS EC2 EBS Snapshot Created by Rare User
34
35EBS snapshots are point-in-time copies of volumes. Adversaries use `CreateSnapshot` (single volume) or `CreateSnapshots` (all volumes attached to an instance) to snapshot target volumes and then use `ModifySnapshotAttribute` to share them with, or `CopySnapshot` to move them into, an attacker-controlled account, enabling data theft without reading the source instance directly.
36
37This rule uses [New Terms](https://www.elastic.co/guide/en/security/current/rules-ui-create.html#create-new-terms-rule) to detect when an identity creates a snapshot from an account, principal, and network-origin combination not seen in the configured history window.
38
39### Possible investigation steps
40
41- Confirm who `user.name` and `aws.cloudtrail.user_identity.arn` represent and whether snapshot creation (`CreateSnapshot` or `CreateSnapshots`) is expected for that principal.
42- Review `source.ip`, `source.as.organization.name`, and geolocation, and whether the call aligns with normal egress for that principal.
43- Inspect `aws.cloudtrail.request_parameters` for the source `volumeId` (`CreateSnapshot`) or `instanceSpecification` (`CreateSnapshots`) and whether the targeted volume or instance holds sensitive data.
44- Correlate with follow-on `ModifySnapshotAttribute` (shared with another account or made public), `CopySnapshot`, and `DescribeSnapshots` in the same session.
45
46### False positive analysis
47
48- Documented backup/DR roles or custom backup tooling taking snapshots; add exceptions by ARN if needed.
49- One-off administrator snapshots before maintenance; confirm the change window and operator.
50
51### Response and remediation
52
53- If unexpected, review any snapshot sharing or copy operations, revoke cross-account snapshot permissions, rotate credentials for the implicated principal, and tighten least privilege on EC2 snapshot APIs.
54
55### Additional information
56
57- **[AWS IR Playbooks](https://github.com/aws-samples/aws-incident-response-playbooks)**
58"""
59references = [
60 "https://docs.aws.amazon.com/AWSEC2/latest/APIReference/API_CreateSnapshot.html",
61 "https://docs.aws.amazon.com/AWSEC2/latest/APIReference/API_CreateSnapshots.html",
62 "https://hackingthe.cloud/aws/post_exploitation/copy_ebs_snapshot/",
63 "https://www.atomicredteam.io/docs/atomics/T1578.001",
64]
65risk_score = 21
66rule_id = "80d7c681-e7e1-43f3-acd9-750796806cf1"
67severity = "low"
68tags = [
69 "Domain: Cloud",
70 "Data Source: AWS",
71 "Data Source: Amazon Web Services",
72 "Platform: AWS",
73 "Data Source: AWS CloudTrail",
74 "Service: AWS EC2",
75 "Tactic: Defense Evasion",
76 "Rule Type: New Terms",
77 "Resources: Investigation Guide",
78]
79timestamp_override = "event.ingested"
80type = "new_terms"
81
82query = '''
83data_stream.dataset: "aws.cloudtrail"
84 and event.provider: "ec2.amazonaws.com"
85 and event.action: ("CreateSnapshot" or "CreateSnapshots")
86 and event.outcome: "success"
87 and source.ip: *
88 and not source.as.organization.name: (
89 "Google LLC" or "Amazon.com, Inc." or "Microsoft Corporation" or "GOOGLE-CLOUD-PLATFORM"
90 or "MICROSOFT-CORP-MSN-AS-BLOCK" or "AMAZON-AES" or "AMAZON-02"
91 )
92 and not aws.cloudtrail.user_identity.invoked_by: (
93 "backup.amazonaws.com" or "AWS Internal" or "dlm.amazonaws.com"
94 or "malware-protection.guardduty.amazonaws.com"
95 )
96'''
97
98
99[[rule.threat]]
100framework = "MITRE ATT&CK"
101[[rule.threat.technique]]
102id = "T1578"
103name = "Modify Cloud Compute Infrastructure"
104reference = "https://attack.mitre.org/techniques/T1578/"
105[[rule.threat.technique.subtechnique]]
106id = "T1578.001"
107name = "Create Snapshot"
108reference = "https://attack.mitre.org/techniques/T1578/001/"
109
110
111
112[rule.threat.tactic]
113id = "TA0005"
114name = "Defense Evasion"
115reference = "https://attack.mitre.org/tactics/TA0005/"
116
117[rule.investigation_fields]
118field_names = [
119 "@timestamp",
120 "user.name",
121 "user_agent.original",
122 "source.ip",
123 "source.as.organization.name",
124 "aws.cloudtrail.user_identity.arn",
125 "aws.cloudtrail.user_identity.type",
126 "aws.cloudtrail.user_identity.access_key_id",
127 "event.action",
128 "event.outcome",
129 "event.provider",
130 "cloud.account.id",
131 "cloud.region",
132 "aws.cloudtrail.request_parameters",
133]
134
135[rule.new_terms]
136field = "new_terms_fields"
137value = ["cloud.account.id", "user.name", "source.as.organization.name"]
138[[rule.new_terms.history_window_start]]
139field = "history_window_start"
140value = "now-7d"
Triage and analysis
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 AWS EC2 EBS Snapshot Created by Rare User
EBS snapshots are point-in-time copies of volumes. Adversaries use CreateSnapshot (single volume) or CreateSnapshots (all volumes attached to an instance) to snapshot target volumes and then use ModifySnapshotAttribute to share them with, or CopySnapshot to move them into, an attacker-controlled account, enabling data theft without reading the source instance directly.
This rule uses New Terms to detect when an identity creates a snapshot from an account, principal, and network-origin combination not seen in the configured history window.
Possible investigation steps
- Confirm who
user.nameandaws.cloudtrail.user_identity.arnrepresent and whether snapshot creation (CreateSnapshotorCreateSnapshots) is expected for that principal. - Review
source.ip,source.as.organization.name, and geolocation, and whether the call aligns with normal egress for that principal. - Inspect
aws.cloudtrail.request_parametersfor the sourcevolumeId(CreateSnapshot) orinstanceSpecification(CreateSnapshots) and whether the targeted volume or instance holds sensitive data. - Correlate with follow-on
ModifySnapshotAttribute(shared with another account or made public),CopySnapshot, andDescribeSnapshotsin the same session.
False positive analysis
- Documented backup/DR roles or custom backup tooling taking snapshots; add exceptions by ARN if needed.
- One-off administrator snapshots before maintenance; confirm the change window and operator.
Response and remediation
- If unexpected, review any snapshot sharing or copy operations, revoke cross-account snapshot permissions, rotate credentials for the implicated principal, and tighten least privilege on EC2 snapshot APIs.
Additional information
References
Related rules
- AWS EC2 Instance Launched With User Data by Rare User
- AWS EC2 NACL Entry Created or Replaced Allowing All Traffic by New Identity
- AWS EC2 CreateKeyPair by New Principal from Non-Cloud AS Organization
- AWS EC2 Network Access Control List Creation
- AWS EC2 Network Access Control List Deletion