Account Discovery: Cloud Account T1087.004
Tactic: Discovery
Adversaries may attempt to get a listing of cloud accounts. Cloud accounts are those created and configured by an organization for use by users, remote support, services, or for administration of resources within a cloud service provider or SaaS application.
Authoring guide
Patterns shared across the 26 rules above: which fields they filter on, what specific values they look for, and what they exclude. The catalog normalizes field names across vendors so Sigma's Image, Elastic's process.name, and Splunk's process_name collapse into one row. Each rule contributes at most once per row.
Fields filtered most (43 distinct)
The fields most rules look at when detecting this technique. The How column shows the operators authors use (eq, wildcard, regex_match, match) and how often each appears. Sample values are concrete examples to start from, not an exhaustive list.
Top indicator values (121 distinct)
Specific (field, operator, value) combinations the rules check for, ranked by how many rules under this technique use each one. The Corpus reach column counts how many rules across the entire catalog (any technique) check the same combination. High numbers point to widely-used indicators that are likely noisy on their own; combine them with another condition for useful signal. Blank means the combination is specific to rules under this technique. Click a value to expand the rules under this technique that use it.
Exclusions (11 distinct)
Field/operator/value combinations excluded by rules under this technique (top-level not() clauses), sorted by how many rules exclude each. These are the false-positive paths the community has learned to filter out. A new rule that ignores the high-count entries here will likely fire on the same noisy paths. Click a value to expand the rules under this technique that exclude it.
Rules under this technique
Every rule in the catalog tagged with this technique, grouped by vendor. Click a rule title for its full predicates, exclusions, and indicators.
Sigma 5 rules
- AWS STS GetCallerIdentity Enumeration Via TruffleHog
- Discovery Using AzureHound
- RBAC Permission Enumeration Attempt
- Role Enumeration
- User Enumeration
Elastic 7 rules
- AWS Account Discovery By Rare User
- AWS Discovery API Calls via CLI from a Single Resource
- AWS EC2 Role GetCallerIdentity from New Source AS Organization
- AWS IAM Principal Enumeration via UpdateAssumeRolePolicy
- AWS STS GetCallerIdentity API Called for the First Time
- Entra ID Sign-in BloodHound Suite User-Agent Detected
- Entra ID Sign-in TeamFiltration User-Agent Detected
Splunk 4 rules
- Azure AD AzureHound UserAgent Detected
- Azure AD Service Principal Enumeration
- Okta IDP Lifecycle Modifications
- Okta Unauthorized Access to Application
Kusto 8 rules
- Cross-tenant Access Settings Organization Added
- Cross-tenant Access Settings Organization Deleted
- Cross-tenant Access Settings Organization Inbound Collaboration Settings Changed
- Cross-tenant Access Settings Organization Inbound Direct Settings Changed
- Cross-tenant Access Settings Organization Outbound Collaboration Settings Changed
- Cross-tenant Access Settings Organization Outbound Direct Settings Changed
- External guest invitation followed by Microsoft Entra ID PowerShell signin
- Guest accounts added in Entra ID Groups other than the ones specified