> 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-added-to-the-sms-admins-local-group.md).
# User added to the SMS Admins local group
### Synopsis
| Field | Value |
| -------------------- | ----------------------------------------------------------------------------------------------------------------------------- |
| Activation Period | 14 Days |
| Training Period | 30 Days |
| Test Period | 3 Hours |
| Deduplication Period | 1 Day |
| Required Data | Requires one of the following data sources:
Windows Event Collector OR XDR Agent with eXtended Threat Hunting (XTH)
|
| Detection Modules | Identity Analytics |
| Detector Tags | Microsoft SCCM Analytics |
| ATT\&CK Tactic | Persistence (TA0003), Privilege Escalation (TA0004) |
| ATT\&CK Technique | Account Manipulation (T1098), Valid Accounts (T1078) |
| Severity | Low |
### Description
A user was added to the SMS Admins local group. This may indicate a potential attack targeting the Microsoft Configuration Manager infrastructure.
### Attacker's Goals
Gain administrative control over Microsoft Configuration Manager to facilitate lateral movement, deploy malicious payloads, or exfiltrate data.
### Investigative actions
* Verify the activity with the performing user.
* Confirm that the group addition was not accidental.
* Review related logs (e.g., Active Directory, SCCM logs) to identify the source of the modification and associated accounts.
* Investigate the user's activity before and after the addition to determine if any unauthorized actions or privilege escalation attempts occurred.
### Variations
User added to the SMS Admins group and removed
**Synopsis**
| Field | Value |
| ----------------- | ---------------------------------------------------- |
| ATT\&CK Tactic | Persistence (TA0003), Privilege Escalation (TA0004) |
| ATT\&CK Technique | Account Manipulation (T1098), Valid Accounts (T1078) |
| Severity | Medium |
**Description**
A user was added to the SMS Admins group and removed within a short period of time, which may be a sign of compromise.
**Attacker's Goals**
Gain administrative control over Microsoft Configuration Manager to facilitate lateral movement, deploy malicious payloads, or exfiltrate data.
**Investigative actions**
* Verify the activity with the performing user.
* Confirm that the group addition was not accidental.
* Review related logs (e.g., Active Directory, SCCM logs) to identify the source of the modification and associated accounts.
* Investigate the user's activity before and after the addition to determine if any unauthorized actions or privilege escalation attempts occurred.
---
# 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-added-to-the-sms-admins-local-group.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.