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.
Expanded Definition
msDS-AllowedToActOnBehalfOfOtherIdentity is the Active Directory attribute that governs resource-based constrained delegation, or RBCD, by listing which security principals may act on behalf of users to a target resource. In practice, it is an authorization boundary rather than a simple configuration flag: whoever can write this attribute can materially change impersonation rights on the resource. That makes it especially sensitive in NHI environments where service accounts, computer accounts, and application identities interact across domains and tiers.
Definitions vary across vendors in how they describe RBCD, but the security meaning is consistent: this attribute controls delegated access at the resource side, not the caller side. NIST SP 800-53 Rev. 5 frames related access control expectations through account management, least privilege, and authorization enforcement, which helps explain why this attribute should be treated as privileged identity configuration, not routine directory metadata. NHIMG research on the Ultimate Guide to NHIs shows that 97% of NHIs carry excessive privileges, which is exactly the condition that makes delegated impersonation paths so dangerous when they are not tightly governed.
The most common misapplication is treating this attribute as a benign admin setting, which occurs when directory operators grant write access without recognising that it can create a durable impersonation path.
Examples and Use Cases
Implementing RBCD rigorously often introduces administrative friction, requiring organisations to weigh delegation flexibility against the cost of tighter change control and continuous review.
- A Windows application service account is allowed to impersonate users only to a specific backend resource, reducing the need to expose broader domain delegation rights.
- An enterprise migration team temporarily configures the attribute for a controlled interoperability scenario, then removes the entry after the cutover window closes.
- A blue team reviews changes to the attribute as part of privileged identity monitoring because a single unauthorized write can enable lateral movement without direct password theft.
- A detection engineering group correlates directory changes with suspicious ticket-granting activity to spot abuse of Top 10 NHI Issues patterns such as over-privileged service identities.
- An administrator documents every approved principal in the attribute and cross-checks it against the service owner’s intended trust relationship, using guidance consistent with NIST SP 800-53 Rev 5 Security and Privacy Controls.
NHIMG’s 52 NHI Breaches Analysis shows how often identity misuse becomes a breach amplifier once trusted relationships are abused rather than stolen outright.
Why It Matters in NHI Security
This attribute matters because it can turn a legitimate service identity into a reusable impersonation mechanism. If a principal can modify it, the attacker does not need to crack a password or steal a token; they can redefine who is trusted to act for users and then pivot through the target resource. That is why msDS-AllowedToActOnBehalfOfOtherIdentity is commonly treated as an identity control plane object, not just an AD field.
In NHI operations, this risk is amplified by weak visibility and excess privilege. NHIMG reports that only 5.7% of organisations have full visibility into their service accounts, and that lack of inventory makes it harder to tell whether an RBCD grant is intentional or malicious. The same gap appears in breach reporting such as the Cisco DevHub NHI breach, where identity trust and access pathways became critical once compromise had already occurred. Practitioners should pair change monitoring with least privilege, approved delegation reviews, and strict ownership for any object that can write the attribute.
Organisations typically encounter the full impact only after an unexpected lateral movement event, at which point msDS-AllowedToActOnBehalfOfOtherIdentity becomes operationally unavoidable to address.
Standards & Framework Alignment
This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.
OWASP Non-Human Identity Top 10 address the attack and risk surface, while NIST CSF 2.0, NIST SP 800-63, NIST Zero Trust (SP 800-207) and NIST AI RMF set the governance and control requirements practitioners need to meet.
| Framework | Control / Reference | Relevance |
|---|---|---|
| OWASP Non-Human Identity Top 10 | NHI-04 | Covers delegated access and privilege paths that can be abused by NHI objects. |
| NIST CSF 2.0 | PR.AC-4 | Addresses access permissions and least-privilege enforcement for identity-controlled resources. |
| NIST SP 800-63 | Identity assurance principles inform how privileged service identities are trusted and governed. | |
| NIST Zero Trust (SP 800-207) | Zero Trust requires explicit, continuously evaluated trust rather than implicit delegation. | |
| NIST AI RMF | AI risk controls apply when agentic systems are granted resource-side impersonation capabilities. |
Apply strong identity proofing and lifecycle controls to the principals that can receive or grant delegation.
Deepen Your Knowledge
Reviewed and updated by the NHIMG editorial team on August 27, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org