AWS IAM User Addition to Group

  1[metadata]
  2creation_date = "2020/06/04"
  3integration = ["aws"]
  4maturity = "production"
  5updated_date = "2024/05/21"
  6
  7[rule]
  8author = ["Elastic"]
  9description = "Identifies the addition of a user to a specified group in AWS Identity and Access Management (IAM)."
 10false_positives = [
 11    """
 12    Adding users to a specified group may be done by a system or network administrator. Verify whether the user
 13    identity, user agent, and/or hostname should be making changes in your environment. User additions from unfamiliar
 14    users or hosts should be investigated. If known behavior is causing false positives, it can be exempted from the
 15    rule.
 16    """,
 17]
 18from = "now-60m"
 19index = ["filebeat-*", "logs-aws.cloudtrail-*"]
 20interval = "10m"
 21language = "kuery"
 22license = "Elastic License v2"
 23name = "AWS IAM User Addition to Group"
 24note = """## Triage and analysis
 25
 26### Investigating AWS IAM User Addition to Group
 27
 28AWS Identity and Access Management (IAM) provides fine-grained access control across all of AWS. With IAM, you can specify who can access which services and resources, and under which conditions. With IAM policies, you manage permissions to your workforce and systems to ensure least-privilege permissions.
 29
 30This rule looks for the addition of users to a specified user group.
 31
 32#### Possible investigation steps
 33
 34- Identify the user account that performed the action and whether it should perform this kind of action.
 35- Investigate other alerts associated with the user account during the past 48 hours.
 36- Contact the account and resource owners and confirm whether they are aware of this activity.
 37- Check if this operation was approved and performed according to the organization's change management policy.
 38- If you suspect the account has been compromised, scope potentially compromised assets by tracking servers, services, and data accessed by the account in the last 24 hours.
 39
 40### False positive analysis
 41
 42- False positives may occur due to the intended usage of the service. Tuning is needed in order to have higher confidence. Consider adding exceptions — preferably with a combination of user agent and IP address conditions — to reduce noise from onboarding processes and administrator activities.
 43
 44### Response and remediation
 45
 46- Initiate the incident response process based on the outcome of the triage.
 47- Disable or limit the account during the investigation and response.
 48- Identify the possible impact of the incident and prioritize accordingly; the following actions can help you gain context:
 49    - Identify the account role in the cloud environment.
 50    - Assess the criticality of affected services and servers.
 51    - Work with your IT team to identify and minimize the impact on users.
 52    - Identify if the attacker is moving laterally and compromising other accounts, servers, or services.
 53    - Identify any regulatory or legal ramifications related to this activity.
 54- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords or delete API keys as needed to revoke the attacker's access to the environment. Work with your IT teams to minimize the impact on business operations during these actions.
 55- Check if unauthorized new users were created, remove unauthorized new accounts, and request password resets for other IAM users.
 56- Consider enabling multi-factor authentication for users.
 57- Review the permissions assigned to the implicated user to ensure that the least privilege principle is being followed.
 58- Implement security best practices [outlined](https://aws.amazon.com/premiumsupport/knowledge-center/security-best-practices/) by AWS.
 59- Determine the initial vector abused by the attacker and take action to prevent reinfection via the same vector.
 60- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
 61
 62## Setup
 63
 64The AWS Fleet integration, Filebeat module, or similarly structured data is required to be compatible with this rule."""
 65references = ["https://docs.aws.amazon.com/IAM/latest/APIReference/API_AddUserToGroup.html"]
 66risk_score = 21
 67rule_id = "333de828-8190-4cf5-8d7c-7575846f6fe0"
 68severity = "low"
 69tags = [
 70    "Domain: Cloud",
 71    "Data Source: AWS",
 72    "Data Source: Amazon Web Services",
 73    "Use Case: Identity and Access Audit",
 74    "Tactic: Credential Access",
 75    "Tactic: Persistence",
 76    "Resources: Investigation Guide",
 77]
 78timestamp_override = "event.ingested"
 79type = "query"
 80
 81query = '''
 82event.dataset:aws.cloudtrail and event.provider:iam.amazonaws.com and event.action:AddUserToGroup and event.outcome:success
 83'''
 84
 85
 86[[rule.threat]]
 87framework = "MITRE ATT&CK"
 88
 89[rule.threat.tactic]
 90id = "TA0006"
 91name = "Credential Access"
 92reference = "https://attack.mitre.org/tactics/TA0006/"
 93[[rule.threat]]
 94framework = "MITRE ATT&CK"
 95[[rule.threat.technique]]
 96id = "T1098"
 97name = "Account Manipulation"
 98reference = "https://attack.mitre.org/techniques/T1098/"
 99
100
101[rule.threat.tactic]
102id = "TA0003"
103name = "Persistence"
104reference = "https://attack.mitre.org/tactics/TA0003/"