msDS-AllowedToActOnBehalfOfOtherIdentity is the Active Directory attribute that stores which security principals are allowed to impersonate users to a resource under resource-based constrained delegation. If this value is modified without authorization, it can create a persistent privilege-escalation path and enable lateral movement.
What the attribute does in Kerberos delegation
msDS-AllowedToActOnBehalfOfOtherIdentity is an access-control attribute in Active Directory, not a generic configuration flag. It defines the security principals that can act on behalf of another user to a specific resource, which is the core trust decision behind resource-based constrained delegation. That makes the attribute a direct gate on impersonation rights.
Because the attribute is evaluated by the target resource, it shifts delegation control closer to the service that is being accessed. That design is useful for delegated application access, but it also means the object owner or defender must treat the attribute as part of the resource’s authorization boundary, not just directory metadata.
How resource-based constrained delegation works
In resource-based constrained delegation, the resource itself states which principals may present delegated access. This is different from older delegation models where trust is configured mainly on the front-end service. The practical effect is that the target object determines who may use S4U flows to obtain access, which can simplify service-to-service access patterns while reducing broad, domain-wide delegation trust.
That model is powerful because it supports selective delegation without granting a service blanket authority across the directory. It also helps explain why the attribute is frequently discussed alongside Kerberos delegation security, since the security question is not merely “can delegation happen?” but “which principal is allowed to impersonate, and to which resource?”
Why unauthorized modification is so dangerous
If an attacker can write this attribute, they can often turn a normal service account, computer account, or other controlled principal into an impersonation path. That can convert limited directory access into a durable privilege-escalation route, especially when the resource is valuable or widely reachable. The risk is not the attribute alone, but the delegation authority it confers when paired with a reachable service.
Because the setting lives on an Active Directory object, abuse can be subtle. A malicious change may not look like a password reset or a new account, yet it can still enable access on behalf of higher-privilege users and create lateral movement opportunities across systems that trust the resource.
What defenders should verify and monitor
Defenders should treat any change to this attribute as a high-value directory event. Exposure review starts with knowing which resources allow constrained delegation, which principals are listed, and whether the resource is reachable in ways that make impersonation useful. In practice, that means checking object ACLs, reviewing who can modify the attribute, and correlating changes with service deployment and admin activity.
Monitoring should focus on unexpected directory writes, suspicious service-account behavior, and post-change access that reflects delegated impersonation rather than direct authentication. If abuse is suspected, the investigation should extend to the resource account, the delegated principal, and any user or service sessions created through the delegation path.
Risk and Threat Considerations
This attribute is a privileged choke point because a single unauthorized write can create a persistent impersonation path. Attackers value it because delegation abuse can blend into normal service behavior while still delivering durable access and lateral movement.
Failure mechanism: An attacker or insider gains write access to the attribute, adds a principal they control, and uses delegated Kerberos flows to impersonate higher-value users to the target resource.
Impact: The environment can shift from constrained access to persistent privilege escalation, stealthy access continuation, and downstream compromise of adjacent systems that trust the same resource.
Standards & Framework Alignment
This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.
MITRE ATT&CK addresses the attack and risk surface, while NIST SP 800-53 Rev 5, NIST Zero Trust (SP 800-207) and CIS Controls v8 set the governance and control requirements practitioners need to meet.
| Framework | Control / Reference | Relevance |
|---|---|---|
| NIST SP 800-53 Rev 5 | AC-6 — Least Privilege | Covers restricting who can grant or use delegated access on a sensitive resource. |
| AU-2 — Event Logging | Supports auditing changes to delegation settings that materially alter access authority. | |
| Recommendation — Limit write access to delegation attributes to the smallest trusted admin set. Log directory writes to delegation attributes and review them as security-relevant events. | ||
| MITRE ATT&CK | T1098 — Account Manipulation | Attribute changes can create or alter delegated access paths used for persistence and escalation. |
| Recommendation — Hunt for unauthorized delegation-attribute changes as potential persistence activity. | ||
| NIST Zero Trust (SP 800-207) | Zero Trust Architecture | Delegation settings define trust boundaries that should be explicitly verified and minimized. |
| Recommendation — Treat delegated impersonation as explicit, continuously verified trust rather than implied trust. | ||
| CIS Controls v8 | CIS-6 — Access Control Management | The attribute is an access-control mechanism whose misuse can expand unauthorized access. |
| Recommendation — Review and restrict who can modify delegation-related access paths. | ||
Practitioner Guidance
Governance implication: Treat ownership of this attribute as part of the resource’s security boundary, not as generic directory administration. Only tightly scoped administrators or automation should be able to change it, and changes should be reviewed as security-sensitive configuration events.
What to watch for: Unexpected delegation entries, changes on sensitive resources, or new impersonation paths on accounts that were never intended to delegate should trigger immediate review. The safest operating assumption is that any unexplained modification deserves the same scrutiny as a privilege assignment.
Related resources from NHI Mgmt Group
Deepen Your Knowledge
Free weekly newsletter
Subscribe to the NHI & AI Identity Journal
The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.
Bonus 33% off our NHI Course when you subscribe.
Reviewed and updated by the NHIMG editorial team on October 31, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org