> For the complete documentation index, see [llms.txt](https://cortex-docs.paloaltonetworks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cortex-docs.paloaltonetworks.com/analytics-alerts/alerts-by-name/user-discovery-via-wmi-query-execution.md).
# User discovery via WMI query execution
### Synopsis
| Field | Value |
| -------------------- | ---------------------------------------------------------------------------------------------------------- |
| Activation Period | 14 Days |
| Training Period | 30 Days |
| Test Period | N/A (single event) |
| Deduplication Period | 1 Day |
| Required Data | XDR Agent with eXtended Threat Hunting (XTH) |
| ATT\&CK Tactic | Execution (TA0002), Discovery (TA0007) |
| ATT\&CK Technique | Windows Management Instrumentation (T1047), System Owner/User Discovery (T1033), Account Discovery (T1087) |
| Severity | Informational |
### Description
Attackers or malware may use WMI queries to list the users of a host, and potentially its owner.
### Attacker's Goals
Attacker or malware can use WMI queries to discover host users and enumerate a huge amount of information.
### Investigative actions
* Examine the process that executed the WMI query and verify that the process is from a trusted source.
* Inspect the system for suspicious activity that is related to that process.
### Variations
User discovery via WMI query execution by an unsigned process
**Synopsis**
| Field | Value |
| ----------------- | ---------------------------------------------------------------------------------------------------------- |
| ATT\&CK Tactic | Execution (TA0002), Discovery (TA0007) |
| ATT\&CK Technique | Windows Management Instrumentation (T1047), System Owner/User Discovery (T1033), Account Discovery (T1087) |
| Severity | Low |
**Description**
Attackers or malware may use WMI queries to list the users of a host, and potentially its owner.
**Attacker's Goals**
Attacker or malware can use WMI queries to discover host users and enumerate a huge amount of information.
**Investigative actions**
* Examine the process that executed the WMI query and verify that the process is from a trusted source.
* Inspect the system for suspicious activity that is related to that process.
User modification via WMIC query execution
**Synopsis**
| Field | Value |
| ----------------- | ------------------------------------------------------------------------ |
| ATT\&CK Tactic | Execution (TA0002), Persistence (TA0003) |
| ATT\&CK Technique | Windows Management Instrumentation (T1047), Account Manipulation (T1098) |
| Severity | Low |
**Description**
Attackers or malware may use WMI queries to modify the users of a host, and potentially its owner.
**Attacker's Goals**
Attacker or malware can use WMI queries to discover host users and enumerate a huge amount of information.
**Investigative actions**
* Examine the process that executed the WMI query and verify that the process is from a trusted source.
* Inspect the system for suspicious activity that is related to that process.
User discovery via WMIC query execution
**Synopsis**
| Field | Value |
| ----------------- | ---------------------------------------------------------------------------------------------------------- |
| ATT\&CK Tactic | Execution (TA0002), Discovery (TA0007) |
| ATT\&CK Technique | Windows Management Instrumentation (T1047), System Owner/User Discovery (T1033), Account Discovery (T1087) |
| Severity | Informational |
**Description**
Attackers or malware may use WMI queries to list the users of a host, and potentially its owner.
**Attacker's Goals**
Attacker or malware can use WMI queries to discover host users and enumerate a huge amount of information.
**Investigative actions**
* Examine the process that executed the WMI query and verify that the process is from a trusted source.
* Inspect the system for suspicious activity that is related to that process.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://cortex-docs.paloaltonetworks.com/analytics-alerts/alerts-by-name/user-discovery-via-wmi-query-execution.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.