Enumeration of Administrator Accounts

  1[metadata]
  2creation_date = "2020/12/04"
  3integration = ["endpoint", "windows", "system"]
  4maturity = "production"
  5min_stack_comments = "New fields added: required_fields, related_integrations, setup"
  6min_stack_version = "8.3.0"
  7updated_date = "2024/03/28"
  8
  9[rule]
 10author = ["Elastic"]
 11description = """
 12Identifies instances of lower privilege accounts enumerating Administrator accounts or groups using built-in Windows
 13tools.
 14"""
 15from = "now-9m"
 16index = ["logs-endpoint.events.process-*", "winlogbeat-*", "logs-windows.*", "endgame-*", "logs-system.security*"]
 17language = "eql"
 18license = "Elastic License v2"
 19name = "Enumeration of Administrator Accounts"
 20note = """## Triage and analysis
 21
 22### Investigating Enumeration of Administrator Accounts
 23
 24After successfully compromising an environment, attackers may try to gain situational awareness to plan their next steps. This can happen by running commands to enumerate network resources, users, connections, files, and installed security software.
 25
 26This rule looks for the execution of the `net` and `wmic` utilities to enumerate administrator-related users or groups in the domain and local machine scope. Attackers can use this information to plan their next steps of the attack, such as mapping targets for credential compromise and other post-exploitation activities.
 27
 28#### Possible investigation steps
 29
 30- Investigate the process execution chain (parent process tree) for unknown processes. Examine their executable files for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
 31- Identify the user account that performed the action and whether it should perform this kind of action.
 32- Investigate other alerts associated with the user/host during the past 48 hours.
 33- Investigate any abnormal account behavior, such as command executions, file creations or modifications, and network connections.
 34
 35### False positive analysis
 36
 37- Discovery activities are not inherently malicious if they occur in isolation. As long as the analyst did not identify suspicious activity related to the user or host, such alerts can be dismissed.
 38
 39### Related rules
 40
 41- AdFind Command Activity - eda499b8-a073-4e35-9733-22ec71f57f3a
 42
 43### Response and remediation
 44
 45- Initiate the incident response process based on the outcome of the triage.
 46- Isolate the involved hosts to prevent further post-compromise behavior.
 47- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business systems, and web services.
 48- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and malware components.
 49- Determine the initial vector abused by the attacker and take action to prevent reinfection through the same vector.
 50- 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).
 51"""
 52risk_score = 21
 53rule_id = "871ea072-1b71-4def-b016-6278b505138d"
 54setup = """## Setup
 55
 56If enabling an EQL rule on a non-elastic-agent index (such as beats) for versions <8.2,
 57events will not define `event.ingested` and default fallback for EQL rules was not added until version 8.2.
 58Hence for this rule to work effectively, users will need to add a custom ingest pipeline to populate
 59`event.ingested` to @timestamp.
 60For more details on adding a custom ingest pipeline refer - https://www.elastic.co/guide/en/fleet/current/data-streams-pipeline-tutorial.html
 61"""
 62severity = "low"
 63tags = ["Domain: Endpoint",
 64        "OS: Windows",
 65        "Use Case: Threat Detection",
 66        "Tactic: Discovery",
 67        "Resources: Investigation Guide",
 68        "Data Source: Elastic Endgame",
 69        "Data Source: Elastic Defend"
 70        ]
 71timestamp_override = "event.ingested"
 72type = "eql"
 73
 74query = '''
 75process where host.os.type == "windows" and event.type == "start" and
 76(
 77  (
 78    (
 79      (process.name : "net.exe" or ?process.pe.original_file_name == "net.exe") or
 80      ((process.name : "net1.exe" or ?process.pe.original_file_name == "net1.exe") and not process.parent.name : "net.exe")
 81    ) and
 82    process.args : ("group", "user", "localgroup") and
 83    process.args : ("*admin*", "Domain Admins", "Remote Desktop Users", "Enterprise Admins", "Organization Management")
 84    and not process.args : ("/add", "/delete")
 85  ) or
 86  (
 87    (process.name : "wmic.exe" or ?process.pe.original_file_name == "wmic.exe") and
 88    process.args : ("group", "useraccount")
 89  )
 90) and not user.id : ("S-1-5-18", "S-1-5-19", "S-1-5-20")
 91'''
 92
 93[[rule.threat]]
 94framework = "MITRE ATT&CK"
 95
 96[[rule.threat.technique]]
 97id = "T1069"
 98name = "Permission Groups Discovery"
 99reference = "https://attack.mitre.org/techniques/T1069/"
100
101[[rule.threat.technique.subtechnique]]
102id = "T1069.001"
103name = "Local Groups"
104reference = "https://attack.mitre.org/techniques/T1069/001/"
105
106[[rule.threat.technique.subtechnique]]
107id = "T1069.002"
108name = "Domain Groups"
109reference = "https://attack.mitre.org/techniques/T1069/002/"
110
111[[rule.threat.technique]]
112id = "T1087"
113name = "Account Discovery"
114reference = "https://attack.mitre.org/techniques/T1087/"
115
116[[rule.threat.technique.subtechnique]]
117id = "T1087.001"
118name = "Local Account"
119reference = "https://attack.mitre.org/techniques/T1087/001/"
120
121[[rule.threat.technique.subtechnique]]
122id = "T1087.002"
123name = "Domain Account"
124reference = "https://attack.mitre.org/techniques/T1087/002/"
125
126[rule.threat.tactic]
127id = "TA0007"
128name = "Discovery"
129reference = "https://attack.mitre.org/tactics/TA0007/"