> 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/potential-sccm-credential-harvesting-using-wmi-detected.md).
# Potential SCCM credential harvesting using WMI detected
### 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) |
| Detector Tags | Microsoft SCCM Analytics |
| ATT\&CK Tactic | Execution (TA0002), Credential Access (TA0006) |
| ATT\&CK Technique | Windows Management Instrumentation (T1047), Unsecured Credentials (T1552) |
| Severity | Low |
### Description
Attackers or malware may use WMI queries to obtain domain credentials that are used by the SCCM.
### Attacker's Goals
Obtain credentials used by the SCCM service.
### Investigative actions
* Examine the process that executed the WMI query and the CGO and verify that the processes are from a trusted source.
* Inspect the system for malicious activity that is related to that process.
### Variations
Potential SCCM credential harvesting using WMI detected from a remote machine
**Synopsis**
| Field | Value |
| ----------------- | ------------------------------------------------------------------------- |
| ATT\&CK Tactic | Execution (TA0002), Credential Access (TA0006) |
| ATT\&CK Technique | Windows Management Instrumentation (T1047), Unsecured Credentials (T1552) |
| Severity | Medium |
**Description**
Attackers or malware may use WMI queries to obtain domain credentials that are used by the SCCM.
**Attacker's Goals**
Obtain credentials used by the SCCM service.
**Investigative actions**
* Examine the process that executed the WMI query and the CGO and verify that the processes are from a trusted source.
* Inspect the system for malicious activity that is related to that process.
Potential SCCM inventory query using WMI detected
**Synopsis**
| Field | Value |
| ----------------- | ------------------------------------------------------------------------- |
| ATT\&CK Tactic | Execution (TA0002), Credential Access (TA0006) |
| ATT\&CK Technique | Windows Management Instrumentation (T1047), Unsecured Credentials (T1552) |
| Severity | Low |
**Description**
Attackers or malware may use WMI queries to obtain domain credentials that are used by the SCCM.
**Attacker's Goals**
Obtain credentials used by the SCCM service.
**Investigative actions**
* Examine the process that executed the WMI query and the CGO and verify that the processes are from a trusted source.
* Inspect the system for malicious activity that is related to that process.
Potential Enumeration of SCCM User, Device, and Deployment Data via WMI
**Synopsis**
| Field | Value |
| ----------------- | ------------------------------------------------------------------------- |
| ATT\&CK Tactic | Execution (TA0002), Credential Access (TA0006) |
| ATT\&CK Technique | Windows Management Instrumentation (T1047), Unsecured Credentials (T1552) |
| Severity | Low |
**Description**
Attackers or malware may use WMI queries to obtain domain credentials that are used by the SCCM.
**Attacker's Goals**
Obtain credentials used by the SCCM service.
**Investigative actions**
* Examine the process that executed the WMI query and the CGO and verify that the processes are from a trusted source.
* Inspect the system for malicious 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/potential-sccm-credential-harvesting-using-wmi-detected.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.