AWS Account Discovery By Rare User
Description
Identifies the first time, within a lookback window, an identity performs AWS Organizations or IAM account enumeration
APIs. Attackers with compromised credentials often map the organization (accounts, OUs, roots, delegated admins) and
account-level metadata (aliases, summary) using the AWS CLI or SDKs. This is a New Terms rule detecting a rare
occurrence of the cloud.account.id and user.name pair for these actions.
Query · kuery
data_stream.dataset: "aws.cloudtrail"
and event.outcome: "success"
and source.ip:*
and not aws.cloudtrail.session_credential_from_console: "true"
and not aws.cloudtrail.user_identity.type: "AWSService"
and (
(
event.provider: "organizations.amazonaws.com"
and event.action: (
"DescribeOrganization" or "DescribeOrgnanizationalUnit" or "ListAccounts" or "ListRoots"
or "ListOrganizationalUnitsForParent" or "ListAccountsForParent" or "ListPolicies"
or "ListAWSServiceAccessForOrganization" or "ListDelegatedAdministrators"
or "ListDelegatedServicesForAccount" or "DescribeResourcePolicy"
)
)
or (
event.provider: "iam.amazonaws.com"
and event.action: ("ListAccountAliases" or "GetAccountSummary")
)
)
and not user_agent.original: (*Terraform*)
Investigation fields
Pivot points the source recommends for triage.
@timestampuser.nameuser_agent.originalsource.ipaws.cloudtrail.user_identity.arnaws.cloudtrail.user_identity.typeaws.cloudtrail.user_identity.access_key_idevent.actionevent.outcomeevent.providercloud.account.idcloud.region
Known false positives
- Organization and security administrators, billing tooling, landing-zone automation, and delegated administrator workflows may call these APIs legitimately. Interactive or one-off use from unusual principals warrants review.
Analyst notes
Investigating AWS Account Discovery By Rare User
AWS Organizations and IAM expose read APIs that reveal organization structure, member accounts, delegation, and
account-level aliases. Threat actors and tools such as Pacu (organizations__enum) chain these calls to understand
multi-account layout after credential access.
This rule uses New Terms to detect when an identity makes a discovery API call that has not been seen in the configured history window.
Possible investigation steps
Identify the actor and session context
- Confirm who user.name and aws.cloudtrail.user_identity.arn represent (human, workload role, automation).
Analyze the source and origin - Review source.ip, geolocation, and whether the call aligns with normal egress for that principal. - Inspect user_agent.original for CLI, Boto3/Botocore, consoles, or unfamiliar tooling.
Correlate with additional events
- Correlate with STS*(GetCallerIdentity, AssumeRole) and broader discovery or privilege changes in the same session.
- If the principal is new or rarely used, review IAM policies and recent key rotation.
False positive analysis
- Documented org-admin or security roles in the management account; add exceptions by ARN if needed.
- Centralized compliance or CSPM that enumerates org structure on a schedule.
Response and remediation
- If unexpected, rotate credentials for the implicated principal, review CloudTrail for follow-on API activity, and tighten least privilege on Organizations/IAM read APIs where appropriate.