> 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/possible-privilege-escalation-using-delegated-msa-account.md).
# Possible Privilege Escalation using Delegated MSA account
### Synopsis
| Field | Value |
| -------------------- | ----------------------------------------------------------------------------------------------------------------------------- |
| Activation Period | 14 Days |
| Training Period | 30 Days |
| Test Period | 1 Hour |
| 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 |
| ATT\&CK Tactic | Privilege Escalation (TA0004) |
| ATT\&CK Technique | Account Manipulation (T1098) |
| Severity | Informational |
### Description
An attacker might abuse dMSA account to escalate its privileges.
### Attacker's Goals
Attackers may leverage dMSA account migration process to escalate privileges.
### Investigative actions
* Confirm that the user is authorized to create and modify dMSA accounts in the domain.
* Verify the user should have permissions on the OU under which the dMSA account was created.
* Validate that the dMSA account should be created under the OU that appeared in the log (use the GUID).
* Verify that the user superseded an account, with the dMSA account, that should have superseded.
* Check the GUID of the dMSA object to get the account itself (can be viewed also in computer account creation event).
* Check what is the superseded account in the attribute 'msDS-ManagedAccountPrecededByLink' of the dMSA object.
* Investigate the host that initiated the dMSA account migration process for malicious activity.
### Variations
Possible Privilege Escalation using Delegated MSA account attempt
**Synopsis**
| Field | Value |
| ----------------- | ----------------------------- |
| ATT\&CK Tactic | Privilege Escalation (TA0004) |
| ATT\&CK Technique | Account Manipulation (T1098) |
| Severity | Medium |
**Description**
An attacker might abuse dMSA account to escalate its privileges.
**Attacker's Goals**
Attackers may leverage dMSA account migration process to escalate privileges.
**Investigative actions**
* Confirm that the user is authorized to create and modify dMSA accounts in the domain.
* Verify the user should have permissions on the OU under which the dMSA account was created.
* Validate that the dMSA account should be created under the OU that appeared in the log (use the GUID).
* Verify that the user superseded an account, with the dMSA account, that should have superseded.
* Check the GUID of the dMSA object to get the account itself (can be viewed also in computer account creation event).
* Check what is the superseded account in the attribute 'msDS-ManagedAccountPrecededByLink' of the dMSA object.
* Investigate the host that initiated the dMSA account migration process for malicious activity.
---
# 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://cortex-docs.paloaltonetworks.com/analytics-alerts/alerts-by-name/possible-privilege-escalation-using-delegated-msa-account.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.