IMPORTANT: No additional bug fixes or documentation updates will be released for this version. For the latest information, see the current release documentation.
« AWS DynamoDB Scan by Unusual User Microsoft 365 Illicit Consent Grant via Registered Application »
Elastic Docs ›Elastic Security Solution [8.17] ›Downloadable rule update v8.17.8

AWS DynamoDB Table Exported to S3

edit
IMPORTANT: This documentation is no longer updated. Refer to Elastic's version policy and the latest documentation.

AWS DynamoDB Table Exported to S3

edit

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 aws.cloudtrail.user_identity.arn for the first time in the last 14 days.

Rule type: new_terms

Rule indices:

  • filebeat-*
  • logs-aws.cloudtrail-*

Severity: low

Risk score: 21

Runs every: 5m

Searches indices from: now-9m (Date Math format, see also Additional look-back time)

Maximum alerts per execution: 100

References:

Tags:

  • Domain: Cloud
  • Data Source: AWS
  • Data Source: Amazon Web Services
  • Data Source: AWS DynamoDB
  • Resources: Investigation Guide
  • Use Case: Threat Detection
  • Tactic: Exfiltration

Version: 3

Rule authors:

  • Elastic

Rule license: Elastic License v2

Investigation guide

edit
## Triage and analysis

Investigating AWS DynamoDB Table Exported to S3

This rule 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 for the first time on a host in the last 14 days.

Possible Investigation Steps

  • Identify the Actor: Review the aws.cloudtrail.user_identity.arn field to identify the user who requested the export. 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.
  • 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.
  • Analyze the Request Parameters: Examine the aws.cloudtrail.request_parameters field to understand the details of the ExportTableToPointInTime request. Look for any unusual parameters or patterns that may indicate malicious intent. This also details the DynamoDB table being exported.
  • 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.

False Positive Analysis

  • Historical User Actions: If the user has a history of exporting DynamoDB tables for legitimate purposes, this may not be a false positive. Review the user’s activity logs to determine if this behavior is consistent with their normal actions.
  • Automated Processes: Some automated processes or applications may perform exports on DynamoDB tables as part of their functionality. If the user is associated with such a process, this may not be a false positive.

Response and Remediation

  • Immediate Review and Reversal: If the ExportTableToPointInTime action is determined to be unauthorized, immediately revoke the user’s access to the DynamoDB table and any associated resources. This may involve disabling the user’s account or removing their permissions.
  • Investigate Compromise: If the ExportTableToPointInTime action is determined to be malicious, investigate the source and destination of the request and any potential compromise of the user’s account. If the destination S3 bucket is not known, it may be a sign of data exfiltration and may require incident response.
  • Review IAM Policies: Review the IAM policies associated with the user to ensure that they have the appropriate permissions for their role. If necessary, update the policies to restrict access to sensitive resources.
  • Monitor for Future Activity: Continue to monitor the user’s activity for any further suspicious behavior. Set up additional alerts or logging to detect any future unauthorized access attempts.

Additional Information

For further guidance on managing and securing SNS topics in AWS environments, refer to the AWS SNS documentation and AWS best practices for security.

Setup

edit

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.

Rule query

edit
event.dataset: "aws.cloudtrail"
    and event.provider: "dynamodb.amazonaws.com"
    and event.action: "ExportTableToPointInTime"
    and aws.cloudtrail.flattened.request_parameters.dryRun: false

Framework: MITRE ATT&CKTM

« AWS DynamoDB Scan by Unusual User Microsoft 365 Illicit Consent Grant via Registered Application »