AWS SES discovery attempt by long term access key

This page is not yet available in Spanish. We are working on its translation.
If you have any questions or feedback about our current translation project, feel free to reach out to us!

Goal

Detect when there is an attempt to determine the status of an organization’s Amazon SES account.

Strategy

Monitor CloudTrail and detect when there is an attempt to determine the status of an organizations Amazon SES account. Attackers target the AWS SES service generally for the purpose of phishing. In order to determine the sending quota of an account or if the account is currently in a sandbox environment, the attacker may use the API call GetAccount.

Triage and response

  1. Determine if the API call: {{@evt.name}} should have been made by the user: {{@userIdentity.arn}} from this IP address: {{@network.client.ip}} .
  2. If the action is legitimate, consider including the user in a suppression list. See Best practices for creating detection rules with Datadog Cloud SIEM for more information.
  3. If the action shouldn’t have happened:
    • Contact the user: {{@userIdentity.arn}} and see if they made the API call.
    • Use the Cloud SIEM - User Investigation dashboard to see if the user {{@userIdentity.arn}} has taken other actions.
    • Use the Cloud SIEM - IP Investigation dashboard to see if there’s more traffic from the IP {{@network.client.ip}}.
  4. If the results of the triage indicate that an attacker has taken the action, initiate your company’s incident response process, as well as an investigation.

Changelog

  • 17 December 2024 - updated rule query.