ATT&CK coverage › Technique
Account Discovery: Domain Account T1087.002
Adversaries may attempt to get a listing of domain accounts. This information can help adversaries determine which domain accounts exist to aid in follow-on behavior such as targeting specific accounts which possess particular privileges.
Events covered
10 catalog events are tagged with this technique by at least one rule.
Authoring guide
Patterns shared across the 41 rules above: which fields they filter on, what specific values they look for, and what they exclude. Field names are normalized 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 (25 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 (845 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.
Common exclusions (2 distinct)
Field/operator/value combinations that rules under this technique routinely exclude (top-level not() clauses). 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.
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 20 rules
- Active Directory Computers Enumeration With Get-AdComputer
- Active Directory Database Snapshot Via ADExplorer
- Active Directory Structure Export Via Csvde.EXE
- AD Privileged Users or Groups Reconnaissance
- ADExplorer Writing Complete AD Snapshot Into .dat File
- BloodHound Collection Files
- HackTool - Bloodhound/Sharphound Execution
- Malicious PowerShell Commandlets - PoshModule
- Malicious PowerShell Commandlets - ProcessCreation
- Malicious PowerShell Commandlets - ScriptBlock
- Potential Active Directory Reconnaissance/Enumeration Via LDAP
- Potential AD User Enumeration From Non-Machine Account
- PUA - AdFind Suspicious Execution
- PUA - AdFind.EXE Execution
- PUA - Suspicious ActiveDirectory Enumeration Via AdFind.EXE
- Reconnaissance Activity
- Renamed AdFind Execution
- Suspicious Active Directory Database Snapshot Via ADExplorer
- Suspicious Group And Account Reconnaissance Activity Using Net.EXE
- Suspicious Use of PsLogList
Elastic 1 rule
Splunk 18 rules
- AdsiSearcher Account Discovery
- Detect AzureHound File Modifications
- Detect SharpHound File Modifications
- Get ADUser with PowerShell Script Block
- Get DomainUser with PowerShell Script Block
- GetWmiObject DS User with PowerShell Script Block
- Network Traffic to Active Directory Web Services Protocol
- SchCache Change By App Connect And Create ADSI Object
- Windows AD Abnormal Object Access Activity
- Windows AD Privileged Object Access Activity
- Windows Domain Account Discovery Via Get-NetComputer
- Windows Find Domain Organizational Units with GetDomainOU
- Windows Find Interesting ACL with FindInterestingDomainAcl
- Windows Forest Discovery with GetForestDomain
- Windows Get Local Admin with FindLocalAdminAccess
- Windows Linked Policies In ADSI Discovery
- Windows Root Domain linked policies Discovery
- Windows Suspect Process With Authentication Traffic