AWS IAM User Anomalous Resource Consumption

Classification:

attack

Tactic:

TA0040-impact

Technique:

T1496-resource-hijacking

Overview

Goal

Detect when an AWS IAM user is launching compute resources and has no prior history of invoking this API.

Strategy

This rule lets you monitor this GuardDuty integration finding:

• ResourceConsumption:IAMUser/ComputeResources

Triage & Response

1. Determine which user triggered the signal. This can be found in the signal.
2. Determine if the user’s credentials are compromised.
   
3. If the user’s credentials are compromised:
   • Review the AWS documentation on remediating compromised AWS credentials.