You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
[Rule Tunings] AWS DynamoDB new terms Rules (#5074)
* [Rule Tunings] AWS DynamoDB new terms Rules
### AWS DynamoDB Scan by Unusual User
- changed new terms field to use cloud.account.id and user.name combination to account for roles and users
- reduced execution window
- reduced history window
- small edits to description, IG and highlighted fields
### AWS DynamoDB Table Exported to S3
- removed inaccurate setup notes
- reduced history window
- small edits to description and highlighted fields
* Apply suggestions from code review
Copy file name to clipboardExpand all lines: rules/integrations/aws/exfiltration_dynamodb_scan_by_unusual_user.toml
+14-13Lines changed: 14 additions & 13 deletions
Original file line number
Diff line number
Diff line change
@@ -2,23 +2,23 @@
2
2
creation_date = "2025/03/13"
3
3
integration = ["aws"]
4
4
maturity = "production"
5
-
updated_date = "2025/03/13"
5
+
updated_date = "2025/09/08"
6
6
7
7
[rule]
8
8
author = ["Elastic"]
9
9
description = """
10
10
Identifies when an AWS DynamoDB table is scanned by a user who does not typically perform this action. Adversaries may
11
11
use the Scan operation to collect sensitive information or exfiltrate data from DynamoDB tables. This rule detects
12
12
unusual user activity by monitoring for the Scan action in CloudTrail logs. This is a New Terms rule that only flags
13
-
when this behavior is observed by the `aws.cloudtrail.user_identity.arn` for the first time in the last 14 days.
13
+
when this behavior is observed by a user or role for the first time.
14
14
"""
15
15
false_positives = [
16
16
"""
17
17
Legitimate users may scan DynamoDB tables for various reasons, such as data analysis or application functionality.
18
18
Ensure that the user has the necessary permissions and that the Scan operation is authorized before taking action.
19
19
""",
20
20
]
21
-
from = "now-9m"
21
+
from = "now-6m"
22
22
index = ["filebeat-*", "logs-aws.cloudtrail-*"]
23
23
language = "kuery"
24
24
license = "Elastic License v2"
@@ -29,12 +29,12 @@ note = """## Triage and analysis
29
29
30
30
This rule identifies when an AWS DynamoDB table is scanned by a user who does not typically perform this action. Adversaries may use the Scan operation to collect sensitive information or exfiltrate data from DynamoDB tables. This rule detects unusual user activity by monitoring for the Scan action in CloudTrail logs.
31
31
32
-
This is a [New Terms](https://www.elastic.co/guide/en/security/current/rules-ui-create.html#create-new-terms-rule) rule that only flags when this behavior is observed for the first time on a host in the last 14 days.
32
+
This is a [New Terms](https://www.elastic.co/guide/en/security/current/rules-ui-create.html#create-new-terms-rule) rule that only flags when this behavior is observed for the first time.
33
33
34
34
#### Possible Investigation Steps
35
35
36
36
- Identify the Actor: Review the `aws.cloudtrail.user_identity.arn` field to identify the user who requested the subscription. Verify if this actor typically performs such actions and has the necessary permissions. It may be unusual for this activity to originate from certain user types, such as an assumed role or federated user.
37
-
- Review the Source IP: Check the `source.address` field to determine the source of the request. If the request comes from an unexpected location or IP address, it may indicate a compromised account or unauthorized access.
37
+
- Review the Source IP: Check the `source.ip` field to determine the source of the request. If the request comes from an unexpected location or IP address, it may indicate a compromised account or unauthorized access.
38
38
- Analyze the Request Parameters: Examine the `aws.cloudtrail.request_parameters` field to understand the details of the Scan request. Look for any unusual parameters or patterns that may indicate malicious intent. This also details the DynamoDB table being scanned.
39
39
- Review Access Key: Check the `aws.cloudtrail.user_identity.access_key_id` field to identify the access key used for the request. Determine if this key is associated with a legitimate user or if it has been compromised.
40
40
@@ -53,7 +53,7 @@ This is a [New Terms](https://www.elastic.co/guide/en/security/current/rules-ui-
53
53
54
54
### Additional Information
55
55
56
-
For further guidance on managing and securing SNS topics in AWS environments, refer to the [AWS SNS documentation](https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/security.html) and AWS best practices for security.
56
+
For further guidance on managing and securing DynamoDB in AWS environments, refer to the [AWS DynamoDB documentation](https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/security.html) and AWS best practices for security.
Copy file name to clipboardExpand all lines: rules/integrations/aws/exfiltration_dynamodb_table_exported_to_s3.toml
+6-6Lines changed: 6 additions & 6 deletions
Original file line number
Diff line number
Diff line change
@@ -2,12 +2,12 @@
2
2
creation_date = "2025/03/13"
3
3
integration = ["aws"]
4
4
maturity = "production"
5
-
updated_date = "2025/07/10"
5
+
updated_date = "2025/09/08"
6
6
7
7
[rule]
8
8
author = ["Elastic"]
9
9
description = """
10
-
Identifies when an AWS DynamoDB table is exported to S3. Adversaries may use the ExportTableToPointInTime operation to collect sensitive information or exfiltrate data from DynamoDB tables. This rule detects unusual user activity by monitoring for the ExportTableToPointInTime action in CloudTrail logs. This is a New Terms rule that only flags when this behavior is observed by the "user.name" for the first time.
10
+
Identifies when an AWS DynamoDB table is exported to S3. Adversaries may use the ExportTableToPointInTime operation to collect sensitive information or exfiltrate data from DynamoDB tables. This rule detects unusual user activity by monitoring for the ExportTableToPointInTime action in CloudTrail logs. This is a New Terms rule that only flags when this behavior is observed by a user or role for the first time.
11
11
"""
12
12
false_positives = [
13
13
"""
@@ -50,7 +50,6 @@ For further guidance on managing and securing DynamoDB in AWS environments, refe
setup = "DynamoDB data events must be enabled in CloudTrail to capture the ExportTableToPointInTime actions. Ensure that the AWS CloudTrail service is configured to log data events for DynamoDB tables."
0 commit comments