> 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/microsoft-configuration-manager-device-registration-and-policy-request.md).

# Microsoft Configuration Manager device registration and policy request

### Synopsis

| Field                | Value                                                                      |
| -------------------- | -------------------------------------------------------------------------- |
| Activation Period    | 14 Days                                                                    |
| Training Period      | 30 Days                                                                    |
| Test Period          | 1 Hour                                                                     |
| Deduplication Period | 1 Day                                                                      |
| Required Data        | XDR Agent                                                                  |
| Detection Modules    | Identity Analytics                                                         |
| Detector Tags        | Microsoft SCCM Analytics                                                   |
| ATT\&CK Tactic       | Credential Access (TA0006), Privilege Escalation (TA0004)                  |
| ATT\&CK Technique    | Valid Accounts: Domain Accounts (T1078.002), Unsecured Credentials (T1552) |
| Severity             | Informational                                                              |

### Description

A user registered a device and requested a Microsoft Configuration Manager policy.

### Attacker's Goals

An attacker aims to extract plaintext credentials of the Network Access Account (NAA) from an SCCM environment, enabling unauthorized access to resources and lateral movement within the network.

### Investigative actions

* Verify the activity with the performing user.
* Review related logs (e.g., Active Directory, SCCM logs) to identify the source of the modification and associated accounts.
* Look for unusual logins using the Network Access Account (NAA), on systems or at times that deviate from normal patterns.
* Looking for signs of credential extraction, such as tools or scripts.

### Variations

<details>

<summary>Suspicious Microsoft Configuration Manager device registration and policy request</summary>

**Synopsis**

| Field             | Value                                                                      |
| ----------------- | -------------------------------------------------------------------------- |
| ATT\&CK Tactic    | Credential Access (TA0006), Privilege Escalation (TA0004)                  |
| ATT\&CK Technique | Valid Accounts: Domain Accounts (T1078.002), Unsecured Credentials (T1552) |
| Severity          | Low                                                                        |

**Description**

A suspicious process registered a new device and requested policies from Microsoft Configuration Manager, triggering a suspicious activity alert due to unusual characteristics.

**Attacker's Goals**

An attacker aims to extract plaintext credentials of the Network Access Account (NAA) from an SCCM environment, enabling unauthorized access to resources and lateral movement within the network.

**Investigative actions**

* Verify the activity with the performing user.
* Review related logs (e.g., Active Directory, SCCM logs) to identify the source of the modification and associated accounts.
* Look for unusual logins using the Network Access Account (NAA), on systems or at times that deviate from normal patterns.
* Looking for signs of credential extraction, such as tools or scripts.

</details>


---

# 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/microsoft-configuration-manager-device-registration-and-policy-request.md?ask=<question>&goal=<user_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.