Join our Newsletter — 33% off our NHI Course
Home› FAQ› Authentication, Authorisation & Trust› How does a nested impersonation chain expand access?
Authentication, Authorisation & Trust

How does a nested impersonation chain expand access?

← Back to all FAQ
By NHI Mgmt Group Editorial Team Updated November 16, 2026 Domain: Authentication, Authorisation & Trust

A nested impersonation chain expands access when one identity can act as another, and that second identity can in turn impersonate more accounts or roles. Each hop inherits the declared permissions on the first identity plus any downstream rights, so a small initial trust relationship can expose broader systems, data, or administrative functions.

How nested impersonation chains turn a narrow trust decision into broad access

Nested impersonation is not just “one account acting as another.” The important security detail is that each hop can inherit the authority of the previous hop and then add its own downstream permissions. That makes the chain cumulative: a tightly scoped starting relationship can become a path into systems, roles, or data that were never intended to be reachable from the original actor.

Once a platform allows one identity to impersonate another, the effective question becomes whether the second identity can also impersonate, delegate, or exchange into something else. If so, access expansion is driven by trust propagation rather than by one broad permission grant. This is why the chain can look legitimate at every step while still producing a much wider effective blast radius than the first approval suggests.

Nested chains also matter because they can cross administrative, application, and service boundaries. A user, service, or automation that seems harmless in isolation may become a pivot point when it can mint or forward authority into a second context. The result is often an access path that is harder to reason about than a direct role assignment, because the final privileges depend on the full sequence of allowed impersonations rather than on any single account alone.

Where nested impersonation creates the most risk

The main risk is privilege amplification through trust chaining. If each hop is accepted as valid without checking whether the resulting authority is still appropriate, the chain can expose protected systems, allow administrative actions, or move laterally into environments that should have stayed isolated. Review the underlying delegation model carefully, because the exposure is often created by the combination of permissions rather than by one obvious overprivileged account. See also OAuth Token Exchange and Delegation Guide for the mechanics of token exchange and delegated authority.

Failure mechanism: The first identity is allowed to impersonate a second, and the second is allowed to impersonate further identities or roles without a hard boundary, audience check, or explicit stop condition. Each hop carries forward enough authority to make the next hop appear legitimate, so the final token or session inherits cumulative access that was never intended for the original actor.

Impact: Attackers or careless operators can traverse from a limited starting point to higher-privilege accounts, broader data sets, or sensitive administrative functions. In practice, that can turn one compromised or misused identity into multi-system exposure, especially when impersonation is accepted as a normal workflow rather than a tightly monitored exception.

How to evaluate and contain an impersonation chain

Start by mapping every place where an identity can act on behalf of another identity, then trace whether that delegated authority can itself be reused. The useful test is not “can account A impersonate B?” but “what additional authority becomes reachable after B is reached?” A chain should be treated as a single access pathway, not as separate harmless steps. The Pretexting Guide is useful here because many real-world impersonation paths begin with a trust decision that was never meant to be reusable.

When a chain exists, the practical control is to reduce where impersonation is permitted, restrict who can re-impersonate, and require explicit breakpoints for elevation. If a downstream hop can reach more sensitive roles than the upstream hop, that is a design signal to split the workflow, shorten token lifetimes, or separate administrative paths. Entra ID actor token flaw (CVE-2025-55241) is a strong example of how impersonation-related trust can become a tenant-wide privilege problem when validation is too permissive.

For organisations that use delegation and on-behalf-of patterns, compare the chain against the intended business function. A legitimate support or automation flow should have a clearly bounded target set, a narrow audience, and a way to prevent recursive reuse. Where the chain is difficult to explain in one sentence, it is usually too permissive or too opaque for production use.

Standards & Framework Alignment

This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.

MITRE ATT&CK and OWASP API Security Top 10 address the attack and risk surface, while NIST SP 800-53 Rev 5 sets the governance and control requirements practitioners need to meet.

FrameworkControl / ReferenceRelevance
NIST SP 800-53 Rev 5AC-3 — Access EnforcementNested impersonation expands access by extending allowed authority across hops.
IA-9 — Service Identification and AuthenticationImpersonation chains often depend on service-to-service identity assertion and token reuse.
AC-6 — Least PrivilegeThe chain becomes dangerous when each hop inherits more authority than needed.
Recommendation — Enforce explicit access decisions at each hop and block unauthorized downstream privilege expansion. Authenticate non-human actors distinctly and constrain token-based delegation paths. Limit each impersonation step to the minimum authority required for the task.
MITRE ATT&CKT1134 — Access Token and Application Token ManipulationNested impersonation is a token and authority manipulation pattern used to gain broader access.
Recommendation — Map impersonation hops to token-manipulation techniques and hunt for abnormal delegation chains.
OWASP API Security Top 10API5 — Broken Function Level AuthorizationDelegated calls can bypass intended role boundaries when impersonation is over-trusted.
Recommendation — Verify that each delegated function call is authorized for the effective identity.

Practitioner Guidance

What to verify: Trace the full hop-by-hop path, not just the first impersonation right. Confirm whether any downstream identity can mint, exchange, or forward authority into a broader role set than the upstream actor was meant to reach.

Common mistake: Treating each impersonation step as independently acceptable. A chain that looks safe at each hop can still be unsafe in aggregate if the resulting authority is cumulative.

Decision rule: If a downstream hop can reach privileged, cross-domain, or sensitive administrative functions, treat the chain as high risk until you can prove the sequence is bounded, logged, and non-recursive.

Practitioner takeaway: The security question is not whether impersonation is allowed, but whether the chain can be reused to compound authority beyond the original trust decision.

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.

NHIMG Editorial Note
Reviewed and updated by the NHIMG editorial team on November 16, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org