« AWS IAM SAML Provider Updated AWS IAM User Created Access Keys For Another User »
Elastic Docs ›Elastic Security [8.19] ›Detections and alerts ›Prebuilt rule reference

AWS IAM User Addition to Group

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

AWS IAM User Addition to Group

edit

Identifies the addition of a user to a specified group in AWS Identity and Access Management (IAM). Any user added to a group automatically gains the permissions that are assigned to the group. If the target group carries elevated or admin privileges, this action can instantly grant high-risk permissions useful for credential misuse, lateral movement, or privilege escalation.

Rule type: query

Rule indices:

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

Severity: low

Risk score: 21

Runs every: 5m

Searches indices from: now-6m (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
  • Use Case: Identity and Access Audit
  • Tactic: Credential Access
  • Tactic: Persistence
  • Resources: Investigation Guide

Version: 212

Rule authors:

  • Elastic

Rule license: Elastic License v2

Investigation guide

edit

Triage and analysis

Disclaimer: This investigation guide was created using generative AI technology and has been reviewed to improve its accuracy and relevance. While every effort has been made to ensure its quality, we recommend validating the content and adapting it to suit your specific environment and operational needs.

Investigating AWS IAM User Addition to Group

This rule detects when an IAM user is added to an IAM group via the AddUserToGroup API call. If the target group holds elevated privileges, this action may immediately grant that user wide-ranging access useful for credential misuse or lateral movement. This rule helps detect unauthorized privilege escalation via group membership change. Treat as high-risk when the destination group has wide scope (e.g., AdministratorAccess or permissive inline policies).

Possible investigation steps

  • Identify the actor and target
  • Check aws.cloudtrail.user_identity.arn for who added the user.
  • From aws.cloudtrail.request_parameters, capture userName (added user) and groupName (destination group).
  • Check source.ip, user_agent.original, cloud.region for unusual patterns.
  • Examine the group’s privileges
  • Use GetGroup, ListAttachedGroupPolicies to see what policies the group holds. Look for AdministratorAccess, iam:*, s3:*, ec2:* or cross-account permissions.
  • Check whether the group was recently created (CreateGroup) or recently escalated (AttachGroupPolicy). Common attacker pattern: create > attach policy > add user.
  • Correlate with surrounding activity
  • Look for preceding events by the actor: AssumeRole, GetSessionToken, CreateAccessKey, AttachGroupPolicy.
  • Follow the added user’s activities after group membership. Look for sensitive operations (e.g., IAM actions, S3 policy changes, EC2 snapshot/AMI activity).

False positive analysis

  • Onboarding or role transitions may legitimately add users to groups.
  • Automated Identity-Management pipelines may add many users to service groups; validate know

Response and remediation

  • Containment:
  • If unapproved, remove the user from the group immediately (RemoveUserFromGroup) and rotate their access keys.
  • Temporarily restrict group policy changes while assessing blast radius.
  • Investigation and scoping:
  • Review all actions executed by the newly added user since the change (ex: PutBucketPolicy, CreateAccessKey, PassRole).
  • Confirm whether other users were added to the same group within the same window.
  • Recovery and hardening:
  • Enforce least privilege by redesigning large-group membership.
  • Restrict iam:AddUserToGroup to only appropriate service principals with approval workflow.
  • Create detections for AttachGroupPolicy to powerful policies and for mass AddUserToGroup patterns.

Additional information

AWS Security Best Practices

Rule query

edit
event.dataset: aws.cloudtrail and
    event.provider: iam.amazonaws.com and
    event.action: AddUserToGroup and
    event.outcome: success

Framework: MITRE ATT&CKTM

« AWS IAM SAML Provider Updated AWS IAM User Created Access Keys For Another User »