Sqs - CraftedSignal Threat Feedhttps://feed.craftedsignal.io/tags/sqs/Trending threats, MITRE ATT&CK coverage, and detection metadata. Fed continuously.Hugoenhello@craftedsignal.iohello@craftedsignal.ioWed, 03 Jan 2024 12:00:00 +0000AWS SQS Queue Purge Detectionhttps://feed.craftedsignal.io/briefs/2024-01-aws-sqs-queue-purge/Wed, 03 Jan 2024 12:00:00 +0000hello@craftedsignal.iohttps://feed.craftedsignal.io/briefs/2024-01-aws-sqs-queue-purge/Detection of AWS Simple Queue Service (SQS) queue purging, which adversaries may leverage to disrupt application workflows, destroy operational data, or impair monitoring and alerting systems by removing critical evidence of malicious activity.This alert detects the purging of an AWS Simple Queue Service (SQS) queue. AWS SQS is a managed message queuing service commonly used to decouple services and buffer events across distributed and serverless architectures. Adversaries may abuse the PurgeQueue action to remove messages, potentially disrupting application workflows, destroying operational data, or impairing security monitoring and alerting by deleting audit and security events. Defenders should investigate unexpected PurgeQueue events, especially in production environments, to determine whether the action aligns with documented procedures and expected operational behavior. The rule focuses on successful PurgeQueue events within AWS CloudTrail logs and should be deployed to monitor critical SQS queues.

Attack Chain

  1. An attacker gains access to an AWS account through compromised credentials or a misconfigured IAM role.
  2. The attacker identifies SQS queues that contain valuable operational or security-related data.
  3. The attacker uses the aws sqs purge-queue command or AWS API to purge the targeted queue.
  4. The PurgeQueue API call is logged as a PurgeQueue event in AWS CloudTrail.
  5. All messages within the targeted SQS queue are permanently deleted.
  6. Downstream systems that rely on messages from the purged queue experience disruption or data loss.
  7. Security monitoring systems that ingest logs from the purged queue miss critical security events.
  8. The attacker further exploits the environment, potentially performing data exfiltration or other malicious activities, with reduced visibility due to the purged logs.

Impact

Successful purging of an SQS queue can lead to significant disruption of application workflows and data loss. If the queue contains security-related logs, it can impair monitoring and alerting capabilities, allowing adversaries to operate with reduced visibility. The impact can range from temporary service interruptions to the permanent loss of critical operational data, depending on the purpose and content of the purged queue. This activity could affect a wide range of sectors using AWS SQS, including e-commerce, finance, and healthcare.

Recommendation

  • Deploy the Sigma rule "AWS SQS Queue Purge Detected" to your SIEM and tune it for your environment to detect unauthorized queue purges in near real-time.
  • Review aws.cloudtrail.user_identity.arn and access_key_id in CloudTrail logs to determine the identity that initiated the PurgeQueue action.
  • Reinforce least-privilege IAM policies to limit which identities can perform the PurgeQueue action, as outlined in the AWS Knowledge Center – Security Best Practices.
  • Enhance monitoring and alerting for destructive SQS actions, especially in production environments, using CloudTrail and CloudWatch.
  • Investigate events where event.action is PurgeQueue and event.outcome is success in AWS CloudTrail logs.
]]>mediumadvisorycloudawssqsdefense-evasionimpact